Agenda: 1) what is up 2) steering committee 3) 1.1.0 4) Eclipse 3.4 party
1) what is up
2) steering committee
4) Eclipse 3.4 party
jgarnettwell the chat started; you can do a formal meeting in a bit.
moovida:) just wanted be sure the time is right
jgarnettI am not sure when the right time is; Jesse_Eichar when?
Jesse_Eicharwell we're all here so we can start now
jgarnettoh - email says 10 mins.
moovidayes, but that was me
Jesse_Eicharsure what ever is best for you guys
Jesse_EicharI'm here now and ready to go whenever you are.
jgarnettsounds good; can you guys ping me hard if you need my vote; I am running around helping people
moovidaok for me
jgarnett(mostly with DnD introduced bugs; making walkthrough 2 hard)
Jesse_Eichar2) Steering committee
moovidashould be ok
Jesse_Eichar1) What's up.
Jesse_EicharRemaining priority issues with 1.1:
Jesse_Eichar- Fix for FF3 has broken drag and drop so drag and drop results in multiple resources being added to map
Jesse_Eichar- The OSX jai plugin is not working when deployed.
jgarnettjgarnett: teaching and improving training materials / wiki - improved PDFs will be uploaded later today
Jesse_Eicharjeichar: more demos and going to South Africa.
moovidamoovida: gt-grassbinary working
moovidabrought grass under imageio-ext
moovidaWill bring it to trunc at some point
moovidaand operations to all coverage
simbossgo moovida go!!!
moovidacurrently trying to import a sextante module in jGrass
moovidasimboss: thanks for the help in Bolsena
moovidamade update sites of JGrass plugins
moovidathey should now work
simbossnp, we'll send you an invoice :-)
moovidasimboss: I'll pay in bottles of wine ;)
moovidahe wanted to say something?
mauricioabout steering committee
mauricioi am new
moovidaok, then 2
mauricioi prefer follow your steps
mauricioin the first time
Jesse_EicharI'm not sure what exactly to say about steering committee. I guess I have 2 big things
Jesse_Eichar1. What do you expect from being on the steering committee?
Jesse_Eichar2. I don't want lots of beauracracy
Jesse_Eicharso 1. Start with Andrea
moovidaYeah, I thought about it pretty much in the last time
moovidain fact it is not so important to be on a PSC,
moovidabut more to understand were Udig is going and exactly which resources will work on it
moovidaa PSC gives me the feeling
moovidaof a mroe regular meeting
moovidaregular == a bit more forced
moovidain the last times things seem a bit more lost in space
moovidaseveral things happened and I feel the need to
moovidabetter define the situation
moovidaso PSC for me would mean just put up again
moovidaa more compact development core
moovidaalso because there is really a lot going on in udig
moovidaat the moment
moovidaThat is all from my side.
mauricioI think we can transmit that that our community expect about udig
mauriciolocal community (spain, italy etc)
mauricioso udig could do a better use of distributed resources
mauriciowe could collaborate more and better
mauricioI think all people are agree
moovidaagrees for sure
Jesse_EicharI thought was an easy sell :)
Jesse_EicharSo first and most important is to get better communication out there.
mauriciowell I think the geotools community have good communication tools
mauriciowiki to share ideas
moovidaThe problem perhaps is a bit the fact that in geotools different colors can coexist in the same environment and ml-lists
moovidainstead with udig it is more difficult
Jesse_EicharAlso we have the problem where we have a problem getting the steering committee together.
moovidaI would love to have the JGrass ml-list merged into udigs
moovidabut understand that it would not make much sense
Jesse_EicharThis is the first time and Jody is only partly here.
jgarnettwell I like the idea of the PSC being able to represent uDig in each timezone; and we can handle some topics/decisions on email.
Jesse_EicharThats a start.
Jesse_Eichar2 things that need to be discussed in broad terms:
Jesse_Eichar1. General what the heck is going on.
Jesse_Eichar2. Direction planning
Jesse_EicharI think 1 is the more important. Meetings are good but too hard to rely on.
moovidalikes the 2 points
Jesse_Eicharso I suggest for 1 we suppliment by 2 days a week each of us sends a "Scrum" style email.
Jesse_EicharTopic can be PSE update
Jesse_EicharAnd has 3 sections: What I've done in the last couple days. What I'm going to do in the next. And what is causing problems.
Jesse_Eichar(Just a suggestion)
Jesse_EicharBut it has been very effective in collaborating with my french counter parts here at work
Jesse_Eicharandrea jody? comments?
Jesse_EicharThe point of it is so you can get a very short shot of what is going on and if something is scary, wierd or something else you can start a longer discussion.
moovidaYes, that sounds good
Jesse_EicharI think people like Jody who has lots of people working with him will need to include some of what they are doing.
moovidathis will go to the devel list, right?
jgarnett(aside: your delete point animation is a hit jesse)
Jesse_Eicharyes just the dev list
jgarnettjody too busy for comments; but I can review after.
moovidawhat is PSE for, anyway?
jgarnettwell I asked about a PSC mostly because I need to program *now* and I always have to check with you guys.
jgarnettI wanted you to know you are the gate keeps; and see if we could trade some of your existing responsibility (which you have anyways)
moovidano, I mean the acronym that Jesse wrote
moovidaPSE instead of PSC
jgarnettwith visibility (ie formal acknowledge your role in the project)
Jesse_EicharProject Steering commitee
Jesse_Eicharoh that was a typo
jgarnett(okay I suck; returning to my course)
moovidaI am really glad you proposed it Jody (if you are answering me)
Jesse_EicharBut I like the question of what is PSC
Jesse_EicharWe should make sure we're all on the same page about it.
Jesse_Eichar1- We have the power to stop other from going crazy and trashing the project.
Jesse_EicharIE I get a big a project and instead of starting a branch I Damage uDig to get it to work for my project
Jesse_EicharYou guys shout at me and tell me to take it to a branch or approach the code base more carefully
Jesse_EicharA second possible responsibility is:
Jesse_EicharWe are all responsible for trying to help maintain and improve the quality of both the project and out private project
Jesse_EicharThat's more or less my view on it. What do you guys think?
moovidaYes, what makes me think is the fact that Jody says we share a certain responsability
moovidaabout udig, which sounds great and good
moovidabut in fact Jesse_Eichar and jgarnett work at a different level
moovidai feel myself like growing also into the core part slowly but constant
mauriciothe risk is very big for us
moovidabut at the time I am an analysis addition
mauriciothe jesse's IE is crystal clear
Jesse_EicharMauricio. is there anything else you'd like to add to my description?
moovidayes, that is the reason for which we need some more regular and fixed meetings or emails or reports or whatever. We have to know what is going on really,
moovidawhich is what we just descibed above, I know, just wanted to underline :)
Jesse_EicharI think the important thing for me is Structured communication. I don't have time to always read every long email. That's why I suggested the PSC Update email.
moovidaI completely agree Jesse, same for me here.
Jesse_EicharI think I'm tapped out.
moovidaso to summarize
moovida- there is no official PSC (or yes?)
jgarnettthere is; it consists of Jesse and myself
jgarnett(ie this page http://udig.refractions.net/developers/)
Jesse_EicharOk so Jody shall we vote for an addition to the PSC?
Jesse_Eichar+1 for me for Mauricio and Andrea
moovidajgarnett: http://udig.refractions.net/developers/ doesn't tell a thing about PSC
Jesse_Eicharkick kick to jody
Jesse_EicharIt does on the right hand side
Jesse_Eicharwelcome you days of cool beers and no stress is now over ;)
Jesse_Eicharunless there is anything else.
Jesse_Eicharas I said before there are 2 critical issue left for me to fix
Jesse_Eichar1. Drop and drop adding multiple layers on a drop.
Jesse_Eichar(update: I think its fixed on my laptop here)
Jesse_Eichardrag and drop that is :P
Jesse_Eichar2. OSX jai install plugin is not working when not in eclipse for some reason.
Jesse_EicharAndrea, Mauricio anything else you'd like to see ?
moovidadid you see that post I sent about layers not getting dirty?
moovidaelse I can summarize quickly
Jesse_EicharI can't remember if it was just creating new features or what.
moovidano, I tried it on modify
moovidajust moved a node and clicked on an empty point
moovidathe shape deselects as it should
Jesse_Eicharok I'll quickly look and see if the listener only is active on create and delete.
moovidabut it also seems to commit changes
moovidabut it really doesn't
moovidatried on polygon
Jesse_Eicharhmm works on points. but you're correct not polygons...
Jesse_Eicharcreate works though
Jesse_Eicharok not for this meeting
Jesse_EicharI will try on that as well but it is less critical as the bug has an obvious work around which is commit often :P
moovidanot for me, I'm glad about the prj stuff
moovida:) thanks for that efforth
Jesse_Eicharits still a little buggy for some Coverages but it is better.
Jesse_EicharEclipse 3.4 party.
moovidathat was jgarnett
Jesse_EicharWe can do for trunk.
Jesse_Eicharno way for 1.1
moovidawould there be real benefits?
Jesse_EicharThe update story is pretty awesome when they get it debugged.
moovidawhat was the aim of point 4?
moovidaask if anyone tried it?
Jesse_Eicharjody suggested it
Jesse_Eichar3.4 came out yesterday
Jesse_EicharWell we'll leave it. The switch when the .1 comes out has worked pretty good so far
jgarnetthi guys; two points; I have a team here that I want to get comfortable with trunk; and with committing etc... so Eclipse 3.4 is a good excuse.
jgarnettthat is it... if we want to wait for 3.4.1 we can do that; however I would like to try (maybe on a branch?) tomorrow.
Jesse_EicharI don't know if that is really the best argument for switching to 3.4... But for trunk I don't care so much as it won't be out til long after 3.4.1 is out
jgarnettyeah this is only for trunk
Jesse_EicharI'm pretty neutral about it
jgarnettand I agree
moovidaok, jgarnett, do you think we could organise that testing parallel to an IRC?
moovidaI would like to assist, so that I get also on trunc. That would give me a start with the new coverage environment
jgarnetthi guys; I need to get back to this ...
Jesse_EicharOk meeting is done.
jgarnettI will organize the time on email and we will be on IRC as a group when we do the work?
jgarnettie whoever is on IRC can help out.
moovida:) let's stop here
moovidayes, please write an email
moovidathanks for the chat
rwhittleseyknows that was a meeting, but that was *the* most activity he's seen in here
Jesse_Eicharhaha. We're spread thin and do most of the talking on email.
Jesse_Eicharby spread thin I mean different time zones.
rwhittleseyyea, I can imagine (no one in their right mind would have a meeting that started at 7 am local time)
Jesse_EicharI prefer meeting in my business day... As do most others
- ► 2011 (21)
- ► 2010 (11)
- ► 2009 (47)
- "code sprint" (8)
- 1.1.0 (1)
- Axios (21)
- beegis (1)
- code sprint (1)
- community (3)
- devel (4)
- development (1)
- documentation (1)
- georeferencing (1)
- geotiff (2)
- git (2)
- github (1)
- gridcoverage (2)
- gsoc (3)
- howto (1)
- irc (10)
- jgrass (5)
- license (1)
- lisasoft (5)
- LocationTech (6)
- MapInfo (1)
- meeting (2)
- neo4j (2)
- nosql (1)
- open source (2)
- openstreetmap (1)
- osgeo (3)
- OSM (1)
- pmc (1)
- projection (1)
- release (22)
- rfc (1)
- seamless (1)
- sprint (3)
- TAB (1)
- testing (1)
- tilesync (1)
- tip (4)
- tool (5)
- training (2)
- tutorial (1)
- udig (18)
- udig 1.2 (3)
- udig 1.2.1 (4)
- usability (2)
- web map tiles (1)
- week in udig (1)
- wms 1.3.0 (1)