Michelle Marovich is preparing to run the Designing for Participation workshop for the People team. She’s looking for some real world examples that can help make the concepts concrete for everyone, so she set up a Contribution Madlib template for people to fill out.
Here is mine, on a contribution idea I have for sometime now.
I want to get more people to contribute to Mozilla Location Service, I need thousands of people to help me on it therefore I will reach out to all established geo-communities and post on all relevant forums and mailing lists in order to publicize the work.
Then I will organize regular open meetings and local meetups with communities on the ground in order to engage with the people who are interested. I break the work down into tasks by creating local teams that can self-organize the work that needs to be done locally.
I communicate those tasks by a form of an online game, so people become more engaged with the contribution opportunities. So that we can work effectively together, I always make sure that we have an open channel on IRC with people on call to answer questions. I continue to raise awareness of the work by evangelizing what the team is doing on the already established channels of the Geolocation industry.
I communicate decisions and progress by delegating this to the people on the Location Services team that are handling progress reports. When we achieve a milestone, reach a goal, or someone does something amazing I recognize them by cool prizes, badges and local recognition titles.
FirefoxOS grew quickly to be a super active project under constant global development by hundreds of people around the world (employees and volunteers in Mozilla). Over the past two years we developed a fully fledged open source mobile operating system based on web technologies. Naturally the least thing you could do as a Mozilla contributor is to try to keep track of what is happening, and arguably this has been really difficult from the start.
On one hand this is understandable. The pace the project is moving is lighting-fast, with requirements and dates changing constantly. On top of that, our partnership with companies of the industry (OEMs, OBs, chipset manufacturers etc) has made the tracking of things even more complex.
On the other hand, the successful end result (and engagement of new people) is a hint (or a proof?) that there might be a way to track things for us mere mortals. With this post I will try to describe the discovery and tracking procedure I am using to keep myself engaged and updated about FirefoxOS. The info I am looking for are one or all of those: dates, owners, projected ETA, code, specs, mockups.
Disclaimer: This is by no means an official guide to feature-tracking but rather a documentation of my personal experience and definitely tailored to my tracking needs. Hopefully this can be proven useful to other people and I will get some suggestions in comments, so comment away!
Let’s start with the basics. Bugzilla is your central source of information about everything happening in Mozilla-verse. But we will need more than that to be successful. We need to be able to understand how things are tracked within Bugzilla. My focus has been Gaia (as the most FxOS-unique part of FxOS stack) so let’s say for the sake of this guide that we are looking for more info on a Gaia feature. (e.g. Custom ringtones)
Our first stop is Gaia wiki. Wiki.mozilla.org is used for all high-level tracking of FxOS features (and pretty much for all other Mozilla projects too)
Navigate through the page and you can find all different major areas of Gaia (Apps, System and their sub-parts) Once you locate the section that your feature is under (in our case System>Sound) click through to land in the wikipage specific to the area of the project. Although the Gaia (and generally FxOS) team has done a fantastic job of updating the wiki with status of features and roadmap you might end up in a not-so-helpful wiki page (like in our example).
Stepping back a bit, our goal is to find more info about a feature. For every feature you might think of there are three different scenarios:
Scenario 1: Feature is a planned, detailed and committed one.
If the feature is something that the Gaia team is committed to deliver (approved in meetings) then one of the following can happen:
The easiest case is that all the info you need is on the wikipage we just explained how to find. Boom you are done!
A slightly trickier case is that the info is not yet on the wiki so you need to search bugzilla for it. Before you do that make sure to check out the UX specs making sure that your feature is part of the committed ones. (Bonus: get lost in the fantastic work that UX team has done!) Searching bugzilla you should use “Advanced Search” with “Boot2Gecko” as the Product and make sure you search for both NEW-ASSIGNED(generally open) *and* RESOLVED status. FxOS team is delivering like crazy and your feature might be already delivered! You can easily identify the “official” commited bugs by their title ([User Story] something_here) and/or their priority/severity (P1/blocking etc)
Once you find the bug you are looking for you can get all the info you want or cc your self to get more info as they come (m0Ar bugmail please!)
Scenario 2: Feature is a proposed one.
In this scenario the feature is something already proposed by someone and there is an active (or not!) discussion around it. Bugzilla is your only help here. Follow the instructions above on Bugzilla search. Most of those bugs will be UNCONFIRMED or NEW (definitely not ASSIGNED and hardly RESOLVED as INVALID or WONTFIX) so tweak the bugzilla search accordingly. Make sure to be constructively involved in the discussion around the feature (based on your expertise) so you can make sure that your lovely FxOS device will soon have your killer feature!
Scenario 3: Feature is not even a proposed one. (It’s all in your head!)
You know the story… File a BUG! But wait! Before you go ahead and file a bug, opening the flood-gates of bugmail, make sure to do the following: Check with UX guidelines to see if you missed something. There might be a case that something is already spec’ed out in UX designs but not translated to a bug. In that case ping UX people on IRC channel #gaia for follow-ups. If UX designs prove to be unaware of your awesome idea you might want to have a look at project Haida. Project Haida is the UX project for proposed features and designs for future versions of Gaia.
If everything fails and you are the sole person in the world thinking about this cool feature, you might as well go ahead and file a bug (following bugzilla guidelines and etiquette) under Boot2Gecko Product and the Component that fits your proposed feature category.
Extra channels: As always make sure to drop by Mozilla IRC on #gaia (or #b2g if that’s suitable) and ask for help if you are stuck. Mozillians there as *awesome* and super responsive.
Hopefully this over-view of my workflow as a non-member of FxOS team will be useful to some other Mozillians out there Please go ahead and comment with ideas and enhancements (or corrections!) of the process. Special thanks to Fredy for his countless hours standing by me navigating through FxOS code, and asuth for his responsiveness on any Gaia related questions we had
When we embarked on our journey with Mozilla Reps almost two years ago we knew that the Mozilla Community was a vibrant and energetic ecosystem of contributors, full of activities and events. We set ourselves the goal to further empower the community, to help Reps grow their local communities, to raise visibility of activities and to document their achievements thoroughly.
Last week we hit an important milestone. On 14th of April 2013 we hit the 1,000 mark. One thousand events that Mozilla Reps organized or have participated in more than 80 countries.
The increasing amount of Firefox OS related events organized by Reps in recent months reflects the incredible momentum that the project is gaining. Reps are ready to play a critical role in our launch markets later this year, actively raising awareness about the project and inspiring new contributors to get involved.
Some “damned lies” for all the statistic lovers out there:
Total events: 1154
Rate of events so far: 1.93 events per day
Rate of events last 3 months: 3.18 events per day
Total Reps: 407
Special thanks to the previous and current council members for all their hard day to day work on the program, and their visionary inputs for the ways forward.
Over the past 4 weeks, the Mozilla Reps Web Development team has been
focused on delivering new discoverability features to enhance our
portal. Last night we landed what we believe to be the most awesome
version of Mozilla Reps portal ever!New features include:New timeline vizualization of events
Having a map to visualize all our events and better document and
manage our events throughout Mozilla was a breakthrough 6 months ago,
on how we . But we wanted to take it one step further. We envisioned
and implemented a timeline visualization for events that works with
our search bar in events. You can now visually identify and scroll
through community events worldwide and through different time periods
Vouched mozillians login
In true spirit of pioneering the integration between Mozilla services,
you now have the ability to login into our portal if you are a vouched
Mozillian (with persona) even if you are not a Rep! You can then
customize a dashboard based on the interest areas of Mozilla you want
to track, and get activities and metrics from Reps that are working on
This new functionality raises the awareness around the countless
activities that Reps are driving across all functional areas and
delivers easy discoverability of Reps working on those areas, so that
you can communicate with them. As always we already have in the
pipeline the enhancement of functionalities around this new feature,
like email abilities, unification of dashboards between Mozillians and
Reps and other cool new dashboard functionalities.
and many more features…
..including the ability to email all participants of an event via a
mail modal in event pages, ability to extract people info and emails
if logged in the site in /people page, ability to search in events
based on date range and enhancing the email notification
As those lines are written our web developers together with our webdev
volunteers are working on a Voting system and new commenting system
and categories for events. You can find all about what is in the works
in our current dev sprint.
Special thanks to our devs Tasos and Nemo, our code reviewer Giorgos,
our production manager Ben and all the Reps for the countless
countinous feedback and improvement pointers.
I would like to take this opportunity and welcome our two new webdevs Tasos Katsoulas and Yiannis “Nemo”Giannelos both django-ninjas at day and beer lovers at night! An obvious fit to our team they worked tirelessly on imporving the functionality of the portal and adding new features. In particular:
Implementing a new ‘Settings’ page for opting in and out mailing features (bug 818036)
Send an email to the owner of a report after each comment (bug 758603)
Enhancements in “mail my mentees” form (bug 763490)
Send email to mentor when a mentee files a new report (bug 762418)
Monthly reminder for new reps to mentors list (bug 774247)
The new mailing features will enable Reps to communicate more efficiently among their activities and streamline the reporting procedure more. Over the past 1.5 years Mozilla Reps have filled over 3000 reports! Feel free to browse through reps and check out their reports and activities!
Other features included:
Custom planning pad urls for events (bug 794008)
iCalendar export for single event (bug 761544)
Show rep of the month on their profile page (bug 784281)
And also some regular Bugfixes:
CSV export is now working fully(bug 815766)
Date reset when event save fails is fixed(bug 778865)
Fix duplicate results in API queries on “People” page (bug 824892)
General housekeeping and many minor improvements.
For our next 3 week sprint we will be working on adding cool new features on our portal with a focus on discoverability and vizualization! Timeline vizualization of the events, communication to event attendees, ability to login to our portal given a vouched mozillians.org account, are just some of the
things to come.
This weekend (in 2 days!) Mozilla Reps will be running a documentation sprint in a collaborative effort to make our Documents and SOPs even better!
We need your documentation, writing, wiki-ninja skills for 3 days starting this Friday 25th Nov till Sunday 27th Nov.
You don’t have to be a master in documentation, devote 3 full days or even be a Rep to join us.
We will be coordinating our efforts in #remo IRC channel and in this EtherPad
Finishing and polishing some SOPs will be our primary focus (more info on the EtherPad). We will make sure to have people on IRC all the time to coordinate efforts and we are expected to hold some calls and IRC chats.
If you plan on joining us, please write your name on the Etherpad and drop by IRC to discuss on what we should focus those 3 days!
We will shortly announce a kick-off 3 hours long call/meeting for Friday (afternoon for GMT)
If you have a question stuck in your head, you need to get an answer.
“Which is the place in the world with biggest Firefox share?”
Antarctica has consistently Firefox share of 80+ % for years now! (Based on all stat/market share agencies that I could dig into). This could come as a surprise to some people, but think about it! It is totally logical. Antarctica is packed with scientists/pioneers/engineers/brilliant minds that can settle for nothing less that bleeding edge technology, and this is Firefox!
Now how about leveraging this power and recognizing this fact? How about a Mozilla Antarctica Community?
Let’s kick this off! Over the next weeks David Boswell, Robert Nyman, Anthony Ricaud and me will reach out to those people, establishing a community where no browser has gone before.
The usual suspect, a brown van arrived once again in my doorstep. This time the package was kinda lightweight. But I should not judge by the weight.
I quickly opened the white wrapping and I had a mysterious grey bag in front of me.
Looking a bit closer, on the tag, my heart jumped “Mozilla ReMo Pack – XLarge”
Finally, it was party time! I cannot remember the moments between the grey bag and having all those super-uber-cool goodies laying on my desk
The bag includes:
10x – Firefox standard-issuebuttons
2x – Firefox old-time-classicslanyards
2x – Mozilla Reps the-little-awesomebuttons (white)
2x – Mozilla Reps the-little-awesomebuttons (black)
5x – Mozilla the-proud-ones transparent stickers (white)
5x – Mozilla the-proud-ones transparent stickers (black)
2x – Mozilla Reps flagship transparent stickers (white)
2x – Mozilla Reps flagship transparent stickers (black)
1x – Mozilla Reps awesome-readypolo shirt
1x – A6 bonus welcome note
When we kickstarted Mozilla Reps back in June, we wanted to make sure that every single Mozilla Rep will be equipped with the finest set of swag to be identified and spread the love. Now we are able to provide it!
Rep mentors will be contacting their mentorees for delivery of those cant-wait-to-have packs
It’s not everyday that you have to wait 2 weeks to be able to gather all updates after a meetup, due to their volume…
Two weeks ago, I was more than lucky to be able to join Arabic Community for their first Inter-Community Meetup. The hosting community was Mozilla Jordan and we were happy to have Majda and Moncef from Algeria, Melek and Sahar from Tunisia, Haitham Sinar and Ahmed from Egypt, Firas and Hatem from Palestine.
Arriving on Thursday, it was pretty obvious that this was going to be a fantastic meetup. The hosts have done excellent job on arranging travels, accommodation and meeting place. Thanks Rami, Rami, and Jordanian team! (Issa, Addy, Abdulrahman e.a). By Friday everyone has arrived and the advantage of no-language barrier (everyone was speaking Arabic) was quickly noticeable. Socializing between the team and sharing best practices started even before the official start of the event.
The First day (after a long breakfast with Egyptian team raiding the place) we focused on presenting the teams and making sure that everyone knows each other. We were lucky enough and more than happy to have Mitchell Baker with us (Chairwoman of the Mozilla Foundation), who was touring Middle East visiting the local communities.
Eman from Mozilla Jordan
After a long reality check session, were we identified Pros, Cons and Ideas for the Community we broke for lunch, and returned having a session on grouping and discussing about individual items that were raised in Reality Check. As night approached, everyone was so engaged in discussions around Mozilla’s presence in Arabic region, that we almost forgot the Amman-by-night walk we have arranged.
Amman is a city of 7 hills, inhabited by several civilizations over the past several thousand years. The multicultural spirit can be seen all around this wonderful city, and was the perfect setting for a Mozilla Arabic meetup!
Second day started with a goal setting session, and task management over specific goals. Cool ideas were examined and are on track (Country wide tours, parallel events within Arab region, common portal expansion and aggregation of Arabic content). Also we did a series of mini presentations about Mozilla projects (REMO, AMO, SUMO etc)
Haitham, Soliman and Mitchell
As promised Sunday afternoon, we had a much-needed hands-on hacking session, were we examined specific projects of Mozilla and ways to contribute on them. Bugzilla introduction, Firefox hacking and add-ons 101 were in the schedule and unfortunately we didn’t have enough time to expand on other aspects of Mozilla. Next time more hacking time! (promise!)
Sunday night was the time for out public event. We arrived in the university right on time (speeding through Amman’s heavy traffic) and although the attendance was not as high as expected, the viewers of the live stream picked at 400 people J Egyptian and Tunisian team did their magic, using social media channels and the event was covered fantastically. Mitchell gave a talk on Mozilla in general, Ahmed fascinated us about Arabic Fonts and Content and their challenges on the web and Melek with Majda gave an excellent introduction to the Open Web in Arabic (and partially French)
Firas, Sahar, Melek and Hatem in the public Event
The impact of the event was huge. Here are some of the posts about the event and some quotes from social media:
Two weekends ago it was time for our biannual Mozilla Balkans Meetup. The splendid tradition has started about a year ago in Skopje and it continued to Ljubljana. This time it was Sofia’s turn (and Mozilla Bulgaria community) to host the Mozilla Balkans Community for a two days event full of workshops and quality time between members.
We all arrived in Friday, and we used most of the day to get ourselves set up in the huge (yet old) Moskva Hotel in Sofia. I was traveling together with the Greek community representatives Kostas Antonakoglou and Fredy Damkalis (our rookie!) We spend most of Friday in catching up with the rest of the team and learning the new faces
Saturday was a community working day. We had great presentations by L10n team (Chofmann, Pike, Matjaz, Milos and Vito) and then we had a community working session around what has been good and bad on Balkans community lately.
The day ended with the Firefox 4 party of Sofia with many local people attending and having a long Q&A session with us all.
Sunday was kinda a wrap up day, as we sat down to our laptops and tried to fixed loose ends of the Balkans Community. Regional websites, L10n caveats, Sumo pushes and community health were covered as we worked throughout all day.
A week after the meeting we asked everyone to fill out their Individual Feedback on the Aftermath page.
Interesting quotes from that page:
everyone made it safely to the meetup and safely back home (yeap.. with taxi drivers of Sofia, that’s an accomplishment)
we need to have 2 full days of work so we have enough time to have presentations, discussions and hacking (+1 for me! 3 days event would be a better option from now on)
no wifi (the epical fail) (that was indeed kinda disturbing but Kostas hosted an adhoc network and we were fine)
The instructions Bogo prepared for printing were perfect, should be used as a template for future events. (Indeed pretty helpful handbook!)
Have an MC / responsible for every unit on the schedule and make sure he knows his rights & his responsibilities. (Important aspect of organization that should be taken care next time)
Next stop: Athens! (we still need to finalize it, but Greek team is getting pretty excited about that!)