Re: TianoCore Community Meeting Minutes (stephano)

Re: TianoCore Community Meeting Minutes (stephano)

[Jeremiah Cox]

Some additional feedback...


General
-------
We would like to have a discussion around goals, what are the top issues we are trying to solve with these solutions?  We believe a primary challenge is getting code integrated downstream.  We would like to see security patches flow to more systems, faster, with higher confidence.  The same applies to new UEFI features.  Part of making downstream integration efficient is getting downstream changes upstreamed, thus we support efforts to improve upstream contribution efficiency & quality.


Patch Workflow Improvement
-------------------------- 
We would like to propose adding Azure DevOps (previously Visual Studio Online) to the list.  Azure DevOps is free for OSS and more feature rich than GitHub: 
https://azure.microsoft.com/en-us/pricing/details/devops/azure-devops-services/ 


Public CI
---------
With respect to using Azure DevOps for CI, we have an example of this working here:
https://dev.azure.com/projectmu/mu/_build?definitionId=4 


Repos & Submodules
------------------
In an upcoming meeting, we would like to discuss code layout and repositories.  We propose to introduce layering and separation for a variety of reasons, best articulated by visiting the following:
https://microsoft.github.io/mu/ 



Kind regards,
Jeremiah Cox

Re: TianoCore Community Meeting Minutes (stephano)

[stephano]

Thank you for the feedback.

Comments below.

On 10/15/2018 4:58 PM, Jeremiah Cox wrote:
> Some additional feedback...
> 
> 
> General
> -------
> We would like to have a discussion around goals, what are the top issues we are trying to solve with these solutions?  We believe a primary challenge is getting code integrated downstream.  We would like to see security patches flow to more systems, faster, with higher confidence.  The same applies to new UEFI features.  Part of making downstream integration efficient is getting downstream changes upstreamed, thus we support efforts to improve upstream contribution efficiency & quality.

This is high on our list of concerns, along with generally making life 
easier for current developers. We would like to address ease of use for 
newcomers, but I've made it clear in calls that making our current 
community's workflow more streamlined and efficient takes priority.

> 
> 
> Patch Workflow Improvement
> --------------------------
> We would like to propose adding Azure DevOps (previously Visual Studio Online) to the list.  Azure DevOps is free for OSS and more feature rich than GitHub:
> https://azure.microsoft.com/en-us/pricing/details/devops/azure-devops-services/
> 
> 
> Public CI
> ---------
> With respect to using Azure DevOps for CI, we have an example of this working here:
> https://dev.azure.com/projectmu/mu/_build?definitionId=4

I've added Azure DevOps to the list of items to be discussed in our CI 
email, along with Cirrus and (I'm sure) Jenkins/Travis. Andrew started 
that and I'll be pulling it out into its own thread shortly.

> 
> 
> Repos & Submodules
> ------------------
> In an upcoming meeting, we would like to discuss code layout and repositories.  We propose to introduce layering and separation for a variety of reasons, best articulated by visiting the following:
> https://microsoft.github.io/mu/

I'd like to specifically call out Project Mu on our next call. That will 
be happening next week, after the Plugfest in Taipei.

> 
> 
> 
> Kind regards,
> Jeremiah Cox
>