During the last two days Mozilla had a booth at push.conference 2016 in Munich. Push unites creative coding and user experience design, by offering a platform for designers, developers and UX professionals.
Among the things we presented to booth visitors were:
Here’s what I learned this week:
Overall, a great couple of days.
Update: Elio’s post has some additional details on #push16 itself.
Last quarter Reps council working with Participation Team begun to work in changes on the Rep program, one of them was to start new Reps Mentors work. I wrote about this project before, if you are interested in this part of the history.
We just end the first cohort training, with 11 new mentors and 1 from the existing mentors group. And now, they are working with their mentees, something that let us welcome new Reps again. We select 20 people from the list of applicants, and we ask for more patience to the people that still have their applications pending.
The training is a mix of readings and live calls. We create a guide that compile information from books and blog post from different resources, and in the live calls, we discuss that content and had some exercises to practice the learnings.
This training last for one month and a half, and just before ending it, I had conversations with all the new Reps mentors to have feedback on the training, and which things needs to be modified. The main concern was that the training seems unstructured and sometimes they weren’t sure about what we were requesting from them.
Now, they begun to work with their mentees, having their first interviews, helping them to identify their goals in the near future, building their path inside the community. And with the creation of the Review Team, these Coach don’t need to review budget and swag request for them. Just focus on their personal development and how they could be even more useful for their communities.
But, one of the main questions that we still have is: how we can measure the utility and usage of this training? How can we know that Mentors are using these techniques and if these are useful for them in their work with the mentees?
If you have ideas, please let us knowWhat we will do in the near future
This week we started the second cohort of the project. This time, we focus on existing Mentors, rather than new ones. We made a call for applications and now we have 12 new candidates, that will begin their training soon.
This training will have more structure, and more exercises. Also, we will be opening the training for Reps (not Mentors) to bring these tools to more people. And we are preparing a second version of the website, that will be available for everyone that want to read it.
We will be using the last part of this quarter to discuss how to continue this project in 2017. Our idea is that with all this people trained, we could scale faster (with more people helping on giving training and updating content and resources).
If you want to leave comments, please us this Discourse topic
Please join us in congratulating Mijanur Rahman Rayhan
Mijanur is a Mozilla Rep and Tech Speaker from Sylhet, Bangladesh. With his diverse knowledge he organized hackathons around Connected Devices
Mijanur proved himself as a very active Mozillian through his different activities and work with different communities. With his patience and consistency to reach his goals he is always ready and prepared for these. He showed commitment to the Reps program and his proactive spirit these last elections by running as a nominee for the Cohort position in Reps Council.
Be sure to follow his activities as he continues the activate series with a Rust workshop, Dive Into Rust events, Firefox Testpilot MozCoffees, Web Compatibility Sprint and Privacy and Security seminar with Bangladesh Police!
As promised to those who attended my talks these past few days, here’s my slide deck on Mozilla & Connected Devices. I do hope that you learned something from my talk. Stay awesome. If you have any questions, please feel free to leave a comment in this post. Maraming salamat po!
As a way to amplify the Participation’s team focused support to communities, we have created a project called Regional Coaches.
Reps Regional coaches project aims to bring support to all Mozilla local communities around the world thanks to a group of excellent core contributors who will be talking with these communities and coordinating with the Reps program and the Participation team.
We divided the world into 10 regions, and selected 2 regional coaches to take care of the countries in these regions.
These regional coaches are not a power structure nor a decision maker, they are there to listen to the communities and establish a 2-way communication to:
We want communities to be better integrated with the rest of the org, not just to be aligned with the current organizational needs but also to allow them to be more involved in shaping the strategy and vision for Mozilla and work together with staff as a team, as One Mozilla.
We would like to ask all Reps and mozillians to support our Regional Coaches, helping them to meet communities and work with them. This project is key for bringing support to everyone, amplifying the strategy, vision and work that we have been doing from the Reps program and the Participation team.Current status
We have on-boarded 18 regional coaches to bring support to 87 countries (wow!) around the world. Currently they have started to contact local communities and hold video meetings with all of them.
What have we learned so far?
Mozilla communities are very diverse, and their structure and activity status is very different. Also, there is a need for alignment with the current projects and focus activities around Mozilla and work to encourage mozillians to get involved in shaping the future.
In region 1, there are no big formal communities and mozillians are working as individuals or city-level groups. The challenge here is to get everyone together.
In region 2 there are a lot of communities, some of them currently re-inventing themselves to align better with focus initiatives. There is a huge potential here.
Region 3 is where the oldest communities started, and there is big difference between the old and the emerging ones. The challenge is to get the old ones to the same level of diverse activity and alignment as the new ones.
In region 4 the challenge is to re-activate or start communities in small countries.
Region 5 has been active for a long time, focused mainly in localization. How to align with new emerging focus areas is the main challenge here.
Region 6 and 7 are also very diverse, huge potential, a lot of energy. Getting mozillians supercharged again after Firefox OS era is the big challenge.
Region 8 has some big and active communities (like Bangladesh and Taiwan) and a lot of individuals working as small groups in other countries. The challenge is to bring alignment and get the groups together.
In region 9 the challenge is to bring the huge activity and re-organization Indian communities are doing to nearby countries. Specially the ones who are not fully aligned with the new environment Mozilla is in today.
Region 10 has a couple of big active communities. The challenge is how to expand this to other countries where Mozilla has never had community presence or communities are no longer active.
Comments, feedback? We want to hear from you on Mozilla’s discourse forum.
The last weeks have been pretty exciting speaking-wise. Within a month I got to visit Germany three times, kicking off this tour with Bonn in Nord-Rhein Westfalia of Germany. It was good to be back in the area after more than 5 years. Having spent 8 years of my childhood in that part of Germany, gives me a certain flavor of nostalgia visiting it. Funny thing is, I will be visiting Germany again in a few days.
Anyway, back to business. I was happy to be talking at FrOSCon (Free Open Source Conference) in Bonn about Mozilla Open Design. FrOSCon is one of the biggest Free & Open Source conferences in Germany, attracting more than 1500 attendees throughout 2 days of multi-track activities. It’s inspired by FOSDEM and has certain elements resembling it, although it features a little more of a corporate sponsor environment, which I personally support, as we need to break the notion of open source only being able to be Free as in free beer.
My talk was in the morning of the 2nd day, so I had some time to kill off and enjoy the conference. One thing I liked about FrOSCon was how interactive the booths were. Most conversations would happen there and it was a great meeting spot to get to know new people. It was especially great to meet up with Jos Poortvliet from Nextcloud and Christoph Wichert from Fedora with which I had some really insightful chats during the conference.
Unfortunately I had few attendees in my talk, due to being the first one speaking on the 2nd day (there was a party the night before, do I need to say more). However the talk was recorded by the CCC Crew and can be found on my FrOSCon speaker profile. I do think that Mozilla (and Fedora as well) need to be present with a booth next year, so I definitely look forward to that. On another note, I hoped there would be some group chat for us speakers, as I was not able to mingle in that much at the conference with fellow speakers. In my past experience, having the speakers mingle in with each other before the conference, sets a really good tone for the event.Summary
Name: FrOSCon 11
Attendees: ~1500 (total)
A month before Paarthibalaji asked for event at his college for software freedom day. It was like a long time planning to introduce more about test pilot in his college. We ( Karthikeyan , vignesh, khaleel, and paarthibalaji) started planning this long back. It is one of big event happening inside Tamilnadu. In another side Prashanth also wanted to initiate Mozilla community related club activities in his college. Both of them are active contributors who are also amazing students in their respective college. Prashanth is more active with respect to quality assurance based activities and paarthibalaji contributes more on IoT track.
Saturday was really a big day very big schedule. Paarthi woke up early and waited for us in the bus stand. Khaleel, me and Karthik joined him and reached his college. His college has really good ambience and his friends are very friendly. We started the event around 10:30, felt bit late. Then Khaleel was giving introduction about FOSS. And Karthik was getting ready for his talks about Mozilla clubs & web vr. Parallelly myself & vignesh went to lab. Vignesh was setting up the IoT kits he got, parallelly Myself and other 4 contributors who are also part of weeks of contribution started installing latest Firefox nightly in around 40+ computers and we opened Mozillatn website, so it will be helpful to know other participants for test pilot installation.
Check out @mozillaTN’s Tweet: https://twitter.com/mozillaTN/status/777046649080197120?s=09
Then Karthik helped students to know more about Mozilla campus clubs. Unfortunately due to lack of proper internet connectivity in seminar Hall he was not able to show webvr demo. Then myself and Karthik left SNS and started to SKCET. We were bit late due to huge traffic in the city. After grand lunch we started our session.
Before reached college, Prashanth has already Installed Firefox nightly in 50+ machine and he has also installed webcompat addon.
The first session we had there was how I get started with Mozilla community and how it impacted me personally. I am always very excited to say how I started and where I am now.
Then Karthik started about Mozilla campus club. Lot of students were very enthusiastic to know more about it and opportunities it have. We then had small Q&A session .
I was very amazed to see the huge crowd (75+) with lot of energy. After this we started towards lab.
In lab the plan was to introduce more about Firefox test pilot and webcompat in parallel Karthik will sharing about Mozvr will people finding bugs in website.
We had installed add-ons first and we’re explaining how each and every add-ons helping me personally to improve my browser usage experience. Then we started with webcompat part, share how to find a bugs how we can report and what all contributions we can do. Students started filling bugs they found in the websites. Some of them filled bug in Mozillatn website.
While students filling bugs Karthik was introducing them to webvr project. Some 10 students missed chance to learn but at same time there were 20+ students who stayed for some more time and was learning more on webvr and seeing the demo.
After this we started for small get together arranged for contributors around Coimbatore. We had some discussion on Mozilla Tamilnadu growth, bringing more evangelist, and some updating Mozillatn wiki pages about all events happening around.
This is the end of week 1 as Mozilla employee. Here’s What I learned This Week …An Overwhelmingly Positive Response by Mozilla Reps
Before joining Mozilla, I sent a message to all Mozilla Reps asking for their opinion on my role in this hybrid volunteer-and-staff-driven community empowerment program:
on Monday 05 Sept, 2016 I will become a Mozilla employee. Following almost 15 years as a volunteer Mozillian I was offered the opportunity to take this new perspective on the Mozilla Project. My job title is Participation Strategist and I am part of the Participation team reporting to George.
At this moment I hold various roles in the Reps Program:
– Module Peer
In my role as a Reps Peer, I have aimed to serve the ReMo program by setting direction and execution on strategic questions.
Moving forward, I’d like to continue contributing to ReMo. I anticipate that my actions will be influenced by the fact that I am a staff Mozillian. Of course I hope that this “bias” will be positive for Reps. At the same time I accept that people are sceptic of too much employee involvement in the program.
For this reason I put my roles in the ReMo program at your disposition. If anybody wants to veto against me being in any or all of the above mentioned three roles, please send a message to our Module Owner Ioana (in CC) and she will take the necessary action ensuring your privacy.
Let’s keep rocking the Open Web.
Always at your service,
Mozilla Rep, Mentor, Peer and soon employee
The answers blew me away. There were responses from many parts of the world congratulating me on becoming Mozilla staff. A huge thank you to the Reps from Uganda, Germany, Bangladesh, Taiwan, Malaysia, India, Hong Kong, Mauritius, Ivory Coast, US, Venezuela, Belgium, Tunisia, France, Italy and many others.An Overwhelming Positive Response on Social Media
Also, as soon as I tweeted and posted a Facebook update, lots of positive feedback arrived.
To all of you who thought of me and dropped me a line: Thank you! I am blessed to be serving our mission to ensure the Internet is a global public resource, open and accessible to all.
This is #3 of 5 posts I had in draft state for a few months, that I decided finish up & post. Here’s hoping my research helps others. I started writing this in May.
“Inessential weirdness of open source”
This term (crediting to Katrina Owen at Github) perfectly describes a conundrum of open participation, whereby we hold onto symbols, processes, and idiosyncrasies of open source in a mix of nostalgia, delusion and … I’m going to say it – arrogance , as the primary (nearly holy) measures of ‘being open’ in community building .
‘But’ve always done x’, is a very common response to change in open communities. Whereby we unintentionally (yet deliberately) avoid change because we believe that that purity of ‘open’ is the only way to innovate further . We even avoid change despite huge potential to grow more diverse and healthy open communities – because… there are slivers of non-open. gah!
Two years ago I ran the ‘Open Hatch Comes To Campus’ workshop at the University of Victoria. I spent 1.5 hours teaching people the skills they needed to ultimately… type ‘hello’ on an IRC channel.. Our workshop implied IRC was a critical doorway, and on-ramp to participation in open source. Saying hello, asking for help – with an instructors guidance: 1.5 hours. What?
I’ve often heard project maintainers say, that obtuse processes like these actually help ensure the success of those who are truly serious about contribution. As if asking basic questions is a holy grail of volunteering- one where only those willing to waste ridiculous amounts of time on discombobulated, obtuse processes and tools are worthy of participation. I call bullshit on any process that makes connecting with others, in an ‘open project’ – an obstacle.
“open and accessible doesn’t beat usable and intelligent”
In the last couple of years we’ve seen open communities faced with an interesting choice of using tools that work really well for working open, but are not themselves open. Github being the most obvious example. Similarly I’ve also followed the Open Data communities use of + Slack + Slackin!
Still in the voice of nostalgia asking us to remember our legacy IRC.
Anyway….what exactly do we need our community software to do? Here’s a short list I used when measuring chat solutions (and sure I am missing things)
A clever human-connection setup should allow new contributors an ability to answer these questions with some clarity:
With this criteria, and questions in mind, here are the results of those I researched for education contributors at Mozilla:
Mattermost – Has potential, but seems unfinished, and little ‘alpha’. Without installing myself ,I couldn’t figure out how to enable a Github feed.
Gitter – I discovered this when looking around Free Code Club. I liked the UI, and possibilities for multiple channels easily toggled, searchable and friendly. Plugins tend to be more developer-friendly, which was a drawback for non-technical contribution – but not a show stopper. Has a great search option for communities. Chat rooms are associated with Github Repos, which has huge potential for building communities around projects and initiatives.
I think Gitter is doing with Github, what Github should be doing for Github projects interested in nurturing participation.
Discord – I found found Reactiflux development via Facebook React’s repo, but was nervous about jumping in.
Seems more like a team project, than community. I found it intimidating, especially with voice, and it wasn’t clear what preferences where. Quickly left.
I revisited this after comments were left about this project portal being community organized (as it had been months since I was there). Aside from struggling to switch login/register status, I do have to say it’s a very easy to lurk into – and has desktop versions (it seems I didn’t have a lot of time to test). I’m not clear on how discover able conversations are outside of this app, but the community has set things up very well to ask questions in a number of ways (which is awesome). Still on the fence about voice chat, but maybe that’s because it’s harder to stay gender-anonymous with voice. Thanks for the comment that made me take another look Mark!
Rocketchat – It’s open source, it looks great – it has the potential to do what Gitter is doing for communities, but it feels very single-instance and Slack-replacement focused. Don’t get me wrong, it’s beautiful, very capable of being a good alternative but I want more – I want ‘open’ feel like more than code. If I had to choose an alternative it would be this one.
Rivr – I couldn’t find inspiration other than free, and not-Slack. Guessing it’s a great alternative too.
Slack should be thought of as first generation example of how community might meet, connect with participation and community, but not as a template, and not as a ‘bar’ that we now try to replicate openly. Reactiflux community has also demonstrated that a cohesive collection of support vrs any one solution is often the best way to go as well.
It’s time we prioritized connection of humans ‘ in the open’- lets end the inessential weirdness of open source.
On June 20th the Swiss Mozillians met in Zurich to discuss the second half of the year. The goal was to come up with objectives for mozilla.ch that are aligned with the current Mozilla strategy and the Participation Team and Mozilla Reps goals.
At first we did a retrospective, here are the key results:
What should we stop doing?
What should we start doing?
What should we continue doing?
With that in mind, we came up with two objectives. Both are aligned with overall Mozilla strategy pieces. The first one is Core Strength, the second one is Prototyping the Future. None of these Key Results are easy to achieve, but we think that with these we can achieve a good base for the upcoming years.
Objective 1: Grow our core contributor strengths and be amazing at being visible in Switzerland
Objective 2: We are a driver in prototyping Firefox for the future
Mobilizers at Mozilla, a framework for Leadership on Social Age and the programs that Participation Team are leading to bring those skills to Mozillians all over the globe
“Each person shines with his or her own light. No two flames are alike. There are big flames and little flames, flames of every color. Some people’s flames are so still they don’t even flicker in the wind, while others have wild flames that fill the air with sparks. Some foolish flames neither burn nor shed light, but others blaze with life so fiercely that you can’t look at them without blinking, and if you approach you shine in the fire.”
― Eduardo Galeano
Every one of us knows people of this kind. Many of them are in our community. When they tell you a story, you live that story at their side. Their passion is so big that it makes you realize how many things we could do together. Those people shine better with others, working and having fun with them.
Nobody is born like that. We develop those skills in our family, school or neighborhood. And everyone can learn to be that way with the right tools and the right people by our side. That’s what we want to create at Mozilla, a space where everyone can learn and improve their inter-personal skills to advance Mozilla’s mission together with other Mozillians.Leadership In Our Times
Our era is a different era for leaders. The type of leadership needed and respected today is not the same that was important and followed 10 years ago. Julian Stodd created a framework about Social Leadership, the type of leadership needed today. He describes a leader’s capacities in 3 dimensions:
Emma Irwin, from the Participation Team, has been leading an effort to «localize» this model for Mozilla. With the immense work of Verena Roberts, Mikko Kontto and Greg Mcverry, they translated those dimensions to Communication, Network and Sustainability.
They are in the process to create a Leadership framework, a compilation of resources that will help any Mozillian to learn and improve their Social leadership skills.
Because of different cultural meanings for the word leader, we prefer to talk about mobilizers, people that will help and inspire others to participate. Mobilizers are a key part in our efforts to make Participation at Mozilla better.Content In Practice
Resources are only half of the work. The Participation Team is working on different ways to bring those skills to Mozillians. With a series of Community Gatherings organized in different parts of the world, we are creating spaces to have sessions and workshops with groups of people interested in mobilizing.
In 2016 we have already organized two Community Gatherings and we are preparing for three more focused on our European, Arabic, and Mexican communities. Each of them serves as an iteration point for our sessions and workshops. Additionally we are creating toolkits to organize this type of events, so every community will be able to organize their local gathering in the future following the same standards.
At the same time, through the RepsNext process we have started a training which will help Mozillians develop coaching skills. We believe this will be useful for community development and to find new ways to participate in the Mozilla Project. I will write another blog post about this program soon, with a reflection of our first cohort of Reps Coaches.
Please join us in congratulating Prathamesh Chavan, Rep of the Month for August 2016!
Prathamesh is an extremely active and super energetic Mozillian of the Indian community. He has successfully led several different events and shown unbelievable leadership skills. One of the most recent examples of his untiring energy was the Mozilla India Community meetup 2016. His skills at managing all the logistical work for such a huge event was a pleasant surprise for all the organizers and senior members of the community.
Prathamesh is famous of going around with a viral smile. If ever asked to do some work, he does it with a smile and also makes sure that the smile virus is perfectly passed on to you…leaving you smiling as well. Prathamesh is a strong supporter of the Open Web and believes that everyone deserves to have access to it. With this thought in mind, Prathamesh also initiated the MILE project here in the Indian community. The purpose of the MILE project is to teach the basics of web to the less fortunate section of our society.
TL;DR As part of the RepsNext a group of experienced Reps has been assembled to improve Reps resource request cycle times. This will enable all Reps to have more impact. This group, called the Review Team, will review bugs as of Monday the 5th of September.
The background of the decision
It all started when we were working on the the future of the Reps program (also known as RepsNext). We realized that resources are a crucial part of the Program. In the past our budget process had been going extremely fast and easy. Unfortunately, it has slowed down due to multiple factors: 1) the program had grown but processes were not scaled appropriately, 2) Reps were not providing enough information on their initiatives, 3) mentors and council were not reviewing budgets on time, and 4) people were focused mainly on decreasing cost instead of maximizing impact.
Those factors created a lot of frustration across the program and disengagement among Reps. We also identified that we wanted to move away from just an events program to a program that would enable Reps to have all the resources needed (hardware, budget, helping documents, guidance on where to focus their energy) in order to have greater impact in their community. We want Reps to be able to do more and not constrain them. For that reason we’ve created the Resources Working Group.
Decisions made in the Reps Working Group
After the Working Groups were formed, we’ve started having meetings on early February, 2016. The conversations were long and impactful and involved both Reps and Council members.
The following decisions were made:
If you want to see how was the whole progress of the group, you could find more about it here
Reps Council and Peers Meeting Decisions
On the Reps Council and Peers Meeting held in April 2016 in Berlin we decided that we will implement our decisions step by step. First, we introduce the Review Team replacing the council for bug review. Then, we gradually start the training for our Resources Reps.
Review Team formation
In the London All Hands (June 2016) the council has agreed on onboarding 5 experienced Reps along with 1 employee and 1 council member on taking the responsibility to be part of the first Review team. You can find more about their selection criteria and responsibilities on this github issue.
The Review Team will be assembled from the following people:
The Review Team won’t take full responsibilities at once. Instead, there will be a 4 weeks transition period, where the Review Team will be coached by the council in order to better understand the needs of the program and effectively review the budget bugs.
For the first 2 weeks, the Review Team will follow all the upcoming budget requests by giving feedback as an advisor reviewer. For the next 2 weeks, the roles will be reversed: the Review Team will be the primary reviewers with the Council taking a supportive role. This transition period will start this Monday September the 5th.
Of course, we need to understand if our assumption of forming the Review Team will help us reduce cycle times in the program. For that reason, we will track approval time for budgets via bugzilla and how satisfied are our Reps with the new decision (via sending out feedback surveys to all our Reps).
Moreover, we will continue investing in the Reps Resources by working on the training for the Reps that want to join the track.
I am really happy for all the changes that have been made and more excited for what’s to come.
Special thanks to all the people who volunteered on contributing to this crucial domain
This is an immense honor and I can only pledge to serve Mozilla’s mission, ensuring the Internet is a global public resource, open and accessible to all. An Internet that truly puts people first, where individuals can shape their own experience and are empowered, safe and independent.
Over the coming months I look forward to working with the Participation Systems team on Mozilla’s Identity and Access Management agenda as well as deepening our research on Volunteer Management Systems.
Onwards, lot’s of learning ahead!
A delegation from the Philippines (known internally within the global L10n Community as the Tagalog Team), composed of four (04) Mozilla Reps, were invited to participate in the Mozilla Asian Localization (L10n) Hackathon 2016 in Kuala Lumpur, Malaysia over the weekend. The Philippine delegation is composed of Kim Domanog, Kevin Ventura, Frederick Villaluna and myself. Each […]
The post Pinoy Mozillians at the Mozilla Asian L10n Hackathon 2016 appeared first on Bob Reyes Dot Com.
With “RepsNext” we increased alignment between the Reps program and the Participation team. The main outcome is setting quarterly Objectives and Key Results together. This enables all Reps to see which contributions have a direct link to the Participation team . Of course, Reps are welcome to keep doing amazing work in other areas.
|Objective 1||Reps are fired up about the Activate campaign and lead their local community to success through supporting that campaign with the help of the Review Team|
|KR1||80+ core mozillians coached by new mentors contribute to at least one focus activity.|
|KR2||75+ Reps get involved in the Activity Campaign, participating in at least one activity and/or mobilizing others.|
|KR3||The Review Team is working effectively by decreasing the budget review time by 30%|
|Objective 2||New Reps coaches and regional coaches bring leadership within the Reps program to a new level and increase the trust of local communities towards the Reps program|
|KR1||40 mentors and new mentors took coaching training and start at least 2 coaching relationships.|
|KR2||40% of the communities we act on report better shape/effectiveness thanks to the regional coaches|
|KR3||At least 25% of the communities Regional Coaches work with report feeling represented by the Reps program|
Which of the above objectives are you most interested in? What key result would you like to hear more about? What do you find intriguing? Which thoughts cross your mind upon reading this?
Let’s keep the conversation going! Please provide your comments in Discourse.
Over the past months we have extensively worked on the future of the Reps program – called RepsNext. In several working groups we worked on proposals to improve the Reps program, keeping up with the Mozilla’s and our Reps’ needs. Following the RepsNext Introduction Video this blog post provides a broad overview of the various focus areas and invites further conversation.RepsNext – The Visual Structure
Here is a visual overview of the RepsNext structure:
With RepsNext there will be three different tracks to be specialized in:
The Functional Goals track is still work-in-progress, so we cannot provide a lot of information yet. We believe this will be a group of Reps who are heavily engaged in Mozilla’s functional areas.
Reps from the Leadership track support other Mozillians and communities through their broad knowledge. Reps in this track will regularly exchange information among themselves, creating alignment among the various functional goals in the Reps program.
For all resource requests there is a dedicated Resources track which is specialized on increasing the program’s impact. The Review team, which is part of this track, is responsible to review budget requests.
Finally, every Rep will have a coach who has strong leadership skills and can provide guidance on Reps’ personal development.
Through this structure Reps from all specialization tracks can work together towards the overall Reps and Participation goals, each Rep contributing with their particular strengths to advance Mozilla’s mission.What are we going to improve in the Reps program?
Let’s compare the current state of the Reps program with the proposed improvements.
|Alignment with Mozilla||There are no formal alignment processes with the Mozilla organization||The Reps Program is aligned with the Participation team’s OKRs. Council members participate in important planning and strategy meetings|
|Budget Request Reviews||All Reps can submit budget requests, leading to a lot of ping pong when reviewing those||Reps can specialize on “Resources” and file requests aligned for impact. This leads to faster reviews|
|Reps Activities||Reps are mostly focused on running events in their communities||Reps will be able to specialize in a certain topic (Resources, Leadership, Functional areas)|
|Mentoring||Mentors are busy with Budget Request reviews||Mentors will be focusing on personal development, no need to do budget reviews anymore (but you can be part of the Resources track)|
|Leadership||Leadership has been part of Reps since its very beginning, it was not formally nurtured very well||With the Leadership track we enable Reps’ personal development and develop their leadership potential for them to expand impact on their fellow Mozillians|
We plan to go into more detail for each of the above mentioned areas in future blog posts. In order to prioritize and invest our (volunteering) energy in the most impactful way, we need your help: Which of the above areas are you most interested in? Where do you want to hear more in the next blog post? Which concerns do you have? What do you find intriguing?
Please let us know in Discourse and we aim to come up with an article answering to all your questions in a timely manner.
Last month in 6/24-26, several MozTW community members flied to Hong Kong visited HKOSCon, Hong Kong Open Source Conference. This is our 3rd time joining the event, and we had tried 3 different forms of participation, here I would like to share a bit about it.HKOSCon
One of the event's characteristic is that HKOSCon is formed by volunteers and students, not by for-profit company (which is pretty similar to COSCUP, another open source conference in Taiwan).
Actually, according to one of the funder (and Mozilla Rep) Sammy Fung said, we can think it as a smaller (around 500 ppls) and more internationalized (English-based) version of COSCUP, which have around 2k participants and use Chinese as main language.
According to my observation, participants in HKOSCon is a combination of local (Hong Kong) enginners and students, speakers and students from Taiwan, and foreign speakers.2014 - Chinese Mozillians Unite Booth and Forum Session
2014 (March 29) is our first time to participating in HKOSCon. We tried to gather 8 Reps from Hong Kong (2), Taiwan (3) and China (3) together in the conference. We host a typical Mozilla community booth, a forum (“Mozilla communities in Chinese-speaking regions”) and a private meetup to discuss various topics about building Mozilla communities in the region.
Hong Kong is a special place that is 1) accessable by people from both Taiwan and China, without many political problems and limitations, 2) use both Chinese / English as primary language, and 3) close to all major east-Asian cities, so it's pretty pratical to be choosen as the place that we all gathered. I also experience that Wikimania 2013 (took place in Hong Kong Polytechnic University) also take the advantage to gathered many China / Taiwan contributors. Singapore has similar advantages but it just 4 times far away for us.What worked and what didn't?
The idea of unite the Mozillians from different places really works, and I believed that we need to do it more (re-engage MozCamp perhaps?) But next time if we want to take HKOSCon as a chance, we may need to plan a whole dedicated day for Mozillian meetup, to work longer besides participating inside confernece, to get into more detailed discussion. (which may look similar to Leadership Summit and MozCamp beta in India?)
Here is my debrief about our participation in HKOSCon 2014,
In 2015 (June 26-27), we take a different approach that bring more Taiwanese Mozillian to get involved to HKOSCon. Total 7 Mozillians (5 Reps) joined. This year we also focus our most effort on the booth, and I personally host a Webmaker workshop.
The theme of the booth is FoxYeah campaign, we asked people to take selfie photos with 5 FoxYeah banners and received stickers. Most participants already know Firefox and was our user, so we would like to recall their attention back to the core value of Firefox.
For the Webmaker workshop, due to the design of the room and session length, it's not really work out well. Also I feel that Webmaker is not really suitable for this developer-focus conference participants that it just too simple.What worked and what didn't?
Designing a more interactive booth event worked really good, we had interacting with many graceful people at the booth, and got more then 40 “FoxYeah photos”.
Webmaker workshop which focus on education and entering level of contributors not work. The main participants of HKOSCon are more engineer based (far more then COSCUP) and we need our workshop to be more technical for them.
Here is my debrief about our participation in HKOSCon 2015, you can also find the link of articles from other participants inside.
Because that we didn't set a booth, it's hard to evaluate how many attendees is interesting in participating Mozilla this time (compare to the previous 2 years that we had contributing forms at our booth).
But the Fuzzing and Othree's HTML5-related sessions, as well as my session did attach many people and I can feel overall better response then last year's workshop. Another reason of the better atmosphere at sessions may due to several OSS participating-related sessions had been organized next each other in schedule, and thus attached the right audiences.And suggestion for the future...
From our previous experiences, here I come up with some suggestions for next year,
Bring in more foreign technical speakers
There are more developers in HKOSCon that is interesting in technical topics, engineering speaker can have better interaction in HKOSCon, things like “how we use Rust” or “How do we do Firefox release engineering” should do well there.
Booth is necessery
With only session, it's hard for us to interaction with all partcipants, booth does that well. Besides giving out stickers and demonstrating hardware / flyers, plan a simple event such as FoxYeah photo campaign in 2015 will please everyone.
7~10 Mozillians is good numbers for participation
We had around 10 Mozillians (excludes local HK Mozillians which are all dedicated to run HKOSCon) in both 2014 and 2015 HKOSCon, 5~7 of them are volunteers. It's enough to both manage a booth and give 3 to 5 sessions with this numbers, and the rate of Mozillians to all participants would be around 2%.
This is part of the result we found from the “How might we (re)invent existing and future MozSpace to run innivation experiments”, which we address different kinds of community space at the community space session on Mozilla AllHands 2016 in London.(see original draft poster from our discussion) The characteristic
There are different types of spaces with various characteristic, eg.
Following is the space various in different type that we found in our expereinces and in different region, it may be a of community space (and probably also same for the community meeting).
Temporary (in time & venue) spaces
Physically communtiy space
It was begin when some people who is interesting in promoting Mozilla and it’s various products gathering and meet online.
Some people may want to meet face-by-face hacking / discussing frequenly
If there are more contributors within in the city, they may able to meet weekly / bi-weekly / monthly and maybe more leisure with loose agenda ccording to the meeting frequency
When more contributors focus on some contirbuting regions, they will run some hackathon / design sprint periodically
If there are some contributors or remoties work more frequenly and host more events, they may want to find a permanently / half-permanently space. We find that sometimes there are good cooperating and supporting from local co-working space.
Similar to the above co-working space, there may be some hackerspace / makerspace already exist and in good align with Mozilla’s mission, the community may like to join or get involved the venue.
We should have some application procedure at this stage, for communities who is interesting in get into next stage of pathway.
After all this stage, the community now has more people and frequenly events and many meetups, they may want to get their own community spaces in order to better hosting and contributing.
The most important thing in this stage is that besides benefit Mozilla community, we want to also help / support other communities within the region, in order to better using the resource, and they most probably also under their early stage of this pathway.
# of core contributors - 10~20 scale of community - 50~ # of non-Mozilla communities involved - 10 and more meeting / event frequency - daily, bi-daily density of the region / distence of the contributors - within city resource invest from Mozilla and community - large monthlySpace inside Mozilla office
If we have more and more remoties working at Mozilla during the growth of the Mozilla community, eventually we will set up a Mozilla office inside the area. It will be similar to the community spaces and have good community-staff relationship if we follow and grow alone the path.
Above different kinds of space is a typical pathway we found in different communities and in our community's 10+ years experience. We had pass all of those stage (besides the office one), and some other communities may currently in one of the earlier stage.
It’s like the flow of the river from upper reach to the ocean, we can imaging the flow as the size of the community / the resource / the reach and the impact. Different communities are not necessery follow the same pathway but it should be somehow similer.
Thanks all of the Mozilla Community Space stewards in the session, especially Henrik, Gaspar, Nikos, Yofie who is in this discussion.
we, we, we, we, we. How can Mozilla talk about “we” when “we” don’t even know what’s going on? - ElioI'm pretty agree the echo from BobChao's comment to Elio's blog post. We had a serious problem here and we need a little more TRANSPARENT PROCEDURE to fix it, just as our manifesto indicated. "Transparent community-based processes promote participation, accountability and trust." And we does need some more participation now!
This is #2 of 5 ‘Draft’ posts I identified as worth wrapping-up vrs. ‘forever a draft’ status.
I wrote this post in April-ish, based on notes I took attempting to reach my goal to contribute to 10 open source projects by July. Some unexpected challenges in my life made this goal impossible, but I still learned a lot… maybe next year.
In January, I set a personal goal of contributing to 10 open source projects by July. A research project of sort, I wanted uncover tools, processes, community engagement, and unknown magic existing beyond my own knowledge and experience. By exploring and researching the modern day experience of contributing to open source, I imagined I could get much better at designing for, and teaching it…
I pledged to myself that I would be select a projects where I could answer the following questions
“I can understand the value of the project on things I care about”.
“I can see how my time might help impact the outcome of that project’s goals, however small”.
Walk a Mile, See a Mile.
I also promised myself, that I would release all arrogance, bias and (most) opinions of how a project might be setup. I adopted “Walk a Mile, See a Mile” to remind myself that the journey towards designing better for people, means being open for what comes next – I would grow with the experience.
In this, my first three months of contributing I’ve already had plenty of adventure.Searching & Finding
My search started leveraging Github ‘Trending Repositories‘ – something I’ve heard recommended for new contributors. The search is limited to filter for language, which already limits this function to technical contribution – which is too bad.
Suggestion to Github – allow projects to tag their repositories with types of contribution available.
I also wanted to find SQL/PLSQL contribution opportunities, but the top trending project had a commit from two years ago. Maybe that’s just my old timey- skill-set speaking ;)
Suggest to Github – define ‘Trending’, or limit results. Wasting time on a dead or old project isn’t a good experience.
Finally, to fulfill my goal of ‘understanding the value’ of a project I am limited to project descriptions, which was hard.
Suggest to Github – provide optional description that states value of project for contributors, or FOSS projects agree on a CONTRIBUTE.MD standard field any query on the web can pull from (omitting Github as a search). We really need better standards for participation. Blarg.
I went through a lot of repos, opting to select only one from Trending, and the rest from referrals or personal interest, which shows you how much we still suck in OS at surfacing projects people can find in their own. I’ve landed on these 5 to start:
Including a link from your repo, to your project webpage, or demo is important.
I hated wandering through code, and issues looking to see what a project looks like, or does. I wanted to get in there and play.
9 out of 10 times I will opt to join a chat channel over forums. I’m in a rush like everyone else, so if I can :
a) see conversation
b) ask a quick question, I’m more likely to stick around for a bit.
Free Code Camp does this well, having both on the main page. I’ll have another post on the different chat software I saw, and liked.
Forums felt like a ‘community resource’ (which has a place) when I visited them vrs a way to engage with people.
Welcome bots, that say hello to new users are awesome, but one of the reasons I also use an alias when lurking. Chat should allow for lurking.
Project-specific newsletters are awesome. I didn’t realize how helpful it would be to have a project news letter (for times when I am too busy to contribute). Rust does this well!
Environment builds are still the worst part of ‘sticking’ to a project.
Marc was almost ready to implement his "hello world" React app pic.twitter.com/ptdg4yteF1
— Thomas Fuchs (@thomasfuchs) March 12, 2016
I am familiar with many technology stacks, and debugging but I have so far found myself stuck on obscure issues that even the most helpful people can’t get me over in a short period of time. Thinking of limiting build-problems to max of 6 hours before abandoning project. Main reason I seem to get stuck – outdated docs, missing dependencies, or worst (in one situation) building the WRONG environment because Google search brought me to an outdated wiki that had not been noted as so…
I like the idea of Virtual Machines, but I’ve found outdated ones of those as well. Perhaps Facebook and React will provide a new way to help overcome environment first-builds.
Too many ‘Garbage Tasks’
I’ve called these out before. A good first task should not look like this. Remove this label when it’s not longer true. Good first tasks are basic like – changing an error message, or debugging CSS alignment.
‘Help-wanted’ tags aren’t enough to invite new contributors – I needed to see ‘beginner, quick task, or something similar’. Maybe I have less patience than others.
Non-Technical Contribution Is Hard to Find
Really, really difficult to imagine the ways you can help if the project is not specifically about that skill. There’s an entirely different highway for non-technical contributors, and that sucks especially if you are interested in both.
I realize if I wanted to contribute in other ways, that would be different research altogether.
Good Documentation & Support
Free Code Camp has a great contribution page – and I LOVED their Gitter had help commands that allowed people to learn more about contributing, and that they have a specific chat just for contribution which is less intimidating than joining a project team chat head-down in a crisis. I know IRC does this, as well, but IRC is a blocker for many.
Jekyll is also really clear.
I LOVED finding this post ‘Diving into Rust’ from community-member Flaki. Describing ‘use cases’ really compelled me to get more involved in a project that had felt a bit abstract to me still. Found via Google-search. I found this page on Rust documentation a bit too much for getting, although I expect it’s a great resource to come back to.
Again, chat channels not forums were my go-to for project questions.
Code of Conduct Matters
Seeing a code of conduct, like the ones in exercism.io and rust made me feel welcome, not just because it’s there, but because the community decided it should be. I’m glad Jekyll had a COC, but without a clear path for resolution, other than project maintainer – it felt only half-way there. There are people much better than me to review CoC but I’ll say personally, I prefer to know who is behind an alias as well.
And that’s what I’ve learned, and experienced so far. Next post will dive deeper into evaluation of chat channels.
Open Has Walls
An update on one other project, I am very interested in (eventually) lending my skills to beyond this experiment is with #OpenCancer. Creative Commons has joined forces with Moonshot to end cancer in our lifetime. The simple question of ‘how can I help scientists, and others using my technology/open/participation/data skills hasn’t yet been answered. Is open science limited to teaching researchers, or is there a bigger movement to get the rest of us involved? I hope so in this case. Another research project perhaps.
I realize .. we’re only really at the beginning of making participation in open projects feel as accessible for everyone. Its hard climbing the walls of open some days, but we’ll get there.
❝The limits of my language are the limits of my world.❞
So last year myself along with other contributors started Weeks of Contribution Program for contributors around MozillaTN . This blog post about the first training session of 2016 Weeks Of Contribution.
As per the plan WOC’16 started with Tamil Mozilla Localization and Translation. Yah!!! :) both First and Second sessions went fine, by I had lot of learning in teaching new contributors and encouraging them to contribute.
Contributors who attended the Hangout sessions:
Discussed topics :
Hangouts session takes almost 2+ hours to finish. The time denotes the strength of the discussion. Almost all the participants raised their questions during the session.
Main agenda of this WOC’16 is, the people who attended the hangout session should contribute first then they have to train some people in their locality. So every person took responsibility to teach minimum 5 people.
Suggestion made by contributors in both Pootle and Pontoon:
Yahoooooooooooooooooo its around 4989…. almost we reached our target…. yah we targeted to suggest 5000 strings in two weeks….. We made it…
Its my pleasure to thanks Vishwaprasath who mentored this team. Thanks ge!!! And my sincere thanks to all my TA_FoxTeam who made this great achievement.
I’m expecting you guys will continue your contribution in future.
This is #1 of 5 posts I identified as perhaps, being worth finishing and sharing. Writing never feels finished, and it’s a vulnerable thing… to share ideas – but perhaps better than never sharing them at all?
I wrote most of this post in April of this year (making this outdated with the current work of the Participation Team), thinking about ways the learning format of the Leadership Summit in Singapore could evolve into a valuable tool for community leadership development and credentialing. Community Leadership Passport(s) perhaps…
At the Participation Leadership Summit in Singapore, we designed the schedule in time blocks sorted by the Leadership Framework. This meant that everyone attended at least one session identified under each of the building blocks. The schedule was structured something like this…
As you can see, the structure ensured that everyone experienced learning outcomes of the entire framework, while still providing choice in what felt most relevant, exciting or interesting in their personal development. You can find some of this content here.
I started wondering..
How might we evolve the schedule design and content into a format for leadership development that also provides real world credentials?
I don’t think the answer is to take this schedule and make it a static ‘course’ or offering, I don’t think it is about ‘event in box’, but I do think there’s something in using the framework to enforce quality leadership development, while giving power to what people want to learn, and how they prefer to learn.
Merging this idea + my previous work with participation ‘steps & ladders’ into something like a passport, or series of passports for leadership.
Really, this is about creating a mechanism for helping people build leadership credentials in a way that intersects what they want to learn and do, and what the project needs. It could be used for anything from developing strong mentors, to project leads in areas like IoT and Rust, to governance and diversity & inclusion. Imagining Passports with 3 attributes:
Experience – Taking action, completing tasks, generating experiences associated with learning and project outcomes. Should be clear, and feel doable without too much detail.
Mozilla Content – Completing a course either developed by, or approved as Mozilla content. These could be online, or in person events.
Learner Choice – Encouraging exploration, and learning that feels valuable, interesting and fun – but with some guidelines for topics, outcomes and likely recommendations to make things easier. For example, some people might want to complete a Coursera Course on IOT and Embedded systems, while others might prefer a ‘learning by doing’ approach via YouTube channels.
Something like a Leadership Passport would obviously require more thought in implementation, tracking and issuing certification. It could also be used to test and evolve Leadership Framework. I prefer it over a participation ladder because it feels less prescriptive in ‘how’ we step up as leaders and more supportive of ways want to learn and lead — and ultimately help us recognize and invest in emerging leaders sooner.
Image Credit: Kate Harding – Quilt of Nations.
Please join us in congratulating Alex Lakatos as Reps of the Month for June 2016!
Alex is a Mozilla Rep based in London, Great Britain, originally from Romania. He is also a Mozilla TechSpeaker, giving talks all around Europe.
In the last 2 months Alex held several technical talks all over Europe (CodeCamp Cluj, OSCAL in Albania, DevTalks in Bucharest and DevSum in Sweden just to name a few) to promote Mozilla’s mission and the Open Web. With his enthusiasm in tech he is a crucial force to promote our mission and educate developers all around Europe about new Web technologies. He covered both the transition we are doing shifting from Firefox OS to a more innovative area with Connected Devices but also changes in Firefox and why you should consider the improvements made on the DevTools side.
As part of organization’s aim to increase developer awareness and adoption of the Web, Firefox, and Mozilla through a strong community-driven technical speaker development program, the Mozilla Tech Speakers Program was created. Mozilla Tech Speakers is a Mozilla Developer Relations (DevRel) program to educate, empower and give back to volunteer Technical Evangelists in regional and […]
The post Joining the Mozilla Tech Speakers Phase 2 – Summer 2016 appeared first on Bob Reyes Dot Com.
Please join us in congratulating Konstantina Papadea as Rep of the Month for May.
Konstantina is a long-time Mozilla Reps from Greece. Additionally she is also responsible for the budget and swag requests in the Reps program.
In the past months Konstantina has helped out with organizing and chairing the Reps weekly call together with Ioana. Further she is helping the Council with the formation of the Review Team we are implementing.
Mozilla India is one of the biggest contributor community and vibrant one. For past few years we are growing very strongly and consistently. Last year 2015 was very amazing year for us, after Taskforce meetup, we contributors had ambition to bring much more contributors, due to this aim number of student contributors grown to huge number due to this everyone had some confusion like how to report the events and contributors they have brought and events they have done, then how to highlight the contribution done by the contributor near them, this should some ways to bring regional communities. Even we in Tamilnadu started a small regional community named MozillaTN with the aim to highlight the contributors in our Tamilnadu so it will be exciting for others to contribute on seeing them, like me everyone had aim to not to move out of Mozilla India community goal. So to make sure the amazing contributors are recognized and everyone goals are align we had Community India planning meetup.
I reached bit late to session on first day, joined from session handled by Haiyya where we learned more about Story telling. It was one of awesome session where we learnt more about us and to project us.
Then George jumped in and started to share what are the vision of Mozilla and Mozilla’s area of focus for the next 6 months. Shared those amazing areas below
Then we divided among us into 5 different groups to learn what are these areas and to share with remaining other contributors. I had opportunity to form team with Ankit and Faisal, one of amazing people. Had good time to interact with them and work with them.
Among those areas listed above, I am glad I am closely following what happening at 1 & 3, then trying to learn 2.
Then we had the design session on forming the Task Force teams. Before that we got to know how the Mozilla India task force team was started and what was its goal by Vineel and Deb. These two are amazing people who used to come forward first whenever we need any help.
Then again we divided as 5 members team and started working on how we should have the task force team for Indian community in future. This time I was sitting with Vineel, Mehul, Prathamesh, Anivar and George was note taking all the points we were discussing. Then the consolidated points were shared by George and Vineel
Some of my suggestion was, there should be an easy way for all sub communities to inherit task force model, functional contribution areas should be there in task force team, and then there should be a team which can work with all the team to work on exciting projects and get it done.
Then we had quick discussion on what happened on that day, and we had grand dinner at hotel and then left to where we stay. And amazing group photo at venue.
Then next day we started the main session with what are the goals of Mozilla India community meetup, tentative date when it will happen.
So my suggestions were like finding new ways of recognition (letter or appreciation , Linkedin recommendation and so on), determining ways for cross sub-community communication. Then we got a chance to learn how Mozilla India community started, which is an interesting and surprise session by Vineel. His talk was always well organized, calm and exciting.
Then we got chance to split and take some amazing responsibilities to work for upcoming days. I got chance to contribute as Regional Co-oridnator along with Mehul, Akhil. We three are responsible to check whether our learning at this Meetup is shared, finding exciting leaders from different parts of countries to share what happened at planning meetup and will also pull up some other ways to contribute, planning to contact various Mozilla Employees with whom I am in touch to know what is their teams focus but for this role also we have an amazing team (staff / functional team) members Sayak and Anivar. There is logistics team which includes Prathamesh, Chandrakant ji , Sayak who is going to take care of the upcoming meeting, they are responsible for making meetup huge success and to document whatever happens we have Ankit, Kailas, Harsha and the we have to do facilitation during meetup and bring amazing contents for that we have very huge team of 5 members Mayur, Anup, Priyanka, Meghraj, Diva, and there is an amazing team who is going to find the shape of taskforce team and form structure of Mozilla India Deb, Vnisha, Prathamesh, Vineel, George +2 people (from the broader Mozilla India community who show great interest and meet).
Then we were discussing how the contributors should be in general, we had some of the amazing selection criteria shared to Mozilla participation team. It was very interesting to sit and discuss with Deb, Sayak , Anivar and Diva regarding this and share our thoughts.
Some of the learning from this meetup is we should have Clear point and should know well to express them, it comes by experience. And a good community members loves to hear form other and then gives positive suggestions. There are contributors who are very committed to the mission and what they contribute, it is purely not committed in terms of hours but it is whole hearted.
I had chance to interact with Chandrakanth ji, he is one of amazing person, helped me whenever i got lost in Pune. I used to talk with him in telegram, finally got chance to meet him. He was interested to mentor amazing contributors who are ready to learn new things and contribute to community. Hope I can find contributors here, so we can learn from him.
I should say thanks for Sayak who was there with me till my flight.
There are many contributors around India who are committed, have lots of energy to contribute and share their knowledge and motivated to take amazing initiatives. It may look like India has lot of sub-communities but we are always standing together to contribute and share our knowledge to others. The upcoming meetup will be bringing lot of new contributors who were learning and talking in online to meet offline, it will be amazing days to choose what we will be driving in our contribution areas. The new journey is about to begin soon with amazing Goal settings and learning.
Hope we all may aware that Mozilla India Planning Meetup 2016 was held on 09-10th July 2016 in C-DAC Pune, India. This is an invitation only event hosted by Mozilla India Community with people from different sub communities based on gender diversity, regional representation, activities and leadership in community. This event will mainly focus on developing options for the direction, vision, strategy and roadmap of the Mozilla India community, and undertaking detailed planning of the second phase that involves the tentative Mozilla India Gathering in Pune, August 26-28, 2016.
Here I am going to write the full report of each and everything that was happened in the event.
This event was super excited for me because of two reasons, I was happy to part of this event for revamping the structure for Mozilla India as well as it was great opportunity to meet some enthusiastic Mozillians around our Mozilla India community.
Here is event agenda.
We started our very first day by filling out one survey based on our experience as a Mozillian – this looks like we are giving an exam. Our awesome fellow mozillian Ankit collected all the survey papers.
Then we were taking opportunity to introduce ourselves.
First of all a big thank you to Haiyya for coming here and facilitating this event.
Then Haiyya organized a fabulous session on story telling – how we can inspire, motivate other mozillian by describing our story.
After that George started sharing about the direction of Mozilla, and 5 important areas of Mozilla’s future strategies.
Reference docs for 5 important areas of Mozilla’s future strategy
Then we have been divided in five group and worked on future strategy. Then we showed our working templates to others.
Here our team was showing our strategic planning on Mozilla Leadership Network.
After that Veteran Community Mentor and Leader Vineel shared growth story of Mozilla India, that was inspiring.
At last we had a discussion on redesigning of Task Force though different ideas.
Here my team was proposing tightly structured design of Task Force. Though this is not final structure. In next week or so, we will open it for every community members to vote or comment on the available proposal/structure to make it more transparent and open. Stay tune for that.
After that we concluded this event by sharing what we have learnt from that day.
This is how the event was ended. Then we headed to Mainland Chaina for dinner.
On the second day, we were gathered in opening circle by sharing our insights of last day event lessons.
That day was truly focused on main meetup. So we immediately started planning on goals.
Then Vineel, Ankit, Vinisha and Kailas helped to categorized it in few topics.
Then again we were divided in 5 teams and each team worked on each. Here are the draft sheet of each goals.At a glance – drafted goals for the meetup
After working on planning, we started working on criteria of participant’s selection for the main meetup. Though this is not final. We are working on this.
Then we selected date and place for the upcoming meetup. Name has not been selected yet. Hope very soon we announce name of event with every details.
After that we started creating working groups for planning the main meetup. Every working group has built a roadmap for the next 6-weeks.
Biraj, Vishal, Ashish, Siddhartha, Shaguftha
Prathamesh, Chandrakant, Sayak
(3) Regional Coord + Invitatations
Mehul, Akhil, Viswaprasath
(4) Staff/functional coordination
Ankit, Kailas, Harsha
Mayur, Anup, Priyanka, Meghraj, Diva
(7) Strategy/Structure for Mozilla India
Deb, Vnisha, Prathamesh, Vineel, George
Communication working group’s draft roadmap for 6 weeks is here
This working group is focused on Strategy/Structure for Future Mozilla India
Deb, Vnisha, Prathamesh, Vineel, George +2 people (from the broader Mozilla India community who show great interest and meet).
Then we concluded this event by committing to bringing this meetup back to our local communities. That’s why we need to host MozCafe as soon as possible with every regional community.
Special thanks goes to Grorge Roter, Umesh Agarwal, Faisal Aziz, Shahid Ali Farooqui and whole pune community for organizing this wonderful event.
After all, we got huge success in this event. But we have to do lot of work.
“We have rebooted now!
Let’s run the program” — This is my quote.
All Pics were taken by me and Harsha.
Though this is very long but I tried to keep it more productive by using more pics and less text.
Hope you enjoyed reading my blog.
Its been a long time since i write any blog post about my contributions and now am excited to share this with you. There you go!
What I really like at Mozilla is the diverse community and the contribution paths. A couple of months back, I have been accepted into REMO- Mozilla Reps program. I am excited to continue my contributions as a Rep now.
Cut to the chase, it’s been around 6 months since I took the responsibilities of Telugu localization. Now, I am glad to publish the growth of statistics for my locale. When I started contributing to l10n, these statistics are very poor compared to the locales other than Indic-locales and the rate of retention of contributors is very less. To make it better, I started working on it.
Report from last 6months for Telugu locale:
Over 10 contributors helped us to achieve these goals from the last 6 months. I really appreciate every one for their contributions. Special thanks to our all-time SUMO stars Sandeep and Jayesh for their awesomeness.
Telugu l10n projects:
These are the few projects which we worked on/still working. In the first half of 2016, these are some of the projects which we kick-started and localized completely:
And we are still working on few other huge projects.
Overall 15000+ out of 16967 strings have been localized so far from telugu team in which 5000+ strings are localized in the previous half of 2016 in pontoon and in mozilla locamotion. Since, our localizers are very much comfortable with pontoon, we are likely to request few more projects to pontoon platform soon.
I hope our team will hit few more goals in the next half of 2016.
Thank you everyone for your support!
Recently on June 25th Black corporation founder & CEO introduced Salem startup space. He had a very good aim of bring knowledge on different domains and skills to Salem community. It was really an exciting day and an amazing day to get started for Salem folks.
I also attended event with aim for learning about people who are in my native. It was really amazing to see lot of ideas related to IoT and software startups jumped in. It was nice to see young amazing entrepreneur at that space from Salem.
I have shared this news about meeting to the trainers who are in #MozillaTNwoc16 are around Salem. At first three told they will be joining, so I thought I can discuss about the improvement and taking the community to next level, but on that day only 2 trainers turned Bhuvana meenakshi and Ashley rose, paarilovely had some issues so he was not able to come to meet on time. And those 2 people have brought in around 8 other young students who willing to learn amazing things.
On that day I was introducing people about what are all contribution I get started and where I am landing now, what’s my future aims for contribution to all the audience. Then at the end of the meet up, I personally called both the trainers and sharing what’s our aim of weeks of contribution, what we planning to achieve and how we can build our community. And was discussing how we can try to use this space for doing events related to Mozilla.
I was very happy to meet another 2 trainers in the list. I was very happy to share my knowledge and get feedback from people in building our community.
One of our plan was to host all the events in weeks of contributions at the Salem and specifically we are planning for 1 day specifically hackathon session related to web extensions during August 15th.
In previous post I shared about #MozillaTNWoc16 after that I wanted to meet all the trainers and mentors who are participating. It will be very helpful to talk in detail for an hour in person and learn more what they think about Weeks of contribution and in general contribution to Mozilla.
It was actually sunny day on 20th June at Chennai, Makilan has came to Chennai to do his project work a week before our meeting. He was about to leave Chennai and told he would like to meet me in person, seriously I have not meet many Mozillains in tamilnadu who are currently active. I was very happy to know he wanted to meet me. Since I will be working at office he told he would like to come and meet there, thanks to him since I use to concentrate more on code in the evenings, he didn’t make any changes to my schedule. He reached around 4:30. Then I took him to nearby restaurant (A2B) pretty decent one in Tamilnadu. We ordered some foods and then started talking about contributions. Rain started all of sudden and we were enjoying our talk and food.
He was asking review about social media channel he is maintaining and about sharing birthday wishes to our region contributors, it’s seriously an amazing idea he brought which is making many contributors to engage more with our social media channels. Then he was talking in general where he can focus more and what are plans for weeks of contribution. Then I was enquiring about his project he done at Chennai. His project was very exciting one[ will get his post and update soon]. He was one of the different background person, and as very little number of contributors think he used to think different and wanted to take internet and contribution awareness to remote places and wanted to train people who are willing to learn and give back. He was also discussing about extending weeks of contribution program structure to build community in his college.
It was really an exciting day, and he is first trainer of #MozillaTNWoc16 I have met. Was very happy to know about him and meet in person, his goals are very amazing to learn and get enriched.
What is loud, intensive and full of Mozillians? No, not (only) beer parties, it’s the Mozilla All-Hands! With June approaching, all Mozilla had the pleasure to meet again in a single place for their bi-annual All-Hands (former Work Week) to GyShiDo within a couple of days. This All-Hands was held in London (funnily right before the Brexit referendum) with more than 1300 Mozillians attending (over 100 from them were volunteers). I am privileged to be invited again this time, with Mozlando being the first All-Hands I attended last year. Unlike last year, I was invited by the Marketing Team though (Participation invited me last year) as part of the Open Design initiative. I am proud to represent the Mozilla Albania community at Open Labs and I hope other local contributors to join in the next All-Hands. The merits are not my own only after all.
However, this time, we were slightly more Mozillians, divided into 3 different hotels and venues. Parallel sessions and ad hoc meetings were on every day’s schedule. A great touch was the fact that we could get lunch in any hotel (which we ended up anyway, as a lot of teams had meetings during lunch). Walking from one hotel to the other was a bit of repetitive though, but we got used to it (7-20min walk from one to the other).
Tuesday started with a Plenary in Dr. Who style. Mark Surman got on stage with the help of the Tardis and opened the plenary with some great talks followed by Chris Beard and Mitchell Baker.
Everything became quite intensive after that. Many meetings at the same time to attend, Birds of a Feather sessions, people to meet, it was chaotic and I loved it. It also felt quite weird as most of my Mozillian friends expected me to be part of the Participation sessions, unaware that I was part of the Marketing team this time (and I’m really happy to see more volunteers invited by Marketing this time!).
It was funny to also see how lower the T=Shirt quota was in the marketing team compared to Participation. Loved the diversity between teams here. We had a fireside chat with Chris Beard as well, who took the time to hang out with contributors after the session as well. You could expect from the CEO rushing from one session to the other, but I loved the way Chris sets some time aside for everyone. Not many executives do that.
On Wednesday we had the Open Design exhibition where the Creative Team showcased the process behind Mozilla-s rebranding where every attendee could chime in as well. You can check out my blogpost regarding Community Design (now Open Design) at Mozilla related to this. The press has also covered this quite well.
We introduced the new Brand Guidelines for all projects across Mozilla and are working with teams to get their visual identity aligned accordingly. It was great to meet with the Creative Team in person and work on the future plans regarding Open Design in the near future.
Further, meeting with fellow TechSpeakers was another highlight for me. If Mozilla is an extended family, TechSpeakers would be one of my favourite cousins. We had various meetings and drinks together and prepared for the coming plans of the next TechSpeakers pilot and Meetup in Berlin in September. Havi and me facilitated a Public Speaking as a Service session as well, which went splendid with a small, but very interested group of people joining!
— Mozilla Hacks (@mozhacks) June 16, 2016
Meanwhile I’m preparing for a few other conferences I will speak as a TechSpeaker in the coming months as well.Wrap Up
Getting through all this procedure with my UK visa was worth it at the end of the day. MozLondon had a unique atmosphere and while we Europeans could have our revenge on the Americans getting some jetlag finally, it was a great productive week which boosted the moral to keep doing what we are doing.
Bonus: You can find the photos from the whole week on Flickr, including the fantastic Steampunk party.
In the following are the event reports of fellow Mozillians, as reporting on the whole event centrally is impossible:
A few months ago we rolled out bulk actions in Pontoon, allowing you to perform various operations on multiple strings at the same time. Today we’re introducing a new string filter, bringing mass operations a level further.
From now on you can filter translations by author, which simplifies tasks like triaging suggestions from a particular translator. The new filter is especially useful in combination with bulk actions.
For example, you can delete all suggestions submitted by Prince of Nigeria, because they are spam. Or approve all suggestions from Mia Müller, who was just granted Translator permission and was previously unable submit approved translations.
See how to filter by translation author in the video.
P.S.: Gašper, don’t freak out. I didn’t actually remove your translations.
So last year myself along with other contributors started Weeks of Contribution Program for contributors around MozillaTN . The first version went fine, by I had lot of learning in teaching new contributors and encouraging them to contribute. At end of 2015 Weeks of contribution we saw 15 new contributors, detailed report is available in one of my previous post
This year again our MozillaTN community is doing Weeks of Contribution. We are making some serious changes to take care of new contributors and yes we are setting some goals in the 4 contribution areas Localization, Support Mozilla, Quality Assurance and Add-ons.
This year I am going to handle Add-ons development along with some bug fixing, planning to help young developers and bring around 25+ add-ons from developers around Tamilnadu. Khaleel will be taking care of the Localization where he made a target of 5000 strings converted by end of 2 months, he has also planned 2 offline events. Karthick has planned to share his knowledge with respect to Support Mozilla, his target is to achieve 40 KB articles translated. Adam and Prashanth are planning to host Firefox test days. So for next 2 months our community members will be busy with learning.
Why these 4 areas alone
There are large number of pathways in which we can contribute to Mozilla Community. For very long time in our community we saw the number of contributors in Localization and SUMO is decreasing and it is very important to have browser in Tamil and support articles in Tamil so we are doing these 2. Quality assurance is very important in software development life cycle, many students who have technical knowledge can contribute to automation testing those without coding knowledge can contribute to Manual testing. And Firefox Addons are moving WebExtensions model, so it is right time to learn about it port old add-ons to this model, develop new add-ons.
Trainers are our Game Changing Contributor of 2016
Last year we had session in Google hangouts on Air that too in English, many contributors know to speak Tamil well and prefer to learn in Tamil than in English. And since it was not closed call, we are not able to track actively what contributors are doing. So this year we have introduced a concept of Trainers. Trainers are amazing people who are active and having willingness to share what they learned and train maximum of 7 people in focused manner. We had Google form so people can fill who have interest. Around 40 people showed interest. But keeping in mind that it is going to be difficult to monitor 40 people and all the contributors who they teach (say appx 450 ppl) we have cut shorted to 20 Trainers. So this year we are having only 20 Trainers. As of now on avg each and every Trainer has planned to teach around 5 new contributors.
What will be my role this year
What’s my expectation at end of this weeks of contribution
One of my main goal is to spotlight contributors who are doing great job around Tamilnadu. Previously I have got chance to participate in amazing events like community India meetup (2014& 2015) and Mozilla All hands at Orlando. These meetup are really great place to learn many things. One of sad thing for me during this 3 events was number of contributors from Tamilnadu region is very low. Many contributors here do amazing contributors but due to low visibility and some guidance they are not getting proper recognition. One of my main aim is to bring amazing contributors and help them communicating with other mozillians in community, then they can easily find the path to improve themselves. I have faith, Surely with the amazing trainers we have got we will be doing well.
My main aim to join open source communities is to contribute to code base and share awareness to other benefits of using open source softwares. One of my main aim is to bring like minded contributors share their work with others through blog post social media and other possible channels.
Some of ways I can contribute is by teaching addons development, community building and helping people to get started with first step of contribution.
At the 2015 Reps Leadership Meeting in Paris it became clear that the program was ready for “a version 2”. As the Reps Council had recently become a formal part of Mozilla Leadership, it was time to bring the program to the next level. Literally building on that idea, the RepsNext initiative was born.
Since then several working groups were formed to condense reflections on the past and visions for the future into new program proposals.
At our last Council meetup from 14-17 April 2016 in Berlin we recorded interviews with Council and Peers explaining RepsNext and summarizing our current status.
You can find a full transcript at the end of this blog post. Thanks to Yofie for editing the video!
Please share this video broadly, creating awareness for the exciting future of the Reps program.
We will focus our work at the London All Hands from June 12th to June 17th to work on open questions around the working groups. We will share our outcomes and open up for discussions after that. For now, there are several discussions to jump in and shape the future of the Reps program:
Additionally, you can help out and track our Council efforts on the Reps GitHub repository.
Moving beyond RepsNext
It took us a little more than a year to come up with this “new release” of the Reps program. For the future we plan to take smaller steps improving the program beyond RepsNext. So expect experiments and tweaks arriving in smaller bits and with a higher clockspeed (think Firefox Rapid Release Model).
Question: What is RepsNext?
[Arturo] I think we have reached a point of maturity in the program that we need to reinvent ourselves to be adaptors of Mozilla’s will and to the modern times.
Question: How will the Reps program change?
[Pierros] What we’re really interested in and picking up as a highlight are the changes on the governance level. There are a couple of things that are coming. The Council has done really fanstastic work on bringing up and framing really interesting conversations around what RepsNext is, and PeersNext as a subset of that, and how do we change and adapt the leadership structure of Mozilla Reps to be more representative of the program that we would like to see.
[Brian] The program will still remain a grassroots program, run by volunteers for volunteers.
[Henrik] We’ve been working heavily on it in various working groups over the last year, developed a very clear understanding of the areas that need work and actually got a lot of stuff done.
[Konstantina] I think that the program has a great future ahead of it. We’re moving to a leadership body where our role is gonna be to empower the rest of the volunteer community and we’re gonna try to minimize the bureacracy that we already have. So the Reps are gonna have the same resources that they had but they are gonna have tracks where they can evolve their leadership skills and with that empower the volunteer communities. Reps is gonna be the leadership body for the volunteer community and I think that’s great. We’re not only about events but we’re something more and we’re something the rest of Mozilla is gonna rely on when we’re talking about volunteers.
Question: What’s important about this change?
[Michael] We will have the Participation team’s support to have meetings together, to figure out the strategy together.
[Konstantina] We are bringing the tracks where we specialize the Reps based on their interest.
Question: Why do we need changes?
[Christos] There is the need of that. There is the need to reconsider the mentoring process, reconsidering budgets, interest groups inside of Reps. There is a need to evolve Reps and be more impactful in our regions.
Question: Is this important for Mozilla?
[Arturo] We’re going to have mentors and Reps specialized in their different contribution areas.
Question: How is RepsNext helping local communities?
[Guillermo] Our idea, what we’re planning with the changes on RepsNext is to bring more people to the program. More people is more diversity, so we’re trying to find new people, more people with new interests.
Question: What excites you about RepsNext?
[Faisal] We have resources for different types of community, for example if somebody needs hardware or somebody training material, a variety of things not just what we used to have. So it will open up more ways on how we can support Reps for more impactful events and making events more productive.
On the first quarter of this year, I led an initiative within the Mozilla Philippines Community (MozillaPH) to start a study group for Rust (Programming Language). Rust is a general-purpose, multi-paradigm, compiled programming language backed by Mozilla (for one, it was created by Graydon Hoare, a Mozilla employee). Some say it competes with C++ and […]
Please join us in congratulating Daniele Scasciafratte as Reps of the Month for April 2016!
I first attended a Mozilla All-hands workweek in 2014 when it happened in Portland. I attended as part of the newly-formed FSA E-board who has been working so hard during the past months in revamping the program led by the amazing Community Manager that we had. FSA is the first (and so far the only) area at Mozilla that I have been a core contributor of in a global level, so I was so excited to meet the people I have been working so closely for the first time. I led the revamp of the Firefox Clubs and I take pride on the sleepless nights I spent working on the new process and training materials. I was ready to rock in Portland.
But it was the first workweek I attended. Less idealism and more serious business, so for the first time ever I was so stressed in a Mozilla event. Each day I had been learning what was really happening inside the organization, mostly cool stuff but sadly, it isn’t the case for the program I am involved with. Portland weather continued to be gloomy and the clouds were getting heavier as I am getting filled with confusion and doubt. It was my first time to be upset about and started questioning how well are we really doing in taking care of volunteers in Mozilla.
Now, what happened? Simple. Apparently there is a difference on how we value this program between us, the volunteer team running it and the team managing it. We all went to Portland with a goal to think about how we can improve the experience of Mozilla’s young volunteers but too bad, we are apparently all about numbers. Indeed I am aware we contribute to that, but I expected they see us beyond. These people we work so hard for are just valued for the numbers they bring. This isn’t even close to what I expected from all the things we have been working on since the revamp. Indeed, reality sucks.
Since Portland, our core team composed of majority volunteers (read: only one staff directly handling us 6 E-board and 30 RALs, with 5 months operating without a Community Manager even) has been working hard, even finding loopholes, keeping these flaws within ourselves just to ensure that the FSAs have a good image of the program and Mozilla, especially of the staff teams we are under in. 2015 was a crazy mix of challenge, fun, hope and stress. I could go on with the problems we had (some were even so embarrassing for a big organization like us) but let’s allow the details to rest. We managed to endure it anyway.
Come Orlando workweek, we were shaken by a huge change. The Community Manager left and we moved to the Participation Team. We were so happy we moved to the team focusing on volunteers but sad our CM, who was our light in all the chaos, left. The rumors are true, magic really happens in Disney. We thought everything will be awesome nonetheless, because hey, finally we will be more about those marketing numbers! We will finally provide a valuable experience that our passionate students deserve. Sadly, fast forward 1 week until the next All-hands later with gigs of data spent on online discussions in the past 5 months, things just gotten worse. And yet again, it was brought by the confusion caused by the difference between how us volunteers and the staff are seeing the program, exacerbated by the unfortunate case of not being able to focus talking about it.
I can’t help but think about one thing: Even after pouring our heart out in our work for the FSA program, no. one. cares.
I will be honest that my 2016 so far has been the most tensed months I have ever experienced volunteering for Mozilla. I am just not giving up, thanks to the inspiration brought by the passionate people I am working alongside with who have been working hard, putting up with all the crap we have been experiencing, motivated to see the end of this storm we are facing. All for the young people committed to protect the open Web.
Congratulations for surviving my 600-word background story. That means you are intrigued to know where I am coming from. Now, what’s the plan for London?
You might have already deduced that I only have one major concern in mind: Our team is tired of this cycle of being eternally confused and most of all, underrated. (Segue: I blogged about my thoughts on the value of youth involvement in Mozilla here.)
So what I simply wanna do is finally bring this discussion on the table and actually focus on it.
Bluntly, here are the questions I aim to get an answer in London:
Diving deeper, my specific goals would be:
Apologies if you expected a very positive and idealistic goal setting post about MozLondon, but in order to make the most out of it and to ensure I communicate my expectations, I wanna spill it all so we can help each other move forward. While all these things happening have truly been depressing, I have never been so motivated to give it all in London to clarify where we will be heading. I love the challenge and I am so excited to be involved as we shape the future of it together.
Enough of the sugarcoating, hiding, delaying and leaving things hanging. Let’s just freaking do this.
Earlier this month a group of people met in Berlin to imagine and design Mozfest 2016.
Blending inspiration and ideas from open news, science, localization, youth, connected devices and beyond – we spent three glorious days collaborating and building a vision of a Mozfest like no other.
The Participation team emerged from this experience with a new vision for Mozillian participation we’re calling ‘Mozfest Space* Contributors’. Roles designed to bring success on the goals of every space in the building. This is a very different approach from recent years where our focus has been more participatory as facilitators, helpers and learners. With this new approach, we’re inviting contribution, ownership and responsibility in shaping the event. Super, super exciting – I hope you agree!
Exploring the potential of contributor roles within Spaces, we found amazing potential! Open Science imagined a ‘Science Translator’ role – helping people overcome scientific jargon to connect with ideas. The Web Literacy group has big plans for their physical space, one where a ‘Set Designer’ would be incredibly helpful in making those dreams come true.
Open News, and others thought about ‘Help Desk’ leads, and more than one space has suggested that the addition of technical mentors and session translators would bring diversity and connection. Can you see yet why this will be amazing?
Outreach for contributors this year will be focused squarely on finding people with the skills, passion, vision and a commitment to supporting these spaces. In many cases roles will be a key part of planning in the months leading up to Mozfest.
Also – we’re already piloting this very idea! having recently selecting Priyanka Nag and Mayur Patil to be part of the Participation team’s Mozfest planning. I’m so grateful for their help and leadership in making this a fantastic experience for wranglers and contributors alike.
On July 15th we’ll post all available roles, and launch the application process. You can find an FAQ here.
Sponsorship from the Participation Team for Mozfest 2016 will be for these roles only. The call for the proposals will be run by the MozFest organizers who will have a limited number of travel stipends available through that separate process.
* Space – an area of Mozfest with content and space built and activated under a certain theme (like Open Science, Youth Zone and Web Literacy)
* Space Wrangler – Person organizing and building a space at Mozilla
Role avatars by freepik.
Please join us in congratulating Rahul Talreja as Rep of the Month for March.
Rahul Talreja is one of the most active Reps and a senior FSA of his community. He started as a FSA in 2013 and since day one he has been doing great work in building the local community and his personal contribution towards Mozilla. He has mentored a lot of people.
Aligned with Mozilla’s new strategy towards Connected Devices, Rahul recently organised an IoT/Connected Device workshop “Web of Things @ Footprints Baroda” in February 2016. That was the first of its scale in India and it helped not only him but the entire community to learn from what he did in that event. The workshop was undoubtedly a great success , which can be seen in Rahul’s blog post about the event.
DORS/CLUC, Days of open systems / Croatian Linux Users’ Conference, is the oldest and biggest regional conference in the Balkans dedicated to topics of free software, open source, open standards and Linux.
It is jointly organized by two non-profit organizations HrOpen and HULK, going on for 23 years, and it gathers prominent individuals and companies from the free software communities and companies. This year’s conference has been held from May 11th – 13th, at the Faculty of Electrical Engineering and Computing in Zagreb. During three days of talks, workshops and fun, DORS/CLUC is a place where hackers, companies, freelances and the public sector meets to learn, exchange contacts, make business and plan projects together, while focusing on free software and Linux.
DORS/CLUC has been divided into two parts: keynotes/talks and workshops. Keynote/talk part falls into following categories: business topics, the newest experiences of FLOSS implementation and migration in industry and tech topics like for example how to use some technology. During workshops which are mostly tech oriented attendees have an opportunity to learn how to use some technology, how to troubleshoot and solve tech problems in the field of free and open source technology.Mozilla’s Presence
Unfortunately, I was the only Mozillian at the event (apart Giannis Konstantinidis, who attended as part of the Fedora Project). For not having a booth however, people approached me quite a lot to ask about Mozilla, specifically in Croatia. It’s a bit of a missed opportunity, as quite some efforts could grow in the Croatian community, with a tiny little bit of mentorship and overview. Something to keep in mind for the Croatian community.
We are in talks of hosting the next Mozilla Balkans meetup in Tirana, Albania in September, so I hope to see representatives of the Croatian community as well, so we can properly prepare for the next edition.My Talk
The main lecture hall where I was giving a talk was quite big, with a capacity of probably over 250 people, and therefore the biggest room I might have talked in. Obviously, the auditorium wasn’t crowded, but a solid amount of people came to my talk, which was great. The talk was recorded and livestreamed.
Once again, I gave a talk about Mozilla Community Design, what lessons we got from involving the community and how people could get involved.
My talk went really well, although a bit short (I guess I need to adjust my slides for 30min sessions) and I had a few questions at the end which sparked some discussions. I still have some breathing issues during giving talks, as I fail to put in the right amount of breaks to catch my breath during presenting. People have told me it’s not something noticeable, but I plan to work on it. I also was trying to avoid fillers like “uhm” or “erm” but which still needs more work. I hope I can improve upon this in one of our next TechSpeaker sessions.Conclusion
The conference was relatively cozy and many people knew each other. It seemed also like a good place for government officials to meet and talk as well. Around 300 attendees might have been part of the conference, in 2 tracks. What I really respect about DORS/CLUC, is the fact that it’s been running for 23 years now! That’s an impressive number! On the other hand, I felt a bit left out of many conversations, as the majority of the material and talks were in Croatian (although seemingly Croatians had amazing English skills).
Definitely looking forward to visit Zagreb soon again!
I was honored to be part again this year at OpenTechSummit 2016 this year where I represented Mozilla and specifically the Community Design initiative, where we encourage contributors to get involved with design at Mozilla. Check out my blog post to find out more about Mozilla Community Design.
The event was quite nice and as it was my 2nd time I was part of OpenTechSummit, I felt quite like home, where I met many old friends, as well as new ones. In the following is a short description of the event:
Topics range from open hardware to open data, design, graphics, software, start ups and digital policies. In a barcamp style track there is space for adhoc meetings, lightning talks and breakout sessions. There will also be dedicated workshops for kids and maker enthusiasts, where you can make your own gadgets (TV-B-Gone, upgrade knitting machines, your own traffic lights) and Fashiontec wearables. In the evening we will have an “OpenTech-Himmelfahrt” lounge. The Linux Professional Institute offers Linux certification at a discounted rate. More than 70 speakers will present the latest technology trends, including Lennart Poettering (Developer Systemd), Michael Christen (Founder Yacy Searchengine), Wan Leung Wong (Tinyboy 3D Printer Hong Kong), André Fiedler (FirefoxOS Engineer), Andreas Bräu (Knitting machine hacker), Jan Suhr (Nitrokey Crypto Device) and Luca Comparini (Power Systems at IBM).
You can listen to a recording of my talk here. There are many things I need to improve when giving a talk, while I keep on striving to polish my speaking skills, but with the Mozilla Tech Speakers program the process becomes a very worthwhile one.
I also extended my stay in Berlin, to work at the Mozilla Office on various Mozilla projects, which was something I have wanted to catch up on for quite some time. Felt good meeting with the Mozilla crew again.Conclusion
The weather in Berlin was wonderful during the event, which might not be the most fitting thing for indoor events. Many talks lacked people due to that, as quite many preferred drinking a beer outside. However, the 1:1 conversations I had after my talk made up for it, and I met with quite some Mozillians during that time. I was really impressed by the 2015 edition, which hooked me up for this edition as well. however I was let down a bit due to some lack of guidance and organization of speakers and their sessions. I hope OTS 2017 will improve on these.
The Janitor was started by Jan Keromnes, a Mozilla employee. While still in an alpha state, Jan gave us access to it so we could test run it at our hackathon. Many thanks to him for spending his Saturday on IRC and helping us out with everything!
Once you’re signed up, you can click on “Open in Cloud9” and directly get to the Cloud9 editor who kindly sponsor the premium accounts for this project. .
At the hackathon we ran into a Cloud9 “create workspace” limitation, but according to Jan this should be fixed now.
After an initial “git pull origin master” in the Cloud9 editor terminal, you can start to build Firefox in there. Simply running “./mach build” is enough. For me this took about 12 minutes for the first time, while my laptop still needs more than 50 minutes to compile Firefox. This is definitely an improvement. Further you won’t need anything else than a browser!
I had my environment ready in about 15 minutes if you count the time to compile Firefox. Comparing this to my previous setups, this solves a lot of dependency-hell problems and is also way faster.
Running the newly compiled Firefox
The Janitor includes a VNC viewer which opens a new tab and you can run your compiled Firefox in there. You can start a shell and run “./mach run” in the Firefox directory and you can start testing your changes.
For some of the bugs we tackled at the hackathon, we needed to run ESLint (well, would be good to run this anyway, no matter what part of the code base you’re changing). The command looks like this:
user@e49de5f6914e:~/firefox$ ./mach eslint --no-ignore devtools/client/webconsole/test/browser_webconsole_live_filtering_of_message_types.js 0:00.40 Running /usr/local/bin/eslint 0:00.40 /usr/local/bin/eslint --plugin html --ext [.js,.jsm,.jsx,.xml,.html] --no-ignore devtools/client/webconsole/test/browser_webconsole_live_filtering_of_message_types.js /home/user/firefox/devtools/client/webconsole/test/browser_webconsole_live_filtering_of_message_types.js 8:1 warning Could not load globals from file browser/base/content/browser-eme.js: Error: ENOENT: no such file or directory, open '/home/user/firefox/browser/base/content/browser-eme.js' mozilla/import-browserjs-globals 8:1 warning Definition for rule 'mozilla/import-globals' was not found mozilla/import-globals 8:1 error Definition for rule 'keyword-spacing' was not found keyword-spacing 18:17 error content is a possible Cross Process Object Wrapper (CPOW) mozilla/no-cpows-in-tests ✖ 4 problems (2 errors, 2 warnings) 0:02.85 Finished eslint. Errors encountered.
As you might see from the input, running this in the Janitor environment results in not finding the Mozilla-specific rules. The reason here is that the eslint npm package is installed globally. Globally installed eslint can’t find the locally installed mozilla-eslint-plugin. In my opinion the easiest fix would be to not install it globally, just within the firefox directory (running “./mach eslint –setup”) while spinning up the instance should be enough here.
We could circumvent this problem by changing the global npm prefix and then running it with “/new/path/eslint …” so it doesn’t call the other one. In hindsight, we could just have installed it to the directory and then call it through node_modules.
Update, May 5, 15:09: Jan has has fixed this plugin issue :)
Creating a patch
Creating a patch is really easy, following the tutorial on MDN is enough. We were very happy to see that the moz-git-tools are already installed by default, so you can just create your own branch, checkin your changes and run “git format-patch -p -k master” to get a Git patch file. Since we need a Mercurial patch, you then run “git-patch-to-hg-patch” and you can upload the resulting file to Bugzilla and you’re set!
Those two commands could maybe be aliased by default so running “create-patch” or similar would directly do this for you to further decrease the work you need to do manually.
Seeing it in action
After some initial account problems, we didn’t really find any other bugs apart from the ESLint situation. Again, thanks a lot to Jan for providing us the environment and letting us test it. This will change the live of a lot of contributors! For now The Janitor supports contributions to Firefox, Chrome, Thunderbird, Servo and KDE. There is also a GitHub repository for it.
Last Saturday we’ve held a Firefox Hackathon in Zurich, Switzerland. We’ve had 12 people joining us.
At first I gave an introduction to Firefox and introduced the agenda of the hackathon.
Dev Tools Talk
Before the hackathon we created a list of “good first bugs” that we could work on. This was a great thing to do, since we could give the list to the attendees and they could pick a bug to work on. Setting up the environment to hack was pretty easy. We’ve used “The Janitor” to hack on Firefox, I’ll write a second blog post introducing you to this amazing tool! We ran into a few problems with it, but at the end we all could hack on Firefox!
We worked on about 13 different bugs, and we finished 10 patches! This is a great achievement, we probably couldn’t have done that if we needed more time to set up a traditional Firefox environment. Here’s the full list:
At the end of the hackathon we did a round of feedback. In general the feedback was rated pretty well, though we might have some things to improve for the next time.
40% of the attendees had their first interaction with our community at this hackathon! And guess what, 100% of the attendees who filled out the survey would be joining another hackathon in 6 months:
For the next hackathon, we might want to have a talk about the Firefox Architecture in general to give some context to the different modules. Also for the next hackathon we probably will have a fully working Janitor (meaning not alpha status anymore) which will help even more as well.
All in all I think this was a great success. Janitor will make every contributor’s life way easier, keep it going! You can find the full album on Flickr (thanks to Daniele for the great pictures!).
From April 15th through April 17th the Mozilla Reps Council met in Berlin together with the Participation Team to discuss the Working groups and overall strategy topics. Unfortunately I couldn’t attend on Friday (working day 1) since I had to take my exams. Therefore I could only attend Saturday and Sunday. Nevertheless I think I could help out a lot and definitely learned a lot doing this :) This blog posts reflects my personal opinions, the others will write a blog post as well to give you a more concise view of this weekend.
Alignment Working Group
The first session on Saturday was about the Alignment WG. Before the weekend we (more or less) finished the proposal. This allowed us to discuss the last few open questions, which are now all integrated in the proposal. This will only need review by Konstantina to make sure I haven’t forgotten to add anything from the session and then we can start implementing it. We are sure that this will formalize the interaction between Mozilla goals and Reps goals, stay tuned for more information, we’re currently working on a communication strategy for all the RepsNext changes to make it easier and more fun for you to get informed about the changes.
Meta Working Group
For the Meta Working Group we had more open questions and therefore decided to do brainstorming in three teams. The questions were:
We’re currently documenting the findings in the Meta working group working proposal, but we probably will need some more time to figure out everything perfectly. Keep an eye out on the Discourse topic in case we’ll need more feedback from you all!
Identity Working Group
A new working group? As you see, I didn’t believe it at first and Rara was visibly shocked!
Fun aside, yes, we’ll start a new Working group around the topics of outwards communication and the Rep program’s image. During our discussions on Saturday, we came up with a few questions that we will need to answer. This Friday we had our first call, follow us in the Discourse topic and it’s not too late to help out here! Please get involved as soon as possible to shape the future of Reps!
On Sunday we ran a joint session with the rest of the Participation team around the topic “How we work together”. We came up with the questions above and let those be answered / brainstormed in groups. I started to document the findings yesterday, but this is not yet in a state where it will be useful for anybody. Stay tuned for more communication around this (communication about communication, isn’t it fun? :)). The last question around “How might we improve the communication between the Participation-Team and the Council?” is already documented in the Alignment Working group proposal. Further the Identity working group will tackle and elaborate further the question around visibility.
Reps Roadmap for 2016
Wait, there is a roadmap?
At the end of our sessions we put up a timeline for Reps for all our different initiatives on a wall. Within the next days we’ll work on this to have it digitally per months. For now, we have started to create GitHub issues in the Reps repo. Stay tuned for more information about this, the current information might confuse you since we haven’t updated all issues yet! It basically includes everything from RepsNext proposal implementations to London Work Week preparations to Council elections.
This weekend showed that we currently have an amazing, hard-working Council. It also showed that we’re on track with all the RepsNext work and that we can do a lot once we all work together and have Working Groups to involve all Reps as well.
Looking forward to the next months! If you haven’t yet, have a look at the Reps Discourse category, to keep yourself updated on Reps related topics and the working groups!
The other Council members will write their blog post in the next few days as well, keep an eye out for link on our Reps issues. Once again, there are a lot of changes to be implemented and discussed, we are working on a strategy for that. We believe that just pointing to all proposals is not easy enough and will come up with fun ways to chime into these and fully understand them. Nevertheless, if you have questions about anything I wrote here, feel free to reach out to me!
Credit: all pictures were taken by our amazing photographer Christos!
We started to organize the Hackathon on Github, so everyone can participate. Geoffroy was really helpful to organize the space for it at Liip.ch. Thanks a lot to them, without them organizing our events would be way harder!
We expected more people to come, but as mentioned above, this is our first self-organized event in the French speaking part of Switzerland. Nevertheless we were four persons with an interest in hacking something together.
Geoffroy and Paul started to have a look at Vaani.iot, one of the projects that Mozilla is currently pushing on. They started to build it on their laptops, unfortunately the Vaani documentation is not good enough yet to see the full picture and what you could do with it. We’re planning to send some feedback regarding that to the Vaani team.
In the meantime Martin and I set up my Raspberry Pi and started to write a small script together that reads out the temperature from one of the sensors. Once we’ve done that, I created a small API to have the temperature returned in JSON format.
At this point, we decided we wanted to connect those two pieces and create a Web app to read out the temperature and announce it through voice. Since we couldn’t get Vaani working, we decided to use the WebSpeech API for this. The voice output part is available in Firefox and Chrome right now, therefore we could achieve this goal without using any non-standard APIs. After that Geoffroy played around with the voice input feature of this API. This is currently only working in Chrome, but there is a bug to implement it in Firefox as well. In the spirit of the open web, we decided to ignore the fact that we need to use Chrome for now, and create a feature that is built on Web standards that are on track to standardization.
After all, we could achieve something together and definitely had some good learnings during that.
After the Hackathon
Since I needed to do a project for my studies that involves hardware as well, I could take the opportunity and take the sensors for my project.
You can find the Source Code on the MozillaCH github organization. It currently regularly reads out the two temperature sensors and checks if there is any movement registered by the movement sensor. If the temperature difference is too high it sends an alarm to the NodeJS backend. The same goes for the situation where it detects movement. I see this as a first step into my own take on a smart home, it would need a lot of work and more sensors to be completely useful though.
Over the past 3 months, we deployed new Pontoon code to production servers 65 times, which means approximately once per workday. Most of the changes were incremental improvements, optimizations or bugfixes, but some of them require a brief introduction. We hope you’ll like them.
Progressive loading of strings
Instead of requesting all strings at once, we now only load the first 50 and add others progressively while you scroll down the string list (in batches of 50). The benefits are particularly noticable when loading resource files with 1000s of strings, with search & filters also becoming snappier. Kudos to jotes for implementing it!
The idea of progressive loading is simple, but its implications go far beyond what the name suggests. It allowed us to add the All Resources menu entry, which makes it easy to load, search and filter strings across the entire project. If you have 7 missing strings in 4 different files, you can finally translate them without manually loading each resource.
In Q2, we’ll make common filters (e.g. strings with pending suggestions) accessible directly from the dashboard.
Some time ago my team decided to change the translation of cookie in Firefox. It would be a nightmare to do it for each string separately in Pontoon, so we had to fire up a text editor and use find & replace. This use case is now covered by Pontoon.
Translation status icons in the string list act as checkboxes, allowing you to select strings. (You can also hold Shift to select a range of strings or use Select All). 3 bulk actions are available (to Translators only) — Approve All, Delete All and Find & Replace.
In Q2, we’ll add new filters to help you with more interesting mass actions. For example, you will be able to delete all suggestions submitted by No Name, because they are spam. Or approve all suggestions from Annie, who was just granted Translator permission.
Improved translation helpers
Translation helpers are the three tabs below translation textarea, where we keep history of user translations (History), translation memory and machine translation suggestions (Machinery) and translations into other locales (Locales).
All helpers are loaded instantly after a string is opened for translation. Additionally, a number of suggestions is displayed in each tab title, so you don’t click on them in vain. Duplicate Machinery results are grouped and sorted by source (in addition to Levenshtein distance).
In Q2, we’ll make it possible for localizers to define a preferred list of locales to get suggestions from.
Homepage and dashboard optimization
Pontoon homepage now loads 70% faster, mostly due to smarter handling of the iframe and loading Persona script on demand. Dashboards are 30-60% faster, thanks to denormalized statistics data and optimized latest activity database queries.
On a related note, you can now access team and project dashboards directly from the main menu in the translate view. Thanks to Emin for submitting the patch!
In Q2, we’ll focus on optimizing sync, because we have a huge room for improvement there. We’ll continue with web interface optimization, but we’re getting to the point where it’s becoming more of a hardware than software problem.
Plans for Q2
We’d love to hear your feedback on the features we’ve shipped. In addition to that, we’d like to invite you to participate in developing our roadmap for Q2. Now is the best time to file feature requests and leave feedback on existing bugs (quarterly goals have priority set to P2).
So, you wanna join us?
The Mozilla Reps program is open to all Mozillians who are 18 years of age and above. Before you become a Mozilla Rep, you must complete a short but rigorous application process in order to demonstrate your interest in and motivation for joining the program. Are you ready to take on the challenges and rewards of advancing your leadership to the next level in Mozilla? If your answer is YES, apply to become a Mozilla Rep today!
Not sure if you're ready for Mozilla Reps? There are many other ways to take the lead in the Mozilla Community. If you're a student, register for the Firefox Student Ambassadors program to gain experience leading projects at your school. And all of our contributor opportunities are available to you on the Get Involved homepage.
The Mozilla Reps application process involves three simple steps:
Fill out and submit the Mozilla Reps application form. A Mozilla Rep mentor will be in touch within 24 hours.
If your application is approved, you'll be invited to be interviewed by a member of the advisory council over IRC or IM that same week. The interview lasts about 15 minutes and you will be asked some simple questions about yourself, your experience contributing to the Mozilla project and, of course, your motivation for becoming a MozRep.
If you're accepted into the Mozilla Reps program, your mentor will get you started and familiar with the tools at your disposal to start organizing events, requesting budgets, swag, etc. And just like that, you could become a Mozilla Rep!
Thanks for your interest in making the Web better with Mozilla!×