public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: Denis Dupeyron <calchan@gentoo.org>
Cc: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] games.eclass policy
Date: Thu, 18 Feb 2016 08:08:48 +0100	[thread overview]
Message-ID: <20160218080848.2ec2dc21.mgorny@gentoo.org> (raw)
In-Reply-To: <CA+CSuALXtJ6-3VwnazBK3P64KMnce_aP2dWuBZ8A_9NG_5j+Jw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2829 bytes --]

On Wed, 17 Feb 2016 18:06:29 -0700
Denis Dupeyron <calchan@gentoo.org> wrote:

> On Wed, Feb 17, 2016 at 11:38 AM, Michał Górny <mgorny@gentoo.org> wrote:
> >
> > Well, maybe it's because you can talk to Python team, discuss and not
> > get ignored by them.  
> 
> We've already established the same is true for the games team. I'm a living
> example of it and I can't imagine I'm the only one.

Good for you. So... ignoring majority is fine as long as you can prove
that they don't ignore one of their old fellows. Good.

> > Unlike games team members who believe it's best to
> > ignore certain developers.  
> 
> I certainly hope we can still ignore abrasive developers since it's been
> proven many times that it's the best way to deal with them.
> 
> So, you don't answer my question. Or rather, you answer with a specious
> statement. Since you're being unusually shy I will say what you're trying
> hard not so say. There are actually first-class projects catered for by
> first-class developers, and those can set rules like the mandatory use of
> an eclass and actually enforce them. Then there are second-class projects
> and developers who can do the same as long as it doesn't bother the
> first-class people. Second-class developers, often working quietly and
> steadily, not wasting their time on mailing-lists like I just did, can see
> their projects trampled over at any time for the mere reason that they were
> trying to keep their business in order, just like first-class developers do.

Now you are trivializing the problem. I wasn't talking about mailing
lists. I was talking about explicit questions, requests, pings. Mail,
IRC, Bugzilla.

If you get bug from the Council asking you what to do... don't you
think it would be fair to reply? Of course, you could say 'mgorny
opened the bug, I'm going to ignore him'. But the fact is, this is
not some kind of 'quiet, steady work'.

This is an explicit attempt of ignoring everyone with differing opinion
by delaying things. Sure, you can disagree. But it's different to
discuss disagreements and reach a consensus. And it's different if you
silently ignore disagreeing opinions and make them wait months for
a single reply, hoping to stall them from having any effect whatsoever.

When was the last time games project got a new member? Where is that
'premiere Linux gaming platform'? What about all these users? Why were
we exposing security issues for almost 10 years?

So we're the bad ones in your opinion, troubling the little closed
team. We want to have some influence, bad us. We should just keep quiet
and let us be ordered. Stand out of the line -- and you're a problem,
you're abrasive developer, you should be ignored.

-- 
Best regards,
Michał Górny
<http://dev.gentoo.org/~mgorny/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 949 bytes --]

  reply	other threads:[~2016-02-18  7:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-07 10:38 [gentoo-dev] games.eclass policy M.B.
2016-02-07 10:43 ` Patrice Clement
2016-02-07 11:09 ` Michał Górny
2016-02-07 12:13   ` Daniel Campbell
2016-02-08 21:49     ` Michał Górny
2016-02-17  2:09       ` Daniel Campbell
2016-02-17  7:39         ` Michał Górny
2016-02-17  7:52           ` Michael Sterrett
2016-02-17 10:42             ` Michał Górny
2016-02-17 15:32           ` Denis Dupeyron
2016-02-17 16:22             ` Michał Górny
2016-02-17 17:19               ` Denis Dupeyron
2016-02-17 17:33                 ` Michał Górny
2016-02-17 18:08                   ` Denis Dupeyron
2016-02-17 18:38                     ` Michał Górny
2016-02-18  1:06                       ` Denis Dupeyron
2016-02-18  7:08                         ` Michał Górny [this message]
2016-02-20  1:25                           ` [gentoo-dev] " Ryan Hill
2016-02-20 17:13                             ` Andreas K. Hüttel
2016-02-22 13:20                               ` Alexander Berntsen
2016-02-23 16:42             ` [gentoo-dev] " Vadim A. Misbakh-Soloviov
2016-02-10  2:49     ` Ian Delaney

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=20160218080848.2ec2dc21.mgorny@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=calchan@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