From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: GRUB 2 documentation
Date: Sun, 01 Jul 2007 13:48:33 +0200 [thread overview]
Message-ID: <87sl88jqem.fsf@xs4all.nl> (raw)
In-Reply-To: <a5a1faa10706270617i1b61e721ka05c587cdfe56fe7@mail.gmail.com> (Khaled Hosny's message of "Wed, 27 Jun 2007 16:17:43 +0300")
"Khaled Hosny" <khaledhosny@eglug.org> writes:
>> > I see this bug
>> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=333516 about
>> > documentation , what is the status of that, we are waiting for grub 2
>> > to hit stable before the documentation is written or what?
>>
>> Well, you can't write 100% accurate documentation now, but GRUB 2 will
>> never be finished (as in: software is never finished), so you do not
>> have to wait. Better start now and improve as we go along.
>>
>> Did you read the texinfo documentation from GRUB Legacy? This is the
>> quality I am hoping for. So not a manpage, but good documentation
>> that explains all features, etc.
>>
>> Really, documentation is as important as the code itself. I would
>> become really happy if you would be willing to work on this. You
>> don't need many technical skills and there are enough people around
>> who are willing to help you, when questions arise.
>>
>> Do you want to work on this? It is a big job, but you can learn a lot
>> from this.
>
> I'd like to work on this, any idea where to begin? should I start with
> grub legacy documentation and update/remove/add information to match
> that of grub2 or should I start from scratch?
You would have to start from scratch. GRUB 2 is a rewrite and
unrelated to GRUB Legacy. Only the style of the documentation should
be matched, nothing else. so the verbosity and quality.
--
Marco
prev parent reply other threads:[~2007-07-01 11:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-26 16:21 GRUB 2 documentation shirish
2007-06-26 17:24 ` Marco Gerards
2007-06-27 13:17 ` Khaled Hosny
2007-07-01 11:18 ` adrian15
2007-07-01 11:48 ` Marco Gerards [this message]
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=87sl88jqem.fsf@xs4all.nl \
--to=mgerards@xs4all.nl \
--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.