From: Fabian Groffen <grobian@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Council discuss: overlapping council terms of two years
Date: Sat, 6 Aug 2011 13:49:21 +0200 [thread overview]
Message-ID: <20110806114921.GA20656@gentoo.org> (raw)
In-Reply-To: <4E3D10B0.80107@gentoo.org>
On 06-08-2011 11:00:16 +0100, Markos Chandras wrote:
> Oh come on Jorge. You know what I mean by slacking arches. I am not
> talking about punishing them. Maybe drop stable keywords or drop keyword
> from X package and shrink their tree so they can keep up with the load.
>
> > This should be the arch more developers use daily and is likely the
> > one with more members (herd count). Also, one should remember the
> > time it takes to compile, test or debug an issue in a recent amd64
> > system or an old / slow box with an "exotic arch" varies
> > substantially. Not to mention that the amount of testing done on
> > "exotic arches" varies substantially between projects.
> I am aware of the problems and this is way I want a solution.
And what solution do you have in mind (in your Council role)?
> > In the last council, I've took the job of promoting some email
> > threads between arch teams, the council, trustees and infra to see
> > what we could do about it. Some of the issues were then opened on the
> > project ml. You are correct that there wasn't a "quick", "final" or
> > even "conclusive" decision, but I'll argue that we needed more debate
> > - including more interest and participation from the community. I do
> > think we had a good discussion.
> Yes, we discussed what was needed etc but I don't really think that
> anything changed since them. If not, then I apologize
What would you have seen changed that the Council can influence upon?
> > If the argument in the end boils down to how many arches Gentoo
> > supports and about leaving support for some arches or killing it so
> > that maintainers aren't "bogged down" by arches, I'll support arches
> > over maintainers.
> >
> I never said to completely drop these arches. When did I say that? I
> just want a more realistic approach on how well an arch is supported.
> Why you people are afraid to admit that we have problems? Having an arch
> with constantly >200 stabilization bugs open clearly proves that the
> manpower cannot handle the situation.
How do you suggest the Council to solve this issue and, as you indicated
before, right now?
--
Fabian Groffen
Gentoo on a different level
next prev parent reply other threads:[~2011-08-06 11:50 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 18:47 [gentoo-project] Council discuss: overlapping council terms of two years Fabian Groffen
2011-08-01 20:25 ` Andreas K. Huettel
2011-08-01 23:24 ` Jorge Manuel B. S. Vicetto
2011-08-02 6:36 ` Fabian Groffen
2011-08-02 15:42 ` William Hubbs
2011-08-02 15:49 ` Rich Freeman
2011-08-02 18:24 ` Roy Bamford
2011-08-02 18:51 ` Rich Freeman
2011-08-02 21:50 ` Markos Chandras
2011-08-02 22:21 ` Roy Bamford
2011-08-02 22:37 ` Markos Chandras
2011-08-03 20:21 ` Roy Bamford
2011-08-04 20:10 ` Donnie Berkholz
2011-08-04 22:31 ` Roy Bamford
2011-08-05 7:51 ` Donnie Berkholz
2011-08-05 10:50 ` Fabian Groffen
2011-08-09 14:01 ` Donnie Berkholz
2011-08-09 17:23 ` Roy Bamford
2011-08-02 16:15 ` Fabian Groffen
2011-08-03 2:26 ` Jorge Manuel B. S. Vicetto
2011-08-03 8:13 ` Fabian Groffen
2011-08-04 20:08 ` Donnie Berkholz
2011-08-05 6:58 ` Fabian Groffen
2011-08-05 7:49 ` Donnie Berkholz
2011-08-05 10:30 ` Ulrich Mueller
2011-08-05 10:40 ` Fabian Groffen
2011-08-09 14:05 ` Donnie Berkholz
2011-08-09 17:25 ` Fabian Groffen
2011-08-09 17:34 ` Donnie Berkholz
2011-08-12 13:12 ` [gentoo-project] " Steven J Long
2011-08-12 17:58 ` Donnie Berkholz
2011-08-02 17:58 ` [gentoo-project] " Roy Bamford
2011-08-03 2:39 ` Jorge Manuel B. S. Vicetto
2011-08-03 20:42 ` Roy Bamford
2011-08-04 20:06 ` Donnie Berkholz
2011-08-04 22:19 ` Roy Bamford
2011-08-05 10:33 ` Markos Chandras
2011-08-05 10:49 ` Fabian Groffen
2011-08-05 11:01 ` Markos Chandras
2011-08-05 12:35 ` Rich Freeman
2011-08-05 13:17 ` Markos Chandras
2011-08-05 13:35 ` Rich Freeman
2011-08-05 13:49 ` Markos Chandras
2011-08-05 13:44 ` Fabian Groffen
2011-08-05 13:54 ` Markos Chandras
2011-08-05 16:32 ` Patrick Lauer
2011-08-05 16:47 ` Markos Chandras
2011-08-05 19:22 ` Rich Freeman
2011-08-05 19:31 ` Markos Chandras
2011-08-05 18:36 ` Matt Turner
2011-08-05 18:43 ` Markos Chandras
2011-08-06 3:11 ` Jorge Manuel B. S. Vicetto
2011-08-06 10:00 ` Markos Chandras
2011-08-06 11:49 ` Fabian Groffen [this message]
2011-08-06 11:59 ` Markos Chandras
2011-08-06 12:24 ` Jorge Manuel B. S. Vicetto
2011-08-06 12:31 ` Markos Chandras
2011-08-06 12:47 ` Fabian Groffen
2011-08-06 12:54 ` Markos Chandras
2011-08-06 14:16 ` Fabian Groffen
2011-08-06 14:36 ` Markos Chandras
2011-08-06 14:54 ` Fabian Groffen
2011-08-06 15:01 ` Markos Chandras
2011-08-06 15:06 ` Fabian Groffen
2011-08-12 20:43 ` Mike Frysinger
2011-08-12 20:52 ` "Paweł Hajdan, Jr."
2011-08-06 15:33 ` Matt Turner
2011-08-06 15:42 ` Markos Chandras
2011-08-06 15:53 ` Matt Turner
2011-08-06 15:58 ` Markos Chandras
2011-08-06 23:59 ` Jorge Manuel B. S. Vicetto
2011-08-07 6:16 ` Tim Harder
2011-08-07 11:08 ` Rich Freeman
2011-08-05 16:33 ` "Paweł Hajdan, Jr."
2011-08-05 16:56 ` Markos Chandras
2011-08-09 14:10 ` Donnie Berkholz
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=20110806114921.GA20656@gentoo.org \
--to=grobian@gentoo.org \
--cc=gentoo-project@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