|
Home > Archive > Debian Developers > April 2004 > Proposal - Constitutional Amendment: Associate Foundation Documents to Releases
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Proposal - Constitutional Amendment: Associate Foundation Documents to Releases
|
|
| Chad Walstrom 2004-04-30, 6:42 pm |
| [This is a counter proposal to Manoj's I originally posted on
debian-vote. I've substituted "Published" with "Ratified" and removed
"versions".]
I propose to add the following to the Constitution:
§ 5.1.4. Ratified versions of Foundation Documents shall be formally
associated to specific releases of the Debian system.
Rational
========
The Foundation Documents were a good idea. Because Foundation Documents
represent portions of Policy, applying specific versions of Foundation
Documents with specific Releases of Debian is perfectly acceptable. An
additional Foundation Document isn't necessary to describe this process.
Although the Foundation Documents themselves are not technical
declarations of policy, they may affect Debian both technically and
infrastructionally. This change to the Constitution focuses the affects
of changes to the Foundation Documents to specific releases of the
Debian system, allowing a flexible and targetable approach to
implementing new policy.
I haven't specified HOW versions of the Foundation Documents are
associated to releases. This leaves the implementation details out of
the Constitution, as it should be.
--
Chad Walstrom <chewie@wookimus.net> http://www.wookimus.net/
assert(expired(knowledge)); /* core dump */
| |
| Raul Miller 2004-04-30, 7:34 pm |
| On Fri, Apr 30, 2004 at 05:17:46PM -0500, Chad Walstrom wrote:
> I propose to add the following to the Constitution:
>
> § 5.1.4. Ratified versions of Foundation Documents shall be formally
> associated to specific releases of the Debian system.
This seems to me to be incomplete.
What's a specific release?
Ok, sure, we know what a specific release is today. But how about after
the next major change of the release system?
Does this proposal cause any problems for us if we move to a release
system which doesn't have specific releases?
What does this proposal have to say about "minor releases" which follow a
"major release"?
What does this mean for the existing foundation documents? Do they
"go away" after the current specific release? If so, that's almost
[but not quite] the opposite of what we need for the most recent social
contract amendment.
Thanks,
--
Raul
--
To UNSUBSCRIBE, email to debian-vote-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
|
|
|
|
|