public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Becoming a Gentoo developer?
Date: Sat, 18 Apr 2015 10:35:59 -0400	[thread overview]
Message-ID: <CAGfcS_njFo-LbKGRVi6JjTQShJ=87Vga7JAx2=k=RKucdr_gBg@mail.gmail.com> (raw)
In-Reply-To: <55325614.4060506@gentoo.org>

On Sat, Apr 18, 2015 at 9:03 AM, hasufell <hasufell@gentoo.org> wrote:
>
> Having a proper review workflow/platform increases the contribution
> factor of the community. And not just that.

Define "contribution factor."  If you mean the number of people
writing patches vs the number of people with commit access, I'll
agree.  If you mean the absolute commit rate to the repository, I'd
say that I have no reason to think that this is true.

>
> I'm also not going to give real-world examples of such workflows in big
> projects: just head over to github.
>

We already have the same workflow in Gentoo.  Anybody can submit a
pull request to the git mirror of the main tree.  It will get reviewed
and committed.  We just don't exclude direct commits.

-- 
Rich


  reply	other threads:[~2015-04-18 14:36 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
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 [this message]
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='CAGfcS_njFo-LbKGRVi6JjTQShJ=87Vga7JAx2=k=RKucdr_gBg@mail.gmail.com' \
    --to=rich0@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