Re: Proposal - preserve freedom of choice of init systems
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi,
I second the general resolution proposal below:
Kind regards, Thibaut.
Le 01/03/2014 00:45, Matthew Vernon a écrit :
> Hi,
>
> I wish to propose the following general resolution, and hereby
> call for seconds. I don't think further lengthy discussion of the
> issues is likely to be productive, and therefore hope we can bring
> this swiftly to a vote so that the project can state its mind on
> this important issue. The substantive text is that which was
> drafted for the purposes of the technical committee's vote (where
> they decided not to pass a resolution on the subject).
>
> Regards,
>
> Matthew
>
> ** Begin Proposal **
>
> 0. Rationale
>
> Debian has decided (via the technical committee) to change its
> default init system for the next release. The technical committee
> decided not to decide about the question of "coupling" i.e.
> whether other packages in Debian may depend on a particular init
> system.
>
> This GR seeks to preserve the freedom of our users now to select
> an init system of their choice, and the project's freedom to select
> a different init system in the future. It will avoid Debian
> becoming accidentally locked in to a particular init system (for
> example, because so much unrelated software has ended up depending
> on a particular init system that the burden of effort required to
> change init system becomes too great). A number of init systems
> exist, and it is clear that there is not yet broad consensus as to
> what the best init system might look like.
>
> This GR does not make any comment on the relative merits of
> different init systems; the technical committee has decided upon
> the default init system for Linux for jessie.
>
> 1. Exercise of the TC's power to set policy
>
> For jessie and later releases, the TC's power to set technical
> policy (Constitution 6.1.1) is exercised as follows:
>
> 2. Loose coupling of init systems
>
> In general, software may not require a specific init system to be
> pid 1. The exceptions to this are as follows:
>
> * alternative init system implementations * special-use packages
> such as managers for init systems * cooperating groups of packages
> intended for use with specific init systems
>
> provided that these are not themselves required by other software
> whose main purpose is not the operation of a specific init system.
>
> Degraded operation with some init systems is tolerable, so long as
> the degradation is no worse than what the Debian project would
> consider a tolerable (non-RC) bug even if it were affecting all
> users. So the lack of support for a particular init system does
> not excuse a bug nor reduce its severity; but conversely, nor is a
> bug more serious simply because it is an incompatibility of some
> software with some init system(s).
>
> Maintainers are encouraged to accept technically sound patches to
> enable improved interoperation with various init systems.
>
> 3. Notes and rubric
>
> This resolution is a Position Statement about Issues of the Day
> (Constitution 4.1.5), triggering the General Resolution override
> clause in the TC's resolution of the 11th of February.
>
> The TC's decision on the default init system for Linux in jessie
> stands undisturbed.
>
> However, the TC resolution is altered to add the additional text in
> sections (1) and (2) above.
>
> ** End Proposal **
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iQIcBAEBCAAGBQJTHX6NAAoJEJOUU0jg3ChA3e8QANd2EpYpVNWBbKN7lzW0oQgD
h8l5zdChw8bUuowWQd3STjEbAwxgjxA0UHtZ0zeHFMI9vfZlzAg7UMAF9+mJ5Wbx
I3eif/MCYJlPCLJPNwKAQX94z+mbmm+r9dMSk1hpx5OQzdSZ+IqBZpAtGwYRhDxT
HXgTh/5cTPiFv8dxYbeiDaAjF00HY7BztfMztOx0LPXmW4mYK01c1mAJPe70d+cv
zwRSkKmtJMF0B9Y+D7AEGkBdSpEQmu6JkD8/XbK3326Y/l+E0DdGe4JqgyCrLYI3
x8tCG68c9R5cvTY6Dv6fyLZJVMkRGnHdrK0VsdocAlAgF81dmfX/rI+oL8QnfcoK
kQwhHIkSrR03OJ/SGDvDiH1rmVx42Dz9I1OQlg/Ho28SKQeeQoiJmZvJpZgfpe5V
1JdRe8d07cwfJKrdP6hLtVMjm063ROyW8/H7GnDMy4hO0FI9N7EYgKPyL2HUOza/
+aMu5baNQUueXsYvX9LlW88RmuRAciEmQCAnxyPMQS7LJfQLm5+DMzG/DkOjdAzM
I6VoTug4wg+/5JTGz0icCuKscc9FEdZ546J8nQpj0g88v8ByvQBs8wH1q8jUL80U
mQyqh/fphsjMSDJ74lhWEme8TDbzLv3/9BoycdbqZ5USJPWyqbC1AigsemST7nnn
mRjPHMW7+jQhCWf0Ya+j
=W4+2
-----END PGP SIGNATURE-----
Reply to: