public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Becoming a Gentoo developer?
Date: Fri, 17 Apr 2015 14:00:30 +0300	[thread overview]
Message-ID: <20150417140030.2a4dc50e53bbebc8a77edef7@gentoo.org> (raw)
In-Reply-To: <5530E162.2010409@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]

On Fri, 17 Apr 2015 12:33:06 +0200 Alexander Berntsen wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> On 15/04/15 15:02, Peter Stuge wrote:
> > the threshold to become a developer with write access to the
> > gentoo repo is very high
> LOL. No. It's way too low, given our review-less workflow in which any
> dev can do essentially whatever they want.

The only net results from strict review workflow (when each commit
of each dev must be reviewed and approved by at least N devs) are
tons of bikeshedding, real quality improvement is marginal, because
people are working in different areas anyway. And if you will
consider, that strict review will require N more times effort and
spent time, actual quality of the tree will drop almost N times,
because number of man hours spent on Gentoo is approximately
constant with the same number of devs.

Really, I'm tired of that review bikeshedding and trolling.
Before continuing talks like that take a list of paper, do some
calculations, think them over.

And do not point at the Linux kernel — they have ~80% paid
developers, so they have resources for that kind of workflow.
We are volunteers here, so we don't.

Best regards,
Andrew Savchenko

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-04-17 11:00 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 [this message]
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
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=20150417140030.2a4dc50e53bbebc8a77edef7@gentoo.org \
    --to=bircoph@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