Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Marco Cavallini <koansoftware@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: openembedded's Wiki license
Date: Sat, 27 Mar 2010 10:19:51 +0100	[thread overview]
Message-ID: <4BADCDB7.4050807@gmail.com> (raw)
In-Reply-To: <1269615592.2305.12.camel@gnutoo-desktop>

GNUtoo ha scritto, Il 26/03/2010 15:59:
> Hi,
> I noticed that buglabs wiki had no license,
> Then buglabs people fixed it(adding a license to it),but they noticed
> that openembedded's wiki was in the same situation.
> 
> Why do we need a license?
> Simply because by default copyright law don't allow modification or
> copying of a work.So if some people modify the wiki,they may be
> infringing the copyright of the previous author.
> 
> Only the previous author can exercise his right(only the copyright owner
> can sue someone)
> 
> That could be a problem,and it would be safer to add a license for
> future contribution,to prevent occurrences of such issues
> 
> Note that it would be difficult to ask permission to all the
> contributors of the wiki for changing the copyright of their work.
> 
> I'm open to every free license for my small contributions(from
> non-copyleft licenses to copyleft ones)
> 
> Denis.

Good point to raise this issue, thanks.

I vote for a license Attribution-ShareAlike 3.0 BY-SA
http://creativecommons.org/licenses/by-sa/3.0/


Cordiali Saluti / Kindest Regards / mit freundlichen Grüssen
--
Marco Cavallini | KOAN sas | Bergamo - Italia
 embedded and real-time software engineering
Phone:+39-035-255.235 - Fax:+39-178-22.39.748
      http://www.KoanSoftware.com



  reply	other threads:[~2010-03-27  9:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-26 14:59 openembedded's Wiki license GNUtoo
2010-03-27  9:19 ` Marco Cavallini [this message]
2010-03-27 18:53 ` Tom Rini

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=4BADCDB7.4050807@gmail.com \
    --to=koansoftware@gmail.com \
    --cc=openembedded-devel@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox