From: Franklin PIAT <fpiat@bigfoot.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Docs
Date: Mon, 11 Feb 2008 20:34:52 +0100 [thread overview]
Message-ID: <1202758492.6450.3.camel@solid.paris.klabs.be> (raw)
In-Reply-To: <20080131143410.GA18526@thorin>
Hi,
Have you made progress regarding the re-licensing of the current grub
manual under GFDL ? (with no cover text and no invariant ?)
Franklin
On Thu, 2008-01-31 at 15:34 +0100, Robert Millan wrote:
> On Thu, Jan 31, 2008 at 02:43:59PM +0100, Yoshinori K. Okuji wrote:
> > On Thursday 31 January 2008 13:50, Robert Millan wrote:
> > > On Thu, Jan 31, 2008 at 12:28:50PM +0100, Yoshinori K. Okuji wrote:
> > > > Anyway, the best way of using texinfo is to start from examples. In our
> > > > case, you can copy the manual from GRUB Legacy, and tweak it. FYI, Emacs
> > > > supports texinfo very well.
> > >
> > > If the manual from GRUB Legacy (or a derived version under the same
> > > license) is in GFDL with invariant sections or front/back cover texts, I
> > > won't be able to add this in the Debian package.
> > >
> > > Is there a way we can get around this? GFDL is fine as far as Debian is
> > > concerned, only invariant sections and front/back cover texts are a
> > > problem.
> >
> > The GRUB manual is licensed under the traditional "as-is" term. It was only
> > because GFDL hadn't been born yet when I wrote the manual, and I stopped
> > working on GRUB Legacy when the FSF urged me to change the license.
> >
> > As the manual is not so long, and the FSF hasn't published a paper version, we
> > can omit Invariant Sections. However, we must change the license to GFDL in
> > GRUB 2, anyway. You can see more info here:
> >
> > http://www.gnu.org/prep/maintain/html_node/License-Notices-for-Documentation.html
> >
> > If the FSF wants to print it out, I will not hesitate to add Invariant
> > Sections. Actually, there was a chance that a printed version would be
> > published, but it was not done, because I pointed out that it had some
> > incomplete chapters, so not tolerable for the payment, and I didn't make
> > effort on finishing them.
>
> We can continue to work together in documentation untill that happens. When it
> happens, I'll have to remove the docs in Debian, and will only add them back if
> someone forks the documentation (I don't have the motivation to do this myself,
> but maybe someone else will). This doesn't preclude that someone else adds them
> to the non-free repository, but again I don't have the motivation to do this
> myself.
>
> Please note that I don't necessarily agree with this policy; in fact I think
> both sides have been overzealous on this, but it is nevertheless the policy that
> I have to abide to.
>
> If you think we can avoid this situation by providing documentation as part
> of a non-GNU package (e.g. grub-doc), or just put it in the wiki, I'd welcome
> that.
>
next prev parent reply other threads:[~2008-02-11 19:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 8:46 Docs Franklin PIAT
2008-01-31 11:28 ` Docs Yoshinori K. Okuji
2008-01-31 12:50 ` Docs Robert Millan
2008-01-31 13:43 ` Docs Yoshinori K. Okuji
2008-01-31 14:34 ` Docs Robert Millan
2008-01-31 15:27 ` Docs Franklin PIAT
2008-02-11 19:34 ` Franklin PIAT [this message]
2008-02-18 22:08 ` Docs Franklin PIAT
2008-02-20 21:28 ` Docs Yoshinori K. Okuji
2008-02-24 15:16 ` Docs Robert Millan
2008-02-25 7:43 ` Docs Franklin PIAT
2008-02-26 22:34 ` Docs Yoshinori K. Okuji
2008-03-01 17:33 ` Docs Yoshinori K. Okuji
2008-03-03 7:24 ` Docs Franklin PIAT
2008-02-26 22:32 ` Docs Yoshinori K. Okuji
-- strict thread matches above, loose matches on Subject: below --
2013-03-22 12:37 docs Jerker Nyberg
2013-03-22 18:18 ` docs Dan Mick
2013-03-22 18:30 ` docs John Wilkins
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=1202758492.6450.3.camel@solid.paris.klabs.be \
--to=fpiat@bigfoot.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.