Firefox 55 new contributors

Josh Matthews

1 response

With the release of Firefox 55, we are pleased to welcome the 108 developers who contributed their first code change to Firefox in this release, 89 of whom were brand new volunteers! Please join us in thanking each of these diligent and enthusiastic individuals, and take a look at their contributions:

Firefox 54 new contributors

Josh Matthews

5 responses

With the release of Firefox 54, we are pleased to welcome the 36 developers who contributed their first code change to Firefox in this release, 33 of whom were brand new volunteers! Please join us in thanking each of these diligent and enthusiastic individuals, and take a look at their contributions:

Revitalize participation by understanding our communities

Ruben Martin [:Nukeador]

As part of the bigger Open Innovation strategy project on how openness can better drive Mozilla products and technologies, during the next few months we will be conducting research about our communities and contributors.

We want to take a detailed, data-driven look into our communities and contributors: who we are, what we’re doing, what our motivations are and how we’re connected.

Who: Understanding the people in our communities

  • How many contributors are there in the Mozilla community.
  • Who are we? (how diverse is our community?)
  • Where are we? (geography, groups, projects)

What: Understanding what people are doing

  • What are we doing? (contributing with)
  • What are our skillsets?
  • How much time we’re able to devote to the project.
  • The tools we use.
  • Why do people contribute? (motivations)
  • What blocks people from contributing?
  • What other projects do we contribute to?
  • What other organisations are we connected to?
  • How much do people want to get involved?

Why: Understanding why people contribute

  • What are people’s’ motivations.
  • What are the important factors in contributing for Mozilla (ethical, moral, technological etc).
  • Is there anything Mozilla can do that will lead volunteers to contribute more?
  • For people who have left the project:why do they no longer contribute?)

How & Where: Understanding the shape of our communities and our people’s networks

  • What are the different groups and communities.
  • Who’s inside each group (regional and functional).
  • What is the overlap between people in groups?
  • Which groups have the most overlap, which have the least? (not just a static view, but also over time)
  • How contributors are connected to each other? (related with the “where”)
  • How are our contributors connected to other projects, Mozilla etc

In order to answer all these questions, we have divided the work in three major areas.

Contributors and Contributions Data Analysis

Analyzing past quantitative data about contributions and contributors (from sources like Bugzilla, Github, Mailing Lists, and other sources) to identify patterns and draw conclusions about contributors, contributions and communities.

Communities and Contributors survey

Designing and administering a qualitative survey to as many active contributors as possible (also trying to survey people who have stopped contributing to Mozilla) to get a full view of our volunteers (demographics), motivations, which communities people identify with, and their experience with Mozilla. We’ll use this to identify patterns in motivations.

Insights

We’ll bring together the conclusions and data from both of the above components to articulate a set of insights and recommendations that can be a useful input to the Open Innovation Strategy project.

In particular, one aim that we have is to cross reference individuals from the Mozillians Survey and Data Analysis to better understand — on aggregate — how things like motivations and identity relate to contribution.

Our commitments

In all of this work we are handling data with the care you would expect from Mozilla, in line with our privacy policy and in close consultation with Mozilla’s legal and trust teams.

Additionally, we realize that we at Mozilla often ask for people’s time to provide feedback and you may have recently seen other surveys. Also, we have run research projects of this sort in the past without following up with a clear plan of action. This project is different. It’s more extensive than anything we’ve done, it is connected a much larger project to shape Mozilla’s strategy with respect to open practices, and we will be publishing the results and data.

We would like to know your feedback/input about this project, its scope and implementation:

  • Are we missing any areas/topics we should get information about our communities?
  • Which part do you feel it’s more relevant?
  • Where do you think communities can engage to provide more value to the work we are going to do?
  • Any other ideas we are not thinking about?

Please let us know in this discourse topic.

Thanks everyone!

Firefox 53 new contributors

Josh Matthews

8 responses

With the release of Firefox 53, we are pleased to welcome the 63 developers who contributed their first code change to Firefox in this release, 58 of whom were brand new volunteers! Please join us in thanking each of these diligent and enthusiastic individuals, and take a look at their contributions:

Firefox 52 new contributors

Josh Matthews

8 responses

With the release of Firefox 52, we are pleased to welcome the 50 developers who contributed their first code change to Firefox in this release, 45 of whom were brand new volunteers! Please join us in thanking each of these diligent and enthusiastic individuals, and take a look at their contributions:

  • 166291: 1310835
  • adamtomasv: 1308600, 1312173, 1313565
  • asppsa: 1304019
  • cody_tran95: 1301212, 1301214, 1301223
  • p23keshav: 1314158
  • patrickkerry.pei: 1264929
  • psnyde2: 1315438
  • u579587: 1287622
  • vinayakagarwal6996: 1304097, 1304167
  • Aaron: 1304310
  • Ajay: 1303708, 1304735
  • Alin Selagea: 1315690
  • Amal Santhosh: 1303356
  • Brian Stack: 1275774, 1304180
  • Chirag: 1296490
  • Dave House: 1307904
  • David Malaschonok: 926579
  • Dhanesh Sabane (UTC+5:30): 1308137
  • Dzmitry Malyshau: 1322169
  • Eden Chuang: 1287664
  • Enes Göktaş: 1302855, 1303227, 1303236
  • Francesco Pischedda: 1280573, 1285555, 1291687
  • Fuqiao Xue: 1111599, 1288577
  • Haard Panchal: 1307771
  • Heikki Toivonen: 209637
  • Horatiu Lazu: 1292299
  • Julia Friesel: 1256932
  • Kaffeekaethe : 1256887, 1307676, 1308931
  • Kanika Narang: 1302950
  • Kirti Singla: 1301627
  • Laszlo Ersek: 1304962
  • Leandro Manica: 1306296
  • Manuel Grießmayr: 1311783
  • Mark Golbeck: 1091592
  • Mark Smith: 1308275
  • Matthew Spencer: 1293704
  • Max Liu: 1312719
  • MikeLing: 1287018
  • Nevin Chen: 1310621
  • Petr Gazarov: 1300944
  • Petr Sumbera: 1309157, 1309246, 1315956
  • Robin Templeton: 1316230
  • Samriddhi: 1303682
  • Saurabh Singhal: 1278275
  • Sourav Garg: 1311343, 1311349
  • Umesh Panchaksharaiah: 1301629
  • Vincent Lequertier: 1299723, 1301351, 1304426
  • Will Wang: 1255977
  • William CS: 1295000
  • Yen Chi-Hsuan (UTC+8): 1143421
  • katecastellano: 1256941

    • Open and agile?

    Chris Mills

    31 responses

    Facilitating openness and including volunteers in agile sprints

    This post is based on a discussion at the Mozilla All-Hands event in December 2016. Participants in that discussion included Janet Swisher, Chris Mills, Noah Y, Alex Gibson, Jeremie Patonnier, Elio Qoshi, Sebastian Zartner, Eric Shepherd, Julien G, Xie Wensheng, and others.

    For most of 2016, the Mozilla marketing organization has been moving towards working agile — much of our work now happens within “sprints” lasting around 2.5 weeks, resulting in better prioritization and flexibility, among other things. (For those familiar with agile software development, agile marketing applies similar principles and workflows to marketing. Read the Agile Marketing Manifesto for more background.)

    However, one aspect of our work that has suffered in this new paradigm is openness and inclusion of our volunteer community in marketing activities. While the agile workflow encourages accountability for full-time team members, it leaves very little space for part-time or occasional participation by volunteers. We are Mozilla, and transparency, openness, and participation are part of our core values. This disconnect is a problem.

    This post explores the issues we’ve found, and shares some potential solutions that we could work towards implementing.

    The problem

    Since moving to an agile, “durable team” model, the amount of interaction we have had with our volunteer community has decreased. This is written from the perspective of the Mozilla Developer Network (MDN) team, but we are sure that other teams have experienced similar negative trends.

    The main reasons for this decrease are:

    • The tools used to track work are not open, so volunteers cannot access them.
    • The agile process in general does not lend itself well to volunteer discovery or contribution. Their work is deprioritized, they feel ignored, they find it harder to participate.
    • There is very little information provided for volunteers who want to participate in a project managed in an agile fashion.

    The challenge we face is how to make the agile process more transparent, so that volunteers can understand what is happening and how it happens; more open so that volunteers can contribute in meaningful ways; and more welcoming so that volunteers feel they are part of a team and are appreciated and recognized for their efforts.

    Solutions

    Let’s look at the solutions that were discussed. These details are fairly brief, but they act as good starting points for further investigation.

    Openness of tools

    We need to review the tools we are using, and make sure that they are open for volunteers to get information and updates. For example:

    • Slack is hard in terms of giving people the right permissions.
    • Some of the “agile tools” can appear closed off and difficult to access for those outside your organization (at least, in the ways we’ve been using them).

    We need to work out better tools/workflows for volunteer contributions.

    Information

    An explainer doc to explain the agile process would be useful, including:

    • How the process works in general, and an explanation of key terms like durable team, “functional team”, “cross-functional”, etc.
    • What the different teams are and what they are responsible for.
    • How to find more information on what you can do for each team at the current time and in the future.
    • How you can contact each team and get updates on their work.

    There is some information that already exists — an explanation of MDN’s agile process, and a glossary of agile terminology.

    When questions are asked, it would be good to make sure that we not only answer them on a public list, but also document the answers to make them easy to find for others.

    When decisions are made, they need to be clearly communicated on the public list for the agile team it relates to.

    Including volunteers

    To participate in an agile team, volunteers need:

    • Access to tools and information, so they can do work and communicate with agile teams.
    • Access to lists of “low hanging fruit” tasks related to the team’s work that they can pick up and work on.
    • A chance for inclusion in the conversation, whether synchronously or asynchronously.

    To achieve this, we need to:

    1. Review our tools, and make sure they can be made open to volunteers.
    2. Make information available, as described in the previous section.
    3. Make lists of tasks that volunteers can do in each agile team easily available. To achieve this, one suggestion is to share Epics with volunteers (don’t overwhelm them upfront with too much detail), but make lists of tasks available on the epic pages, along with who to contact about each task.
    4. Make it clear how you can communicate with agile teams — a clear mailing list and IRC/slack channel would be the minimum.
    5. Keep an open dialog going with our community:
      • Open up planning meetings to allow volunteers to take part in the planning.
      • Say what we are working on next before the sprint starts and what work volunteers can do.
      • Say how things are going during the sprint, and what help we need at each stage.
      • Report on how things went at the end of the sprint.
    6. Make meetings (standups, mid-sprint review, post mortem, etc.) more useful.
      • Include an IRC channel running at the same time, for further communication and to provide notes that people can read afterwards.
      • Allow people to talk about other subjects in meetings, to make them more human.
      • Sometimes conversation can be monotonous (e.g. “I’m still working on the same task” for 5 days running). If this is the case, use the time more usefully.
      • Use the meetings as an opportunity to update volunteer asks; if we find we need more help than we initially thought, do a shout out to the community.
      • Consider office hours for agile teams (whether in Vidyo, IRC, etc.), so team members and volunteers alike can drop in and talk.
      • Record video meetings so others can benefit from them asynchronously.

    We ought to fit communication with the community/volunteers into each agile meeting, as a recurring agenda item.

    Further points

    1. Make sure there is always someone present to help volunteers with questions they have, all the way through a sprint. Keep communication public; don’t let conversations happen in private, then risk the team member going on holiday or something.
    2. We should relax a little on the agile principles/processes — use them where they are useful, but don’t stick to the letter of the law for the sake of it, when it isn’t helpful. As an example, the MDN durable team has gone from everyone having a standup every day, to two standups per week for the writers, and two standups per week for the developers. We found anything more to be too high-frequency, and a waste of time.
    3. One situation that might make using open tools difficult is if any of the work is sensitive, e.g., discusses security issues. We could get around this by dealing with such issues inside private bugs on Bugzilla.

    Next steps

    We want to get feedback on this, and hear about other people’s pain points and solutions or insights for working open inside agile teams. If you have any other thoughts about how the process could be improved, please do share!

    After that, we want to distill this information down in a set of documentation to help everyone in marketing (Mozilla, or otherwise) to be open while working in an agile form.

    Mozilla at FOSDEM 2017

    Francisco Picolini

    With over 17 talks hosted in our packed Mozilla Devroom, more than 550 attendees at our booth, and our #mozdem hashtag earning 1,8 million impressions, Mozilla’s presence at FOSDEM 2017 February 4-5 was a successful, volunteer-Mozillian driven initiative.

    FOSDEM is one of the biggest events in the Open Source world and attracts more than 6,000 attendees from all over the world — Open Source advocates, Technical developers, and people interested in Copyright, new languages, and the open web. Through our booth we were able to hear from developers about what they expect from Mozilla — from our tools and technologies, our involvement in the open source community, how we can improve our contribution areas. We had a full day Devroom on Saturday with 17 talks (8 from volunteers) averaging nearly 200 attendees per talk that covered several topics like Dev Tools, Rust, A-Frame and others. There were also presentations about community motivation, Diversity & Inclusion, and Copyright in Europe. Together these allowed us to show what’s important for Mozilla right now, what ideas and issues we want to promote, and what technologies are we using.

    In working with volunteer-Mozillians to coordinate our presence, the Open Innovation team took a slightly different path this year, being more rigorous in our approach. First, we identified goals and intended outcomes, having conversations with different teams (DevTools, DevRel, Open Source Experiments, etc). Those conversations helped us to define a set of expectations and success for these teams. For example, Developer Relations was interested in getting feedback from participants on Mozilla and web technologies, since the event has an audience very relevant for them (web developers, technical developers). Open Source Experiments was interested in create warm leads for project partners, to help boost the program. So we had a variety of goals, which were shared with volunteers, and that helped us to measure the success of our participation in a solid way.

    DevTools talk Graphic

    DevTools talk Graphic

    FOSDEM is always a place to discuss and have interesting conversations. While we covered several topics at the Devroom and at our booth, Rust proved to be a common talking point on many occasions. Although it can be considered a new programming language, we were asked about how to participate, where to find more information and how to join the Rust community.

    All in all, the Mozilla presence at FOSDEM proved to be very solid and it couldn’t had happened with the help of the volunteers that staffed the booth and worked hard. I would like to mention and thank (alphabetically): Alex Lakatos, Daniele Scasciafratte, Edoardo Viola, Eugenio Petullà, Gabriel Micko, Gloria Dwomoh, Ioana Chiorean, Kristi Progri, Merike Sell, Luna Jernberg and Redon Skikuli and a lot of other volunteers that went there to help or only participate at the event. Also big kudos to Ziggy Maes and Anthony Maton, who helped to coordinate Mozilla presence.

    our volunteers at FOSDEM 2017

    our volunteers at FOSDEM 2017

    Some highlight numbers of our presence in this edition:

    • Nearly 200 people on average per talk in our devroom
    • Mozillians directly engaged with around 550 people during the weekend at our booth
    • More than 200 people checked our Code of Conduct for our devroom
    • Our hashtag #mozdem, had around 1,8 Million impressions
    • The Survey we ran at the event was filled out by 210 developers

    There are a lot of pictures and blogposts from mozillians on medium, or in their blogs. If you want to see some tweets, impressions and photos, check this storify.

    Community Spaces in 2016

    Brian King

    1 response

    Reposted from: http://brian.kingsonline.net/talk/2017/01/community-spaces-in-2016/

    As 2017 gets into full swing, the goal of this post is to reflect on the impact of the Mozilla volunteer-run community spaces we have in Asia. These are the spaces in Jakarta, Manila, and Taipei. I’ll be presenting data and some analysis based on that.

    In summary, there was:

    • 351 events
    • 173 Developer focused events, vs 178 other types of events
    • 4832 event attendees
    • Taipei sees the most traffic, in terms of events and attendees

    Yet data only tells some of the story. We’ll be also getting input from space stewards with insights on what worked and what didn’t ‘on the ground’ throughout the year.

    What?

    First, a reminder of what the community spaces program is all about. It is an initiative to open (or use existing) physical spaces for Mozillians around the world. It’s an experiment to create open spaces for people who are passionate about the open web, to collaborate with other communities, attract more talent into Mozilla, to strengthen local communities. The main hypothesis is that great things will happen. At Mozilla it was started by the WPR team in collaboration with the Community Building team in 2014, and in 2016 the Participation team took over the oversight of the project. Huge hat tip to William Quiviger who led the project until I took over in March.

    Here are some hypotheses we wanted to work on in 2016:

    1. We can engage more with developers in the local communities that the spaces are in, to promote what’s new in Firefox and Web technologies in general
    2. We can work with more partners (organisations, companies, individuals, …) to amplify common goals
    3. The local spaces strengthen the local Mozilla communities

    Events

    While it can be used for other purposes such as co-working, the main function of the space that we encourage is events. These can be presentations, workshops, hackathons, and so on. The goal is to promote knowledge sharing, learning, building relationships, and of course raising awareness of what Mozilla does from new and exciting technologies for the web platform going into Firefox to the issues campaigns we run to advocate for users and a better Internet.

    Focus

    In Q2 we teamed up with the developer marketing team to make a targeted effort to have more events in the spaces for developers. The goal was not just to introduce that audience to the latest and greatest technologies coming out of Mozilla, but to talk about the best in Web tech in general. We provided general guidelines on topics to focus on, and tips on how to run effective events. Then we introduced mentors to space stewards, and then left enough room for the magic to happen.

    Metrics

    So let’s jump in and look at some numbers, with a reminder that these are not for the whole year but from April onwards. Another caveat is that Jakarta has a handicap of only starting events in mid-May, so 1.5 months less than other spaces.

    For reference, the full report is here. Thank you to Rizki Kelimutu for putting together this great report based on event data we logged since April.

    Events Overview

    Events breakdown, in total and per event type

    There were 351 events in total, which is almost 1.3 events a day in the collective. This averages out between the three spaces at 117 per space. That’s is a solid rhythm but as you can see the number is not evenly distributed. Taipei comes out on top, with 55.8% of all events.

    There is almost an split between developer focused events and other events 173 vs 178. Looking at the breakdown of events between developer focused vs other types, per space they mirror the total however with Taipei a little stronger on developer events and Jakarta stronger on other events.

    Events Over Time

    Event over 3-week periods

    The over time trends shown here for each space show consistency, with several peaks and troughs. They can for the most part be attributed to holidays. For example, in Manila the summer vacation saw a peak as people had time to attend events, and the start of college classes in May/June resulted in a drop. During some months Taipei was seeing close to 25-30 events per month, meaning almost one a day! The November to December rise was helped by a visit from Alex and Nina from wizardamigos.com who hosted seven events to help people code for the first time in JavaScript.

    Attendees Overview

    Attendees breakdown, both new and returning, and per-event type numbers

    In general, the number of attendees reflects the number of events in each space. A couple of things jump out however:

    • The high number of returning attendees in Taipei. People coming back time after time to the pace shows high positive sentiment and engaging content for the local tech community
    • Manila attracts significantly more new attendees. This could be for a number of reasons, such as a large local community, compelling new content, a wide variety of different topics covered, or increased awareness in 2016 of the Manila space.

    And here is the the space by space comparison of attendees:

    Attendees Over Time

    Attendees over 3-week periods

    What is interesting here is the more frequent ups and downs in new attendees in all spaces, but take note that it is exaggerated by the smaller range (150) than returning (300). Attracting both new and returning visitors is a challenge. At its core however, it is about forming a strong sense of community, and ensuring strong and compelling content for people to learn and grow. In general for new vs returning, more detailed exit surveys would be needed to really find out the real story behind the data.

    There is one other topic that warrants a look, and that is the size of events. Here is how we classified them, in terms of number of attendees:

    • >30 Large
    • 10-30 Medium
    • <10 Small

    Let’s see how the spaces shape up. One thing to keep in mind is that the capacity when comfortably accommodating people is around 30 people, with only Taipei able to fit in more safely by removing tables. So large events would need to happen elsewhere, e.g. there is a cafe below the Jakarta space that they can rent out for bigger events.

    Jakarta Event Sizes

    Manila Event Sizes

    Taipei Event Sizes

    So I would say that the main barometer for success in general is that the majority of events lie at the mid-size level. And that seems to be mostly the case in Jakarta and Taipei, with Manila fairing worse with events most months having <10 attendees.

    What trends do you see in the report, and what other conclusions would you make from the data? Leave comments on this post if you have anything.

    Happenings and Highlights

    For me the highlight was visiting the three spaces in 2016. In January I went to Taipei to explore the idea of merging the staff space with the community space. While that didn’t happen this time, I did see up close the prolific and crucial work that volunteers do in the city and more broadly in Taiwan.

    In May I visited Jakarta and Manila. The purpose was to be present for the official Jakarta opening as well as: Check the status of the space in Manila, and visit other spaces in the city to see what the co-working/incubator/Maker Space scene is like; Talk to Mozillians in both communities to gauge community health; Monitor progress so far of, and provide guidance for, the developer engagement program; Get a feel for the wider tech scene in both cities to see where Mozilla sits and how we can spread our wings and make new relationships.

    MozSpaceJKT - Opening Party

    Listening and watching at the Jakarta space opening. Picture by Yofie Setiawan. More photos.

    I came away with a fresh appreciation of the intense dedication that a core group of volunteers in the community have towards Mozilla, the impact they have, and more context on the vibrancy of the wider tech scene they are working in.

    Here are some more insights and highlights on 2016 from some of the space stewards.

    Jakarta

    (by Yofie Setiawan)

    The Jakarta Space has been and continues to take part in campaigns for Mozilla. We are reaching the local Rust community, Developer community, and Web of Things. We took part in the Inter-Connected Community session at Mozilla Festival 2016, and we also support Mozilla’s marketing campaigns throughout the year.

    MozSpaceJKT

    Our space is limited to maximum 25 people that can fit in the space. Already we have run many events that are really inspiring for many people. The Mozilla Community Space Jakarta Launch Party of course was the most crowded event, which happened on May 2016. We invited many inspiring speakers to share knowledge and do workshops at our space.

    MozSpaceJKT

    Our strengths include that we have a good location central in Jakarta, that is easy to access. We have strong relationships with many inspiring people and communities who love to share their knowledge and ideas through Mozilla Community Space.

    Some groups or communities that we’ve been working with are:

    • WebVR Community
    • PHP Indonesia
    • Blogger
    • Framework (NodeJS, Rust, etc)
    • Rust Community
    • Python Indonesia
    • Open SUSE
    • Linux Community

    MozSpaceJKT

    Our main challenge is managing human resources, especially keyholders who help as volunteers to taking care the space when there are events running. We continually adjust for efficiency, so everything will stay well managed.

    We would love to see more events, especially which also relate to the ideas, vision, and mission of Mozilla.

    Some categories of events that we are looking forward to are:

    • Web of Things workshop
    • Mozilla Tech Speaker workshop
    • SuMo workshop
    • Teach the Web
    • WoMoz programming workshop
    • Engage more activity with Open Source Community
    • Rust Community
    • WebVR Community

    Manila

    (by Bob Reyes)

    The year 2016 saw a couple of firsts for the Mozilla Community Space Manila (MozSpaceMNL). Launched in August of 2014, MozSpaceMNL in 2016 became the venue of choice for new or re-established developer communities around the metropolis.

    Manila Space

    As for Mozilla Philippines Community’s part, we began conducting Introduction to Rust Programming Language events on a monthly basis. This led to the creation of a RustPH Group and the subsequent formation of a RustPH Mentors Group. Said group is now in the process of formulating a Standard Training Module for people in our locale interested in learning Rust as a second programming language.

    Rust in Manila

    In Summer of 2016, MozSpaceMNL played as host for the 2nd run of Maker Party for Kids (several days in the month of May). Conceptualized in 2015, the Maker Party for Kids events were able to train more than ten (10) kids aged 6 to 12 years old on the basics of HTML, CSS and JavaScript the Webmaker’s Thimble as the primary teaching tool.

    Also in 2016, a couple of events related to Privacy awareness were held at the Community Space in Manila. Noteworthy was the forum to discuss the Implementing Rules & Regulations (IRR) of the Philippine Data Privacy Act of 2012 with no less than the Deputy Commissioner of the Philippine Privacy Commission as our resource speaker. This event was followed by smaller weekend pocket sessions targeting on students to be aware of issues related with data and online privacy.

    Data Privacy in Manila

    Aside from MozillaPH-organized events, MozSpaceMNL also served as venue for meetups of other like-minded organizations:

    • Several Code Camps co-organized with Developers Connect Philippines (DevConPH)
    • Emacs Users Group Philippines Meetup
    • Manila WordPress Meetup (which eventually led to the resumption of Word Camp Manila)
    • Mechanical Keyboard Warriors Meetup
    • Philippine Web Designers Organization Meetup
    • Google Developer Group Philippines (GDGPH) Firebase Live Viewing Party
    • Virtual Reality Philippines (VRPH) Meetup

    Manila Space Event

    In October 2016, MozSpaceMNL participated in the very first Inter-Connected Community Spaces activity during the Maker Festival held in London, England.

    Inter-Connected Community Spaces in Manila

    For 2017, we plan to continue with at least one Rust-related event per month. Co-organizing developer-related events with like-minded organizations will also continue. MozSpaceMNL’s support to other organizations by means of providing venue for their meetups and the like will still be there. We also hope for more inter-connected community spaces activities soon.

    Taipei

    (by Irvin Chen)

    2016 is the third year of Mozilla Community Space Taipei. MozTW and more than 30 local open (source/culture/data/gov) communities together, we had host 320+ various events for 3300 people, and introduced Mozilla and our Mission to more than 600 first time visitors.

    Happy Birthday Firefox

    A typical MozTW Lab in a special day

    The best event in the space is “MozTW Lab” (as always), the local Mozillian’s weekly meetup. Volunteers gathering each Friday night to socialize, work, and give lightning talks on different topics including Mozilla’s latest update. This meetup had been running for 8 years, and in 2016 we had visitors from all over the world including Mark Surman, Brian King, Larissa Shapiro, William Quiviger, Max Ogden, Fa-ti Fan, 田爱娜 and many more.

    Mozillians all around!

    Mozillians all around! (click/touch and drag image to explore)

    Another highlight of 2016 for the Taipei space is the diversity of the events, visitors and connected communities. There are growing types of the communities, dev-rel, open culture, open source and civil society community host events, workshops, meetups, talks, hackathons, and study groups. Different types of fun almost every night happened in Community Space Taipei.

    Baking some Firefox cookies

    Baking some Firefox cookies

    For dev-rel topics, Rust and WebVR workshops are the newest. But people also shared knowledge on JS / NodeJS, Python, Swift, React, Spark, OpenStack, C#, Clojure, Java, D3, Functional Programming, Android App… You can learn and meet community for almost every programming languages, popular or not. We also help by providing the venue for new dev communities such as “WizardAmigos CodeCamp” (local one).

    For open culture and non-dev technical events, Wikipedia and OpenStreetMap use Taipei Space for regular meetup, and there are workshops and meetups on Ubuntu, openSUSE, Fedora, R, Arduino, InfoSec, students and many more. There are also many gender based technical communities and events such as WoFOSS, R Ladies, Swift Girls and PyLadies. Larissa Shapiro’s visit in January reminded us of the importance to keep the space a place of diversity and inclusion for all.

    Taiwanduino 組裝工作坊

    Have you ever build your own Arduino?

    One of the most special part of the Taipei space is the events and meetups from local civil societies, open government and open culture communities. Gov. hackers and programmers played an important role in democracy development recent years in Taiwan, and Taipei Community Space had become a base for popular open communities such as Open Culture Foundation and G0V. Our keyholders also actively support events about digital human rights or internet governance from Taiwan Association for Human Rights and Citizen Congress Watch. People came to making, hacking and watching not only the technology, but also the human rights, democracy and civil society in the community space.

    Happy Birthday Firefox

    What do you want to share in Community Space Taipei?

    Wrap-up

    Let’s revisit our hypotheses and see how we fared.

    We can engage more with developers in the local communities that the spaces are in, to promote what’s new in Firefox and Web technologies in general.

    We teamed up with developer marketing, and had a total of 173 developer-focused events since April. This was everyone from beginners to experienced developers, on a host of technologies related to the Web.

    We can work with more partners (organisations, companies, individuals, …) to amplify common goals

    All three spaces have built up a network of all different technology companies and organisations. They engage at different levels, from working together on projects to sharing the space to have events.

    The local spaces strengthen the local Mozilla communities

    The Philippines community has in recent years been one of our largest and most dynamic, most notably in the area of student engagement. However, 2016 presented a number of challenges that decreased engagement. They have reached out for support from Mozilla and have a desire to bounce back. The communities in Taiwan and and Jakarta have a strong core, and while they have the classic growth challenges that all communities have, they have been trying new things and working in different ways to strengthen the broader open source movement.

    On balance, 2016 was a strong year for our community spaces. It has been shown that with the right support, and with alignment with community development and Mozilla goals, spaces can make an impact and raise Mozilla’s profile locally. Other communities around the world have been paying attention, and have requested support for the own spaces leading to an open question is how can we scale this model.

    Looking beyond, we can keep momentum going and identify areas for improvement. One thing I would like to see is teams at Mozilla working more directly with the spaces on programs that can help them achieve their goals. So far in conversations I’ve been having, Developer Relations, Developer Marketing, and Connected Devices are interested in doing this. And a broader question is how can the current spaces help with our broader Firefox product goals in Asia.

    Many thanks the community space stewards and keyholders who devote their free time to this. It is a great pleasure working with you, and I salute you for what you do!

    Firefox 51 new contributors

    Josh Matthews

    7 responses

    With the release of Firefox 51, we are pleased to welcome the 47 developers who contributed their first code change to Firefox in this release, 42 of whom were brand new volunteers! Please join us in thanking each of these diligent and enthusiastic individuals, and take a look at their contributions:

  • c3.sazae3: 1296123
  • fiveNinePlusR: 1291830
  • habeebahma1: 1261313
  • ktakashi19980515: 1291061
  • longsleeper: 1293567
  • mgsudhanva: 1282910
  • p.panayiotou2: 1285745
  • rsurve: 1255843
  • skoji: 1295866, 1298571
  • Adam: 1288745, 1299143, 1299144
  • Akihiko Odaki: 1298565
  • Akshay CV: 1296182
  • Andrew Magdy: 1293000
  • Anthony Miyaguchi: 1277595
  • Arseny Malkov: 1295531
  • Bhuvnesh Maheshwari: 1299207
  • Calvin Lui: 1287594
  • Divyanshu Vishwakarma: 1292998
  • Dragoslav Mlakar: 1282289
  • Glenn Fernandes: 1022545, 1292542, 1296395, 1296945
  • Gregory Moore: 1298709
  • Hallvord R. M. Steen: 1291069
  • Hassan Ali: 1256929
  • Igor: 1197328, 1197331, 1289890, 1293384, 1296180
  • Jason Woofenden: 1008019
  • John Paul Adrian Glaubitz: 972945
  • Julian Chu: 1296748
  • Kacper Michajłow: 1297794
  • Kim Moir: 1277579, 1293730, 1296088
  • Ninad Bhat: 1301628
  • Paul Yang: 1286513
  • Pierre Bertet: 1224863
  • Piyush Sinha: 1274167
  • Prakhar Agrawal: 1298909
  • Pranaydeep Singh: 1293738
  • Saheda Reza: 1298016
  • Sumit Tiwari: 1290566, 1290698, 1292999, 1298512
  • Tanuja : 1285940
  • Udayan Baidya: 1297693
  • Wil Clouser: 1288178
  • Wladimir Palant: 918600, 1300735
  • Yuri Kazuna: 1291481
  • kashyap: 1290701
  • kevin: 1134307, 1140286, 1254867, 1273369, 1283704, 1301126
  • ou shinjo: 1266165, 1274484
  • sj: 1295080, 1295556
  • tuhina chatterjee: 1293002
  • yusukeTMJP: 1297000

    • Regional communities and Reps in 2016

    Ruben Martin [:Nukeador]

    Full static version is on the wiki and its conversation on discourse, feel free to point there anyone that might be interested.

    What got shipped

    from the Reps and Regional Communities Team

    Index

    • Executive summary
    • The Team
    • Release notes

    Executive summary

    Our two objectives for 2016 were:

    1. A focus set of relevant training and learning opportunities for mobilizers are systematized and they regularly access these opportunities to be more effective in their contributions and as a result providing more impact to Mozilla’s main initiatives.
    2. Reps is the program for most core volunteers where many communities feel their voice represented and influencing the organization, and where mozillians join to be more aligned, grow their skills and be more impactful in mobilizing others.

    During 2016, the Reps and Regional communities team delivered:

    • A coaching training material to systematize training and coaching support to core mobilizers and communities, starting to be completely volunteer-driven in 2017.
    • An initial Leadership toolkit tailored to invest on the main identified skills our core mobilizers need to support Mozilla’s focus initiatives and areas.
    • Five in-person community gatherings in our top focus regions (Brazil, India, Europe, Arabic and Mexico) to test, iterate and deliver these coaching and leadership opportunities to key core mobilizers, as well as document and systematize this effort to allow volunteer to run their own local ones by themselves in 2017.
    • Support the creation (and regular update) of Activate Mozilla, a site to summarize the main focus areas for Mozilla (Rust, Servo, Test Pilot, WebVR, Internet Issues…) and how to provide value through activities co-created with functional partners.
    • Clear alignment, re-activation and impact delivery from the five focus communities, re-energizing and providing value to organization goals with Activate Mozilla activities during 2016 and helping them to come up with aligned plans for 2017 to support focus projects, including future partnerships with local organizations.
    • Alignment and impact delivery from regional communities around the world, with our Reps mobilizing almost 150 activities and events in more than 23 countries in the last 4 months supporting Test Pilot, Webcompat, Rust, Addons and E10s 2016 team goals.
    • A big update to Mozilla Reps (RepsNext) to evolve the program by supporting all these learning opportunities and becoming the main alignment, leadership, mobilizing and backbone force at the volunteer community (improving internal processes, mentors, coaching and regional representation/support).
    • Expand the support to our core contributors communications by enabling a discussion channel for NDA volunteers and staff and keeping core mobilizers in the loop with the organization communications, direction and encouraging conversations.
    • 100% increase in the positive sentiment about Reps program and Participation from our core mobilizers, as well as a very positive re-activation, engagement and alignment with 35 local communities thanks to Reps Regional Coaches.

    The team

    Release notes

    December 30, 2016 (Q4HB4)

    • The Reps Review Team managed to reduce the budget approval time by 30%, this means that now it’s easier than ever for volunteers to request resources to support their activities.
    • Data from our last community survey shows that in the past 6 months we had a 100% increase in the positive sentiment about Reps program and Participation from our core mobilizers.
    • The coaching training material is available for anyone to use and will enable to systematize coaching training and be volunteer-driven thanks to the first cohort of new coaches we trained.
    • The Leadership Toolkit has now generated 13 new workshops and has a solid group of core contributors with a strong background developing and testing the material.

    December 2, 2016 (Q4HB3)

    November 11, 2016 (Q4HB2)

    • We held the Mexico Community Gathering in Mexico City, with a clear focus on reactivating the community, solving conflicts and aligning with the focus priorities.
    • 10 existing Reps Mentors began the new coaching training, expanding this way our coaching efforts to the existing mentor group in an effort to refresh and improve their skills.
    • At least 35 local communities showed a very positive sentiment about the re-activation, alignment and support from the Reps Regional Coaches.

    Mexico Community

    October 21, 2016 (Q4HB1)

    • There is now a wiki page where the budget allocation of the Reps program is explained each quarter, a transparency effort and also a way to signal Reps about the priority areas at Mozilla.
    • Reps Regional Coaches were provided with training on coaching and conflict resolution an identified need to better perform in their work with communities.
    • The Arabic Community Gathering took place in Casablanca, Morocco, reactivating, aligning and improving the community health.
    • The plan for systematizing coaching training was presented with the initial learnings from the work we have done so far.
    Arabic Community

    September 23, 2016 (Q3HB3)

    • The European Community Gathering took place, with special focus on reactivating communities and align with the Copyright campaign.
    • The first cohort of Reps Coaches started their work onboarding new Reps.
    • Reps Regional Coaches started their work meeting with all Mozilla local communities as a way to understand their current status, needs and align them.
    • The new Reps Review Team started to operate as an administrative body to review and approve the resource requests from the community and align the allocation with the current priorities. This body is accountable and overseen by the Reps Council.

    European gathering

    August 26, 2016 (Q3HB2)

    India gathering