On Tuesday, December 11, 2012 12:15:42 PM UTC-8, Dave Townsend wrote: > As part of landing the Add-on SDK APIs in Firefox we need to choose > > where to put them in the source tree. We had some early work in > > toolkit/addon-sdk however I think the Add-on SDK is a well owned module > > so there is no reason to put them under toolkit. I'd like to create the > > new top-level directory, addon-sdk and use that instead. Any objections?
I need to vet top-level additions and renames, so please mail directly (my m.governance reading is in batches). Currently we have at the top of mozilla-central: http://hg.mozilla.org/mozilla-central/file/1b6ab3a080d8 By alphabetical grouping: accessible b2g browser build caps chrome config content db dbm docshell dom editor embedding extensions gfx hal image intl ipc js layout media memory mfbt mobile modules mozglue netwerk nsprpub other-licenses parser probes profile python rdf security services startupcache storage testing toolkit tools uriloader view webapprt widget xpcom xpfe xulrunner Many of these are historical one-offs. Some are category containers (gfx image memory -- at least memory is), with the next level down consisting of instances of the category. Is addon-sdk for Firefox only? Is it tied to XUL? What does it depend on? If it is an independent module, it still could go under toolkit. Modules can and do contain other modules. Flat is better than nested, but a sprawling top level that mixes too many ad-hoc or specific modules with more general/high-level/category-container directories is not good for approachability and understanding and navigation. /be _______________________________________________ governance mailing list [email protected] https://lists.mozilla.org/listinfo/governance
