We actually proposed this module with guidance from other council members and with Pierros' blessing.
The services provided by this module have never been provided through Reps. We only used Reps Council to verify the "authority" of the people making the requests to make the requests. That wasn't working well and Reps Council doesn't have time to maintain this responsibility. If you read the previous messages in this thread, you'll see that David and I did discuss accountability. This proposal has been accessible to you for a long time. If you reach out to us, we would be more than happy to explain the module and the program in more detail. On Fri, Jun 17, 2016 at 3:58 PM, Rubén Martín <nukea...@mozilla-hispano.org> wrote: > Hello, > > Historically the Mozilla Reps Program has been in charge of most > decisions concerning local communities and volunteer resources (and we > still are). > > I have a major flag here since it's unclear to me the authority this > module would have to decide on them. Authority and accountability that > currently the Reps Council has and it's widely recognized as a > governance body representing the core volunteers population. > > To whom this module would be accountable to? Should it take decisions > without review from a body that represent the community? Why? > > I will run this also with the Reps Council because just recently learned > that certain decisions we are already accountable for will be under this > module and I feel we don't agree with that. > > Cheers. > > El 16/02/16 a las 16:41, Majken Connor escribió: > > I have been working with Tom Farrow (tad) and some other community > members > > to put together a proposal for better delivering Web Services to > > Communities.This would restructure the delivery of services like hosting, > > domains and emails which are currently provided to communities. Creating > a > > module would provide clear authority around these services, as well as > > allowing communities to be equal stakeholders in what services are > > delivered, and how. > > > > The module also creates accountability on the part of communities which > > will allow for better communication between resource owners and the > groups > > that provide them (eg Community Ops), faster problem solving (eg downtime > > recovery), and impact (better supported sites are better quality sites). > > > > This document is what we think is realistic plan for implementing the > > module. > > > https://docs.google.com/a/mozilla-community.org/document/d/1zXuNp8dwyLOW-UqZ4FqcRVxhszHWYqgjClDKZ5kYrTQ/edit?usp=sharing > > > > This document is a our vision of what the module could become once fully > > implemented: > > > https://docs.google.com/document/d/1YdNWOy7QNc1xXcnHGN5IW4HhRgRJCjOdKMu_gHFjUM4 > > > > We are proposing that the module be called Mozilla Communities Web > > Services, that Tom Farrow be the module owner, and that myself and > Michael > > Kohler be peers. Suggestions for additional peers are welcome, but the > > intention for now is to add people as they take on leadership roles. > > > > Questions and suggestions are of course welcomed. > > _______________________________________________ > > governance mailing list > > governance@lists.mozilla.org > > https://lists.mozilla.org/listinfo/governance > > > -- > Rubén Martín [Nukeador] > Mozilla Reps Mentor > http://www.mozilla-hispano.org > http://twitter.com/mozilla_hispano > http://facebook.com/mozillahispano > > > _______________________________________________ governance mailing list governance@lists.mozilla.org https://lists.mozilla.org/listinfo/governance
