[Fwd: Re: Release Update: freeze guidelines, testing, BSP, rc bug fixes]

[Franklin PIAT <fpiat@bigfoot.com>]

Hello,

Regarding the wiki page NewInLenny[1] and the possibility to reuse it's
content in the Release Notes, I'm wondering what's the actual license
that apply to the R.N ?

We would have two option to migrate the wiki page license :
1. Ask each contributor to re-license his contribution under license X.
2. Use Vincent's idea, described below, and use
   [Include(NewInLenny-oldlicense)] to include the old page in the new
   one (so it remains visible). and content can be move from one page
   to the other by it's author

I am quite interested in the first scheme, as it would be a trial for we
can do for the whole wiki.

Franklin

[1] http://wiki.debian.org/NewInLenny

-------- Forwarded Message --------
> From: Vincent Danjean <vdanjean.ml@free.fr>
> Cc: Debian Developers <debian-devel@lists.debian.org>
> Franklin PIAT wrote:
> > On Mon, 2008-09-01 at 11:46 -0700, Daniel Burrows wrote:
> >> On Mon, Sep 01, 2008 at 08:01:29AM +0200, Luk Claes <luk@debian.org> was heard to say:
> >>> Release notes
> >>> ~~~~~~~~~~~~~
> >>> There is still quite a lot of work to be done on the lenny release notes.
> >>> Coordination for this will happen on the debian-doc@lists.debian.org
> >>> mailing list (further information to appear in a mail to that list). If
> >>> you know of any issues that need to be documented, file them as bugs
> >>> against the ``release-notes'' pseudo package.
> >>   Do you know where I can find the current version of the release notes?
> >> I don't want to file bugs asking for documentation of things that are
> >> already documented.
> > 
> >>  Or is the NewInLenny page the staging ground for the release notes?
> > 
> > Due to license incompatibility, the content of the NewInLenny wiki page
> > can't be copied to the release notes.
> 
> Cannot you rename NewInLenny to NewInLenny-oldlicense and recreate a
> NewInLenny page (with a link to NewInLenny-oldlicense ?)
>   The new NewInLenny page would have a licence compatible with the
> release notes and can be fed up with the content of the current release
> notes...
> 
> > So if you write some text, then you should also send a mail to the
> > release-notes maintainers (We won't repeat that mistake for Squeeze).
> > 
> > Franklin
> 
>   Vincent