On Sun, Jan 5, 2014 at 6:34 PM, Nicholas Nethercote <n.netherc...@gmail.com> wrote: > - There is an semi-official policy that the owner of a module can dictate its > style. Examples: SpiderMonkey, Storage, MFBT.
AFAICT, there are not many rules that module owners are bound by. The reason module owners can dictate style is because module owners can dictate everything in their module. I think we should wait until we've heard from module owners that strongly oppose the style changes and then decide how to deal with that. Imposing changes on module owners, that the module owners don't agree to goes against the governance system we have in place. Our governance system is based on the idea that module owners (and peers) will make good decisions. Implicit in that is the idea that module owners may need to make decisions that are sub-optimal for them, but which are optimal for the project in general. > There appears to be no good reason for this and I propose we remove it. > Possibly with the exception of SpiderMonkey (and XPConnect?), due to it > being > an old and large module with its own well-established style. I guess you are implicitly excepting NSS and NSPR too, which are C code. As far as PSM is concerned, my main ask is that such reformatting of security/manager/ssl/src/* be done in February or later, so that the current urgently-needed big refactoring in that code is not disrupted. Cheers, Brian -- Mozilla Networking/Crypto/Security (Necko/NSS/PSM) _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
