On Wed, Dec 20, 2017 at 2:10 PM, Kan-Ru Chen <ka...@kanru.info> wrote:
> > > > If we choose to make this a module, I'm not sure which section of > > https://wiki.mozilla.org/Modules/All it would fall under. > > > > If we choose not to make this a module, I guess this list of people would > > instead be put onto https://wiki.mozilla.org/Oxidation. > > If we expect our Rust expertise to grow quickly (I think we should) this > list would not be necessary. Therefore I support to put it onto > https://wiki.mozilla.org/Oxidation. > That's a good point. To restate and expand: - We don't have "C++ peers" because C++ expertise is an implicit prerequisite for being a peer in a module containing C++ code. - We don't have "JS peers" because JS expertise is an implicit prerequisite for being a peer in a module containing JS code. - Ditto for other languages (e.g. Python for build system modules). Rust is currently special because it's so new, but eventually it'll be like the others: - We won't have "Rust peers" because Rust expertise will be an implicit prerequisite for being a peer in a module containing Rust code. In other words, this list of people will become less necessary over time, which is not what you'd expect for a Mozilla module. So I will not make this a module and just put it on the Oxidation wiki page. Thank you to all those who responded. Nick _______________________________________________ governance mailing list governance@lists.mozilla.org https://lists.mozilla.org/listinfo/governance
