From my POV grep we get lots of requests to move to SVN or git (or just to update CVS more often), and that if only we did we would have a thriving community of developers
In my experience however going to source control as a first step has never done anything; the committed devs go out, implement the stuff they want implemented, write the code they want to write, build the website they want to own, and *then* worry about how to reconcile with the official code when it becomes inconvenient to do it manually.
The thing about hosting a website is that it just doesn't lend itself to source control like an application does; the assumptions about release cycles, beta versions, commit freezes, installations, etc, just don't apply when there are customized websites that serve many people.
The way webDip development works can go in a couple of different ways:
- Take webDip, make your own site with your own twist on the whole concept, with its own niche. Some stuff you do may get shared back in, it may inform future development, it may remain a unique specialty feature.
- Come up with some compelling feature you think official webDip should have, and you want to see on webdiplomacy.net. Post it on the dev forum and see if it is realistic, get advice on how best to do it, then grab the code and take a crack at it. If you do a good job of it it will likely make it in (if not, and you still think it's a good idea, try the former approach)
Also although I realize forking is a sort of taboo in application based FOSS development I think that for web dev it's totally necessary. Can you imagine phpBB getting to where it is now if the only developers were working on phpbb.com/community ? The only reason FOSS websites thrive is that there are many people each with their own websites, making and sharing improvements; so fork away
)
LETS LETS GET A QUICK GAME GOING !
)
)
)
)