From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-66565-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id 0E8FF13877A
for <garchives@archives.gentoo.org>; Wed, 9 Jul 2014 17:48:29 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 9D264E08AA;
Wed, 9 Jul 2014 17:48:23 +0000 (UTC)
Received: from mail-vc0-f181.google.com (mail-vc0-f181.google.com [209.85.220.181])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id A8F0CE083E
for <gentoo-dev@lists.gentoo.org>; Wed, 9 Jul 2014 17:48:22 +0000 (UTC)
Received: by mail-vc0-f181.google.com with SMTP id il7so7751685vcb.12
for <gentoo-dev@lists.gentoo.org>; Wed, 09 Jul 2014 10:48:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=mime-version:sender:in-reply-to:references:date:message-id:subject
:from:to:content-type:content-transfer-encoding;
bh=bImLVlSduGLy2rBakK6lzSMO2E9DF+an36J6XYkLN+g=;
b=R+yOQKOjE6F/OtkGy6F5JzuraCEheCv5YRpawnvv34J5sgl7KUiiNso9WN3AX/Im0g
XPw6pFRyeutuupNBrJSz4Vouebe5EGZdUgdobxDQnCxzvJ9Ax8FaAgfmaAvlfu9SRQZl
qCoN1ZJRQ38pwHeQ8F9V46UcaXlSyZQpscuCMxcIptpDHTFFMEBIPiqwJXXQc7P9s2x1
09+lcZnh+jNZwzX0LMpPnBsv232iB+Ms8Njv5KZmqNHaOFCSV3Agm+O+lbPDvf0qglBV
G1cvadIms72HJ5O6gvHVtwfbPbpcFGoOwTvN1MNACopa+rdW/yMQzpL7AJ+kqn3EHxTk
vBUA==
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
X-Received: by 10.58.29.16 with SMTP id f16mr42045983veh.23.1404928101902;
Wed, 09 Jul 2014 10:48:21 -0700 (PDT)
Sender: freemanrich@gmail.com
Received: by 10.52.72.19 with HTTP; Wed, 9 Jul 2014 10:48:21 -0700 (PDT)
In-Reply-To: <53BD5FA4.8060106@gentoo.org>
References: <20140707234502.3009929a@pomiot.lan>
<lpgii1$kik$1@ger.gmane.org>
<20140708133859.3bc01349@pomiot.lan>
<CAGfcS_mO_G6oDdo2ZuF8kvJUmp7WvxNbi2dbzje4FcdtA5vPtQ@mail.gmail.com>
<CAB_KkxxndmYZij27cv-yhh45or4KKJzN4o=xXYseFf1cDYBNaQ@mail.gmail.com>
<53BC0CCA.4000702@gentoo.org>
<53BC273C.6070602@gentoo.org>
<1404846619.828.1.camel@localhost>
<53BC7A09.6020505@gentoo.org>
<53BD5FA4.8060106@gentoo.org>
Date: Wed, 9 Jul 2014 13:48:21 -0400
X-Google-Sender-Auth: ZfV561NIiF3fjvvqGYpCelqx5WA
Message-ID: <CAGfcS_kikyzRb_oFkJb9J1_DxiLoYGjTzzU3e_ON=MRNUXO3gg@mail.gmail.com>
Subject: Re: [gentoo-dev] Re: The request to abolish games team policy
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: b67ae496-31a7-494f-9b16-1c79a323f8f7
X-Archives-Hash: 20d62716d8c36f392457fe3cffb60a10
On Wed, Jul 9, 2014 at 11:28 AM, Sergey Popov <pinkbyte@gentoo.org> wrote:
> But, honesly, i can not see problem in this. We have similar problem in
> ARM team, which was fixed by electing new leads by those, who really did
> most of ARM stuff AND actively responds on e-mails.
Doing this and giving the games team a chance to set its own destiny
seems like a reasonable first step. This should include their
considering Micha=C5=82's proposals and reacting. Then the community can
gauge whether intervention "from above" is still needed.
Does anybody want to step up as somebody who wants to join the team
and be the point of contact for anybody else who wants to join in
(basically an interim lead only for the purpose of organizing a
meeting and electing a lead including of course all existing team
members)? Devs can probably add themselves to the alias already, and
if non-devs want to participate they can reach out to the coordinator
to be added.
If anybody has an objection to the influx then somebody can deal with
that (new council if worst comes to worst), but otherwise this should
give the team a shot in the arm.
I think it is best to just look forward, of course accepting input
from what was done in the past so as to learn from it.
Just my personal suggestion, but unless somebody really objects I
don't think it needs anybody's blessing. By all means speak up if you
think it is a terrible idea.
Rich