incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Leo Simons <>
Subject (in)appropriate wiki use (was:Re: Proposal for OFBiz to Join the ASF)
Date Wed, 18 Jan 2006 08:53:42 GMT
On Tue, Jan 17, 2006 at 06:16:09PM -0500, Geir Magnusson Jr wrote:
> Is this becoming the current de-facto process, posting to a wiki? 

Seems like it.

> (or "@)#!)#@ wiki", as I tend to think of them...)

(LSD *hugs* wikipedia...)

> Can we please have things go to the mail list, as that should be the 
> 'primary institutional memory' of the incubator community.  Feel free to 
> also have on a wiki for collaboration to get it done, but after that, 
> the final proposal should, IMO, go to the mail list.
> Does anyone else feel this way?  Mail archives will live for years in 
> distributed places.  Wiki's seem to be single-sourced and a lot more 
> ephemeral....

Feel? I'll word it more strongly :-)

>From an infra@ point of view and as one of the people supposedly
maintaining the wiki I can answer with authority that the wiki is not
to be expected to live for years in distributed places and should not
ever ever be used for things like "institutional memory". Backups, uptime,
etc, are not guaranteed (not that we've ever lost stuff since we first set
one up, but that's not the same thing). Infra@ ensures integrity for three 
things -- SVN, mailing lists, distributions. Everything else is

Any PMC that keeps "vital" stuff anywhere but in those locations is making
a mess of things. Of course, "vital" is ambiguous, but I'll argue that
anything that deals with a pmc [VOTE] should be about something "fully"
available within the combination of SVN/mailing list/distribution.

Now, the current wiki install does send out change notifications (for the
incubator they go to It could be reconfigured
to send those notifications to general@incubator. Just say the word.

>From an incubator point of view, one other alternative mechanism to "edit
on wiki, e-mail to list" would be "send to list, add to SVN, submit patches
to mailing list, commit patches to SVN, send to list". This is a bit more
of a learning curve for people not yet used to working so extensively with
centralized version control, but its not neccessarily bad -- we want people
to learn that anyway.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message