From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1I0FN8-00053z-Oa for mharc-grub-devel@gnu.org; Mon, 18 Jun 2007 07:26:14 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I0FN7-00051y-CR for grub-devel@gnu.org; Mon, 18 Jun 2007 07:26:13 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I0FN5-00051L-6k for grub-devel@gnu.org; Mon, 18 Jun 2007 07:26:12 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I0FN5-00051I-1W for grub-devel@gnu.org; Mon, 18 Jun 2007 07:26:11 -0400 Received: from ug-out-1314.google.com ([66.249.92.169]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1I0FN4-0002mL-Jn for grub-devel@gnu.org; Mon, 18 Jun 2007 07:26:10 -0400 Received: by ug-out-1314.google.com with SMTP id 34so643556ugf for ; Mon, 18 Jun 2007 04:26:08 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=X6PTyFSi45r1Lkh48W0LZy6tPkduZSdvISHKdQaJU3Y2gHOY622OO7bu/yAABOjZ7G5wcSn/bS2UlqhnxQsJo9fNp65TfFmOzHloLF59Yr8rzbURVyWElzkvnF6jAVRiv6CfC5Cvbr/2h6DK3V7OWT5jiHlQn22Pi0HWOJUpkDg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=K4ijQS35ikIZpP7l+eoDq0fAOb/TvqkTtrbGRJafkxUlR+MD4o/o+G0eGGm2l00+szjnH+IvOz7izPZYLom6U26ivmGGi+KIxw0bkhR+MzvjJAGDToE0hOh6ile6KRRWA4fTBb1yG1d0dbN/4O8vLnd+Z0HRIJUAFHn+zWPzu+M= Received: by 10.67.88.20 with SMTP id q20mr4993291ugl.1182165968917; Mon, 18 Jun 2007 04:26:08 -0700 (PDT) Received: from ?172.16.51.37? ( [193.144.12.226]) by mx.google.com with ESMTP id t57sm4841793uga.2007.06.18.04.26.08 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 18 Jun 2007 04:26:08 -0700 (PDT) Message-ID: <46765CF7.7040107@gmail.com> Date: Mon, 18 Jun 2007 12:22:47 +0200 From: adrian15 User-Agent: Thunderbird 1.5.0.8 (X11/20061107) MIME-Version: 1.0 To: The development of GRUB 2 References: <46752D5B.1000001@nic.fi> In-Reply-To: <46752D5B.1000001@nic.fi> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-detected-kernel: Linux 2.4-2.6 (Google crawlbot) Subject: Re: 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: Mon, 18 Jun 2007 11:26:13 -0000 Vesa Jääskeläinen escribió: > 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. You're too optimistic. :) I was thinking about 2015. Anyway,... I will work hard this summer in grub2 because it needs it. > I think it would also be important to coordinate more different > activities within grub 2. Ok. > In example graphical menu has been issue for > several years now :). I am sorry not being an expert on this area. > 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 also think groups are a good thing. > 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 also like the specs idea. > 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 issues. > > - Graphical menu (needs API spec, configuration file specs, guidelines > for implementation, information how to integrate with scripting) I might collaborate on the "how to integrate with scripting" part. > > - Network support (needs API spec, driver architecture, protocol stacks, > file system support) No idea about this subject. > Perhaps some others too... (please add) I am going to work in grub-disk. A collection of grub2.cfg files or maybe more that will define useful collection of command such as Search linux kernel, linux initrd and load them. Something similar to Super Grub Disk. > 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. My current todo: # Current development * pause command * map, mapboot and usbshift commands # Short term development * grub-disk scripts * grub2 scripts testing * grub legacy commands porting # Long term development * install and setup commands for grub2 If you want more details please visit: http://grub.enbug.org/AdrianGibanel > 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. Can we use the bugs system maybe? A friend of mine uses trac ( http://trac.edgewall.org/ ) and he likes it a lot. I do not know if it fits our needs. adrian15