Lennart Poettering píše v St 15. 12. 2010 v 06:59 +0100:
On Tue, 14.12.10 13:53, Miloslav Trmač (mitr@volny.cz) wrote:
Changing the semantics of /etc/fstab without any consultation with fedora-devel or even notification of Fedora that something so long-standing is changing is hardly constructive either.
I can happily live with "systemd is a new, better init system" without knowing the details. I consider "systemd replaces 15% of /etc and changes semantics of another 5%" without discussing the details in advance unacceptable for the distribution as a whole, although this decision is of course FESCo's.
All these things are actually discussed very much on IRC, and systemd upstream mailing lists and similar places.
That's not what I was talking about. My point is that systemd is an "unbounded" project - looking at a system feature, I don't know whether it is in scope or out of scope to be rewritten by systemd.
From the Fedora feature page: "systemd is a replacement for SysVinit and
Upstart that acts as a system and session manager.". Based on this description, who would expect systemd to: * obsolete "crontabs" package * add yet another file identifying the distribution to /etc * introduce a new mechanism for setting the default system locale, keyboard and font layout * manage temporary directories?
It seems that "systemd is a project to replace existing distribution-specific infrastructure by a new, different infrastructure, with sometimes different defaults and mostly different primary configuration files" would be a more fitting description - but it leaves me guessing about the scope as well.
Or, to turn this around: if you want to have a say, if you want to influence systemd's design, then join devlopment upstream, or otherwise become involved.
I don't think reviewing each commit and saying "find the subject matter experts and get their sign-off before releasing this" about 10% of them, which is all I really want to say, can really count as a contribution. (Given the unbounded scope of systemd, the burden of identifying and involving the subject matter experts is necessarily on the systemd project because others can't _know_ they should be involved.) Mirek