grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: Dee Sharpe <demetrioussharpe@netscape.net>
Subject: Re: AFS and BFS removed. Unacceptable license.
Date: Sat, 29 Oct 2011 17:37:46 +0200	[thread overview]
Message-ID: <4EAC1DCA.4040809@gmail.com> (raw)
In-Reply-To: <E653F58A-12EE-411D-96D8-B6F033508D5C@netscape.net>

[-- Attachment #1: Type: text/plain, Size: 2395 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?
>
They need to be rewritten. Assignment can be discussed. I've already
done a part of BFS (using "practical file system design" book as a
reference) and since AFS is similar it can use same file with some
defines. So it should
Actually if you want to help what I need the most is the way of mkfs and
write to AFS (or as a variant something which already generates AFS with
files on it like xorriso can do for iso9660) for automated testing purposes.
It has to run on my testing system (Debian GNU/Linux)
> A. Demetrious Sharpe
>
> It's not a question of why I'm better than you,
> it's a question of why you're not as good as me.
> The fact that you fail to see the difference between the two, answers both questions!
>
> Sent from my iPhone4
>
> 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 --]

  reply	other threads:[~2011-10-29 15:39 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 [this message]
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=4EAC1DCA.4040809@gmail.com \
    --to=phcoder@gmail.com \
    --cc=demetrioussharpe@netscape.net \
    --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).