All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: copyright management
Date: Fri, 28 Oct 2005 16:34:08 +0200	[thread overview]
Message-ID: <200510281634.08717.okuji@enbug.org> (raw)

As Marco agreed, I send this information to the list.

Currently, the copyright handling at the FSF is very confused, and this slows 
down the procedures of copyright assignments very much.

Until now, our policy was to apply patches _after_ the copyright is completely 
transferred to the FSF, but we cannot avoid facing on a policy change, since 
we do not want to delay the development too much.

So I'd like to go in this way as a temporary solution *until the copyright 
clerk gets sane*:

1. When you have not signed a copyright assignment yet, we will ask you if you 
accept assigning your copyright on GRUB to the FSF.

2. If you agree, you send a request form to the FSF.

3. Based on this agreement, we start integrating your patches. To reduce a 
potential risk, we don't give you a direct write access to the CVS at this 
moment.

4. Once it is finished correctly, we give you a write permission to the CVS, 
if this makes things easier.

IIRC, these people are in intermediate states: Ruslan, Vincent Guffens, 
Timothy, Vladimir. Do I miss anybody? Now I must dig out the archive to look 
up all pending patches...

Okuji



             reply	other threads:[~2005-10-28 14:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-28 14:34 Yoshinori K. Okuji [this message]
2005-10-28 16:04 ` copyright management Vladimir Serbinenko

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=200510281634.08717.okuji@enbug.org \
    --to=okuji@enbug.org \
    --cc=grub-devel@gnu.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.