Children: |
Contact: | ||
|---|---|---|
Tracker: | GEOT-4156 Transition to GitHub | |
Tagline: |
|
|
As per our blog post on the topic:
Hi all,
the GeoTools developers have been working, so far, with Subversion as the main version control system. However various core developers have been using Git as a SVN client for quite some time so far, and an [official mirror|https://github.com/geotools/geotools] of Geotools, automatically kept in synch with Subversion, is already available on GitHub.We are now considering switching permantently from Subversion to Git, meaning the Subversion repository will eventually be abandoned and only the Git official central repo will be kept up to date.
Before making such move we'd like to hear from the users community, please take one minute to share your opinion about the switch to Git:
The results of this poll were:
|
The poll generated 212 votes (this is greater than our number of comitters!)
This is not a suggestion to move to git - it is a proposal to move to github:
* uDig found that using http://gitorious.org/ worked out well - but still failed due to lack of documentation. Indeed most advice on using git comes from the github docs; stack exchange where github is always used as an example.
* The ease of use of the "fork me" / "pull request" workflow provides the critical glue to allow an open source project to work; as distributed version control no longer provides the motivation for contributors to obtain direct commit access.
* github is simply fashionable. Anecdotal evidence of this is an "if it is not on github must be dead" attitude encountered on IRC
There are three more hesitations which have now been resolved:
1) The active developers needed to be comfortable with the use of git. This has now taken place.
2) We needed a good story to tell for windows developers. With the release of the http://windows.github.com/ we now have a sensible suggestion.
3) GeoTools 8
Additional discussion and support on the email list:
Checklist form justin:
This proposal is under construction; and won't be submitted until the tasks are sorted out and GeoTools 8 is released.
Voting has not started yet:
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 |
|---|
Source Code Try out the docs using the official github fork Using Git Do we need the Fork me instructions here? With a link to developers guide? Update the developers guide with a note about pull requests; and any other requirements: a quick Working with Git primer for people with sample commands for common tasks Working on a stable branch a list of git does and donts, ie don't rebase on a public branch, etc... 
Comitters - update with instructions for commit access Creating your own Module Hacking (change to How to take part) Update the build procedure: Contact github about the size of the repository; uDig experience shows this will be fine - but it is good to ask. Do westart from the official github fork? YES (If we need to grab anything else we will do so on request)
Make the old repository read only http://trac.osgeo.org/osgeo/ticket/913 Transition comitters Transition the build machinery
