From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org,Michael Sterrett <mr_bones_@gentoo.org>
Cc: Daniel Campbell <zlg@gentoo.org>,comrel@gentoo.org
Subject: Re: [gentoo-dev] games.eclass policy
Date: Wed, 17 Feb 2016 11:42:12 +0100 [thread overview]
Message-ID: <68FA070A-985B-40DE-BBF2-7CAADE664F3C@gentoo.org> (raw)
In-Reply-To: <CA+rTEUNnh5p12pwrHYkhyt=+t61OnCPE9SFiTXnQKsmo0i=dsw@mail.gmail.com>
Dnia 17 lutego 2016 08:52:31 CET, Michael Sterrett <mr_bones_@gentoo.org> napisał(a):
>On Wed, Feb 17, 2016 at 2:39 AM, Michał Górny <mgorny@gentoo.org>
>wrote:
>
>> The games team was pretty much formed of two kinds of developers back
>then. One kind was retired developers, the other kind was developers
>who did what they cared about and ignored everything and everyone else.
>Bugs, join requests, complaints, all went ignored and games team kept
>silent claim to games in gentoo.
>
>False and slanderous.
>
>> So the first Council case against games team was that they did not
>accept any new members. Or rather, silently ignored join requests. They
>also ignored inquiries wrt the case and the Council.
>
>Also false.
>
>> The result was that the Council set up someone external to take care
>of inviting new members, and electing new team lead afterwards. As it
>could be predicted, nobody wanted to join, or rather be forced into the
>team they weren't welcome in.
>
>Speculative and false.
>
>> Then the case against policies started. The first abolished myth was
>games team sole claim to games in gentoo. Where Council pretty much
>only confirmed that they have no right for that and everyone can
>maintain game ebuilds without having games team approval or
>co-maintenance.
>
>Making things up.
>
>
>> During the whole process, I don't recall a single reply from games
>team member.
>
>Well, here's at least one.
>
>However, I'm not sure why anyone would reply to your drama, slander,
>and lies so I'm not surprised that's been your experience.
Nice to hear from you. Please don't expect me to write things I didn't know about.
So maybe games team did reply. To the people that were worthy replying to. Did this group include the Council or QA team?
As I see it, this only adds to your case. Ignoring messages is inappropriate at least. Ignoring them in order to stall others from doing their Gentoo work is more serious.
--
Best regards,
Michał Górny (by phone)
next prev parent reply other threads:[~2016-02-17 10:43 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 [this message]
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
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=68FA070A-985B-40DE-BBF2-7CAADE664F3C@gentoo.org \
--to=mgorny@gentoo.org \
--cc=comrel@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mr_bones_@gentoo.org \
--cc=zlg@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