I'll take a first go at answering these questions, but Pierros or Tom might have important info to add:
On Tue, Feb 16, 2016 at 12:25 PM, David Ascher <[email protected]> wrote: > 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: > There is some context that applies to many of these questions in that several years Mozilla decided to support community sites with resources, both financial and technical. The group providing the technical resources is almost entirely volunteers (Community IT which became Community Ops). The idea was not to obtain any *control* over the sites, though centralizing some resources, like domains, creates a much better experience. We've been providing these services under the umbrella of Community Ops, even though they aren't all Ops tasks. That is one of the issues that would be solved through the creation of a module. > > - what kinds of websites does Mozilla offer / underwrite, and for what > purpose? Same for domains and email services. > Mostly regional community sites, though we have also managed project related sites, like the Firefox 10 site and the community Discourse. This proposal is meant to cover the decentralized community sites. Experiments like Discourse fit under the new Participation Software Lab (ParSoL). > - how does someone ask for such services, what are the criteria we use, > etc? > Currently it's a Reps request which is reviewed by at least one member of Reps council. This was because Reps better know the communities and could make sure the request is coming from the right place. The criteria have evolved a bit, but generally they have tried to make sure the resource has a reliable owner (Rep or staff because of official commitment to Mozilla) and an existing project - the community has needed to exist for 6 months. So a single person can't say hey, I want to *start* a community, give me resources. Part of the purpose of this module is that we'd have the mandate to review this process and improve it. Reps Council is too busy. > - 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? > Not all communities have the resources to run their own website. Many communities are only running a WordPress blog. Also many communities are much more idealistic and don't trust these other organizations as much as they trust Mozilla. Also, and this is a big deal to us, open can't just be about writing websites. To keep it open, people need to also be able to publish. If we provide these services on resources that we manage, we are providing our volunteers with a place to develop skills necessary to maintaining an open internet. At least two of us have gotten jobs out of our contributions to Community Ops. > - to bkerensa's point, how do we mitigate the various risks associated > with hosting content on behalf of someone else > This is a good question. We're doing it already, I'm not sure what difference a module would make. I don't know if it makes a difference that this is a volunteer managed project. However, supporting this group of people who wish to develop these skills would provide more oversight than exists now. We're Mozillians, we care about privacy and we want to do it right. As you can see from the proposal we do want support from different functional areas to provide expertise so that these sites are effective and kept to a high standard. > - 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 suppose the same way that Reps relates to Participation Infrastructure. This is specifically about providing the web services to these groups. > > 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. > Short version is, again creating a module gives us a mandate to answer these questions. I think the only other alternative is to decide we're not providing these resources at all. However if they're being provided then we need clear authority and accountability to do a good job. Happy to provide a longer version with specifics, but I have a meeting now and want to send this off. > > --david > > _______________________________________________ governance mailing list [email protected] https://lists.mozilla.org/listinfo/governance
