From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: AFS and BFS removed. Unacceptable license.
Date: Sun, 30 Oct 2011 16:12:57 +0100 [thread overview]
Message-ID: <4EAD6979.7000004@gmail.com> (raw)
In-Reply-To: <E653F58A-12EE-411D-96D8-B6F033508D5C@netscape.net>
[-- Attachment #1: Type: text/plain, Size: 1906 bytes --]
On 29.10.2011 17:22, Dee Sharpe wrote:
> Ok, so I'd assume that the AFS driver needs to be rewritten. Is it absolutely mandatory that copyright be assigned to the FSF?
>
I rewrote both BFS and AFS (which is a minor modification to the
former). Can you give me the tools (mkfs + a way to write to AFS)
necessarily to automatically test it for regressions in future?
> Sent from my iPhone4
Please avoid posting such advertisements here.
> On Oct 29, 2011, at 4:37 AM, Vladimir 'φ-coder/phcoder' Serbinenko<phcoder@gmail.com> wrote:
>
>> 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
>>
>>
>> _______________________________________________
>> Grub-devel mailing list
>> Grub-devel@gnu.org
>> https://lists.gnu.org/mailman/listinfo/grub-devel
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
prev parent reply other threads:[~2011-10-30 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 9:37 AFS and BFS removed. Unacceptable license Vladimir 'φ-coder/phcoder' Serbinenko
2011-10-29 15:22 ` 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 [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=4EAD6979.7000004@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).