From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: ppc <ppc@gentoo.org>, ppc64 <ppc64@gentoo.org>
Subject: Re: [gentoo-dev] Status of ppc and ppc64 teams.
Date: Sat, 16 Aug 2014 11:32:18 +0200 [thread overview]
Message-ID: <1408181538.14509.1.camel@gentoo.org> (raw)
In-Reply-To: <53E00322.20101@gentoo.org>
El lun, 04-08-2014 a las 18:03 -0400, Anthony G. Basile escribió:
> 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.
>
Then, you will finally try to keep current stable tree as big as
current :/? (I am referring only to stable tree, not about dropping
keywording entirely that wasn't ever the plan)
next prev parent reply other threads:[~2014-08-16 9:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 22:03 [gentoo-dev] Status of ppc and ppc64 teams Anthony G. Basile
2014-08-04 22:04 ` [gentoo-dev] " Tony Vroon
2014-08-05 6:56 ` [gentoo-dev] " "Paweł Hajdan, Jr."
2014-08-16 9:32 ` Pacho Ramos [this message]
2014-08-17 20:48 ` Anthony G. Basile
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=1408181538.14509.1.camel@gentoo.org \
--to=pacho@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=ppc64@gentoo.org \
--cc=ppc@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