[Phpwiki-talk] What should I do?

[Jeff D. <da...@da...>]

I'm in a quandry.

There are numerous features I'd like to implement for my Wiki.

I think most of us are in agreement about what features would be nice to add.
(Version history is at the top of my list.)

But nobody seems to like my coding style, so at this point I'm afraid (or too 
polite) to touch the code in the main branch of the CVS --- I particularly 
don't
want to make a large change (eg. new database API).

A few weeks ago, Steve posted a request for discussion of how to fit
(among other things) version history into the database API.  I posted
my idea (the jeffs_hacks API).   Other than complaints about my coding
style there has been frustrating little discussion on how to implement
version history.

I'd like version history soon.  I'm willing to do the work to get it. 
(I've already done it once in jeffs_hacks.)

So what to do?

1. Just hack away by myself.  This means basically fork my own private
   version (which will look a lot like the old jeffs_hacks-branch.)
   I'd be perfectly happy doing this, however it seems seems a shame,
   since the whole reason for my fork would be to implement features
   that it seems many people are interested in.
   (I think it is unlikely that much of this would make it back the
   main branch: witness jeffs_hacks-branch.)

2. Officially fork the code.   Maintain (a new) jeffs_hacks-branch,
   either as an official branch of PhpWiki, or as a separate project.

3. Screw-em-all (:->) and just hack away on the main branch.  No,
   I'm not that type of guy.

4. Wait for Arno (or whoever) to implement version history (on the assumption
   that this is going to happen reasonably soon.)

I don't mean to sound pissed off --- I'm not, I'm just a little frustrated.

Any above the above options would be fine with me.  Truly.

Option #1 is my choice at the moment (after all, that is what everyone else
does to get features they want into their own PhpWiki); however, I would be
interested in hearing your input on the matter before I commit to it.

Jeff