I hereby propose the L versions from git:
== dependencies rider version L (Loose coupling) ==
Software outside of an init system's implementation may not require
a specific init system to be pid 1, although degraded operation is
tolerable.
Maintainers are encouraged to accept technically sound patches
to enable improved interoperation with various init systems.
as amendments to my own formal proposal, and do not accept them.
I hereby call for votes on my own formal proposal.
Ian.
Options on the ballot:
DT systemd default in jessie, requiring specific init is allowed
DL systemd default in jessie, requiring specific init NOT allowed
UT upstart default in jessie, requiring specific init is allowed
UL upstart default in jessie, requiring specific init NOT allowed
OT openrc default in jessie, requiring specific init is allowed
OL openrc default in jessie, requiring specific init NOT allowed
VT sysvinit default in jessie, requiring specific init is allowed
VL sysvinit default in jessie, requiring specific init NOT allowed
GR project should decide via GR
FD further discussion
== introduction (all versions except GR) ==
We exercise our power to decide in cases of overlapping
jurisdiction (6.1.2):
== version D (systemD) ==
The default init system for Linux architectures in jessie should
be systemd.
== version U (Upstart) ==
The default init system for Linux architectures in jessie should
be upstart.
== version O (Openrc) ==
The default init system for Linux architectures in jessie should
be openrc.
== version V (sysVinit) ==
The default init system for Linux architectures in jessie should
be sysvinit (no change).
== version GR (General Resolution) ==
The Technical Committee requests that the project decide the
default init system for jessie by means of General Resolution.
(This is advice, pursuant to Constitution 6.1.5.)
== clarification text for all versions except GR ==
This decision is limited to selecting a default initsystem for
jessie. We expect that Debian will continue to support multiple
init systems for the foreseeable future; we continue to welcome
contributions of support for all init systems.
Therefore, for jessie and later releases, we exercise our power to
set technical policy (Constitution 6.1.1):
== dependencies rider version T (Tight coupling) ==
Software may require a specific init system to be pid 1.
However, where feasible, software should interoperate with
all init systems; maintainers are encouraged to accept
technically sound patches to enable interoperation, even if it
results in degraded operation while running under the init system
the patch enables interoperation with.
== dependencies rider version L (Loose coupling) ==
Software outside of an init system's implementation may not require
a specific init system to be pid 1, although degraded operation is
tolerable.
Maintainers are encouraged to accept technically sound patches
to enable improved interoperation with various init systems.
== rider for all versions except GR ==
If the project passes (before the release of jessie) by a General
Resolution, a "position statement about issues of the day", on the
subject of init systems, the views expressed in that position
statement entirely replace the substance of this TC resolution; the
TC hereby adopts any such position statement as its own decision.
Such a position statement could, for example, use these words:
The Project requests (as a position statement under s4.1.5 of the
Constitution) that the TC reconsider, and requests that the TC
would instead decide as follows:
--
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
