[wicked] What should be in wicked 1.0?

[Jason M. Felice]

I've decided that I'd like to make a real release of wicked, but I think
there's more to do before we get there--both features and cleanup and
bugfixes.  So I'd like to solicit use case studies and feature requests.
Nothing formal, but I'd like to know:

  1) How much you use wicked, how much you depend on it.

  2) *How* you use wicked.  What do you store in it.  Do you use it for
     discussion or fact-keeping or tech support, etc.

  3) What changes or features would be useful to _you_ in wicked.  If
     you have a technical, how-to in your head about how to accomplish
     something, that's useful info, but I'm really looking for what the
     needs are.  For example, I would much rather see, "We need ability to
     give clients access to a part of the wiki--but only a part," than
     "Nested pages (e.g. Foo/Bar) with inherited permissions."

I want to build and document a profile of what wicked's requirements (in
the form of needs) are in addition to how we get there technically for
1.0, then I hope to get a day every week or so to work on stuff.

To start, we use it all the time for documentation of our systems,
company policies, and project information.

We don't use it for discussion, since it doesn't facilitate discussion
well.  We want it to, and that's our first need.  To accomplish this, we
need to get users notified when discussion pages change.  We are
thinking of a subscription model and e-mail notification to do this.
Also the ability to subscribe to the entire wiki would help.

We would like to give customers access to pages on their own projects in
our wiki.  Currently we make a new wiki for that customer and export the
pages, but then we have to keep the pages in sync, and that is hairy.
(We forget, edit the wrong page.)  We are thinking of the nested pages
like UseMod mentioned above.

We have a need to store different kinds of content in the wiki, for
example network diagrams, UML diagrams, spreadsheet-like data, and
typesettable documents (all to be edited collaboratively).  I'm thinking of
serving this need by implementing a page content-type feature, and having
display/editing plugins.

I'm really excited to hear other people's ideas, too, so post lots :)

-- 
 Jason M. Felice
 Cronosys, LLC <http://www.cronosys.com/>
 216.221.4600 x302