This seems like a good idea to me. It establishes a forum for style and language feature discussions, as well as establishing some form of authority.
On Wednesday, March 9, 2016 at 1:20:33 PM UTC-8, Nathan Froyd wrote: > Hi all, > > Several of us have been talking about having a module that covers various > aspects of how we use C++, including, but not necessarily limited to: > > - language feature usage > - standard library versions/usage > - compiler/toolchain versions > - formatting/naming style (The C++ bits of > https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Coding_Style > , essentially) > > Some of these areas (e.g. compiler/toolchain versions) have not had an > explicit owner, but have simply been driven by whoever was most motivated > to push changes forward. (Or not push changes forward, as the case may > be.) We think it would be valuable to clearly delineate the people > responsible for making these decisions and doing the work, if necessary. > There is some overlap of this module with Core/Build Config, but it seems > to us that there's enough difference to make it a separate module. > > The Rust parts of this would be more forward-looking, as Rust is not yet a > significant part of Gecko, nor do we have some of the complications > provided by C++ when dealing with Rust (e.g. multiple > compiler/toolchain/standard library providers). The Rust community also > has somewhat more established guidelines around style as well. > > The proposed peers of this module would be Ehsan Akhgari, Botond Ballo, > Jeff Walden, Mike Hommey, and myself. For lack of enthusiasm about being > module owner from the other peers, I suppose it falls to me to be module > owner. > > Questions and suggestions welcome. > > -Nathan _______________________________________________ governance mailing list governance@lists.mozilla.org https://lists.mozilla.org/listinfo/governance
