public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: Rich Freeman <rich0@gentoo.org>
Cc: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Status update of Sunrise project?
Date: Sun, 12 Apr 2015 14:03:11 +0200	[thread overview]
Message-ID: <20150412140311.1306ec7f@pomiot.lan> (raw)
In-Reply-To: <CAGfcS_=W+xXF0mPvQrFOyqbtZSBwUnwOtr+3A+SB8Q5M6mB8CQ@mail.gmail.com>

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

Dnia 2015-04-12, o godz. 07:22:17
Rich Freeman <rich0@gentoo.org> napisał(a):

> On Sun, Apr 12, 2015 at 5:59 AM, hasufell <hasufell@gentoo.org> wrote:
> > On 04/11/2015 01:54 PM, Rich Freeman wrote:
> >>
> >> 1.  What does proxy-maintainers lack in comparison to sunrise
> >> exclusively.  The immediate question is whether sunrise should be
> >> migrated to proxy-maintainers, so this specific comparison is
> >> important.
> >>
> >
> > proxy-maintainers lack:
> > 1. a repository with a usable VCS
> 
> proxy-maintainers is using git.  Am I missing something?
> 
> > 2. an actual review workflow... @proxy-maintainers are just some sort of
> > backup committers. it's not a hub for contributors to gather, discuss,
> > get reviews and improve skills
> 
> My understanding is that github pull-requests are being used.  I'll
> buy that the project is still fairly immature but it seems like they
> have a decent foundation for a review-oriented workflow.  Perhaps you
> might consider getting involved and building improvements?
> 
> > 3. means to ensure the tree doesn't break
> 
> Well, we don't even do this well in the main repository.
> proxy-maintainers can use repoman, as can committers, but I'll buy
> that those aren't the best solution.  There are already efforts to get
> travis-ci working on the main tree, and presumably this could be
> applied to proxy-maintainers as well.

Some of the proxy-maintainers have already switched to our git Gentoo
repo mirror. There, the pull requests are automatically checked using
repository-wide pcheck runs thanks to travis. This is actually better
than what most of Gentoo developers do, even though I asked them
multiple times to use the mirror when in doubt.

-- 
Best regards,
Michał Górny

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 949 bytes --]

      reply	other threads:[~2015-04-12 12:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-06  6:15 [gentoo-project] Status update of Sunrise project? Ben de Groot
2015-04-09 18:57 ` Thomas Sachau
2015-04-09 22:55   ` Ben de Groot
2015-04-10 16:14     ` Thomas Sachau
2015-04-11  5:38       ` Ben de Groot
2015-04-11 10:12         ` hasufell
2015-04-11 11:54           ` Rich Freeman
2015-04-12  9:59             ` hasufell
2015-04-12 10:02               ` Patrick Lauer
2015-04-12 10:04                 ` hasufell
2015-04-12 10:13                   ` Patrick Lauer
2015-04-12 10:21                     ` hasufell
2015-04-12 10:34                       ` Patrick Lauer
2015-04-12 11:22               ` Rich Freeman
2015-04-12 12:03                 ` Michał Górny [this message]

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=20150412140311.1306ec7f@pomiot.lan \
    --to=mgorny@gentoo.org \
    --cc=gentoo-project@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