...
- Andrea Aime
- Ben Caradoc-Davies
- Christian Mueller
- Ian Turton
- Justin Deoliveira +1
- Jody Garnett +1
- Simone Giannecchini
Tasks
This section is used to make sure your proposal is complete (did you remember documentation?) and has enough paid or volunteer time lined up to be a success
| no progress |
| done |
| impeded |
| lack mandate/funds/time |
| volunteer needed |
|---|
- JD: Update the documentation for checkout and build (can use the uDig docs as a good starting point for this)
- Try out the docs using the official github fork
- JD: Update the developers guide with a note about pull requests; and any other requirements:
- a quick primer for people with sample commands for common tasks
- a list of git does and donts, ie don't rebase on a public branch, etc...
- line endings figured out re Bens comment
- JD: Update the build procedure:
- Maven: a way to get git revision info from the build...
- Hudson: update the scripts to pull from git
- JD: Transition the repository
Contact - July 1st Weekend
Contact github about the size of the repository; uDig experience shows this will be fine - but it is good to ask.Can we can start - Set up a GeoTools organisation (PSC members as group owners), with a group for commiter
- Do westart from the official github fork? Or do YES (If we need to go back and pull more history?
- Turn off the old repository; create an Track issue for OSGeo SAC
- grab anything else we will do so on request)
Make the old repository read only http://trac.osgeo.org/osgeo/ticket/913- Turn on github
- JD: Transition comitters
- Grab the commuter comitter list from OSGeo servers; send out an email asking for github IDs
- Create GeoTools PSC and GeoTools Committers Groups (uDig organisation is an example here)
- Add github IDs as appropriate
- Transition the build machinery
- hudson configuration
- release scripts
- JG: Release 8.0-RC3 form the new repository to show we made it
- Update any of justin's automated scripts
- Update the how to cut a release page in the docs