Hi all, I don't have too much experience with the module system, other than knowing that it exists for code, where it is fairly simple to understand. I have been excited since I first saw discussion here for extending the module system for all projects within Mozilla as I think it's a really great system and will help bring consistency, structure and transparency to the other teams and projects.
ReMo isn't simply a mailing list for people to discuss the objectives Alina has rightly listed. Take facilitating resources, for example. Part of the role of the Reps program is to distribute resources to local communities to support their efforts in promoting Mozilla. Not everyone can be a Rep, there is a screening process where we look for a certain level of skill within the Mozilla project as well as a commitment to promoting Mozilla regularly. Our volunteers sign NDAs. There is a lot that is Reps specific to oversee. As the Reps program is taking off, there is also some turbulence about how Reps volunteers are treated vs non-reps volunteers. I think having a formal module well help define where Reps fit in the Mozilla project. I also hope to see more modules for managing (and encouraging and recognizing) other types of volunteers. I agree there is overlap in the goals with the modules Alina has listed, but these are distinctive teams within Mozilla. Is there a similar example with coding modules overlapping? Either way, I don't think any module operates in a bubble, success depends on interaction. It would be great to have someone from the participation metric module help guide Reps tools and practices in that area (if that isn't happening already). We may see more and more module overlap as we include more teams. On Wed, Feb 20, 2013 at 2:28 PM, Alina Mierlus <[email protected]>wrote: > Hi, > > I mostly agree with Lukas and Axel's comments. I also don't see the > "chairman" as a module owner. > And I don't see the "why?" for a REMO specific module (together with its > submodules, including Council). > > Looking back at REMO's objectives, they are: building tools for > community, facilitating resources, building local participation. > > If I look at the Governance Module System, there are already modules like > Participation Metrics module, Productive Communication Module and other > code modules where current/former council members and mentors could > contribute (eventually as peers). > > -Alina > > > > We seem to have fallen off the list with this discussion. >> Chairmanship will rotate every 2 months and during that 2 months the >> person needs to be listed in the Wiki as a module owner? >> >> I'm definitely concerned then that this will results in potentially stale >> documentation and a tremendous lack of historical perspective for the >> Mozilla Reps module itself. The Module system seems to exist largely to >> give each module a sense of historical perspective: the hows and whys of a >> module over time. Sure, there are other reasons too but the history of >> decisions around a module's path forward seems to me the largest loss if >> ownership changes hands every 2 months. >> >> -Lukas >> >> >> On Feb 20, 2013, at 6:45 AM, William Quiviger <[email protected]> >> wrote: >> >> >>> On Feb 20, 2013, at 3:40 PM, Gervase Markham <[email protected]> wrote: >>> >>> On 20/02/13 05:59, Lukas Blakk wrote: >>>> >>>>> If the chair of the council is a rotating position, I am a bit >>>>> concerned about module ownership churn. Most of our module owners >>>>> seem to get the position and then stay attached to their module(s) >>>>> for a fairly long time. >>>>> >>>> >>>> Do you think there is a valid distinction here between code and non-code >>>> modules? Clearly there's advantage to a code module owner being in place >>>> for a long time. Is that equally true of all non-code modules? >>>> >>> >>> I would argue that it is not equally true for non-code modules. >>> >>>> >>>> In this case, it's effectively that a different peer becomes owner in >>>> each period, then goes back to being a peer. >>>> >>>> than "the current chair" if that position rotates often and I'm not >>>>> sure what that would look like. Perhaps the current and most recent >>>>> former chair so that there's some coverage from the past at the same >>>>> time? >>>>> >>>> >>>> Can someone remind us of the frequency with which the chairmanship >>>> rotates? >>>> >>> >>> Chairmanship used to rotate on a monthly basis, but starting March 1st >>> it will be every 2 months. >>> >>> - w >>> >> >> ______________________________**_________________ >> governance mailing list >> [email protected] >> https://lists.mozilla.org/**listinfo/governance<https://lists.mozilla.org/listinfo/governance> >> >> > > -- > Alina Mierlus > @alina_mierlus > > ______________________________**_________________ > governance mailing list > [email protected] > https://lists.mozilla.org/**listinfo/governance<https://lists.mozilla.org/listinfo/governance> > _______________________________________________ governance mailing list [email protected] https://lists.mozilla.org/listinfo/governance
