Hi All

 

I just read the IRC meeting on the 19 June 2006, and made a summary for all of those who missed it J

 

1)       Jalopy (before merge)

 

·                      Merging branches is a mess because of different formattings.
·                      Start using Jalopy as part of the build.
·                      Need to update Jalopy settings to the correct header.
·                      Possibly format all current branches with the main pom.xmls all having the same plug-in formatter and config.
·                      At least run Jalopy on coverage and rendering to help the GC branch merge in.
·                      Autoformat on commit is the ideal solution, but not right now.
 
2)           Doc Ownership
 
·                      2 issues:
                                                          i.                          Who has the copyright?
                                                      ii.                          What is the license?
 
·                      Easy strategy for copyright would be to have the authors jointly hold the copyright, making the license impossible to change later on.
·                      Consensus seems to be that OsGeo hold the copyright, thus authors need to explicitly assign copyright to OsGeo.
·                      The PMC requires an official request from OsGeo for:
                                                          i.                          their acceptance of the copyright, ideally with some commitment to keeping it 'free' and
                                                      ii.                          some mechanism for us to assign our rights to them.
 
·                      Timeframe required so that no more time is spent thinking about it.
 
·                      Q: how can the PMC officially ask OSGeo to receive copyright for our docs?
            A: write a letter indicating that the copyright is being assigned to OSGeo.
 
·                      Q: Who is Rich Steele?
            A: Rich Steele is the OSGeo lawyer ([EMAIL PROTECTED]).
 
·                      Acuster will write a letter to the lawyer asking how to proceed and hopefully get a letter of assignment. Once this is done, formal voting from the PMC to accept the process can take place on the mailing list.
 
3)           GC Rocks out!
 
·                      Q: what still needs to be done before starting the merge of gc onto trunk?
            A: there are basically NO new things to do, just some more testing and bug fixing as we are doing
 
·                      Coverage branch includes grib support.
·                      Grib support not ready to be released, not officially    .
·                      Plans to try out the branch in uDig.
·                      Having things on trunk will greatly speed up bug hunting
 
·                      Q: What happens if we just do two svn move to swap the branch and the trunk on the server?
            A: 
·                             [simboss] we could do this
·                             [simboss] we first synch the branch
·                             [simboss] we send out some emails to warn committers
·                             [simboss] we swap
·                             [simboss] and we test things for a couple of days
·                             [jgarnett] horrible
·                             [jgarnett] What you are replacing is *very* broken...
·                             [jgarnett] Either way GC is merging to trunk
 
Thanks
Oliver
 
 

 

_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to