From: adrian15 <adrian15sgd@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: status update for grub 2 developments?
Date: Mon, 18 Jun 2007 12:22:47 +0200 [thread overview]
Message-ID: <46765CF7.7040107@gmail.com> (raw)
In-Reply-To: <46752D5B.1000001@nic.fi>
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
next prev parent reply other threads:[~2007-06-18 11:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-17 12:47 status update for grub 2 developments? Vesa Jääskeläinen
2007-06-17 13:34 ` Robert Millan
2007-06-18 2:52 ` Ashok kumar
2007-06-18 10:22 ` adrian15 [this message]
2007-06-18 13:32 ` Robert Millan
2007-06-18 15:40 ` Vesa Jääskeläinen
2007-06-19 12:13 ` adrian15
2007-06-19 15:13 ` Vesa Jääskeläinen
2007-06-19 12:08 ` adrian15
2007-06-23 12:57 ` Marco Gerards
2007-06-23 14:31 ` Bean
2007-06-23 14:50 ` Marco Gerards
2007-06-24 4:22 ` Bean
2007-06-24 11:47 ` Bean
2007-07-22 12:42 ` Marco Gerards
2007-06-23 14:52 ` Marco Gerards
2007-06-23 15:59 ` Bean
2007-06-23 16:10 ` Marco Gerards
2007-06-23 16:23 ` Bean
2007-06-23 16:38 ` Marco Gerards
2007-06-23 20:19 ` Yoshinori K. Okuji
2007-07-01 17:49 ` adrian15
2007-06-25 18:41 ` Bean
2007-06-26 4:13 ` Ashok kumar
2007-07-22 14:31 ` Marco Gerards
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=46765CF7.7040107@gmail.com \
--to=adrian15sgd@gmail.com \
--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.