grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: AFS and BFS removed. Unacceptable license.
Date: Sat, 29 Oct 2011 11:37:46 +0200	[thread overview]
Message-ID: <4EABC96A.70904@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 937 bytes --]

An unfortunate discovery has been done: our AFS code is based on
fsys_afs.c and afs.h from Syllable GRUB Legacy. The files in question
are not under FSF copyright, not licence-compatible and it wasn't
announced what's the code based on when the patch was sent or committed.
While first one is a minor issue I could grant exception for, the 2
other ones are fatal. I remind to all of you that a license-incompatible
can put the whole project in jeopardy and the need of both announcing
where code came from (refer to your copyright assignment if you have
one) and proper acknowledgement and traceability. The later is very
important if the code can come from several possible sources. In this
case if the code has been based on Haiku's BFS it would have been fine,
unfortunately it wasn't, without proper traceability it's hard to
differentiate between such cases.

-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]

             reply	other threads:[~2011-10-29  9:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-29  9:37 Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-10-29 15:22 ` AFS and BFS removed. Unacceptable license Dee Sharpe
2011-10-29 15:37   ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-03 19:06     ` Dee Sharpe
2011-10-30 15:12   ` Vladimir 'φ-coder/phcoder' 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=4EABC96A.70904@gmail.com \
    --to=phcoder@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).