| articleBody
| -
asdofindia:
The people who are at the bad end of mis-behaviour of reps is not going to be vocal people like me. It is people who are new, people who are outside the communication channels, and people who have no clue that the rep is not behaving appropriately. By saying âoh, if only you had reported we would have actedâ you are just putting your head under the sand.
Iâm sorry you feel this way. Asking here not to challenge you but to understand how we can solve the problems. I hear we should be proactively asking for feedback about Reps work because people might not feel empower or know how to provide this feedback. I agree and Iâm making a note for Council to think about this. But we canât change the past, thatâs why I ask for notifying any situation that happened in the past with details in private and with the person you feel most comfortable, letâs at least investigate and fix that now.
asdofindia:
I clearly mentioned that this is not about specific events/behaviour. I wrote all this up from what I have experienced and heard from others experiences. On the other hand, I havenât quite felt/heard a lot of times about a rep doing their task brilliantly. To any one reasonable person that should be a bad smell. I donât know if your nose is working.
We have different views here, Iâve been hearing and seeing the great work a lot of Reps have done in the past year supporting important campaigns that translated into huge value for Mozilla and its mission. If this is not easily visualized, we should improve here, also adding to my notes but I would like to understand which channels are we missing.
asdofindia:
You are just being comfortable with the existing system. If you care about transparency, there are ways to make these numbers public without the sensitive things being out. What if you add a column to the reps events page where the budget requested and the swags requested can be included? The rep will have to enter that info and whoever approves the budget can also verify that they have entered the correct numbers. Thatâs just one idea. If there is a will, there will always be a way.
What Iâm hearing from you is that you want the exact figure we expend in each budget. We wonât be doing that outside the requester, we had a conversation in the past with Mozilla legal team and thatâs something we not going to disclose publicly. But this is information Reps in certain roles have (review team, Council and Module owner) to keep everyone accountable for our expenses. Yearly reports on the percentages expend by initiative and country are provided in the public for transparency. I know you donât agree with this, but this is a limitation we need to live with.
asdofindia:
Should I list down the profile of reps who have just had two âactivitiesâ in the last 24 months just so they donât get kicked for being inactive?
You can ping the Council about inactive Reps. Definitely having inactive people is not helping communities and we will reach out to reactivate or transition to alumni.
asdofindia:
Do you know how much âcampaigningâ happens for council elections? What makes you think a âdemocraticallyâ elected council is the best way to govern the reps program? (Imagine this situation. Reps council has a say in the reps program, who gets in, who doesnât etc. And then, it is the people who get in that vote the next council. And then the council has a say in the reps program. That is such a fertile ground for inbreeding depression.)
Can you make a list of cumulative term duration of each council member and other leaders of the reps program? Are these numbers going to look good when you talk about âvoluntary leadership principles and leadership rotationâ?
Module owner and peers have been working on a few proposals to make the Council selection better and basically to solve some of the concerns I feel you have about this process. You can see how the elections have been evolving over time, and now are more inclusive. Module owner and peers will continue this work and keep you all posted and gather feedback on this discourse.
|
![[RDF Data]](/fct/images/sw-rdf-blue.png)
