public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Manuel Rüger" <mrueg@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Gentoo-hosted code review
Date: Sun, 1 Nov 2015 20:50:28 +0100	[thread overview]
Message-ID: <56366D04.3070906@gentoo.org> (raw)
In-Reply-To: <563666AA.9090100@gentoo.org>

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

On 01.11.2015 20:23, hasufell wrote:
> On 11/01/2015 06:44 PM, Michael Palimaka wrote:
>> There's been a lot of discussion about relying on GitHub for pull
>> requests and code review and such, so I have set up a Phabricator
>> instance against gentoo.git to see how a free alternative might work.
>>
>> Here's a few examples of how things could work:
>>
>> General post-commit review:
>> http://phabricator.astralcloak.net/rGENTOO27ba62d0c7fcabdc79ce82a064b43d67b3b11cca
>>
>> Tracking commits with issues that need attention:
>> http://phabricator.astralcloak.net/audit/query/open/
>>
>> Pre-commit review: http://phabricator.astralcloak.net/D1
>>
>> Phabricator also has all sorts of fancy (optional) features that could
>> be useful for collaborative development (see http://phabricator.org/ for
>> more info).
>>
>> What do you think?
>>
>>
> 
> phabricator is horrible. I'll definitely use it less (if at all) than
> bugzilla.
> 

On 10.10.2015 16:15, Julian Ospald wrote:
> That's a great start for us, having developers announce publicly that
> they will ignore our project or require us to create bugs for every
> missing "|| die" in an ebuild.

*chuckles*



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

  reply	other threads:[~2015-11-01 19:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-01 17:44 [gentoo-dev] Gentoo-hosted code review Michael Palimaka
2015-11-01 18:08 ` James Le Cuirot
2015-11-02  8:33   ` Patrice Clement
2015-11-02  9:29     ` [gentoo-dev] " Duncan
2015-11-02 10:28       ` Patrice Clement
2015-11-02 11:36         ` Duncan
2015-11-01 18:18 ` [gentoo-dev] " Bertrand Jacquin
2015-11-01 18:34 ` Michał Górny
2015-11-01 19:40   ` hydra
2015-11-02  0:37   ` [gentoo-dev] " Duncan
2015-11-01 19:23 ` [gentoo-dev] " hasufell
2015-11-01 19:50   ` Manuel Rüger [this message]
2015-11-01 21:27     ` hasufell
2015-11-01 21:18   ` William Hubbs
2015-11-01 22:16     ` Michael Orlitzky
2015-11-02 12:33   ` [gentoo-dev] " Michael Palimaka
2015-11-01 22:07 ` [gentoo-dev] " Michael Orlitzky
2015-11-01 22:38   ` Luca Barbato
2015-11-02 12:26   ` [gentoo-dev] " Michael Palimaka
2015-11-02 13:04     ` Kristian Fiskerstrand
2015-11-02 19:24       ` Dirkjan Ochtman
2015-11-03 12:48         ` Michael Palimaka
2015-11-02 11:08 ` [gentoo-dev] " Alexander Berntsen
2015-11-02 13:24   ` [gentoo-dev] " Michael Palimaka
2015-11-02 14:01     ` Alexander Berntsen

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=56366D04.3070906@gentoo.org \
    --to=mrueg@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