From: Jack Morgan <jmorgan@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] About current ppc/ppc64 status
Date: Tue, 29 Jul 2014 19:16:34 -0700 [thread overview]
Message-ID: <20140730021634.GA15473@toyama.bonyari.local> (raw)
In-Reply-To: <53D40FBF.8060906@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 3307 bytes --]
On Sat, Jul 26, 2014 at 04:29:51PM -0400, Anthony G. Basile wrote:
> On 07/26/14 09:44, Pacho Ramos wrote:
> > El sáb, 26-07-2014 a las 09:37 -0400, Anthony G. Basile escribió:
> >> On 07/26/14 09:28, Pacho Ramos wrote:
> >>> El sáb, 26-07-2014 a las 14:55 +0200, Andreas K. Huettel escribió:
> >>>> Am Samstag, 26. Juli 2014, 13:56:02 schrieb Pacho Ramos:
> >>>>
> >>>>> I guess we will need to wait for the next Council to officially decide
> >>>>> to do this as it will be a big change for ppc* users :/ (I remember
> >>>>> their action was needed for the move to testing of some arches and the
> >>>>> "package-by-package" proposal for others)
> >>>>>
> >>>>> Also, I am not sure if any other arch teams (sparc, ia64?) would want to
> >>>>> get this policy too :| (I got ppc* because this concrete case ;))
> >>>> At first this is an arch team decision. No need for the council.
> >>>>
> >>>> (Given that in this case there is a responsive and addressable arch team...)
> >>>>
> >>>> --
> >>>>
> >>>> Andreas K. Huettel
> >>>> Gentoo Linux developer
> >>>> dilfridge@gentoo.org
> >>>> http://www.akhuettel.de/
> >>>>
> >>> The problem is that blueness looks to be the only member currently
> >>> replying :/, I have checked their page and I see no team lead or
> >>> similar. Then, I am not sure how to get the ok to proceed or not :| (to
> >>> prevent this from getting stalled and we keep trying stabilizing all the
> >>> things).
> >>>
> >>> I remember from older thread (one related with udev stabilization), that
> >>> blueness was also the only one replying.
> >>>
> >>>
> >> Yeah, not having a clear lead is a problem. No one wants to just make a
> >> big decision on behalf of the team without making sure everyone is on
> >> board. Pacho, do you have access to timberdoodle? If so, join both
> >> teams and just take the initiative and let any other "claimants" step
> >> forward now. BTW, taking the lead doesn't mean doing all the work
> >> yourself. I want to see ppc/ppc64 in good shape. I'll be happy to
> >> write scripts to do the demoting to ~ etc etc.
> >>
> > I don't even know about timberdoodle :(
> >
> > I forwarded the mail to both alias (as I forgot first time), then,
> > hopefully they will review it :/
> >
> > Will CC them again to this just now with this link to allow all to read
> > the full thread:
> > http://comments.gmane.org/gmane.linux.gentoo.devel/92151
> >
> >
> >
>
> I think its clear who cares about ppc/ppc64. If there are no
> objections, I'll take the lead of those teams and see this plan
> through. I'll wait a few days for people to voice concerns. Then I'll
> start by generating a list of all stable and testing packages on ppc and
> ppc64. I'll post then and then continue the conversation on just the
> ppc and ppc64 lists. Don't worry, I won't start dropping to ~ until we
> have a concise plan and we're all on board.
I don't think you can/should just take over the leadership of an arch.
Why not have meeting/discussion for team members. Especially since you
are proposing such a big change.
Thanks,
--
Jack Morgan
Pub 4096R/761D8E0A 2010-09-13 Jack Morgan <jmorgan@gentoo.org>>
Fingerprint = DD42 EA48 D701 D520 C2CD 55BE BF53 C69B 761D 8E0A
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-07-30 2:13 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 19:28 [gentoo-dev] About current ppc/ppc64 status Pacho Ramos
2014-07-25 19:38 ` Anthony G. Basile
2014-07-25 19:50 ` Pacho Ramos
2014-07-25 19:57 ` Anthony G. Basile
2014-07-25 20:07 ` William Hubbs
2014-07-26 8:36 ` Pacho Ramos
2014-07-26 8:44 ` Pacho Ramos
2014-07-26 9:09 ` Johannes Huber
2014-07-26 11:57 ` Manuel Rüger
2014-07-26 11:59 ` Pacho Ramos
2014-07-26 12:16 ` Anthony G. Basile
2014-07-26 10:22 ` Anthony G. Basile
2014-07-26 11:36 ` Pacho Ramos
2014-07-26 11:47 ` Anthony G. Basile
2014-07-26 11:56 ` Pacho Ramos
2014-07-26 12:23 ` Rich Freeman
2014-07-26 13:25 ` Pacho Ramos
2014-07-26 12:55 ` Andreas K. Huettel
2014-07-26 13:28 ` Pacho Ramos
2014-07-26 13:37 ` Anthony G. Basile
2014-07-26 13:44 ` Pacho Ramos
2014-07-26 20:29 ` Anthony G. Basile
2014-07-26 22:01 ` Pacho Ramos
2014-07-29 14:30 ` Anthony G. Basile
2014-07-30 2:16 ` Jack Morgan [this message]
2014-07-30 10:26 ` Anthony G. Basile
2014-07-30 21:18 ` Joseph Jezak
2014-07-30 23:44 ` Anthony G. Basile
2014-07-31 0:21 ` Jack Morgan
2014-07-26 11:44 ` Samuli Suominen
2014-07-26 12:53 ` Andreas K. Huettel
2014-07-26 15:39 ` William Hubbs
2014-07-26 16:20 ` William Hubbs
2014-07-26 16:31 ` Andreas K. Huettel
2014-07-26 17:19 ` William Hubbs
2014-07-26 17:33 ` [gentoo-dev] " Michael Palimaka
2014-08-01 8:52 ` Raúl Porcel
2014-08-01 9:35 ` Joshua Kinard
2014-08-02 8:59 ` Joshua Kinard
2014-08-01 10:28 ` Duncan
2014-07-26 16:40 ` Michael Palimaka
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=20140730021634.GA15473@toyama.bonyari.local \
--to=jmorgan@gentoo.org \
--cc=gentoo-dev@lists.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