Hello Mozilla Community,
I’m writing to you all on behalf of the Mozilla Reps Council.
We are starting this topic to gather comments, feedback and feelings from everyone (all community members, not just Reps), we believe it’s our duty as a leadership body in the community.
Over the last months (and especially the last weeks) we have been hearing from volunteers more and more concerns about the recent Mozilla announcements. We care about community and we care about Mozilla, so we think the only way to surface this is to send a clear open letter to Mozilla’s Leadership summarizing it and asking for their answers.
Also we know some of you are no longer motivated to engage in conversations, but we ask you to give us a last chance to showcase how you feel and what you think Mozilla should do. We want this to be a transparent process and we want everyone to be part of it, so also please ask and transfer any comments you are getting from your local community.
In this topic we want to understand and we ask you to share:
- What do you feel about the current direction Mozilla is heading (including all recent announcements)?
- What do you think Mozilla should do to succeed that we are not doing right now?
Please, note that the second point is especially important in order to communicate not only how we feel, but also what the volunteer community is asking the rest of the organization to do/change.
We will keep this topic open for one week (until Saturday, 11.02.2017 early morning UTC) and then we will draft an open letter we’ll send to everyone at Mozilla’s leadership, asking them for a clear reply to our points (we’ll post a copy here too).
Also, if you don’t feel comfortable sharing this under your name you can reach out directly to us (reps-council at mozilla.com) or create an account here under another name. But please be civil and constructive in your comments, we will make sure this conversation is as productive as possible.
We will edit and summarize this first post with the things we are hearing.
How do we feel:
- Reps Regional Coaches: there were a few concerns on Telegram that people who expected to be contacted by Regional Coaches weren’t contacted (Reps Telegram Group, Saturday)
- Campus Clubs: There are concerns that “it’s not moving forward”, as well as concerns about it not supporting our flagship product (Firefox). There were a lot of comparisons with FSA (for example missing recognition program and more structure in CC) (Reps telegram group, Saturday)
- Contributor pathways for Firefox are hard, apart from “just writing a patch and see” (Reps telegram group)
- Concerns that we were ahead in the past, but we are not anymore, as well as concerns about Rust (below, striptm)
- Hard to get in touch with the right people at Mozilla. There is an expectation to know the internal workings of Mozilla. This makes it hard to collaborate with Mozilla as a person outside of the whole structure. Also there are concerns about Mozilla doing it’s own thing (conferences) instead of partnering with others. (Florian’s answer below)
- Major concerns about WebExtensions and it’s implementation timeline (irvin & yfdyh000’s answers)
- Some people don’t know how to feel about the current directions and are asking if there are any directions (Michal’s answer below)
- Given the amount of depth we have in the comments, giving them small summaries doesn’t seem to be valuable enough, we will read through everything again when we create the letter draft
What do we ask:
- Build circles of trusted friends. Don’t ask them to be Reps if they don’t have time for that. See if you can help them otherwise. Ask them to say a good word about you. See that they don’t have to become Mozilla experts to work with you. Maybe try hiring someone who built up a larger community project. (Florian’s answer below)
- Clear documentation of how the WebExtension decision came to be, start a more transparent and deep communication with Add-on developers, set a more realistic plan, better documentation and guides for Add-ons (Irvin’s answer below)
- More performance improvements like js-startup-cache and Quantum instead of Sync or Pocket, content for performance improvements, more “are we…yet” websites to track new thing, review wont fix bugs regularly to see if the opinion changed (yfdyh000’s answer below)
- Be more open. Better communication. It’s very hard to know what Mozilla is doing. Maybe create a list of projects that are being worked on in a central place, facilitate a better way to contact people inside Mozilla, better announcements of what is happening and why. This also goes for activate, campus clubs etc, there is no single place to reach those websites apart from finding them trough a search engine or link (Michal’s answer below)
- Given the amount of depth we have in the comments, giving them small summaries doesn’t seem to be valuable enough, we will read through everything again when we create the letter draft
Thanks.
–
Michael
on behalf of the Reps Council.