From: Vladimir 'phcoder' Serbinenko <phcoder@gmail.com>
To: etherboot-developers@lists.sourceforge.net
Cc: The development of GRUB 2 <grub-devel@gnu.org>
Subject: gPXE and GRUB2
Date: Sat, 14 Nov 2009 00:28:01 +0100 [thread overview]
Message-ID: <4AFDEB81.7050507@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2077 bytes --]
Hello, all. I'm currently importing gPXE into grub-extras to allow a
tighter interraction and integration. I would like to discuss
collaboration between our two projects. GRUB2 is under GPLv3+ and gPXE
is mostly GPLv2+-compatible. I will keep the original licences on all
imported files this way improvements made to files originating from gPXE
can find their way back. I see 3 collaboration models:
1) I import all files we need and which are under compatible licence. We
keep licences, notify you about improvements which may be worth
incorporating into gPXE
2) I write a python script which does automatic importing and adds few
GRUB-specific patches. This way syncronisation is easier. Patches which
aren't GRUB-specific would be redirected to gPXE
3) Add a secondary target to gPXE to produce series of GRUB modules. Due
to big differences between build systems this may be problematic and
result in frequent breakage
Of course any GPLv2-only file is excluded from this collaboration.
Currently I haven't finished importing so don't know which files may
pose problem and that I'll have to rewrite or import from a different
source. Currently I have following problems:
1) Some files like netl/mii.c are labeled as GPL without explicit version
2) Some files like net/ftp.c, net/icmpv6.c, net/ipv6.c, net/ndp.c and
include/gpxe/ndp.h
Would it be possible to clarify their legal status, if possible opt for
GPLv2+ or 2-clause BSDL
3) include/gpxe/list.h is under GPLv2-only. I already created a
workalike for it from scratch so it's not very important but would still
be nice if we could share this code one way or another.
4) A lot of drivers are GPLv2-only. Would it be possible to relicence
them as GPLv2+ ?
Technical comments are welcome too. Currently I imported directories net
and include/gpxe omitting files under unclear licence or GPLv2-only as
well as files core/base64.c, core/uri.c and core/uuid.c. The whole still
has 94 unresolved symbols and I'll work on fixing it.
Thanks in advance
Vladimir 'phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]
next reply other threads:[~2009-11-13 23:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 23:28 Vladimir 'phcoder' Serbinenko [this message]
2009-11-14 15:44 ` gPXE and GRUB2 Robert Millan
[not found] ` <422fdd8a0911140615n5e16d736l7462dfcf968e2f23@mail.gmail.com>
2009-11-14 15:57 ` [Etherboot-developers] " Vladimir 'phcoder' Serbinenko
2009-11-14 17:38 ` Robert Millan
[not found] ` <422fdd8a0911141003j3839662dm30489e08e87da90e@mail.gmail.com>
2009-11-14 18:46 ` Robert Millan
2009-11-19 9:10 ` Arends, R.R.
[not found] ` <4B0517EC.7FDC.0010.0@hro.nl>
[not found] ` <422fdd8a0911190153qa7c58bcle4780880401b1720@mail.gmail.com>
2009-11-19 10:00 ` Arends, R.R.
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=4AFDEB81.7050507@gmail.com \
--to=phcoder@gmail.com \
--cc=etherboot-developers@lists.sourceforge.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 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.