On 01/13/19 04:59, Rebecca Cran wrote: > On Friday, 11 January 2019 12:26:30 MST stephano wrote: > >> Patch Review System Evaluation >> ------------------------------ >> After evaluating Github, Gitlab, and Phabricator, we will be remaining >> with the mailing list for now. Github did prove a possible "2nd runner >> up" (albeit distant). Also, Stephano / Nate from Intel will be reviewing >> Gerrit use with a report being sent back to the community sometime next >> week. > > I wonder if we might want to have a separate mailing list for reviews? > > I find it a bit overwhelming having both patches and more general discussions > on the same list, since I only check it every few days. >
I vaguely recall that this topic (separate mailing lists) has come up before. I don't remember what the consensus was back then (or if there was a consensus to begin with). Personally, while I slightly prefer the single mailing list for now, I'd certainly not oppose multiple mailing lists either. I could still filter both "design" and "patch" lists into the same local folder. Some pitfalls to consider: - In some (infrequent) cases, a patch thread could be cross-posted to the design list as well -- in such cases, it might be more difficult to establish context for those people that are only subscribed to one of the lists, or filter them to separate folders. - If we have multiple lists, then we'll have to subscribe the agents of external archivers to them separately (such as mail-archive.com). - If we have multiple lists, and cannot lift the "subscribe to post" requirement, then the initial inconvenience for participants could increase. But, again, I totally understand Rebecca's perspective, and many open source projects use different lists for different themes / emphases. Thanks, Laszlo _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
