Jody Garnett wrote:
> Hi Everyone,
>
> Looks like most people are going to be around for the IRC meeting today,
> this is a reminder - and the start of an agenda.
>
simboss> but right now
<simboss> people are doing it on trunk
<simboss> with the feature part of the world
<simboss> and I cannot afford
<simboss> having half of geoserver
<simboss> the part of it that relies on the feature world
<simboss> at least
<simboss> that is unstable
<simboss> so
-->| AlFa
([EMAIL PROTECTED]) has joined
#geotools
-->| iant__ ([EMAIL PROTECTED]) has joined #geotools
<simboss> I had to step back to 2.3.x
-->| jdeolive ([EMAIL PROTECTED]) has
joined #geotools
<desruisseaux> All right.
<simboss> soon
<simboss> both udig and geoserver
<simboss> trunk
-->| Administrator__
([EMAIL PROTECTED]) has
joined #geotools
<simboss> will be based on 2.3.x
<simboss> besides
<simboss> I think sometimes geotools
=-= Administrator__ is now known as aaime
<simboss> is running too much
<simboss> in comparison to
<simboss> its best users
<simboss> udig and geoserver
<simboss> geoserver is still based on 2.2.1
<simboss> as wellas udig is
<simboss> in myopinion his is quite bad
<simboss> IMHO :-)
-->| brent ([EMAIL PROTECTED]) has
joined #geotools
<aaime> Well, you can't ask uDig and Geoserver to work against
unstable branches
<aaime> they have users
<aaime> issuing an unstable release would be quite bad to their
reputation
<aaime> plus working on unstable makes it more difficult to develop
<aaime> you have to develop your own and fix the library at the
same time
<aaime> (well, fix it more than on a stable branch anyways)
<simboss> I agree
<simboss> but sometimes
<simboss> In my opnion
<simboss> geotools
<simboss> kid of run too much
<simboss> compared to the other projects
<simboss> many people like martin work on trunk
<chorner> run?
<aaime> You are right, yet I've encountered in practice gt2
limitations that are still unresolved, and that require quite a bit some
changes
<simboss> nad it soon becomes difficult to backport fixes
<desruisseaux> My point is that coverage plugins development
seems to happen on the 2.3 branch right now, so 2.3 sound like a
development branch, not a stable one right now, no?
<desruisseaux> As said previously, it is not a big deal for me
since I do not rely on 2.3 at all.
<aaime> that's the whole point of "stable development" Simone
spoke about on the ml and various meetings
<aaime> it's always the same tension
<jdeolive> last meeting we said that developing of plugins
withotu api change can be considered stable
<aaime> between people wanting to add things that do not break
the system
<desruisseaux> Ok.
<aaime> and people needed a little revolution
<jdeolive> not last meeting, sorry, a couple of weeks ago i guess
<jdeolive> but that is still open to debate of course
<jgarnett> hi everyone.
<jgarnett> I sent out a meeting reminder, with a couple of topics.
<aaime> I say stable development is ok as long as people remember
to forward port changes
<Jesse_Eichar77> porting forward changes being the key ;)
<aaime> Besides that, I'd say it would be important not to
accumulate too many changes in the trunk, and release more often
<jgarnett> gtbot add 2.2.1
<gtbot> Added agenda item '1: 2.2.1' to the list.
<aaime> (well, ok, I'm stating the obvious)
<jgarnett> gtbot add 2.3.x
<gtbot> Added agenda item '2: 2.3.x' to the list.
<jgarnett> gtbod add GTSteering
<jgarnett> gtbot add GTSteering
<gtbot> Added agenda item '3: GTSteering' to the list.
-->| thx ([EMAIL PROTECTED]) has joined #geotools
<jgarnett> gtbot add unsupported modules
<gtbot> Added agenda item '4: unsupported modules' to the list.
<jgarnett> gtbot add 2.4.x POJO work
<gtbot> Added agenda item '5: 2.4.x POJO work' to the list.
<desruisseaux> gtbot add Directory structure reorganisation along
Maven standards
<gtbot> Added agenda item '6: Directory structure reorganisation
along Maven standards' to the list.
<desruisseaux> gtbot add Constructor injections
<gtbot> Added agenda item '7: Constructor injections' to the list.
<desruisseaux> gtbot add Version numbering
<gtbot> Added agenda item '8: Version numbering' to the list.
<desruisseaux> (I'm done)
<jgarnett> and apparently agenenda topic one was stable vs
unstable :-) looks like we are still agreed - does someone want to prep
a page for the developers guide?
<jgarnett> (or do we need to make a motion for the PMC)
<desruisseaux> gtbot add Line length in jaloppy configuration
<gtbot> Added agenda item '9: Line length in jaloppy
configuration' to the list.
<desruisseaux> (forgot that one)
<aaime> Too many things for today meeting I guess... let's try to
be quick...
<jgarnett> I am going to update this page
(http://docs.codehaus.org/display/GEOT/Working+on+a+stable+branch) to
say new modules are cool, as long as no new API is added.
<iant__> sounds good to me
<aaime> Thanks Jody :-)
<rgould_> gtbot: start
<gtbot> Logging started.
<jdeolive> wow, busy meeting today :)
<desruisseaux> Some items will be quick.
<aaime> So, topic 1?
<rgould_> gtbot: list
<gtbot> Agenda Items:
<gtbot> 1: 2.2.1
<gtbot> 2: 2.3.x
<gtbot> 3: GTSteering
<gtbot> 4: unsupported modules
<gtbot> 5: 2.4.x POJO work
<gtbot> 6: Directory structure reorganisation along Maven standards
<gtbot> 7: Constructor injections
<gtbot> 8: Version numbering
<gtbot> 9: Line length in jaloppy configuration
<gtbot> End of agenda items.
<rgould_> 1) 2.2.1
<aaime> Ok, so for 2.2.1 we still do miss some announcements, right?
<chorner> sf.net, mailing lists, + world
<iant__> osgeo?
<chorner> any volunteers to take on portions?
<aaime> I can do those tomorrow morning I guess
<aaime> at least, I can try
<jgarnett> (page updated:
http://docs.codehaus.org/display/GEOT/Working+on+a+stable+branch)
<aaime> How does that sound?
<jgarnett> Cory updated the anouncement wiki page, so it should
be 30 mins up copy and paste
<aaime> cool
<jgarnett> sounds great, tag in help on IRC if needed (say
FreshMeat login help).
<aaime> I'll do that, tomorrow... I'm on a 14" screen, I either
participate at the meeting or do announcement now
<jgarnett> cool, next.
<jgarnett> 2.3.x
<jgarnett> simboss this is all about you :-)
<aaime> PMC should have a reserved way to access username/pw for
the various sites...
<aaime> can you send me all relevant username/password I do miss?
<aaime> (PMC -> PMC members)
<jgarnett> sure, thus far it has been up to PMC members to sign
up for all these silly websites.
<jgarnett> (or whoever is doing the anouncement)
<simboss> well, all I have to say for 2.3.x
<rgould_> me and jody have access to most of the sites I think
<aaime> I guess I can't just sign up as a random user and pretend
to do announcements for project X, right?
<aaime> (at least on freshmeat?)
<rgould_> jody might be able to grant you access once you have
signed up
<aaime> k, let's go on with the meeting, sorry for the interruptino
<jgarnett> andrea, lets try and see how far you get - send an
email to the list of any sites listed that you could not "anounce" on
and I will pick them up.
<jgarnett> simone?
<aaime> k
<simboss> is that I just released the new arcgrid plugin I asked
permission for a couple of weeks ago
<FrankW> BTW, it is [EMAIL PROTECTED] for OSGeo announcements.
-->| groldan ([EMAIL PROTECTED]) has joined #geotools
<simboss> I have a guy who is working on a plugin for pnm images
<simboss> and another one working on the jgdal thing (very slowly
though :-( )
<aaime> thanks Frank, I'm going to update the gt2 release page
with that mail address too
<simboss> all the work is happening
<jgarnett> thanks frank, updating the page now - looks to be a
cut and paste mistake on my part
<simboss> an svn dir un der ext of geotols 2.3.x
<simboss> outside the build process
<aaime> ok, so jgarnett does it
<aaime> What about ecw? I thought the plugin was ready?
<jgarnett> sorry andrea? what? I am hoping we are on the "2.3.x
release" agenda topic and simone is asking or scheduling help for this week.
<aaime> (just curious)
<simboss> the plugin itsel is more or less ready
<simboss> but I am not cnvinced yet
<simboss> if the quality of the gdalfraemwrok behind it
<simboss> the guy working on it
<simboss> is now busy w3ith its least exam of his master
<simboss> hence the plugin as well as the jpeg2k plugin is more
or less in standby
<simboss> beginning of nov
<aaime> Ok, let's allow time for it to develop and mature then
<FrankW> simboss: I'd be interested in hearing about jgdal
progress and problems.
<simboss> now?
<jgarnett> simone I hope to set up an "unsupported" directory
(and then download) that will allow for situtations like this...
<simboss> that would be cool jody
<FrankW> simboss: later
<FrankW> (ie. by email)
<simboss> frank: cool
<jgarnett> Simone let me ask - is there anything you need to make
the 2.3.x release this week?
<simboss> time ? :-)
<jgarnett> (or failing that Martin and Rgould do you think the
release will go smoothly for Simone?)
|<-- AlFa has left freenode ("What?! Open source isn't good
enough for you? Bersirc 2.2 [ http://www.bersirc.org/ - Open Source IRC ]")
<simboss> I got to know that next week I have to go to the US
<jgarnett> cool, anywhere close to us :)
<simboss> norfolk
<simboss> virginia (?)
<simboss> the arcgrid plugin
<jgarnett> okay, well if that is it for the agenda item - lets
move on. Simone please send *lots* of email as you go through with
questions etc... if you get stuck chances are someone can unstuck you.
<simboss> was one of the last thing
<simboss> playing with the release process
<simboss> yeah
<aaime> Cool. Next topic?
<aaime> 3) GTSteering?
<jgarnett> Right - everyone read it?
<jgarnett> or anyone read it :-)
<simboss> I did :-)
<desruisseaux> I did too
<iant__> I skimmed it
<aaime> Me too
<jgarnett> and importantly I collected feedback from many people
(thanks!)
<jgarnett> So here is the deal, can I "publish" it ...
<jgarnett> a) I am trying to make geotools visible
<jgarnett> b) I am trying to make geotools predictible :-)
<jgarnett> c) I am trying to address some specific concerns from
those that "invest" into geotools.
<aaime> Well, you should ask PMC members to sign it
<aaime> this is a good way to make people really read it :-p
<iant__> +1
<desruisseaux> What will be the process for updating it after
publishing?
<simboss> I have a couple of small things to clarify (very small)
<jgarnett> (so a lot of this is in response to acuster pointing
out we should ask Paul and Chris for maintence work, rather then hope
for OSGeo to facilitate funding)
<jgarnett> good question Martin, I can commit it into svn - it is
an open office document.
<jgarnett> Before publishing it I would like to find an OSGeo
template and font and logo (but beating that out of their website is my
own personal tragady)
<jgarnett> sure ...
<aaime> So?
<jgarnett> (aside: Martin for updating I would like to make one
of these every quarter, this document is for october)
<jgarnett> simboss, clarify away.
<desruisseaux> Thanks for the updating clarification :)
<simboss> for example
<simboss> on the project structure
<simboss> page
<simboss> 4
<simboss> I would remove gtopo30 and arcgrid from unsupported
<jgarnett> got it, for those following along at home it shows a
breakdown of (module, plugin, ext and ... "unsupported")
<jgarnett> okay cool, I was only speaking from personal (lack of
- experience)
<simboss> and put it under geotools plugins
<simboss> if you prefer I can send an email
<simboss> after the meeting
<simboss> so that everybody can grab its own copy
<jgarnett> moved them now.
<simboss> and double check
<jgarnett> okay, so here is the question - to the community
rather then the PMC
<jgarnett> can I publish this - I do not mind if it is offical,
only that it represents what we want to do right now.
<simboss> You can publish it
<simboss> and then
<simboss> we can update it
<simboss> as requested by the community
<simboss> along the w3ay
<simboss> (that's my 2 cents)
<aaime> +1 from me too
<iant__> +1
<jgarnett> Okay i will commit into SVN, and we can figure out if
we want the PMC to sign the next one.
<jgarnett> +1
<jgarnett> cool thanks dudes :-D
<jgarnett> next?
<jgarnett> 4: unsupported modules
<jgarnett> This is a change proposed for 2.4.x - and documented
in that GTSteering document.
<jgarnett> I would like to create an "unsupported" directory for
modules that
<jgarnett> a) represent research projects
<jgarnett> b) represent plug-ins that do not meet our "QA" standards.
<jgarnett> (exact discussion of QA standards left up to a cross
between Andrea and the Developers Guide)
<jgarnett> Does anyone have any comments? Feedback? Is this a
good idea, etc...
<groldan> I assume the imposibility of run unit tests means a
module does not passes the QA standards (aka, arcsde)
<jgarnett> good question gabriel
<iant__> it sounds like a good plan to me
<jgarnett> we probably need a good QA breakout IRC session to
figure this out ...
<aaime> well.... we could trust the developer stating that when
having the right backend the coverage is good enough
<aaime> (I mean, we're not children, are we?)
<jgarnett> I would assume that a CruiseControl bot testing
arcsde, db2, oracle would work enough for things to be supported.
<aaime> That would be the best solution of course
<jgarnett> andrea, trust developers yes (ie trust module maintainer)
<groldan> btw, I can ping Saul Farber again, he offered a sde
instance to run tests against (access would be restricted by IP)
<jgarnett> but also no, - to be useful to me the module(s) need
to be a lot more trustworthy.
<jgarnett> so a compromise is needed.
<groldan> (where IP means Internet Protocol, not Intellectual
Property) ;)
<aaime> It's not like compromise, it's that you need resources
and for certain things like ArcSDE the cost is... well... outrageous?
<jgarnett> Gabriel can we take on QA and how to improve things
for GeoTools 2.4 as a seperate topic :-)
<jgarnett> I would like to focus on opening up geotools with a
less restrictive process, so we can attrack new developers and research.
<aaime> Back on unsupported... unsupported seems to mean research
stuff from official developers in my mind... what about "community?"
<jgarnett> (this is on page 2 of the GTSteering document BTW, the
motivation that is)
<jgarnett> My first draft had "community" and I liked it ...
<aaime> ah right, Paul did not like it
<jgarnett> but the feedback I got from Paul was more in keeping
with the QA side of things.
<jgarnett> Unsupported is both a) true and b) negative
<jgarnett> so people would be prepaired when they tried out an
"unsupported" oracle plugin.
<jgarnett> so things like full table scans for bound information
would not come as such a surprise.
<aaime> oh well, it's ok, as long as we make clear to other
people that unsupported is a free area to play with new things, even
from outside the PMC and developers circles
<aaime> Heh...
<jgarnett> It may also motivate fixing of those blocking IRC
bugs, finally it allows a way for the code to get out and reviewed by
the public even before it is up to our usual geotools standards.
<jgarnett> Thanks for the comments ... andrea and gabriel. Vote?
or more discussion...
<aaime> It's perfectly ok to me
<jgarnett> (note: I do not "like" unsupported from a commuity
point of view, but I feel it may be a good idea and ... honest)
<jgarnett> +1
<desruisseaux> I'm fine with a "community" directory. It bring us
to the "directory structure reorganisation" agenda item, later...
<desruisseaux> (ou an "unsupported" directory)
<aaime> +1 for unsupported since it makes happy our svn provider :-p
<iant__> +1 (but we need to document how to become "supported")
<groldan> +1 on ian's comment
<chorner> +1
<jgarnett> iant__ ++ agreed, and that document needs to be called
the developers guide ;-)
<jgarnett> okay cool.
<rgould_> +1
<jgarnett> <gtbot> 5: 2.4.x POJO work
<groldan> aka. I want to know how to take arcsde to supported
land besides fixing the pending bugs
<jgarnett> A couple of introductions here ... refractions is
hosting a couple of fine young hackers
<aaime> brb
<jgarnett> that are looking into Pojo support, with spatial queries.
<jgarnett> So they would like to be our first test victims, of
the unsupported directory ;-)
<jgarnett> Over to them to describe their idea/tech:
<thx> hey guys...we're working on JPOX Spatial...
<thx> which is a plugin for JPOX (www.jpox.org) which is the
reference implementation for JDO (java data objects)
<thx> its basically an O/R mapper with a well defined API in
we're integrating support for spatial types in it...
<thx> Jody's idea was now to implement OGC Filter API as well and
integrate all that somehow into GeoTools
<CIA-10> magnasound * r22158
/udig/community/lavila/plugins/org.cgiar.cip.diva.data.importtogridfile/:
Initial import.
<jgarnett> at the end of the day I would like, as with hibernate
datastore, to make an Abstract DataStore by which people could
<jgarnett> drop their own objects into the library and watch them
sing and dance (well at least render)
<jgarnett> We have until December for this, and it is the second
"goal" of the GeoTools 2.4 release.
<jgarnett> Andrea is the hibernate datastore work available to
us, and do you have any plans for release?
<jgarnett> (this is a similar approach using a different Object
Relational mapping technology)
<jgarnett> oh - aamie --> brb != back so we should move on...
<jgarnett> So here is the request, and perhaps a policy change.
Can we get these guys svn access ... and what should the procedure be?
<jgarnett> 1. minimum: wiki page and email request? Approved by
any PMC?
<jgarnett> 2. medium: wiki page, jira, IRC meeting attendence and
PMC vote?
<jgarnett> what do you guys want to do?
<CIA-10> magnasound * r22159
/udig/community/lavila/plugins/org.cgiar.cip.diva.data.importtogridfile/
(22 files in 11 dirs):
<aaime> back
<aaime> Hem... at the moment I'm a little swamped, much work to do
<iant__> It would certainly be good to see progress reports at
IRC meetings (even if I can't always come)
<jgarnett> andrea, question was about hibernate datastore plans,
could you dump it in an unsupported directory?
<aaime> but I think I can take hibernate data store in the
current state and just drop it in the unsupported directory
<aaime> heh
<jgarnett> iant__ that may be a good idea, attend meeting or send
out email?
<iant__> either would work - I mostly manage to read the irc logs
<jgarnett> thx - how do you feel about that?
<aaime> Hmm... I'd prefer mails, but that's my personal preference
<aaime> (keeps things focused and makes only interested people
participate in the thread)
<jgarnett> email sounds good to me, would like to keep this "lite".
<jgarnett> alternative is to update the wiki page :-P
<iant__> ok email is fine
<thx> weekly status report by mail would be fine with us...
<aaime> Nah, who's going to notice wiki page updates?
<jgarnett> how about "creating" these things, ie getting svn
access for unsupported directory.
<iant__> now I have an rss feed off the wiki that would be fine too
<aaime> Wiki pages would be good for on the fly docs thought
<jgarnett> two options were listed above, it strikes me we should
also ask them to read the developers guide.
<aaime> He he he, it seems me and Ian have different approaches
to collaboration :-)
<iant__> try the rss feed its really good
<aaime> I'll do :-)
<jgarnett> okay let me try again, the result will be put into the
developers guide...
<jgarnett> 3. wiki page, email request, weekly status email,
approved by any PMC, read the developers guide
<iant__> +1
<CIA-10> magnasound * r22160
/udig/community/lavila/plugins/org.cgiar.cip.diva.data.importtogridfile/src/org/cgiar/cip/diva/data/importtogridfile/wizards/ChooseTypeOfImport.java:
<jgarnett> +1
<jgarnett> (gabriel: answered your arcsde to supported question
in email)
<jgarnett> okay anyone else with a vote? rgould? aaime? then we
can move on ...
<groldan> thanks
<jgarnett> okay if we do not get a vote I will take this to email
....
<jgarnett> 6: Directory structure reorganisation along Maven
standards
<jgarnett> desruisseaux - ping - your agenda item is up
<desruisseaux> Can I call for a "everybody out of the pool" this
Sunday?
<desruisseaux> (on trunk only)
<rgould_> which pool(s)?
<rgould_> ah
<desruisseaux> I means, commit every pending work on trunk before
Sunday.
<desruisseaux> If peoples agree, I could reorganize the directory
structure according Maven standard Sunday.
<aaime> np from where I stand
<jgarnett> emal sent abour the proposed "process" for the
unsupported directory.
<rgould_> ditto
<simboss> cool
<jgarnett> sounds nice martin, question.
<desruisseaux> ?
<jgarnett> - unsupported, data, jdbc, xml - all of these
directories have now been approved (some of them only appeared on the FM
branch)
<jgarnett> did we want to do that at the same time, or after...)
<jgarnett> jdeolive may also have feedback here.
<jgarnett> but yes +1 for out of the pool on sunday
<iant__> +1 too
-->| acuster ([EMAIL PROTECTED])
has joined #geotools
<simboss> +1
<desruisseaux> Better do create the new directory Sunday too, in
order to process with only one "out of the pool" call. Developers will
need to remount their IDE setting after the directory structure change.
<acuster> oh hey all, (me is a little late)
<desruisseaux> Hello Adrian
<desruisseaux> Are the new directories documented in the
GTStering document?
<desruisseaux> (I remember well about "unsuported", but I missed
xml and the other - maybe I read too fast)
<jgarnett> I will check, we asked back in Febuary and did the
change on the FM branch, was fairly smooth.
<jgarnett> yes they are there, and one more change - moving WMS
to module/wms
<jgarnett> (as it defines new API and is not actually a plugin)
<desruisseaux> Could you email a list of the new directory with
their content (which module/plugin) please?
<jgarnett> I can try and put it together with jdeolive, I recall
doing the work in a hour or so of svn mv statements...
<jgarnett> So martin I will see that you get an email ...
<jgarnett> next?
<desruisseaux> Lets just on the directory structure (just the
part below the 'src' directory level) by emal.
<jgarnett> BTW: that appeared to pass with +3
<desruisseaux> (typo: lets just agree...)
<desruisseaux> Next item: Constructor injection
<jgarnett> 7: Constructor injections
<jgarnett> once again the floor is yours martin ...
<desruisseaux> Finally (after long discussion) it appears that we
can see FactoryFinder as nothing else than a way to provides default
value to constructor injections.
<aaime> Yawnn...can we do 8 and 9 before? They do seem to be
faster and it's already pretty late...
<desruisseaux> So lets start with constructor injection: I'm just
calling for a volunter here.
<jgarnett> understood, I would like to volunteer and I am now
working on trunk. But it remains to be seen if I can set aside the time
for useful feedback (so I have not stepped forward)
<jgarnett> martin do you just want a code review?
<desruisseaux> Anyone up to add (FooFactory1, FooFactory2...)
arguments in the relevant constructors? I can pass after that and
complete (if pertinent) with factory finder for providing the default
values.
<desruisseaux> No, asking for a volunter for adding the
appropriate arguments in the appropriate constructors (nothing to do
with factory finder at this level).
<desruisseaux> and let me known which class have been modified
for constructor injection that way.
<jgarnett> Martin I expect this to take a good deal of time on
the 2.4.x development cycle - there are lots of cases of
FilterFactoryFinder used in the code ... I do not mind doing work in
this direction, but perhaps a bit of organization is needed.
<desruisseaux> Okay. Lets push that to a later discussion.
<jgarnett> we can send email out as the constructor injection
stuff is added ...
<jgarnett> 8: Version numbering
<jgarnett> rgould, you wanted to go with maven defaults here?
<rgould_> i am inclined to, yes
<jgarnett> (or was that someone on the geoserver list?)
<rgould_> because that is easier
<aaime> which are?
<jgarnett> I do not mind, just update the developer's guide.
<desruisseaux> I agree with Maven default, but the default was
2.3-RC1-SNAPSHOT?
<rgould_> i thought I had
<desruisseaux> (typo: I agree with using Maven default for making
life easier)
<rgould_> the default development version is the previous version
with the lowest number incremented (RC0 to RC1, etc.) and -SNAPSHOT suffixed
<desruisseaux> Okay
<desruisseaux> So we are done on the "version numbering" topic.
<chorner> where did we break from this practice?
<desruisseaux> In 2.2 branch.
<desruisseaux> It was 2.2-SNAPSHOT before 2.2.0.
<desruisseaux> (not 2.2.0-SNAPSHOT)
<chorner> ah
<jgarnett> <gtbot> 9: Line length in jaloppy configuration
<desruisseaux> Current setting is 80 characters.
<rgould_> hmm I think maven might have defaulted to 2.2-SNAPSHOT
<jgarnett> I thought we moved up to 100 - ie sun defaults w/ 100
character width
<jgarnett> I don't mind what it is as long as we have a tool and
not developers fussing over it :-(
<desruisseaux> In 2002, previous Geotools PMC agreeded on 100 too.
<aaime> But something happened in the middle
<desruisseaux> Personnaly, I would prefer 120.
<aaime> when I got back, people were using 80 in various packages
<CIA-10> magnasound * r22161
/udig/community/lavila/plugins/org.cgiar.cip.diva.utils/src/org/cgiar/cip/diva/utils/
(StolenColorEditor.java Utils.java):
<jgarnett>
http://docs.codehaus.org/display/GEOT/5.1+Coding+Conventions ---> does
not say anything about 100
<aaime> Having a long discussion won't help
<aaime> Let's vote for 100?
<jgarnett> indeed, but a proposal will ...
<aaime> (I mean, it's a matter of taste)
<jgarnett> martin do you actually like 120? It all tastes the
same to me.
<acuster> does code width == doc width?
<aaime> For example to me 120 is too long.... :-p
* acuster would like doc width at 80 chars
<aaime> see?
<desruisseaux> There is no distinct configuration for doc and
code in jalopy
<jgarnett> okay ... heh, fun.
<rgould_> i like 80 for doc, longer for code
<acuster> because we occaisionally want to annotate in the
margins/publish on web site ...
<aaime> well, what's wrong with reformatting on the fly to 80
when you need to publish?
<acuster> same for code but I'm willing to live with the
consequences of making Martin happy :-)
<desruisseaux> Is it for performing a copy-and-paste between
javadoc source and some HTML page?
<acuster> it also just for reading text
<desruisseaux> On printed copy?
<acuster> TeX by default has very few words in a line
<acuster> there's a reason for that
<acuster> humans read shorter lines better than longer lines
<aaime> yeah, speedier reading
<acuster> i.e. your newspaper is in columns for a reason
<jgarnett> sad part is code is usally only 60 character, just
indented as all heck.
<jgarnett> okay, so we have 100 characters proposed? Do we want
to vote on that....
<iant__> +1 (again)
<aaime> +1
<jgarnett> +1
<acuster> yes, and java, unlike C, has
reallyLongNamesForThingsWhichShouldJustBe a
<desruisseaux> +1
<jgarnett> Okay, so we got two actions here:
<aaime> (Adrian, I disagree on that, but let's go on :-p)
<jgarnett> 1. update that page (jgarnett)
<jgarnett> 2. update the jalopy settings? (if needed)
<simboss> +1
<aaime> k
<aaime> yes, it's needed
<jgarnett> andrea can you update jalopy settings, and then lets
call this meeting over
<jgarnett> (but surprisingly efficient)
<desruisseaux> I can update the jalopy, since I spotted the place.
<desruisseaux> Are we done?
<aaime> Yes
<rgould_> looks like it
<rgould_> gtbot: stop
<gtbot> Logging stopped.
<gtbot> Posting news to GeoTools confluence...
<gtbot> Unable to post news to Confluence. Saving logs to a local
location.
<gtbot> Logs saved in /home/rgould/IRC Meeting - 16 October 2006.log
<aaime> Martin, have you setup an IM? :-p (sorry for pestering)
<jgarnett> thanks, and sorry for letting this run over time.
<rgould_> :(( gtbot chokes on CIA's commit messages
<acuster> grep -v CIA
<aaime> Ah well, way too late for me... it's been a long day. See
ya tomorrow :-)
<aaime> Cheers
<desruisseaux> No, I completly forgot the IM side of thing.
<aaime> np Martin, I'm here to remember you :-)
<aaime> LOL!
<desruisseaux> :)
<desruisseaux> By all
<aaime> k, bedtime for me :-)
<iant__> bye
<rgould_> night
|<-- desruisseaux has left freenode ("Chatzilla 0.9.69.3 [Firefox
1.5.0.7/2006090918]")
|<-- iant__ has left freenode ()
|<-- aaime has left freenode ("Chatzilla 0.9.75 [Firefox
2.0/2006100319]")
<simboss> ciao ciao
<jgarnett> ciaox2
<groldan> bye all
|<-- groldan has left freenode ("Leaving")
<jgarnett> simone I have uploaded the revised GTSteering document
(and pdf)
<simboss> k
<simboss> I am going to read it again
<simboss> right now
<simboss> do you have a quick link :-)
<acuster> jgarnett, url?
<acuster>
http://docs.codehaus.org/download/attachments/16158/GTStee.pdf maybe?
<acuster> GTSteering
<acuster>
http://docs.codehaus.org/download/attachments/16158/GTSteering.pdf
<simboss> thx
<jgarnett> thanks!
<jgarnett> Sorry i was off in email land ...
<simboss> np
|<-- rgould_ has left freenode ("Chatzilla 0.9.75 [Firefox
1.5.0.7/2006090918]")
<acuster> woops just missed him
<acuster> anyone else have an irc log they can email acuster -at-
gmail.com ?
<jgarnett> this IRC chat?
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
