From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id E9295138A1F for ; Mon, 4 Aug 2014 22:01:41 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4FB1AE0929; Mon, 4 Aug 2014 22:01:36 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 70048E08C6 for ; Mon, 4 Aug 2014 22:01:35 +0000 (UTC) Received: from [192.168.3.7] (cpe-74-77-145-97.buffalo.res.rr.com [74.77.145.97]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: blueness) by smtp.gentoo.org (Postfix) with ESMTPSA id 5321E340055; Mon, 4 Aug 2014 22:01:34 +0000 (UTC) Message-ID: <53E00322.20101@gentoo.org> Date: Mon, 04 Aug 2014 18:03:14 -0400 From: "Anthony G. Basile" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org, ppc , ppc64 Subject: [gentoo-dev] Status of ppc and ppc64 teams. Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 75edca47-6f5f-4600-879d-ba01ccc0b997 X-Archives-Hash: 3251c64e6e81b41eb5cf4348f6bf3ea8 Hi everyone, The ppc and ppc64 team members just had a meeting. One of our main issues was reconstituting those teams because they were in a state of disorganization. We've come up with a plan to move forward and address Pacho's original concern about ppc/ppc64 falling behind. Here's what we came up with: 1. We elected jmorgan as the lead for both ppc and ppc64. He's our point person for any ppc/ppc64 related issues. 2. If you are interested in helping out, whether you are a current team member or not, please speak up! There are people formally listed as part of the ppc/ppc64 herds, but there's so much inactivity, we'd like to know who's going to be active. Of course we understand there is this thing called "real life" but there is a difference between a little help and no involvement at all. We are considering culling the team members accordingly. (/me hides!) 3. We are going to try to keep ppc and ppc64 going as it has been, with the usual STABLEREQ and KEYWORDREQ. We think we can do it without overloading ourselves, especially if we get help. We do have a shared ppc64 system. The bigger problem is actually KEYWORDREQ's so we are going to request maintainers not ever drop ~ppc or ~ppc64 even when they feel a major bump has occurred, eg a deep rewrite to a library. We know this is living dangerously but we'll going to make use of the community in this regard --- either someone will bug us on a broken ~ppc/~ppc64 package, or we'll catch it at stabilization. We'll try to move ppc/ppc64 chatter to those lists, but it was important that everyone know where we're at. -- Anthony G. Basile, Ph.D. Gentoo Linux Developer [Hardened] E-Mail : blueness@gentoo.org GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA GnuPG ID : F52D4BBA