Have you considered using a distributed version control system, for example Git instead of Subversion ? It makes the developers life much easier, as it is possible to create local branches, to test patches, or some random ideas, and publish the work in progress branch so other can look into, and judged what should go into the mainline, and what should stay out of. And helps the fork makers life easier. As I know, google code already support mercurial and git too, so probably worth thinking about it?

Yes, I've already use git-svn to follow the development, but I don't know that there is a git repo, so I will follow that too But anyway it's a little bit simpler if the upstream is a git repo too.Anyway, thanks !

I see, I guess you don't want to store a lot's of precompiled binaries in the repository, that's why you removed all the previous history (currently my git repo with the full svn history is more than 500MB ... )

It's just for building pms.jar. The binaries would take the repo size over the free GitHub limit. That wouldn't be an issue (and the history would be preserved) if we moved to git or GitHub permanently, but at the moment it's just a convenience/experiment.

It's just for building pms.jar. The binaries would take the repo size over the free GitHub limit. That wouldn't be an issue (and the history would be preserved) if we moved to git or GitHub permanently, but at the moment it's just a convenience/experiment.

I see. Fortunately googlecode supports git, and the repo can be 2GB, so it would enough Until I think I will use git-svn locally, and not the github repo.