From: hasufell <hasufell@gentoo.org>
To: Rich Freeman <rich0@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Becoming a Gentoo developer?
Date: Sat, 18 Apr 2015 11:15:56 +0200 [thread overview]
Message-ID: <553220CC.3050104@gentoo.org> (raw)
In-Reply-To: <CAGfcS_mBuMP4=r5xW_-7Qy+h_Tc01u448h+3sOu+QBB6rj9pWQ@mail.gmail.com>
On 04/17/2015 07:15 PM, Rich Freeman wrote:
> On Fri, Apr 17, 2015 at 10:41 AM, Alexander Berntsen
> <bernalex@gentoo.org> wrote:
>>
>> On 17/04/15 16:33, Andrew Savchenko wrote:
>>> The problem is double effort: previously one developer effort was
>>> needed, now effort is doubled at least
>> You have correctly identified the problem; in order to do things
>> properly one must do things properly, which is more difficult than not
>> doing things properly.
>>
>
> "Properly" is just a matter of requirements. Gentoo has 18k packages
> right now. In my general experience, they install fine maybe 95% of
> the time.
>
Can you back up your "general experience" with a tinderbox log? In
addition, you are decreasing "QA" to "compiles". That's not the definition.
> Right now we
> end up dropping packages because we can't find one person to maintain
> them. With a review workflow we'll drop packages if we can't find two
> people to maintain them.
Nah, that's really not true. With a review workflow there is less need
for actual maintainers! That's the whole point.
I am really confused. I guess some people have never really been in a
different workflow than gentoo to know that it's really not
state-of-the-art. And it really isn't. Not even for distros.
next prev parent reply other threads:[~2015-04-18 9:16 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-12 12:17 [gentoo-dev] Becoming a Gentoo developer? Yanestra
2015-04-12 13:08 ` Pacho Ramos
2015-04-12 14:27 ` Yanestra
2015-04-12 14:44 ` Andrew Savchenko
2015-04-12 15:05 ` Andreas K. Huettel
2015-04-15 3:33 ` Yanestra
2015-04-15 6:40 ` Diamond
2015-04-15 13:02 ` Peter Stuge
2015-04-16 17:27 ` hasufell
2015-04-16 22:59 ` Kent Fredric
2015-04-17 19:38 ` Pacho Ramos
2015-04-17 21:09 ` Andreas K. Huettel
2015-04-18 9:45 ` hasufell
2015-04-17 10:33 ` Alexander Berntsen
2015-04-17 11:00 ` Andrew Savchenko
2015-04-17 11:12 ` Kristian Fiskerstrand
2015-04-17 11:14 ` hasufell
2015-04-17 12:26 ` Andrew Savchenko
2015-04-17 12:50 ` hasufell
2015-04-17 14:33 ` Andrew Savchenko
2015-04-17 14:41 ` Alexander Berntsen
2015-04-17 17:15 ` Rich Freeman
2015-04-18 9:15 ` hasufell [this message]
2015-04-18 9:26 ` Patrick Lauer
2015-04-18 12:35 ` Rich Freeman
2015-04-18 13:03 ` hasufell
2015-04-18 14:35 ` Rich Freeman
2015-04-17 21:12 ` Andreas K. Huettel
2015-04-17 23:16 ` Kent Fredric
2015-04-18 9:10 ` hasufell
2015-04-21 10:33 ` Sergey Popov
2015-04-17 19:14 ` [gentoo-dev] " Justin Bronder
2015-04-17 23:30 ` Kent Fredric
2015-04-18 4:07 ` Rich Freeman
2015-04-15 20:46 ` [gentoo-dev] " Pacho Ramos
2015-04-16 14:22 ` Bob Wya
2015-04-16 22:50 ` Kent Fredric
2015-04-17 11:13 ` Andrew Savchenko
2015-04-13 10:27 ` Daniel Campbell
2015-04-13 12:20 ` Patrice Clement
2015-04-13 12:37 ` Patrice Clement
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=553220CC.3050104@gentoo.org \
--to=hasufell@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=rich0@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