From MozillaWiki
Jump to: navigation, search

See the thread started on compatibility mailing-list

MozCamp follow up (Larissa)

MozCamps_2014 MozCamp 2014 Wiki and IRC #mozcamp2014

Current Status, MozCamp Beta in Bangalore is moving forward with a small number of content areas. Engagement decided to focus on the $25 phones for this camp. The larger "main" camps

  • Larissa:This year MozCamp is moving away from something like a celebration event to more of a learning event. The wiki page currently is oriented around the "beta" event. Basic gist: it was decided that MozCamp should be centered around educating people on how to build contributions. There were 10 areas defined, Web Compat is one.
  • Larissa:Three non-Beta MozCamps: September 2014 in Asia, November 2014 in Europe/North Africa, January 2015 in Latin America. I will get the most recent content templates and share them with your team.
  • Larissa:Next steps: There should be a template and a schedule around expected revisions, curricula, speakers, etc. I'll make sure your team is up to speed on that.
  • Karl:If the Beta event is not successful... what are the success criteria for the beta event?
  • Larissa:We're going to do the beta, then reconvene the design committee. We're not planning to not have the next MozCamp, but we might radically change how we do it. I do not anticipate changing the types of content.
  • Mike:How many people would you anticipate from our team to be at these events?
  • Larissa:The ratio of staff/volunteers should be stable. We might 2 to 3 persons. The more people, the more chances we need to have people specialized in the area to be able to break up in groups.
  • Larissa:We have 3 hour contribution sessions, and we'll be repeating them twice (perhaps 3 times for a larger event). In that sense having more than one person there is a good idea, so it's less exhausting. With 3 hours, we can get through why, what and how, and some action planning.
  • Karl:How long in advance will you know about the next event? To be able to prepare material, booking, etc.
  • Larissa:Best guess, the events team is working on venues and dates right now. I'm guessing before the end of June we'll have all the times and days.
  • Karl:Do you have an idea where they might be?
  • Larissa:We want to have the Asian event in Singapore. Possibly Morocco, I have no heard about Latin America.
  • Karl:Do you need something from us in the next two weeks?
  • Larissa:No. I think we should reconvene in the next few weeks and I can give you more information. The list we're using is the community events list for discussion. I've been pushing to have the same updates be published to the About: Community blog.

Pathways to new contributors (Larissa)

  • Larissa:I wanted to ask about how new folks are getting engaged and what their first opportunities are. And if I can be any help there. We have this contributor lifecycle, that may be helpful.
  • Karl:We have a core team of people that have been doing the work for a long time. The process is well-known. But it's something where we need to engage more people... or allowing them to have a sense of ownership over web compatibility at large. People should not have to rely on us, they should be able to do the work themselves. It's more useful in my mind if people are doing something to help the web, rather than do something because someone from Mozilla asked them to do something.
  • Brad:We're also hoping to get other vendors involved, not just volunteers to help in a Mozilla effort.
  • Mike:We are building this Web site It is functional. We (Alexa, and myself) are trying to get people involved in these reported issues.
  • Larissa:We are trying to grow active contributors. How do you know if someone is really involved?
  • Karl:There are almost two types of contributors. There are people who will try to contact engineers, companies, sites, etc. And trying to get their sites fixed, e.g., Abdul. It's a little different than just taking a core issue and submitting a patch. Sometimes it's a bit tough.
  • Larissa:To plant a couple of ideas, I'm wondering whether the goal of the initiative is getting websites fixed, rather than building a community.
  • Lawrence:We need a large number of people. We're a small group, we can sustain it. There's various types of contributions, small and large. The idea behind is to build an easy place/tool where people can come and contribute.
  • Larissa:It sounds like one of the big challenges is getting people to "stick" and form a community.
  • Karl:And many people working on issues does not make a community in itself.

what is the pathway for new contributors to web compat?

  • karl:from the top of my head: articles, twitter, and conferences/workshops.
  • Larissa:Other options for finding webcompat contributors may include about:mozilla (the newsletter), the new Get Involved page (revamp coming this year) and other forums.

But this is not the only meaning of a pathway for me. What I'd really like to discuss is our team's observations (and learnings) of the process of developing a contributor community, as documented at: and how I can support web compatability's goals, if at all, using a similar process.

how people's contributions are tracked?

(this should be on the list)

  • karl:People's contributions are currently not tracked. And it doesn't really make sense to really track them if they don't get something out of it such as their own dashboard for knowing about their own work. So maybe a better question, do people need/want to track their work? As for tracking the progress on our activities, we monitor the components of Tech Evangelism. So we know when a bug is not being taken care of anymore. We can either help with additional comments on helping finding the right contacts. And sometimes need info the person. It has happen that I sent a private message to the person to ask if she/he wanted to continue the work or to just give it up so we can dispatch to a new person. It's essential that someone can feel free to leave. But to leave or abandon the work properly is essential to not have bugs in limbo. For example, the person can remove her/himself from the bug ownership. It's a strong indicator "I do not intend to work on it anymore."

Plans beyond just MozCamp to get more contributors.

  • Mike:I have been working on learning emberjs to build the issues stuff. It has a fun learning curve. I need to restandup Alexa has commented on some issues and made progress on the mock ups for the issues design.
  • Alexa:I'm focused on github UI, but I might need to reconsider.
  • Mike:I like the idea of being close of the github style and keeping some UI conventions. Everyone should comment on the issue

Contribution sections

Bug for WCIDFM

Topic: Broken Voices of the Web

Check the Planet Web Compatibility for the community news. Here a few posts lately published.

Topic: Web Compatibility Progress