Re: [edk2-announce] Community Meeting Minutes

[Rebecca Cran <rebecca@bluestop.org>]

On Thursday, 7 February 2019 11:30:38 MST stephano wrote:

> My apologies if I was not clear in the minutes. We are not rejecting 
> Github, but rather taking time to evaluate how we can supplement 
> Github's features to emulate our current patch review requirements. We 
> do not want to rush into change and risk losing data or causing 
> frustration for those developers currently contributing on a regular basis.
> 
> I am currently working off this list of issues that Laszlo brought up:
> 
> https://lists.01.org/pipermail/edk2-devel/2018-December/033509.html
> 
> To be clear, Laszlo is not the only package maintainer that has voiced 
> these concerns. The longevity of pull request branches and the fact that 
> email notifications lack context are top on my list. There are several 
> ways to overcome these obstacles, and finding the best solution will 
> ensure that if we transition to Github, that transition is successful.
> 
> The ability to allow developers to work offline (or with intermittent 
> connections) is an important aspect as well. We cannot practice 
> exclusionary or ostracizing behaviors if we expect to grow and maintain 
> a community. I cannot imagine that Github has become as popular as it is 
> if it cannot facilitate ease of offline use.

I wonder if Phabricator could be considered again, since I believe it supports 
all the features mentioned: the only thing it doesn't support as a first-class 
feature is mutli-patch reviews, which need to be done by linking separate 
reviews together using the dependency feature. I wonder if it could either be 
enhanced to support that, or people's workflow modified?

-- 
Rebecca Cran