Sorry for the delay in responding.
Projects have run wikis with different policies. The podling's
governing group (PPMC) needs to decide on the policy and implement it.
All I'm offering is different policies that you can consider.
Craig
On Aug 18, 2010, at 2:42 AM, Christian Grobmeier wrote:
thanks for your input. I think this is quite valuable. To which
degree
do we need to care about taking over stuff from the wiki into our
real
docs, if a user without iCLA contributed it?
Let me give an example: If a user writes a short example code
snippet
(whatever 3-5 lines) which we would consider valuable to have in
the
real docs, would he need to sign an iCLA?
I wouldn't worry too much about 3-5 LOC. But it might be easier on
all
concerned to err on the side of caution.
thats surely the easier and more secure way. However, I doubt that
many
of our users will have signed an iCLA, so our purpose for the wiki
might
be lead ad absurdum somehow.
Are you all speaking about signing a CLA before contributing to a
wiki? I am not sure about all the legal stuff, but is it really
necessary to restrict a wiki so much?
For example at commons.apache.org everybody can write to a wiki.
Changes are mailed to the dev list. If there is something weird devs
could interact.
For my taste I would keep restrictions as low as possible while having
an initial "frame" of the content like Tobias said is a very good
idea. If it does not work out well it can be changed later at any
time.
Christian
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:[email protected]
P.S. A good JDO? O, Gasp!
