> -----Original Message-----
> From: Ed [mailto:ed_at_kdtc.net]
> Sent: Friday, 4 December 2009 1:03 PM
> To: dev_at_subversion.apache.org
> Subject: Re: New website organization (html vs. wiki, and then some)
>
> PMJI,
>
> >
> > Wiki pages should be editable by those with :
> >
> > i. A cla on file.
> > ii. be a committer on the project that owns the wiki.
>
> Isn't this like saying someone can commit to the repository
> if he/she has a CLA on file AND owns the part of the code?
Not really, having a CLA on file means they are giving away all rights to
the code they commit, it becomes ASL v2 licensed and anyone can use it.
If wiki pages are to become part of your documentation then a CLA is
required. As stated in another mail, you can have public wiki areas if you
want for contributions, but that is unofficial stuff, the intent of the
original post I thought was to use the wiki to create your official
documentation.
> Or am I missing some vital information? It was my understanding
> that the Wiki page would be a 'group' effort and thusly
> those who are serious enough to apply for a Wiki-edit position
> would know what he/she is doing?
Those who are serious enough will sign a CLA and then there is no problem.
>
> >
> > In other words the wiki content should be treated like code,
> > wiki/documentation
> > contributions from anyone outside the project would have to be sent as a
> > patch
> > and applied by a committer.
>
> Wouldn't it put a heavier burden on the committer if he/she has to
> review both patches to the repository AND to the wiki page, assuming
> the final decision is to make a Wiki page? Or should there be a
> designated set of Wiki committers such that patches go to them?
>
> Again. As the saying goes, mistakes will be made. The issue is
> whether it will affect the actual Subversion code. I believe
> the answer is a resounding "no, it won't". It should then give
> a lot of people the ability to contribute to the project that
> won't break a Subversion build if he/she were to make a spelling,
> and/or grammatical error.
I think it's more of a legal thing than a code will break thing. People
break code too and someone jumps in and fixes or reverts it.
>
> Don't get me wrong, I don't mean to take a complete lackadaisical
> attitude towards wiki-edit applications; but I think a common-sense
> approach should do. In fact, this is the same issue as allowing people
> to become moderate the mailing lists. Prior to joining the ASF,
> those who are inclined in taking their time with moderating
> the mailing lists are welcomed. (Again, said with a bit of
> bias.) Right now, even though I've applied for a moderator
> as dev, I'm not sure if ASF mailing lists require moderators.
> (Of course, I could be very much wrong on this.)
Some lists require moderators, others don't. I don't think we have any
moderators for ASF mailing lists that are not ASF committers. But list
moderation is not tied to belonging to a project, I'm a moderator for a few
lists that I don't participate in.
>
> Just my humble $0.02.
2c welcome thanks! Seriously though, posts like yours of course are needed
if we are to clarify things and move forward.
Gav...(the other one)
>
> Edmund
>
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 9.0.708 / Virus Database: 270.14.87/2536 - Release Date: 11/30/09
> 17:31:00
Received on 2009-12-04 13:12:11 CET