Good to see a proposal. I think it'd be good to articulate a bit more of the plan and its purpose, before diving into the details of module structure, which feel a bit premature to me.
In particular, I'd like to understand: - what kinds of websites does Mozilla offer / underwrite, and for what purpose? Same for domains and email services. - how does someone ask for such services, what are the criteria we use, etc? - why does it make sense for Mozilla to provide these services on hardware we control (virtualized or not) as opposed to underwriting/managing hosted services run by people who do this at scale? - to bkerensa's point, how do we mitigate the various risks associated with hosting content on behalf of someone else - how does this relate with other community-facing and community-managing activities across Mozilla, especially those that are focused on local and regional -- Reps, Mozilla Clubs, campus campaigns, etc. I'd also like to understand a bit of a roadmap -- what's the state of affairs now, where are we trying to go, by when, etc. --david _______________________________________________ governance mailing list [email protected] https://lists.mozilla.org/listinfo/governance
