openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Weir <>
Subject Re: Access to wiki
Date Sun, 07 Aug 2011 16:34:29 GMT
On Sun, Aug 7, 2011 at 11:55 AM, Eike Rathke <> wrote:
> Hi Rob,
> On Sunday, 2011-08-07 11:27:26 -0400, Rob Weir wrote:
>> So assigning an open license is entirely optional.  I could upload a
>> page under by personal copyright and demand payment of 20 chickens or
>> 1 goat for copying the document.  For example:
> Hehe, Clayton was very fast to ensure you won't need a new shed for all
> those chickens and goats ;-)

Didn't Clayton just say that he had left the project.  So why does he
still have super-user privileges?  And since when does a non-project
member have the right to revert a change by a Committer, with no

>> I think this is a problem.  Although I could easily accept some
>> sandbox where random contributions could be made under a variety of
>> eclectic licenses, we should be concerned with a few things:
>> 1) How do we ensure that contributions are made in a way that is
>> consistent with the rights we need to even host the contributed
>> content.
> Ensure that contributions are made under a proper license by having
> a statement at a prominent place when editing a page. Have a bot running
> that searches for terms like license and copyright and such and review
> those pages, reject/undo edits if necessary.

That could work.  But it is a change from how the site works today.
Would be good to have it in the terms presented to the user when they
sign up for an account as well.

>> 2) How do we prevent core documentation and project pages from being
>> contaminated by contributions that are incompatibly licensed?  In
>> other words, how do we preserve the rights of this project and our
>> users and downstream consumers to be able to copy, modify, translate,
>> redistribute, etc., contributed content.
> The same as for 1)
>  Eike
> --
>  PGP/OpenPGP/GnuPG encrypted mail preferred in all private communication.
>  Key ID: 0x293C05FD - 997A 4C60 CE41 0149 0DB3  9E96 2F1A D073 293C 05FD

View raw message