public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Rebecca Cran <rebecca@bluestop.org>
To: edk2-devel@lists.01.org, Sean Brogan <sean.brogan@microsoft.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	stephano <stephano.cetola@linux.intel.com>,
	"Zimmer, Vincent" <vincent.zimmer@intel.com>
Subject: Re: [edk2-announce][RFC] Collaboration Software
Date: Sat, 17 Nov 2018 15:03:33 -0700	[thread overview]
Message-ID: <1916170.9KSsKqBpt2@photon.int.bluestop.org> (raw)
In-Reply-To: <CY4PR21MB0184DEF1B3355EF33C9D0742E1DE0@CY4PR21MB0184.namprd21.prod.outlook.com>

On Friday, 16 November 2018 19:42:51 MST Sean Brogan via edk2-devel wrote:
> Mike,
> 
> I like the github teams option for discussion as it is just there, free, and
> easy.  It integrates nicely with all other parts of github.  Notifications
> are supported for those that want email.   Is there any reason this path
> doesn't get used now as a test since tianocore is already in github?  

I do wonder why there aren't more _big_ open source projects using Github if 
it _is_ there, free and easy to use. I'm aware lots and lots use it for 
hosting their repositories, but I'm not aware of many that use it for code 
reviews, discussions etc.

I found that CoreBoot uses Gerrit: https://review.coreboot.org/q/status:open

GNOME evaluated Phabricator and GitLab (but not GitHub, because "GitHub is not 
Free Software, of couse, which makes it unacceptable to many in the GNOME 
community") - https://wiki.gnome.org/Initiatives/DevelopmentInfrastructure .
They decided to go with GitLab:
https://mail.gnome.org/archives/desktop-devel-list/2017-May/msg00051.html

One comment from a user on the GNOME evaluation (https://wiki.gnome.org/
Initiatives/DevelopmentInfrastructure/Comments) said:

"We tried migrating libnice to phabricator.freedesktop.org and it was a bit of 
a disaster as the "drive-by" contribution process is horrible with 
Phabricator, requiring to either download a tool or copy-paste patches into a 
webpage. Upstream Phabricator is also very hostile to the github style of 
reviews (where you can review small patches, not everything squashed into one 
SVN style). Even Bugzilla with Splinter is nicer for new contributors.. So 
let's go with GitLab. That said, all of Collabora's Phabricator tools are 
already public. ? OlivieCrete"

-- 
Rebecca




  parent reply	other threads:[~2018-11-17 22:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-16 16:59 [edk2-announce][RFC] Collaboration Software stephano
2018-11-16 17:35 ` Kevin D Davis
2018-11-16 17:56   ` Zimmer, Vincent
2018-11-16 19:13     ` stephano
2018-11-16 19:55       ` Kinney, Michael D
2018-11-16 20:46         ` stephano
2018-11-16 22:14           ` Philippe Mathieu-Daudé
2018-11-17  0:34             ` stephano
2018-11-17  0:37               ` Rebecca Cran
2018-11-17  1:36                 ` stephano
2018-11-19 10:46             ` Tomas Pilar (tpilar)
2018-11-17  2:42         ` Sean Brogan
2018-11-17  4:58           ` Rebecca Cran
2018-11-17 19:01           ` stephano
2018-11-17 21:22             ` Rudra ठाकुर
2018-11-17 22:03           ` Rebecca Cran [this message]
2018-11-16 20:52       ` Rebecca Cran
2018-11-16 21:42         ` stephano
2018-11-16 21:51           ` Rebecca Cran
2018-11-17  0:22             ` stephano

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-list 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=1916170.9KSsKqBpt2@photon.int.bluestop.org \
    --to=devel@edk2.groups.io \
    /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