On Wed, 2016-03-16 at 22:05 +0000, Kinney, Michael D wrote: > > I responded to an earlier email:
Ah, apologies — it wasn't clear this was intended as an answer to that question. This is one of those examples with the common email behaviour of placing the response below a carefully-selected citation would have helped a great deal, FWIW. > I think there are several methods we can support for development. > > 1) Simple bug fixes/features sent directly to edk2-devel for PRs. > 2) A larger or more complex bug fix/feature can optionally post a link > to a branch on personal github fork to help simplify the review process > for those reviewers that prefer to use that method. This type of bug > fix or feature is usually owned by a single subject matter expert. > 3) A larger or more complex feature that requires design/dev/test by more > than one subject matter expert. > > We already support (1) and (2) today. Feature branches on edk2-staging are > intended for (3). So the answer would be that it allows more than one person to collaborate on a submission? I'm not sure we need a whole new process document just for that, do we? It's not as if it's hard for people to share access to their repositories, or just pull from each other's. ================== On Wed, 2016-03-16 at 15:15 -0700, Andrew Fish wrote: > I think David's point is any github repository can be used for this, > if I understand David's point? Precisely so. > So the only value to branches is an official place for them to live? > Thus a way they can be discovered. Can't they already be discovered at https://github.com/tianocore/edk2/pulls ? This is the normal workflow. People (individuals or otherwise) put together some work, discussion happens (and is archived and discoverable) in a pull request. New versions of the tree can be submitted to the PR at any time. We don't need to invent anything new and different, just to allow more than one person to work together on a submission. -- David Woodhouse Open Source Technology Centre [email protected] Intel Corporation
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
