I have recently made the switch from subversion to mercurial (quite happily), and OpenNLP is still using ancient CVS.
Would there be support for moving to either git or mercurial? Details here:
In my opinion we should keep CVS in the short term, the 1.5 release could be a good point to move the code to a new repository.
We should also consider moving OpenNLP away from sourceforge, I am a little unhappy with it.
A few of the things I don't like right now could be fixed others maybe not:
- The forums are not indexed by google, yahoo, etc. using these to search for OpenNLP related issues
rarely results in a forum post hit. That could be fixed by using mailing lists instead, that also has the advantage that I can just reply to a mail instead of logging into sourceforge which often takes a while because the sf interface is kind of slow.
- Especially if multiple people start to work on OpenNLP we need an issue tracker, the one we have right now isn't really used and I somehow don't like it. Over at Apache many use jira, that could be something for OpenNLP too. Any other suggestions ?
- We should automate the build as much as possible, for that we need a build server, not sure if its possible to get one at sf.
Do you have experience with other hosting platforms than sf ?
We discussed moving over to Apache, but that requires lots of work just to get us in there.
Jörn
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've begun using Google Code for another project (http://code.google.com/p/textgrounder/) and so far am happy with it.
I like the simplicity of the project site, and it seems to have most of the stuff you'd want. So, I'd support a switch to Google
Code if others would. I'm not too aware of other options, though I've heard GitHub is good.
How far away is the 1.5 release?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am just an OpenNLP user and the fact the source code is hosted on CVS and the lack of mailing list is slowing my conversion into a patch contributor. CVS is such a pain to use compared to git and mercurial.
I really like the git + github.com combo. github is especially good for changeset oriented code reviews with inline comments in an ajax UI. The social features of github might also help the project get more visibility.
mercurial + google code is also a decent combo even if I prefer github.
Moving to the Apache Incubator would even be better in terms of visibility and community acceptance. IMHO Apache projects suffer from the centralized and slow svn repos, but at least there are automatically mirrored on both http://git.apache.org and http://github.com/apache which makes it easy for wanabe contributors to maintain there feature branches prior to acceptance in the trunk, without commit access.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Right now it looks like the preferred place to go is Apache Incubator.
We will soon start to write the proposal in our wiki here, contributors are welcome.
I have recently made the switch from subversion to mercurial (quite happily), and OpenNLP is still using ancient CVS.
Would there be support for moving to either git or mercurial? Details here:
http://sourceforge.net/apps/trac/sourceforge/wiki/Mercurial
https://sourceforge.net/apps/trac/sourceforge/wiki/Git
Jason
In my opinion we should keep CVS in the short term, the 1.5 release could be a good point to move the code to a new repository.
We should also consider moving OpenNLP away from sourceforge, I am a little unhappy with it.
A few of the things I don't like right now could be fixed others maybe not:
- The forums are not indexed by google, yahoo, etc. using these to search for OpenNLP related issues
rarely results in a forum post hit. That could be fixed by using mailing lists instead, that also has the advantage that I can just reply to a mail instead of logging into sourceforge which often takes a while because the sf interface is kind of slow.
- Especially if multiple people start to work on OpenNLP we need an issue tracker, the one we have right now isn't really used and I somehow don't like it. Over at Apache many use jira, that could be something for OpenNLP too. Any other suggestions ?
- We should automate the build as much as possible, for that we need a build server, not sure if its possible to get one at sf.
Do you have experience with other hosting platforms than sf ?
We discussed moving over to Apache, but that requires lots of work just to get us in there.
Jörn
I've begun using Google Code for another project (http://code.google.com/p/textgrounder/) and so far am happy with it.
I like the simplicity of the project site, and it seems to have most of the stuff you'd want. So, I'd support a switch to Google
Code if others would. I'm not too aware of other options, though I've heard GitHub is good.
How far away is the 1.5 release?
Mercurial is good for me; since it is supported by NetBeans also.
git would mean I'd have to find a plugin for NetBeans.
James
Hi all,
I am just an OpenNLP user and the fact the source code is hosted on CVS and the lack of mailing list is slowing my conversion into a patch contributor. CVS is such a pain to use compared to git and mercurial.
I really like the git + github.com combo. github is especially good for changeset oriented code reviews with inline comments in an ajax UI. The social features of github might also help the project get more visibility.
mercurial + google code is also a decent combo even if I prefer github.
Moving to the Apache Incubator would even be better in terms of visibility and community acceptance. IMHO Apache projects suffer from the centralized and slow svn repos, but at least there are automatically mirrored on both http://git.apache.org and http://github.com/apache which makes it easy for wanabe contributors to maintain there feature branches prior to acceptance in the trunk, without commit access.
Right now it looks like the preferred place to go is Apache Incubator.
We will soon start to write the proposal in our wiki here, contributors are welcome.
To get into Apache Incubator we have to follow the
incubation policy:
http://incubator.apache.org/incubation/Incubation_Policy.html
Its says that we have to write a proposal, here is
a link to a guide how to write it:
http://incubator.apache.org/guides/proposal.html
In the end a vote on the incubator mailing list decides if we are accepted
or not.
Jörn