On Wed, May 15, 2013 at 2:11 PM, Tom Wijsman <tom...@gentoo.org> wrote: > On Wed, 15 May 2013 13:25:11 -0400 > Rich Freeman <ri...@gentoo.org> wrote: > >> In any case, there really isn't any "decision" to make here. > > Then for what purpose is this discussion still going on? >
No comment on that... Maybe another way of saying things is that really the onus is on those who want others to change their behavior to explain why they should change. So, if you're seeking a change in behavior be up-front about what change you want. If you're not seeking a change in behavior, then there really isn't much point in going on unless it is to resist a proposed change. Personally I think a reasonable balance is: 1. Maintainers do not have to take initiative to create systemd units. (status quo) 2. Maintainers should accept contributed units from the community, even if they can't personally test them. This can be done at their convenience. (slight addition in work for maintainers) 3. Maintainers can ask users to contribute units upstream if not already done. I don't think this should be a hard requirement (ie accepting a non-upstreamed unit is not a QA violation). If upstream makes this difficult this should not be an excuse for marking bugs invalid. The goal is to work with upstream, not harass them. (some more work for bug submitters and maintainers). Bottom line - maintainers don't have to go out of their way to support systemd, but they should be friendly facilitators when others are willing to do the work. This is no different from accepting desktop entries and such even if you don't use a Freedesktop-compatible environment. Rich
