From: Rebecca Cran <rebecca@bluestop.org>
To: "Sean Brogan" <sean.brogan@microsoft.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Zimmer, Vincent" <vincent.zimmer@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
stephano <stephano.cetola@linux.intel.com>
Subject: Re: [edk2-announce][RFC] Collaboration Software
Date: Fri, 16 Nov 2018 21:58:40 -0700 [thread overview]
Message-ID: <etPan.5befa173.327b23c6.53cd@bluestop.org> (raw)
In-Reply-To: <CY4PR21MB0184DEF1B3355EF33C9D0742E1DE0@CY4PR21MB0184.namprd21.prod.outlook.com>
On November 16, 2018 at 7:42:51 PM, Sean Brogan via edk2-devel (edk2-devel@lists.01.org(mailto:edk2-devel@lists.01.org)) wrote:
> I really can't get behind the Phabricator tool suite as it just has too many downsides (self-hosted or pay, lack of integrations, lack of support and limited searchability, poor ci integration, etc).
>
At least with Phabricator you don’t have to pay to self-host it. And look at all the features you don’t get with Github unless you pay them:
https://github.com/pricing
Rebecca
next prev parent reply other threads:[~2018-11-17 5:13 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 [this message]
2018-11-17 19:01 ` stephano
2018-11-17 21:22 ` Rudra ठाकुर
2018-11-17 22:03 ` Rebecca Cran
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=etPan.5befa173.327b23c6.53cd@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