logo       
Google Custom Search
    AddThis Social Bookmark Button

Development strategy?: msg#00028

Subject: Development strategy?
Hi there,

I just wonder how the development of coWiki would proceed after 
PHP5 going official.

I'm just giving a try to TikiWiki, and I realize it has a whole lot of pretty 
advanced and very useful features coWiki does not. However, it seems
not as clean an implementation as coWiki, as I can feel from the user's 
side (haven't started to browse the huge masses of its code yet).

I just want to decide whether it is worthwhile to stay with coWiki (the 
development of which has been "demonstratively" ;) stalled due to  
relatively minor, but admittedly annoying and repeated PHP5 beta 
problems), or would it pay of better for a hacker like me to go with the 
masses and help out e.g. TikiWiki.

What would you guys think of this aspect?

I must say I like coWiki much better, regarding quality, but strategically 
I'm just not sure it can ever get enough momentum, seeing how monsters
like TikiWiki suck all the available manpower from the finite "wiki 
hacker pool".

(I cannot right now see how preserving the high standards of coWiki 
and also lowering the threshold for massive incoming development workforce 
can be achieved at the same time. And coWiki needs both to keep pace 
with other serious wiki-like products, I think.)

Thanks,
Sz.


-- 
This is the coWiki developer mailing list (http://develnet.org)

Unsubscribe: send an empty email to <cowiki-dev-unsubscribe@xxxxxxxxxxxx>
ML commands: send an empty email to <cowiki-dev-help@xxxxxxxxxxxx>







Try Searching:
servers, voip, java, networking, microsoft ...
<Prev in Thread] Current Thread [Next in Thread>