So, before we start testing out and customizing Wiki packages, I ask
this: what kind of information are we trying to capture with a Wiki,
and can it be better served by a more structured model, like what we
attempted to do with the "herder"?
I'm thinking more along the lines of persistent group communication. Case in point: with the new book review program, I've been trying to figure out a good place to put the various guidelines for the reviews. Also, it would be nice to have a place to put the various suggestions for how we want to handle the reviews. These sorts of things don't lend themselves well to something that could fit within the catherder.
For that matter, a lot of the ideas related to the foscon/oscamp discussions might also be handy to have in a central place since people tend to ask questions about it on and off over time.
I think there is a lot more going on in the group than there was maybe a year ago (I was only watching the mailing list and wasn't even in Portland at the time, so I can't speak authoritatively). It would be nice to have someplace to post random items of interest for the group as a whole.
I think one of the keys to maintaining a group wiki is for there to be at least one person (preferrably more) who "sheppards" the wiki. Granted, in our rather loose organization it might be hard to get this going, but I think we're reaching the stage where it is a possibility at least.
_______________________________________________ PDXRuby mailing list [email protected] IRC: #pdx.rb on irc.freenode.net http://lists.pdxruby.org/mailman/listinfo/pdxruby
