From: "Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com>
To: "Horst von Brand" <vonbrand@inf.utfsm.cl>
Cc: linux-kernel@vger.kernel.org,
"Kalin KOZHUHAROV" <kalin@thinrope.net>,
"Jesper Juhl" <jesper.juhl@gmail.com>, "Greg KH" <greg@kroah.com>
Subject: Re: Linux kernel development
Date: Mon, 5 Jun 2006 22:51:29 +0200 [thread overview]
Message-ID: <4d8e3fd30606051351i5533b04vcbe9fe500201c3bb@mail.gmail.com> (raw)
In-Reply-To: <200606051738.k55HcrC2025442@laptop11.inf.utfsm.cl>
On 6/5/06, Horst von Brand <vonbrand@inf.utfsm.cl> wrote:
> Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com> wrote:
> > On 6/5/06, Horst von Brand <vonbrand@inf.utfsm.cl> wrote:
>
> [...]
>
> > > Could you add a README (including contact info, etc), and perhaps a TODO
> > > (and a copy of SubmittingPatches, which I assume applies here too?) to the
> > > project? A license for the text is required, AFAIU (GPLv2, or one of the
> > > Creative Commons licenses perhaps?).
> >
> > Not and exepert in this area, I think I'll release it under GPL2.
>
> Did you write all (most) of it? If not, you'd have to ask the original
> author(s).
>
> BTW, thinking it over in the shower today, if/when this is translated into
> asciidoc(1) (or whatever), a "source code" license (like GPLv2) would be
> appropiate IMHO. Besides, using the same license as what it describes is
> sensible.
>
> > What's the normal approach? Can I just add:
> > # This document is distribuited under
> > # GNU GENERAL PUBLIC LICENSE
> > # Version 2, June 1991
> > # http://www.gnu.org/licenses/gpl.txt
> >
> > To the text?
>
> The license text spells it out ;-)
>
> I would add language to that effect to the README file, and bundle the
> standard COPYING file with the package
Modified and pushed out, since part of the document is from inkernel
documentation I choose GPL v2.
Thanks!
--
Paolo
http://paolociarrocchi.googlepages.com
next prev parent reply other threads:[~2006-06-05 20:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-03 13:36 Paolo Ciarrocchi
2006-06-03 18:28 ` Horst von Brand
2006-06-04 10:00 ` Paolo Ciarrocchi
2006-06-04 10:30 ` Paolo Ciarrocchi
2006-06-04 23:05 ` Horst von Brand
2006-06-05 11:39 ` Paolo Ciarrocchi
2006-06-05 14:58 ` Steven Rostedt
2006-06-05 20:52 ` Paolo Ciarrocchi
2006-06-05 17:38 ` Horst von Brand
2006-06-05 20:51 ` Paolo Ciarrocchi [this message]
2006-06-06 19:22 ` Paolo Ciarrocchi
2006-06-06 22:09 ` Horst von Brand
2006-06-07 21:59 ` Paolo Ciarrocchi
2007-07-16 21:04 Linux Kernel Development Paolo Ciarrocchi
2007-07-16 21:34 ` Michal Piotrowski
2007-07-16 21:37 ` Paolo Ciarrocchi
[not found] <CAK8ka9y1VhMzS0X2GSEg4AQzSMPwOkS3HQxBuX4t-Rp-_OwDow@mail.gmail.com>
2011-08-22 4:51 ` linux kernel development Niloofar Fazlollahi
2011-08-22 4:53 ` Américo Wang
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=4d8e3fd30606051351i5533b04vcbe9fe500201c3bb@mail.gmail.com \
--to=paolo.ciarrocchi@gmail.com \
--cc=greg@kroah.com \
--cc=jesper.juhl@gmail.com \
--cc=kalin@thinrope.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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
all inboxes | Powered by JetHome®