Re: [Postgres-xc-general] License of Postgres-XC related documents and contents

[Ashutosh B. <ash...@en...>]

The Postgres-XC documentation and articles/talks/presentation etc.
material, based on XC are two different matters.

For Postgres-XC documentation, the license similar to code should apply. I
don't think there is

For rest of the material/media produced, I don't think, we can enforce any
kind of copy-right as such. The copy-right/licensing will solely depend
upon the author OR the sponsor for such work OR the media where the
material gets published. In fact, we may not be able to enforce any rules
on such production.

If any individual on his/her own is producing a piece of information about
XC, its experience etc. s/he will decide how this material can be further
used and will be governed by the material s/he uses to produce this
material. If the work is being sponsored by someone, the sponsor would be
deciding the terms of usage of such material. In many cases, where such
material is published in magazines or conferences or proceedings, the
publishers have their own copy-right/license rules.

We still can decide what rules to apply to the material produced till date,
which is out of any copy-right/licensing terms.

On Thu, Jul 12, 2012 at 11:10 AM, Michael Paquier <mic...@gm...
> wrote:

>
>
> On Thu, Jul 12, 2012 at 2:34 PM, Koichi Suzuki <koi...@gm...>wrote:
>
>> As raised by Mason and commented by many members, I think it's a time
>> to determine how XC-related documents/contents license should be.
>> Here's my idea.
>>
>> 1. As Mason proposed, I think creative commons is suitable for XC
>> documents/contents (except for the code and the reference, they're
>> licensed under PostgreSQL license).
>> 2. Only for non-commercial use.   For commercial use, need specific
>> approval.
>> 3.  Share-alike.  Can distribute the resulting work only under the
>> same or similar license.
>>
> OK here.
>
>> 4. Original Author.   I'm thinking at least "Postgres-XC development
>> group" should be referred as an original author in derived work.
>>
> As suggested by Pavan and you, XC Development group will be enough... This
> is going to be a pain through years if we look for a special author on a
> special document.
>
>




>
>> If anybody would like to use XC documents/contents commercially, they
>> need to have specific approval.
>
> Or they can make a new one from scratch.
>
>>   I'm also thinking to establish "fund
>> raising group" who receives and approves commercial use, as well as
>> future fundraising work.   This is closed group consists of selected
>> XC mailing list reader.   I'd like to draft update to the charter of
>> the group for comments.
>>
> Those are good ideas, able to diversify the origin of funds able to reach
> the project.
> --
> Michael Paquier
> http://michael.otacoo.com
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>
>


-- 
Best Wishes,
Ashutosh Bapat
EntepriseDB Corporation
The Enterprise Postgres Company