public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Rick \"Zero_Chaos\" Farina" <zerochaos@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Going against co-maintainer's wishes (ref. bug 412697)
Date: Sun, 26 May 2013 12:15:46 -0400	[thread overview]
Message-ID: <51A23532.8030806@gentoo.org> (raw)
In-Reply-To: <CAB9SyzRsRUUGippNqOXXwDDiv2nx3WTm5ySuvk5_GpsBnQadgw@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/26/2013 11:21 AM, Ben de Groot wrote:
> On 26 May 2013 18:04, Rich Freeman <rich0@gentoo.org> wrote:
>> On Sun, May 26, 2013 at 3:43 AM, Michał Górny <mgorny@gentoo.org> wrote:
>>> On Sun, 26 May 2013 15:23:44 +0800
>>> Ben de Groot <yngwin@gentoo.org> wrote:
>>>>
>>>> Where is this policy documented?
>>>
>>> Nowhere, I think. I've seen it coming in the late thread, looked common
>>> sense enough to me.
>>>
>>> If it is to be documented, I think we should document it in a more
>>> general fashion. To cover all stuff like completions, logrotate and so
>>> on.
>>>
>>
>> As others have already pointed out, we are an organization, not a CPU.
>>  We can't make EVERYTHING a rule, and devs should act in a cooperative
>> manner so that this remains the case.
>>
>> Sure, this can be made into a policy, and if things get out of hand
>> I'm sure it will be.  I'm not quite sure I see the need yet, as we
>> don't have an example yet of a maintainer not cooperating with the
>> systemd team on the installation of init files (in the present example
>> Ben isn't actually a maintainer, since he stepped down).
> 
> In packages I maintain, I will not be adding any systemd related files.
> All bug reports requesting such additions will be closed as an upstream
> matter.
> 
>> If Ben wants to boycott systemd by not maintaining any packages that
>> support it, that is his choice.  I just suspect that the end result of
>> that will be that he'll end up not maintaining much of anything.  I'd
>> hate to see that happen, as it would be a loss for Gentoo.  But,
>> frankly, letting any one person dictate the direction of the entire
>> distro by essentially threatening to quit would be worse.
> 
> Gentoo is evolving in directions I do not agree with. I am feeling less
> and less at home here. More and more often it seems I am the
> minority voice of protest. I am not enjoying this role, and increasingly
> the thought arises that I should just get out of people's way and
> find another place that is closer to my ideas of what a distro
> should be.
> 
>> Gentoo is about choice - and the nature of choice is that most of the
>> choices it supports are ones that you wouldn't personally make.  We do
>> a reasonably good job letting everybody have their cake and eat it
>> too.  However, it really isn't an appropriate distro for absolute
>> purists of almost any kind - it reeks of compromise.  We package
>> proprietary software (we don't redistribute the copyrighted parts), we
>> more-or-less run on Windows/OSX, we support that X32 alternate
>> architecture that some believe has no useful purpose, and so on.
>>
>> If you really want to influence the battle of the init
>> implementations, then write code, not emails.
> 
> I am not a programmer, I am a simple package maintainer.
> 
>> Maybe that is a wrapper
>> that allows OpenRC to support systemd units.  Maybe that is more
>> functionality for OpenRC.  Maybe it is something else.  However,
>> trying to influence things by just spitting into the wind isn't going
>> to do much but get your face dirty. Sure, devs can quit, but that
>> isn't just a loss for Gentoo.  Frankly if your main goal in life is to
>> avoid systemd then you're better off supporting Gentoo which is likely
>> to support that option nearly forever far better than any other
>> distro.
> 
> If forcing Gentoo package maintainers to add systemd support
> to packages they maintain is your idea of the best option to
> avoid systemd, then I respectfully disagree.

Perhaps this was covered already, but how exactly did this one file,
added by your co-maintainer, hurt you?  Did it cause additional bugs?
Did it break a working ebuild?  Did it kill your cat?

It would seem to me that the co-maintainer (a person who cares that some
users are interested in systemd enough to add one file to the package)
made the package support a slightly wider range of systems (gentoo is
about choice) and this affects you in exactly no way.

What am I missing here?  Are you just trying to force your will on
others or do you have an actual issue caused by this commit?  It is not
for us developers to force one way on the users, gentoo is supposed to
be about choice, your co-maintainer chose to support systemd, an action
which as far as I can see didn't harm you, and helped some users.  This
has been a very long thread for something I don't get at all.  Please,
seriously, what am I missing here?

- -Zero
> 
> Obviously I have better (and more fun) things to do.
> --
> Cheers,
> 
> Ben | yngwin
> Gentoo developer
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRojUxAAoJEKXdFCfdEflKNXUQAJufMr9HC/7KPLQEWxZG+LH0
kWzrzSjH9I5OLNhTxuVs3IuMupeHL2BPA2oXZV/hj/NKhJid8FXKlNRB9PCuE6qq
ClrnSLuYcdabTNzUmePM+h0CEU5FMkA4Z3GJiT2GtB9fv8CbnjcbuqZAYK4zYupT
B8O61/o/uYCYPEgekqi/vU3xOtPA+wzzwXILV4Kf/YNb9A/z/SyIIsJv4JN2qvSm
UYCe5Q4h7JqUTz0DzL3lVFLhTFdvCWPErP5Okrn1yk8cCL5878ixDkQBm5dL53NH
NNu3EPPhvnljV6Ja1CEAOKmORp2Ry+DDSbYUhx0SK0g/fzo4JQP1TD/IraicQExV
2nFBQL3MKT9It5uzZp0+PsNkfAZMmv2W7Xkx1YNQcj5Zjip5ChdQJqk60uqBUoGs
aenj1CYucki3owKnE4mwb/2Vk6jlZ51uEuJ29GuzYxHXVaonBo1JQNFVw9foDKqV
XQISK7U9HVFD80uH6Gj6bhlWF/CCzw2rX5C1WnGsGr/rk0T87cECS79gPqp2wuA7
gI9amGaK3RaHbYoUqobGSKBH8lY6HQwtF2XHzOILMm39gacVGV6vM4E0m77Ia0Zd
Oze9UfnFMj81qxBCmIyN/YI3BEckc5pMuI/GmW9eW/9EWkIgOI9RPafED492+/GJ
kKbF8ogtV3E3SiTfN22q
=chEY
-----END PGP SIGNATURE-----


  reply	other threads:[~2013-05-26 16:15 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-25 16:14 [gentoo-dev] Going against co-maintainer's wishes (ref. bug 412697) Ben de Groot
2013-05-25 16:48 ` Michał Górny
2013-05-25 17:38   ` Rich Freeman
2013-05-25 20:02     ` Chí-Thanh Christopher Nguyễn
2013-05-25 20:40       ` Rich Freeman
2013-05-25 20:45       ` Michał Górny
2013-05-25 21:38   ` Luca Barbato
2013-05-26  7:23   ` Ben de Groot
2013-05-26  7:43     ` Michał Górny
2013-05-26 10:04       ` Rich Freeman
2013-05-26 15:21         ` Ben de Groot
2013-05-26 16:15           ` Rick "Zero_Chaos" Farina [this message]
2013-05-26 17:14             ` Matt Turner
2013-05-26 17:19             ` Andreas K. Huettel
2013-05-26  7:54     ` Pacho Ramos
2013-05-25 17:00 ` Pacho Ramos
2013-05-25 17:14   ` Carlos Silva
2013-05-26  7:15   ` Ben de Groot
2013-05-26  7:44     ` Pacho Ramos
2013-05-26  7:45     ` Michał Górny
2013-05-26  9:59       ` Luca Barbato
2013-05-25 18:13 ` Markos Chandras
2013-05-25 19:53   ` Anthony G. Basile
2013-05-25 19:58     ` Mike Gilbert
2013-05-25 21:55       ` Anthony G. Basile
2013-05-25 19:59     ` Rich Freeman
2013-05-26  7:00     ` Michał Górny
2013-05-26  7:22     ` Tiziano Müller
2013-05-26  7:46       ` Pacho Ramos
2013-05-26  7:49       ` Michał Górny
2013-05-26  7:00   ` Ben de Groot
2013-05-26  7:37 ` [gentoo-dev] Reusing systemd unit file format / forking systemd (was: Going against co-maintainer's wishes (ref. bug 412697)) Michał Górny
2013-05-26  8:32   ` Ben de Groot
2013-05-26  9:49     ` Rich Freeman
2013-05-26 10:12       ` Robert David
2013-05-26 10:31         ` Michał Górny
2013-05-26 11:12           ` Rich Freeman
2013-05-26 11:31           ` Robert David
2013-05-26 11:47             ` [gentoo-dev] Reusing systemd unit file format / forking systemd Luca Barbato
2013-05-26 10:23   ` Luca Barbato
2013-05-26 11:15     ` Michał Górny
2013-05-26 11:59       ` Luca Barbato
2013-05-26 13:35         ` Sergei Trofimovich
2013-05-26 14:22           ` Luca Barbato
     [not found] <51A1A294.3000609@sporkbox.us>
2013-05-26  6:24 ` Re: [gentoo-dev] Going against co-maintainer's wishes (ref. bug 412697) Daniel Campbell
2013-05-26  6:55   ` Michał Górny
2013-05-26  7:37     ` Daniel Campbell
2013-05-26  7:56     ` Pacho Ramos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51A23532.8030806@gentoo.org \
    --to=zerochaos@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox