[cowiki-dev] Redefining my role

Sy <[email protected]>
Newsgroups gmane.comp.php.cowiki.devel
Message-ID <[email protected]>
Ok, I've come to the conclusion that I'm not nearly as active with
coWiki as I ought to be.  Part of this is because I'm overwhelmed at
the amount of stuff that I'm interested in doing.

So in order to help streamline "me", and let me understand what I
should do, I will be redefining my role thusly:

* Maintain www.cowiki.org, beginning with a refactor of the site for
organization.
* Read all the mailing lists, Help answer newbie questions and update
the site appropriately.
* Argue for/against features and usability / user interface from the
perspective of someone who has heavily used coWiki.
* Work with developing a roadmap and arguing priorities of features.
* Test a dev version of coWiki only via dev.cowiki.org, when it exists.

I will not:

* Install a development version of coWiki on my own machine.
* Work with cvs or snapshots or patches at all.
* Care about technical discussion (such as the merits of databases)
which is abstract and does not present features to a user.

---

Just so everyone knows, I haven't been active with my own coWiki
installation in a very long time.  There are features and ease of use
issues with MediaWiki which make it 90% what I need.  Also, when it
came to implementing an internal wiki for two local usergroups and my
work, I chose MediaWiki.  Aside from some documentation-related
quirkiness, it has been a joy to work with.

Furthermore, the upcoming featureset of MediaWiki completely
eliminates any gap in featureset between coWiki and MediaWiki -- for
my use.


So why am I here?

Well, I still believe that coWiki has great potential, and I'm seeing
that more and more every time another interested developer appears.  I
still want to "put to rest" my features lists and ideas because I
still think that they could be implemented one day.  I still like you
guys and want to help out.

I have no time, and aside from learning Ruby, I no longer want to
develop new skillsets.  I think I'll be more valuable by restricting
how I think and what I do.


coWiki has a spirit that is far stronger than other projects I've
looked into.  It's still making fairly sane decisions for features and
priorities, so I think it has a good future.. one that I'd like to be
a part of.


I guess it comes down to:  I don't really use coWiki, but I want to
help so that one day I can.  The 90% satisfaction I get from my other
tools could, in time, be 100% with coWiki.. I think that's worth
working for.


Thanks for your time, and sorry if this is a wierd post.  =)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.