Re: menu-policy: education
On Sun, Jan 14, 2001 at 06:09:28PM -0800, email@example.com wrote:
> oh good greif. This reminds of that Dilbert strip:
> "Are you sure it's okay to jump right into a pre-meeting without
> "Okay, let's start this planning session for the pre-meeting" :-/
Yeah, I know that particular strip. Sorry, I wrote that on not nearly
enough sleep. It's much simpler than I put it:
1. old method: approach archive maintainer and they'll add a new section
if they think it's appropriate
2. new method: ??? there is no new method because the archive doesn't
have sections anymore
All I'm saying is since there's no new method, someone is gonna have to
*devise* a new method. I have been told that it should just be a matter
of adding a policy. This isn't just red tape, the policy document would
tell a developer "here are the sections you should add your package to,
and roughly what belongs in each" much as we now have a menu sub-policy.
You can't just "check the current release to see what sections are in it"
as the policy manual says, because if you look at the new package pools
arrangement, the sections simply are not there.
Is that clearer?
> Can't "whoever's in charge of the releases" just decide, "Hey, in the next
> release there will now be an Education section" ?
No. I have asked directly. It's not quite so simple as that. We *do*
need a policy.
nSLUG http://www.nslug.ns.ca firstname.lastname@example.org
Debian http://www.debian.org email@example.com
[ pgp key fingerprint = 7F DA 09 4B BA 2C 0D E0 1B B1 31 ED C6 A9 39 4F ]
[ gpg key fingerprint = 395C F3A4 35D3 D247 1387 2D9E 5A94 F3CA 0B27 13C8 ]