From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1HzuAG-00027q-IL for mharc-grub-devel@gnu.org; Sun, 17 Jun 2007 08:47:32 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HzuAE-00027i-7K for grub-devel@gnu.org; Sun, 17 Jun 2007 08:47:30 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HzuAB-00027W-Pz for grub-devel@gnu.org; Sun, 17 Jun 2007 08:47:28 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HzuAB-00027T-IX for grub-devel@gnu.org; Sun, 17 Jun 2007 08:47:27 -0400 Received: from pne-smtpout3-sn2.hy.skanova.net ([81.228.8.111]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HzuAB-00022K-1E for grub-devel@gnu.org; Sun, 17 Jun 2007 08:47:27 -0400 Received: from [127.0.0.1] (88.193.32.97) by pne-smtpout3-sn2.hy.skanova.net (7.2.075) id 4667D3200006862C for grub-devel@gnu.org; Sun, 17 Jun 2007 14:47:23 +0200 Message-ID: <46752D5B.1000001@nic.fi> Date: Sun, 17 Jun 2007 15:47:23 +0300 From: =?UTF-8?B?VmVzYSBKw6TDpHNrZWzDpGluZW4=?= User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: The development of GRUB 2 X-Enigmail-Version: 0.95.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: Quoted-Printable X-detected-kernel: Solaris 8 (1) Subject: status update for grub 2 developments? X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jun 2007 12:47:30 -0000 Hi all! I think it would be wise to keep some kind of status updates from time to time so we can keep track on what people are doing (related to grub 2). If we continue with current situation we are long in 2010's before we have next release. I think it would also be important to coordinate more different activities within grub 2. In example graphical menu has been issue for several years now :). Therefore I would propose that we would setup a group of people that would concentrate on specific issues related to implmentation (like a work group or something). I do not see it as a requirement that this group of people would implement the feature (though that would be good), but most importantly to draft out how features should work. When there is a spec written how feature should work then it would be much easier to implement that feature and then it would match ideology of other relevant developers (eg. to get patch accepted). I would see that at least following working groups should be formed. Of course we could tackle design issue at a time and then move to other issu= es. - Graphical menu (needs API spec, configuration file specs, guidelines for implementation, information how to integrate with scripting) - Network support (needs API spec, driver architecture, protocol stacks, file system support) Perhaps some others too... (please add) Anyway. First of all I would like to hear if you are developing something above or something else, reply this e-mail and tell us about it, there is no reason that work should be duplicated. Especially if you are already developing a feature your words would be good to be heard. If you are just reporting back list of stuff you are working on, please keep list as simple and clean as we want only big picture :). You could also describe how are you progressing with the feature. Ideas are welcome where to store this information are also welcome :). We would need to track requirements for features on component level. More automated the better. Thanks Vesa J=C3=A4=C3=A4skel=C3=A4inen