[REBOL] Re: UHURU/RSL
From: joel:neely:fedex at: 26-May-2001 9:01
Thanks! I didn't want to say anything until hearing from you,
since it was your idea and your server.
I've built and used wiki-like tools at work and think it's a
great way to manage information in a distributed project and/or
discussion. I'm just wondering about how the transition from
mail list to wiki can be done most effectively.
I see three options, and I'd like your thoughts on the best
way to proceed:
1) Stay on rebol-list, and just log stuff to the wiki for now.
Pro: We may get input from people who haven't been saying
much up til now.
It will look more like an open, community-level
Con: The mailing list is a poor medium for a permanent
record, especially when bringing someone up to date.
It would take extra effort to duplicate material to
the wiki (although I'd be available to help).
2) Publicize the wiki to the entire list.
Pro: Nobody is excluded, keeping the "community spirit".
Nobody has to do any extra work to keep the list and
the wiki in synch.
Con: Too broad a group too early could lead to possible
loss of focus or difficulty in getting consensus.
Someone who gets really annoyed could mess things up
for everyone else. (I just witnessed an "incident"
on another list I monitor where two guys got into a
flame war that escalated out of control and sucked in
a bunch of other people as well. I think this group
is MUCH more mature, but given that a wiki is totally
open, there is the possibility...)
3) Make the wiki invitation-only. Post summaries to the
mailing list at appropriate points in the discussion.
Pro: More control.
Con: More control.
This could make the effort read much less like a
"community library" and foster more of a "them vs.
us" mentality. The number of possible contributors
is small enough that a split would add real risk.
Is one of these a winner? Are there any other alternatives?
John Schuhr wrote:
> Joel -- Feel free to distribute the username/password/url for
> the UHURU WikiWeb at your discretion. Maybe we can get this
> stuff consolidated, organization and stored for posterity.
Programming languages: compact, powerful, simple ...
Pick any two!