From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1N95Z1-000836-58 for mharc-grub-devel@gnu.org; Fri, 13 Nov 2009 18:28:23 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N95Yw-0007zm-Rd for grub-devel@gnu.org; Fri, 13 Nov 2009 18:28:18 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N95Yu-0007z8-3e for grub-devel@gnu.org; Fri, 13 Nov 2009 18:28:17 -0500 Received: from [199.232.76.173] (port=43541 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N95Yt-0007yt-TP for grub-devel@gnu.org; Fri, 13 Nov 2009 18:28:15 -0500 Received: from ey-out-1920.google.com ([74.125.78.149]:2430) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N95Yt-0002SB-Bx for grub-devel@gnu.org; Fri, 13 Nov 2009 18:28:15 -0500 Received: by ey-out-1920.google.com with SMTP id 3so1008812eyh.34 for ; Fri, 13 Nov 2009 15:28:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:x-enigmail-version :content-type; bh=bsveZ0yujwYjH0G1K1pAv+l2eEG9c/dG9xSiGvnGdTs=; b=HwS2bEaNWSffFNIJTYQxdAmfWWtRCEsJZtY7AInDT6krmGrhfvB/m14hhurO2FCj48 MGKBQSyDLTtQJWQAgvl1yQ2zlBZzUV4E2fKii/0aXGgt4vf4KDzGikLTuaJSB/5ZNOQ9 cIXKkHvV9chf7chO2rdp5jIqwOXcWd7NvQvyY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :x-enigmail-version:content-type; b=fYMFMJRkJjaCnwWW26Pxcs2Hzkwab3dWmMQK4iGWmhTDX6koDLcIthN1QAeyfpCijQ MRGQ8PsTvay1chVveSKVOWhyvEkxB0exqOpqA0rYRBK+v/KCmKuqTvBo2LvoUDJlNdLC uQVuADVf5el4aZWQqfbeUs5wZTaY0lM2zXr3g= Received: by 10.213.23.66 with SMTP id q2mr496585ebb.6.1258154894370; Fri, 13 Nov 2009 15:28:14 -0800 (PST) Received: from debian.bg45.phnet (125-69.1-85.cust.bluewin.ch [85.1.69.125]) by mx.google.com with ESMTPS id 5sm1245465eyh.18.2009.11.13.15.28.13 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 13 Nov 2009 15:28:13 -0800 (PST) Message-ID: <4AFDEB81.7050507@gmail.com> Date: Sat, 14 Nov 2009 00:28:01 +0100 From: Vladimir 'phcoder' Serbinenko User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20091109) MIME-Version: 1.0 To: etherboot-developers@lists.sourceforge.net X-Enigmail-Version: 0.95.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enig184C10E814C3B645C7533D21" X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Cc: The development of GRUB 2 Subject: gPXE and GRUB2 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Nov 2009 23:28:19 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig184C10E814C3B645C7533D21 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 --------------enig184C10E814C3B645C7533D21 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iF0EAREKAAYFAkr964wACgkQNak7dOguQgn2TQD/XhY0kFx9Zi8lKHKAtP/qh0Dg c1dyc60s7xbDACC8epkA91iN/CYcOPHs2jE7pH5Nrz/SvhJTaDH3qhHAXflUYws= =Q2kD -----END PGP SIGNATURE----- --------------enig184C10E814C3B645C7533D21--