From: Jeremiah Cox <jerecox@microsoft.com>
To: stephano <stephano.cetola@linux.intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: TianoCore Community Meeting Minutes (stephano)
Date: Mon, 15 Oct 2018 23:58:11 +0000 [thread overview]
Message-ID: <MWHPR21MB0176F88EF2389B667560FDDFADFD0@MWHPR21MB0176.namprd21.prod.outlook.com> (raw)
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
next reply other threads:[~2018-10-15 23:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 23:58 Jeremiah Cox [this message]
2018-10-16 18:45 ` TianoCore Community Meeting Minutes (stephano) 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=MWHPR21MB0176F88EF2389B667560FDDFADFD0@MWHPR21MB0176.namprd21.prod.outlook.com \
--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