I have seen this issue raised in a few places. I did a quick search and don't think it's been raised here before, but please link me to past conversations if it has.
Volunteers are supposed to be the backbone of Mozilla, but there are so many "little" things that they can't do that widen the gap between employee and volunteer. This one is incredibly problematic. As a peer of the Reps program, I just raised the issue to my fellow peers that Ruben Martin aka Nukeador is making blog posts that should be coming from the council chair. (Reps blog - https://blog.mozilla.org/mozillareps/ ) The Reps program has a council chair specifically to try and raise the visibility of the Reps council and leadership. Council members take turns being the face of the program to make it easier for those not so closely involved with the leadership to recognize and put a name to the council. Ruben is paid staff and not on council, but because of the current restrictions on posting to blog.mozilla.org our council cannot blog for themselves. Core volunteers cannot speak for their teams. Only paid staff. I'd like to know if anyone is working on a solution to this problem, and if so I'd like to be sure that solving this problem is a priority, not a "nice to have." I'd also like to understand how these sorts of restrictions were implemented in the first place so that we can avoid using the same justifications to make similar decisions in the future. I'm sure there were good reasons to do it the way it was done, but if we are going to say volunteers and employees are equal, or that volunteers are core team members, then any reasons that allow us to create such a divide in privilege can't be viewed as "good enough." _______________________________________________ governance mailing list [email protected] https://lists.mozilla.org/listinfo/governance
