From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1OV1u2-0005w2-QS for garchives@archives.gentoo.org; Sat, 03 Jul 2010 12:33:03 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B8259E0BBD; Sat, 3 Jul 2010 12:32:52 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 8DA55E0BBD for ; Sat, 3 Jul 2010 12:32:52 +0000 (UTC) Received: from [192.168.0.3] (e177090144.adsl.alicedsl.de [85.177.90.144]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPSA id B54361B40A5 for ; Sat, 3 Jul 2010 12:32:50 +0000 (UTC) Message-ID: <4C2F2DEF.6090609@gentoo.org> Date: Sat, 03 Jul 2010 14:32:47 +0200 From: Sebastian Pipping User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100419 Thunderbird/3.0.4 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org MIME-Version: 1.0 To: gentoo-project@lists.gentoo.org Subject: Re: [gentoo-project] Re: [gentoo-dev] The mis-concept of "slacking" in Gentoo References: <4C184B06.8040806@gentoo.org> <4C18FFE4.4080908@gentoo.org> <4C1909D4.7010703@gentoo.org> <4C1975F7.5010903@gentoo.org> <4C2A8BFF.5040400@gentoo.org> <4C2AB477.3050309@gentoo.org> <4C2DEEDB.8020100@gentoo.org> <4C2E83CC.3010905@gentoo.org> In-Reply-To: <4C2E83CC.3010905@gentoo.org> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit X-Archives-Salt: 4a57fbb4-8d7b-4ae1-bc64-2cb0042c5689 X-Archives-Hash: ba6f7999f3544b061fc765b0433c4d7c Jorge, On 07/03/10 02:26, Jorge Manuel B. S. Vicetto wrote: >> I wonder if we could start making a stronger distinction between these >> two cases of retirement. If it isn't a throw-out I would prefer to have >> that made so very clear that no one ever feels thrown out that way. >> Especially that there's no guarantee to be allowed to return feels a bit >> odd to me. > > please read the undertakers page and the resolution of the retirement > bugs carefully as you seem to be confused about our policy to retired > developers. Confused about what exactly? > The only case where re-admittance is subject to particular > scrutiny is when a developer is retired for disciplinary reasons. As you > can read in the second email template[1], we specifically inform the > developer that: > > "If we do retire you, it's pretty easy to come back when you are ready. > Just do the ebuild/end-quiz again and you're back on. You also always > have the option of contributing as your schedule allows via proxy or > bugzilla." > > We also make sure to mention in the retirement bugs that a developer can > always return as seen on an example bug[2]. My apologies to Caleb to > link directly to his bug, but I needed one concrete reply to show > undertakers work. Agreed, it could be worse. I would personally not trust on "you can come back any time" though and looking forward to another round of ebuild quizzes doesn't sound inviting to me either (not saying that developers don't need to be up to date with Gentoo). I'm not sure if I'm really the most or only sensitive person in Gentoo if that's coming to your mind now. Let me quote an excerpt by another developer. When I stumbled upon his inactivity-based retirement bug I was asking if he really means to retire. He said: "If Gentoo likes to retire me, fine. I won't stop them. I don't think, this will will help Gentoo get back on track, though, if there is a way back at all." So I don't seem to be the only one having a bad impression of our current concepts of retirement. Do you read it differently? Before I propose anything: What ways do you see to improve our concept and realization of retirement? Best, Sebastian