Re: TianoCore Community Meeting Minutes

[stephano <stephano.cetola@linux.intel.com>]

On 10/12/2018 6:27 AM, Leif Lindholm wrote:> I know at least one 
organisation that would be prevented from using it
> until they had explicit approval (which could take a while), and it
> puts me in the position of having to keep a spare x86 machine on my
> desktop in order to participate.
> 
> Solutions I know would work in this scenario (i.e. work without
> plugins or downloads in any modern browser) are:
> - google hangouts (requires accounts, not ideal for China)
> - Skype (not SFB though, only plain old Skype)
> - Bluejeans (requires organiser account)

We needed an organizer account for Zoom since our meeting was 1 hour 
long. So switching to something paid is not an issue.

I've used Bluejeans with success in the past. I'll look into switching 
to this platform if no one else has any objections. I'd like to stay 
away from my other preferred google hangouts because so many of our 
members are in PRC.

>>
>> The was a concern raised over potential lock-in to Github's, specifically in
>> regards to history retention.
>> Several Github users brought up that this shouldn't be an issue.
> 
> Hopefully they said more than that.
> What does "shouldn't be an issue" mean.
> Were these users from multiple organisations?

I will ask for more details in the next meeting, but the comments were 
that the API is quite robust and lends itself to readily accessible data.

> 
>> Shawn mentioned some benefits to stock Github such as
>> it is always up to date, it includes APIs to extract data, pull
>> requests
> 
> Since we are discussing multiple different development systems, can we
> try to be a bit more explicit? This is referring to github's web-based
> branch-based ticketing system, yes?

Yes that's correct.

> 
> I know language drift and all, but
> https://www.kernel.org/doc/html/latest/maintainer/pull-requests.html
> is what pull request means to at least 3 participants in this conversation.

I think this is an important distinction to make and I'm sure it will 
come up in future discussions. I'll be sure to bring this up.

> 
>> lend themselves to simple(r) automation, and it has a much more modern web
>> UI than Gerrit.
> 
> It seems somewhat less than ideal to me that all of the github
> proponents were on the opposite call to me and Laszlo (and Ard). Were
> any of them Asia-based or could we try to get them on the call with
> Europe next time? I'm sure me and Laszlo could be somewhat more
> accommodating than your 7AM, but we're not going to stay up for a 3/4AM
> meeting about source control.

That's understandable. I'm not sure where Shawn and Nate are located, 
but I believe it is in the US. We could certainly move the AM call a bit 
later if it makes it easier to get more folks from the US on that call.

>> -How can we better track the code quality of BaseTools and the current build
>> system on the whole. Should we add a "requires documentation change" flag to
>> BZ so that it will be easier to compile a list of required doc changes.
> 
> Could we also have a thread on someting that you sort of mention in
> the text, but not the bullet points?:
> - Suggestions for improvements to BaseTools.

Of course. I'll add this to the list of "community conversations" that I 
will start up on the list this week.

Cheers,
Stephano