Re: [Phpwiki-talk] Wiki spam and the future of phpwiki

[Reini U. <ru...@x-...>]

> | Releasing more often is probably also important.
>
> "Release early, release often" .. That's one of the main bazaar rules.
> It's really important for the developpement to go nicely.

I don't feel comfortable with releasing bad stuff.
And I empathize with the administrators who have to update their wikis.

> | Finally, I believe this goal would be aided if there were much less
> code | to maintain. For example, support only one backend. I see so much
> work | going into different database ports, needlessly. I vote for
> MySQL, since | that is what I am using. However, I might even go with a
> CVS backend | (*shudder*) if that were the community's will, as long as
> it supported | query-able relationships between 2 things (exactly like
> backlinks, or | we've expanded also to ratings, categories, and in the
> future perhaps | list items), and multiple instances from the same code
> base (currently | with multiple MySQL DBs).
>
> About backend, I really like the "large" choice of backends. But maybe
> the persistence abstraction layer is not that good ... that means too
> much work in the backend layer ...
> Maybe we should keep only one SQL library (ADODB ? PEAR ?) ... but we
> shouldn't drop flatfile, cvs, dba, etc ... they are very important, make
> the install process very simple in most cases ...

IMHO that's not the problem.

> I think we must find a different dev/commit model to attract more
> developpers and ... keep us working on phpwiki ... Should we have
> several cvs/svn trees and decide on a process to merge them every ...
> week ? Or have several cvs branches ? Should Reini or Steve give write
> access to any/more contributors ?

We have 4 admins!
A lot of people have write access!
But almost nobody helps out.

-- 
Reini Urban
http://phpwiki.org/   http://xarch.tu-graz.ac.at/home/rurban/