Re: [Proxool-developer] Staring with the doc pages

[Bill H. <bi...@lo...>]

Hei Christian!

Good to hear from you :)

Actually, as soon as I sent that last message I realised that I should have
been clearer and not confused a Wiki with forking. Let me deal with each of
those in turn:

GitHub is an obvious place to host a Git repository. It gives you a Wiki
that makes it much easier to maintain the documentation. The Wiki is only
editable by designated collaborators (equivalent to the small group of
committers we have at SourceForge). It's not the only solution by far but
it's much easier to change than the present documentation which is just
static HTML. I'm approaching this from the aspect of that there needs to be
almost zero developer effort since I'm not aware of anyone having time to
work on this. Copy and pasting from the current website into GitHub Wiki
would be relatively easy.

If anyone is prepared to put the effort in, getting the documentation under
source control would be wonderful. It isn't at the moment. I'm open to any
suggestions.

As to "collaboration through forking", Git makes it simple (even desirable)
for external collaborators (ones that we haven't chosen or selected in any
way) to fork the project and make their own changes as they see fit. Git
also makes it simple to pull those changes back into the master repository
(in a controlled way). The whole thing is much more democratic with each
commit making it back into the project on its own merits.

-
Bill