All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: OE Manual: License change?
Date: Tue, 01 Apr 2008 21:48:09 +0100	[thread overview]
Message-ID: <1207082889.4916.25.camel@dax.rpnet.com> (raw)
In-Reply-To: <47F25AAA.8020705@gmx.net>

On Tue, 2008-04-01 at 17:54 +0200, Robert Schuster wrote:
> Marcin Juszkiewicz schrieb:
> > OpenEmbedded documentation use "Creative Commons Attribution License 2.0", 
> > Poky Handbook use "Creative Commons Attribution Non-Commercial Share 
> > Alike 2.0" license. Copying from Poky Handbook to OpenEmbedded manual 
> > require change on OE doc license to CC-NC-SA.
> > 
> > I vote for changing OE manual license to CC-NC-SA as there is lot of good 
> > stuff in Poky handbook which would be nice to have also in OE manual.
> OMG not any of these broken *-NC licenses. ;)

Why 'broken'? What does it stop you doing which you want to do?

> A manual is a functional work and therefore should IMHO not restrict the
> uses.
> 
> Any chance of changing poky manual's license to something less
> restrictive? CC-BY-SA/CC-BY preferably?

Not really. We went around in circles with the manual licence and on the
one hand we want it open, we want people to be able to make changes and
we want it to be useful for everyone. How you protect work invested in
something like Poky is very tricky however, particularly when we're keen
on giving back to the community. At the end of the day, Poky is
commercial to some degree and what we don't want is someone to rebadge
Poky and its manual and then make money on the result and this approach
gives us some protection.

I'm relatively happy with the outcome and whilst its a shame the
licenses aren't compatible, I don't think this will be too much of an
issue. People are free to submit to one, the other or both and may the
best manual win :) Don't underestimate the amount of work involved in
writing these things...

For the record I personally don't think -NC is appropriate for OE's
manual.

Cheers,

Richard





      reply	other threads:[~2008-04-01 20:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-31 14:07 New OE user question E Robertson
2008-03-31 15:33 ` Cliff Brake
2008-03-31 16:19   ` E Robertson
2008-03-31 17:12     ` Cliff Brake
2008-03-31 17:09   ` E Robertson
2008-03-31 17:33     ` Cliff Brake
2008-03-31 15:44 ` Leon Woestenberg
2008-03-31 16:12   ` Koen Kooi
2008-03-31 16:26     ` E Robertson
2008-03-31 16:34     ` Geoffrey Wossum
2008-03-31 17:47       ` Leon Woestenberg
2008-04-01  5:45         ` Ulf Samuelsson
2008-03-31 16:01 ` Geoffrey Wossum
2008-04-01  6:40   ` OE Manual: License change? (was: Re: New OE user question) Marcin Juszkiewicz
2008-04-01 11:00     ` OE Manual: License change? Jeremy Lainé
2008-04-01 13:08       ` Leon Woestenberg
2008-04-01 15:27         ` Marcin Juszkiewicz
2008-04-01 15:54     ` Robert Schuster
2008-04-01 20:48       ` Richard Purdie [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1207082889.4916.25.camel@dax.rpnet.com \
    --to=rpurdie@rpsys.net \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.