You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@esme.apache.org by Vassil Dichev <vd...@apache.org> on 2009/01/21 11:06:02 UTC

Publically editable wiki

Hello Bertrand, Daniel,

It would be beneficial for the ESME team if we have a world-editable
wiki, at least for the time being. Some of the contributors are still
sorting out issues with the ICLAs (e.g. Richard Hirsch), so can't edit
the Confluence wiki at cwiki.apache.org.

I am confused at this point what is possible- Daniel mentioned that
the MoinMoin wiki is world-editable, while Bertrand pointed out there
could be a public Confluence wiki too (indeed this is the case with
SLING). What are the differences between the two and what are the
restrictions? Do you have any recommendations for one or the other?

Lastly, if a publically editable Confluence wiki is not a good choice
for ESME, how can I volunteer for maintenance of the ESME MoinMoin
wiki? Is writing a short letter to the infrastructure team enough?

Thanks in advance,
Vassil

Re: Publically editable wiki

Posted by Robert Burrell Donkin <ro...@gmail.com>.
On Wed, Jan 21, 2009 at 3:58 PM, Bertrand Delacretaz
<bd...@apache.org> wrote:
> On Wed, Jan 21, 2009 at 4:44 PM, Vassil Dichev <vd...@apache.org> wrote:
>>...I wanted to know about the ICLA process in order
>> to follow it and have no intention of circumventing it. E.g. the ESME
>> site was created by Dick, but uploaded by Bertrand, so there must be
>> perfectly clean ways for someone like Dick to contribute. I wanted to
>> know where to draw the line....
>
> In this case, Dick, when updating his patches to ESME-2, checked the
> "grant license to ASF" option, visible at
> https://issues.apache.org/jira/secure/ManageAttachments.jspa?id=12410470
> - that makes it fine for a committer to apply those patches.

documentation is - in some ways - a difficult subject than code

a typical code contributions will be - as a derivative work - covered
by AL2.0 clause 5.  apache always try to be as clear and transparent
as possible - the click through license isn't usually strictly
necessary but it's good for contributors to actively make an explicit
choice to donate.

however - Bertrand said - it is important to ask any multiple
contributors for a CLA (as part of encouragement aimed at persuading
them to join the community)

> There's no such option for wiki content unfortunately, AFAIK.

+1

> Still, when someone starts updating lots of patches (whatever that
> means) in this way, projects usually ask them to submit an iCLA - it's
> also a good way to make people aware that their contributions might
> help them become a committer at some point.

+1

- robert

AW: Publically editable wiki

Posted by "Hirsch, Richard" <ri...@siemens.com>.
 
I'm working on getting my iCLA through. I'm having to deal with corporate bureaucracy. I'll probably submit it as an individual but I'm checking the legal side first to make sure that there are no conflicts with my existing contract with Siemens. 

I assume that it is in everyone's interest that everything is squeaky clean IP-wise before I start officially contributing. 

D. 

-----Ursprüngliche Nachricht-----
Von: bdelacretaz@gmail.com [mailto:bdelacretaz@gmail.com] Im Auftrag von Bertrand Delacretaz
Gesendet: Mittwoch, 21. Jänner 2009 16:59
An: esme-dev@incubator.apache.org
Betreff: Re: Publically editable wiki

On Wed, Jan 21, 2009 at 4:44 PM, Vassil Dichev <vd...@apache.org> wrote:
>...I wanted to know about the ICLA process in order
> to follow it and have no intention of circumventing it. E.g. the ESME
> site was created by Dick, but uploaded by Bertrand, so there must be
> perfectly clean ways for someone like Dick to contribute. I wanted to
> know where to draw the line....

In this case, Dick, when updating his patches to ESME-2, checked the
"grant license to ASF" option, visible at
https://issues.apache.org/jira/secure/ManageAttachments.jspa?id=12410470
- that makes it fine for a committer to apply those patches.

There's no such option for wiki content unfortunately, AFAIK.

Still, when someone starts updating lots of patches (whatever that
means) in this way, projects usually ask them to submit an iCLA - it's
also a good way to make people aware that their contributions might
help them become a committer at some point.

-Bertrand

Re: Publically editable wiki

Posted by Bertrand Delacretaz <bd...@apache.org>.
On Wed, Jan 21, 2009 at 4:44 PM, Vassil Dichev <vd...@apache.org> wrote:
>...I wanted to know about the ICLA process in order
> to follow it and have no intention of circumventing it. E.g. the ESME
> site was created by Dick, but uploaded by Bertrand, so there must be
> perfectly clean ways for someone like Dick to contribute. I wanted to
> know where to draw the line....

In this case, Dick, when updating his patches to ESME-2, checked the
"grant license to ASF" option, visible at
https://issues.apache.org/jira/secure/ManageAttachments.jspa?id=12410470
- that makes it fine for a committer to apply those patches.

There's no such option for wiki content unfortunately, AFAIK.

Still, when someone starts updating lots of patches (whatever that
means) in this way, projects usually ask them to submit an iCLA - it's
also a good way to make people aware that their contributions might
help them become a committer at some point.

-Bertrand

Re: Publically editable wiki

Posted by Vassil Dichev <vd...@apache.org>.
> I would be very strongly opposed to mechanisms that circumvent the CLA ICLA
> process.  A clear set of code ownership and rights to create such code is
> critical for others to use ESME.  Both the lawyer and the business side of
> me wants to make sure the ESME code stays clean.

No question about it. I wanted to know about the ICLA process in order
to follow it and have no intention of circumventing it. E.g. the ESME
site was created by Dick, but uploaded by Bertrand, so there must be
perfectly clean ways for someone like Dick to contribute. I wanted to
know where to draw the line.

In this context, it would make sense to clarify what's fair game in
terms of contributions before ESME's inclusion in Apache. Things are
not straightforward here, that's why I'm asking. E.g.
http://esmeproject.googlecode.com/files/actions.pdf was contributed by
Richard, but it was probably based on the quick help on the actions
view (contributed by David).

I hope I'm not being dense here- I'm not a lawyer. I as much as anyone
else want to keep ESME clean- without throwing away help which we
could legally use.

Re: Publically editable wiki

Posted by David Pollak <fe...@gmail.com>.
I would be very strongly opposed to mechanisms that circumvent the CLA ICLA
process.  A clear set of code ownership and rights to create such code is
critical for others to use ESME.  Both the lawyer and the business side of
me wants to make sure the ESME code stays clean.

Thanks,

David

On Jan 21, 2009 6:05 AM, "Daniel Kulp" <dk...@apache.org> wrote:

On Wednesday 21 January 2009 5:06:02 am Vassil Dichev wrote: > It would be
beneficial for the ESME t...
Can I ask what the hold up is with the icla's?   If he's going to contribute
in a meaningful way, he needs to get that in.

> I am confused at this point what is possible- Daniel mentioned that > the
MoinMoin wiki is world-...
We can definitely create a public confluence space.  That's not a problem.
They question is how useful will it be?   ANYTHING that gets added there
cannot be then moved over into official documentation or into svn or
anything
like that.   It sounds to me like you want a place to start collaborating on
some design docs and such.   In that case, it really CANNOT go on a public
wiki as, most likely, it would get moved into official docs as it gets
finalized.    That's mostly why I HIGHLY recommend getting on the ball and
getting ICLA's in.

One note: in the non-world-editable confluence space, anyone can create
comments attached to pages.   Thus, you could start some pages and he or
anyone else could comment on it.   You could then use the comments to adjust
things, etc....

Anyway, I'd like to here the full use case that you and Richard are trying
to
achieve on a public wiki.   If its potential documentation or web site
material, then no, it doesn't go on a public wiki and no need to create one.

--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog

Re: Publically editable wiki

Posted by Daniel Kulp <dk...@apache.org>.
On Wednesday 21 January 2009 5:06:02 am Vassil Dichev wrote:
> It would be beneficial for the ESME team if we have a world-editable
> wiki, at least for the time being. Some of the contributors are still
> sorting out issues with the ICLAs (e.g. Richard Hirsch), so can't edit
> the Confluence wiki at cwiki.apache.org.

Can I ask what the hold up is with the icla's?   If he's going to contribute 
in a meaningful way, he needs to get that in.

> I am confused at this point what is possible- Daniel mentioned that
> the MoinMoin wiki is world-editable, while Bertrand pointed out there
> could be a public Confluence wiki too (indeed this is the case with
> SLING). What are the differences between the two and what are the
> restrictions? Do you have any recommendations for one or the other?

We can definitely create a public confluence space.  That's not a problem.   
They question is how useful will it be?   ANYTHING that gets added there 
cannot be then moved over into official documentation or into svn or anything 
like that.   It sounds to me like you want a place to start collaborating on 
some design docs and such.   In that case, it really CANNOT go on a public 
wiki as, most likely, it would get moved into official docs as it gets 
finalized.    That's mostly why I HIGHLY recommend getting on the ball and 
getting ICLA's in.  

One note: in the non-world-editable confluence space, anyone can create 
comments attached to pages.   Thus, you could start some pages and he or 
anyone else could comment on it.   You could then use the comments to adjust 
things, etc....

Anyway, I'd like to here the full use case that you and Richard are trying to 
achieve on a public wiki.   If its potential documentation or web site 
material, then no, it doesn't go on a public wiki and no need to create one.  

-- 
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog

Re: Publically editable wiki

Posted by Vassil Dichev <vd...@apache.org>.
Robert, Daniel, thanks for the comments.

> documentations is source and any source which makes it into apache
> releases needs to be of known provenance. confluence works well as a
> lightweight way of creating releasable documentation provided that
> everyone who has write access has signed a CLA.

The full implications of "documentation as source" is something I
neglected to pay close attention to.

> Can I ask what the hold up is with the icla's?   If he's going to contribute
> in a meaningful way, he needs to get that in.

Good, I'm now aware of the restrictions. AFAIK, Dick just wants to
make sure his company couldn't have any claims on his contributions.
It's probably a matter of time.

> Anyway, I'd like to here the full use case that you and Richard are trying to
> achieve on a public wiki.   If its potential documentation or web site
> material, then no, it doesn't go on a public wiki and no need to create one.

I imagined a use case similar to when a patch for compilable source
code is sent by a non-committer and reviewed by the committer before
being accepted. I now realize an ICLA is probably required for this
case too. I failed to make the mental jump that even minor changes
like formatting, correcting spelling mistakes and moving content
around in a wiki need to be controlled- and there's no way to put a
line between "minor" and "major".

Comments on the Confluence pages should suffice for our needs for now-
thanks for reminding us!

Thanks again for your patience clarifying the small print. We'll make
sure all of our contibutions conform to the rules.

Vassil

Re: Publically editable wiki

Posted by Robert Burrell Donkin <ro...@gmail.com>.
On Wed, Jan 21, 2009 at 10:06 AM, Vassil Dichev <vd...@apache.org> wrote:
> Hello Bertrand, Daniel,
>
> It would be beneficial for the ESME team if we have a world-editable
> wiki, at least for the time being. Some of the contributors are still
> sorting out issues with the ICLAs (e.g. Richard Hirsch), so can't edit
> the Confluence wiki at cwiki.apache.org.
>
> I am confused at this point what is possible- Daniel mentioned that
> the MoinMoin wiki is world-editable, while Bertrand pointed out there
> could be a public Confluence wiki too (indeed this is the case with
> SLING). What are the differences between the two and what are the
> restrictions?

a little bit of context...

documentations is source and any source which makes it into apache
releases needs to be of known provenance. confluence works well as a
lightweight way of creating releasable documentation provided that
everyone who has write access has signed a CLA.

so, a standard use case of a confluence wiki here at apache is to
create releasable documentation, which means it's restricted to those
with CLAs only.

apache doesn't have any way ATM of doing this with MoinMoin so
confluence is the only choice for this use case.

the other use case is for publicly editable documents overseen by the
community but not released. this is what's meant by a public wiki.
either MoinMoin or confluence instances can be used as public wiki's

> Do you have any recommendations for one or the other?

(i'll leave this to others...)

> Lastly, if a publically editable Confluence wiki is not a good choice
> for ESME, how can I volunteer for maintenance of the ESME MoinMoin
> wiki? Is writing a short letter to the infrastructure team enough?

MoinMoin (or confluence when it's used as a public wiki) doesn't
really take any maintainance so it's usually enough just to ask for
one

- robert