On 09/09/14 07:43, Jordan Justen wrote: > This file's content is partially based on the QEMU project's > MAINTAINERS file. > > Contributed-under: TianoCore Contribution Agreement 1.0 > Signed-off-by: Jordan Justen <[email protected]> > --- > > All: It seems like there was a positive response to this idea. How > does this look for a starting point? > > Maintainers.txt | 150 > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 150 insertions(+) > create mode 100644 Maintainers.txt
It's been a month -- may I ask if this file is coming along? I'd like to see this file appear in the tree not because I want to see my name in it. (Well, not primarily for that reason.) I'd like to have this file with *working* email addresses because my own self needs to CC maintainers occasionally. And https://github.com/tianocore/tianocore.github.io/wiki/EDKII-Packages while well-meaning, is quite unwieldy. edk2 is big; contributors should be able to CC subsystem maintainers directly. This is a quasi-standard in the open source world for big projects (see the Linux kernel, qemu, etc). I'm aware of the so-called "privacy concerns" wrt. @Intel email addresses in that file. I think that concern is unfounded. The email addresses in question can already be snarfed from the list archive, with varying levels of annoyance. Resistance to publish these *work emails* only makes contact hard for legitimate users; it won't thwart spammers. Thanks, Laszlo ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
