- What is, in your own view, the Mozilla Reps program’s biggest strength and weakness?
A lot of people from different culture, languages and continents with the same ideals, promoting the Mozilla manifesto (inside the same program).
Also, not all the Reps are involved or aligned in what the Reps program is doing, so we need to let our fellows mozillians to help the program to grow, not only to support their community.
The Reps program is not anymore a way to get funds or swag but more, and we need that this important update is understood from everyone.
- Identify something that is currently not working well in the Mozilla Reps program and which you think could be easy to fix. How would you approach a possible fix?
I said one year ago the Portal, and I think the same as developer. Now also with the integration of Community Analytics is an important part of the Mozilla ecosystem because what we do is tracked and used to plan what Mozilla have to do and how is going.
In few words is a critical piece of the big puzzle that is Mozilla because what we do is used to plan what we will do later.
Only doing our bests, helping our community to be healthy, growing and get fun.
In few words we need a better report system, automatized if possible, and that every Rep as part of the task he has to do report everything. Remember if you are not reporting anything but you are doing something in any case for the Reps program you are an inactive Reps. Check https://reps.mozilla.org/dashboard/kpi/ to see this issue.
To fix that other than improve the interface and simplify we need to enforce to use it to all of us.
- What are the top three issues you want the Council to address in case you get elected? Why? How would you approach these issues?
When I will join the Council again I will continue to work on the accountability of the Council and of the Reps starting from the onboarding to the report system.
Many times I talked about how to improve the Reps portal, starting from the report system from a browser extension to prototype a new interface to maybe a telegram bot?
I don’t know right now the best solution, but we need to see who is active and about what, the report system is our core way to check it, and we need that to be more simple.
Mission Driven Mozillians will be our north star for the future, and I was already involved on leading the project for the Council. We need to do more to be ready to cover that role for all the Mozilla communities.
The Mozilla Reps program is not anymore a way to get swag or budget but a way to empower your community to grow and do their best, this three points are part of my vision that are only an evolution of my points of a year ago.
- What are the specific qualities and skills that you have that you think will help you be an effective Council member?
- An year ago I wrote: Coaching, Motivation on changes and Experience. Today I think that now they are improved but I will focus more on: Accountability of the Council, Rules changing and Experience.
- The Council can be slow and need to be supported, so we need to help as Reps and after an experience of a year (also as a Council Chair) is important to track what the Council is doing for the program.
- Rules changing, we need to adapt the program to Mission Driven Mozillians, so we need to be update many things for the challenges that are waiting us as community. As example renewability, reporting, recognition and metrics.
- Experience again because now I have also the experience of a year in the Council and a better overview of the program.
- Which of your contributions from the past 18 months had the biggest impact on the Reps program on a programmatic level?
I was part of the initiative of a year ago of Reps Mobilizer Experiment before to join the council. This helped to understand what the program has to do for Mobilizers, community mobilizers that is the focus of our program.
18 months ago I was involved also on Reps Regional Coaches defining the structure but now the project is dormant because of different priorities, again Mission Driven Mozillians.
In the last month I started to contribute back on the portal with different improvements with new little things but more an in the queue.
Inside the Council I worked on create and leading the Onboarding team, to publish the Open Letter (switched to open Conversation), maintenance of old applications still opened after months/years, working on the first internal draft for Reps Mobilizer, write last 2 all hands summaries and many other things.
- Which past achievement as a Rep would you tell your best non-Mozilla friend about?
When I joined Mozilla and my local community, Mozilla Italia, was missing in a lot of events in the country but also on internet. Now the situation is different with the help of many members of my community now we are part of the Italian Open Source movement more strong than 5 years ago.
What means be part of the Italian Open Source movement? Good question, this means that people are reaching us (for many reasons) because know that we exist.
A collateral achievement that I wasn’t thinking is friendship inside my community and in the international one. I wasn’t thinking that is possible to have friends that you met maybe twice for year, that are international also, and you talk with them daily.
- Not all Reps are using the reporting form to report their Reps activities. Why do you think that is?
Today the only way to reward Reps is checking what they are doing and is not fair to everyone to have in the program people inactive.
The accountability is important because everyone has to do what the Reps role is asking us, so to encourage them we need more mentors to have a friend to ask everything and to help to be aligned with the Mozilla mission.
On the onboarding I tried to reactive applications incomplete or without answers from the applicants after weeks or months. Now we have the rule to close or reject an accepted application after 3 weeks of silence. This is one of the things about accountability that we need to do similarly also on reporting.
We need to enforce the reporting to all the Reps and automatize the process: if you are not reporting nothing you are not aligned with Mozilla (probably) and the program so is required a specific onboarding.
I already explained above different issues of the reporting and actually for me the reasons for people that is not reporting that is self-made, not automatized and veryyyyyy boring to fill.