Takuya Murata wrote:
I don't aim to discuss which one is better CVS or
wiki.
First of all, again I am not so sure developing in wiki
works. Some think it won't work and some (including me, only
me?) think it might.
But think of the reality. Don't we need better mechanism for
development? Wiki might not work I know that. But I am not
sure yet.
Why don't we try? Is there any technical trouble to publish
wikipedia software sourcecode? It seems to me that it is
possible to publish sourcecode and some sysops apply them
regularly. If it didn't yield good result, it doesn't hurt
anything anyway.
Oh, maybe am I only one who believes development in wiki
might work? If so, I should do that in my own.
There is no benifit from using a wiki to develop software. There are
only cons:
1) There is no "barrier" so everybody who has read a 2 hour tutorial on
PHP can just start editing,
which will help nobody.
2) Versions of articles (or source code files) are only linear, and
there is no connection between distinct files (their versions).
3) It encourages small edits which lead to choas.
4) Think about an edit war on source files. That´s rediculous.
5) You can´t run/compile etc. it. You can´t edit it offline or with an
appropriate editor. You can´t use
any tools.
6) all the things I forgot
To sum it up: There will be a chaos in versions, small changes which
don´t fit together and lose the view for the large picture, you can´t
use editors, run it, use tools ... at best the software will be hacked
(in the worst sense) together trash which somehow manages to run.
A wiki might be the right thing for geniouses: Ah, he did that change,
that was because of this and that, it leads to that and this, now put it
toghether with my ideas, ...
If anybody who could handle that exists, he would do just fine with
CVS/sourceforge.
Hope this is not to harsh :)
Flo