From MozillaWiki
< Reps‎ | SOPs(Redirected from ReMo/SOPs/Reports)
Jump to: navigation, search
Warning signWarning: With effect from 1st September 2023, the Mozilla Reps program was closed and activities ended.

MozRep-Final-Outline.png Main | Join | Procedures (SOPs) | Leadership (Resources) | Meetings | Website | FAQ

Reporting Your Activities

Report - Community Portal

Some activities will automatically be reported in your Community Portal profile as you contribute as a Rep. At the moment, the Community Portal documents when you create an event, indicate that you will attend an event or participate in a campaign. You will find those activities in your profile (we invite you to adjust your privacy settings so that your activities are visible to, at least, registered users).

Please report all relevant events in the portal (on-line or in-person). If you give a talk in a larger event you can report the talk as a single event. If you have a community meeting you should also report it as an event.


Some reps activities, however, are not reported in the portal. You can self-report those activities by filling out the reps reporting google form. Please note that you should only report Reps-specific activities, to say those activities that Reps carry out as community coordinators. See here for more details on how to use the form. A summary of the activities reported using the form can be seen here. If your name is not in the table, please contact a community manager.

Reporting during and after an event

  • A Mozilla Rep sponsored to attend or organize an event is responsible for blog posts about that event. The number of blog posts is based on the length of the event, and the posts should be spread throughout the event.
    • 1 or 2 days = at least 1 blog post.
    • 3 days = at least 2 blog posts.
    • 4 days = at least 3 blog posts.
    • N days = at least N-1 blog posts.

NB: here is awesome example of a blog post written after an event:

  • The Mozilla Rep who is owner of an event should encourage all the other Mozillians participating in this event blog, tweet and publish photos of the event.
  • The blog must be aggregated on Planet Mozilla.
  • A brief summary of event should be sent to Events category on Reps discourse at the end of the event that provides links to all the blog posts, both by the event leader and by other community members at the event.

Content Suggestions for reporting

The following are some general questions to think about when reporting back about an event and/or blogging about it.

  • How many people were at the event? Was the Mozilla booth busy?
  • What kind of comments did you receive about Mozilla? What were the most recurrent questions?
  • What were the biggest complains about Mozilla? And the most common words of praise?
  • Were there any questions that were asked many times?
  • Were there repeated suggestions for improvement in a particular area for Mozilla?
  • Did you meet anyone using Mozilla in an interesting way or on a large scale?
  • Did you give any talks or lead any sessions? What did you cover? How many people attended?
  • How much swag did you give away? What swag was popular? What swag was not so popular?
  • Did you sign up any new Mozilla contributors? If so, to which projects?
  • Include pictures in your blog post if at all possible.
  • What other open source projects or like-minded organizations participated at the event? Did you learn anything interesting from these organizations/projects? Did you make any interesting contacts?

Event Debrief on Discourse

Sharing a short debrief of an event you attended with other Mozilla Reps through Reps Events Discourse is also a very effective way at helping others learn through your experience and replicate your successes.

Here's an example of simple event debrief format that you can use:

Topic name: [NAME OF EVENT] - [CITY], [COUNTRY]

[BRIEF SUMMARY in max 3 sentences]

  • Audience type and size
  • Mozilla's participation at this event
  • Audience reactions
  • Evening event/party
  • Materials (eg. slides, presentations, audio clips, photos etc…)
  • Other notable presentations
  • Other open projects attending (if applicable)
  • Organization rating (1: bad - 10: excellent)
  • Overall feel of the event
  • This event helped us...
  • Was it worth it?
  • Should we participate again?

Here's an example of a event debrief you could send to Reps Events Discourse:

Debrief: Super VanJS, Vancouver, Canada

Christian Heilmann and I spoke at the Super VanJS conference ( 
in Vancouver January 14th, right after our work week.

-= Audience and size =-

I was told there were close to 200 people who had signed up for the event, consisting of mostly 
local web developers. Overall, they seemed to have good work experience and interested in open 
source and building things for everyone.

-= Our participation =-

Among the five presentations, I and Christian gave one presentation each. I was first out 
talking about Mozilla's Web Apps initative, introducing them to what the project is about 
and how you can start building Web Apps. Christian then spoke about reclaiming HTML5 for 
building good things everyone can benefit from and also to show how easy it is to build 
powerful web sites with all the APIs we have at hand today.

-= Audience reactions =-

My goal was mainly to make people aware about Mozilla's Web Apps and get them interested 
in learning more, and from the feedback after, it seems like it went well. Second to that
 was going through technical possibilities, and I hope it made them realize how they can 
utilize their already existing skills to build Web Apps.

Christian wanted to get developers more aware how we can use new technologies like HTML5 
and CSS3 for every web site, and not just build shiny demos that go away/become useless 
after the first hype. From talking to people, they were very happy with his talk and walk-
through of various tools web developers have.

-= Evening event =-

After the conference there was a organized meetup where the speakers and attendees could 
mingle, discuss more and exchange experiences. It was a down-to-earth context and a good 
way to talk more.

-= Materials =-

Slides from my presentation are available at
web-apps-supervanjs and the audio and content from Christian's presentation is available 

All the talks were also filmed by our very own Jeff Griffiths 
(, and we hope 
to be available to share the videos further on.

-= Other presentations =-

Rebecca Murphey - Spoke about Toura Mulberry ( and mobile 
Preet Jassi - Gave a presentation on YUI
Jim Andrews - Delivered a different kind of presentation, arguing for how we can use 
HTML5 canvas to create art, through the help of Math

-= Direct competition =-

No competition, just a bunch of speakers talking about how we can create things with 
technology. :-)

-= Organization =-

To my knowledge, this was the first time this local meetup was arranged with that many 
attendees, and I think it all worked well. Everything was in place, and we just showed 
up and did what we are supposed to do.

-= Overall feel =-

Good interest from the audience in an exciting scene that has spurred PhoneGap and other 
interesting projects.

-= Leads =-

Getting in touch with local web developers, and establish/improve their relationship to 

-= Was it worth it? =-

I think so. People were happy to see us and discuss and learn more.

-= Should we go again? =-

Yes. It's a local event with good outreach, and we both have local presence and close 
proximity to San Francisco/Mountain View. We also sponsored this event, and my feeling 
is that it's worth that investment.

Best regards,