QA/Contribute/Training the Trainers/2014-07-15

Meeting notes

• sessions want to recognize contributors, sorting interest, teaching Mozillian habits- working in the open, interaction between contributors @Moz.
• 7 suggested session, please add other ideas, will also put out call on dev-quality
• introduction, mini-activity/interactive exercise, debrief

discuss

• rbillings - I prefer working on multiple sessions, as opposed to being responsible for an entire one or two
• likely to be easier to create a template and then copy it into the other sessions
  • This is where the Webmaker teaching kits will come in handy
• mbrandt:

-interactive activities are good, giving a problem set, discussing it, letting them do it, and then debriefing

• • zacc and Romanian team did this well for automating FF OS
    • Lots of contributors came to this event, was different in that it was participatory rather than listening event, but it went well
  • webmaker is all about creating portable content that can be presented by anyone easily
• are we looking at building community, or building out our FF OS story?

k: emphasis on recruiting volunteers, FFOS can be part of that, is the next part of mobile, is on the roadmap, QA is a good way to get in

m: so we want to create a funnel, where to start, as go down funnel they become more focused, more core contributor

m: do we have Reps in Tunisia? we should reach out to Reps and ask them what tools THEY need, what training THEY need that QA can give them to make them more effective. They are the trainers who will engage the broader community

m: series of small asks have shown to be more beneficial than broad/large scope asks; create a workshop to engage the room to come up with a strategy; talk about how community is formed, interactions are created. We bomb people with technical stuff, but that isn't the way to start community- look at how we welcome people, what the story is, also there is a cultural aspect- need to respect what works for them. Create an onboarding ramp to our funnel- series of small asks, ask them to help fill it in. Actions come from that- needing better documentation, or understanding QA wanted tags, find the low-hanging fruit.

k: that fits well with '= Developing locally relevant resources =' session; developing cultural awareness is def. part of that package

Suggest:

• talking to Larissa Shapiro re: contacts in Tunisia, if she has ideas on what would be a good session
• contact Misty Orr re: intern

R: how would we know if the event was successful?

k: if we have reps who are ready to talk to Mozilla local comm, why it's impt, why they should help out. what QA is specifically looking for in contributors, able to see who would be a good contributor

r: they already do the first 3 things, sounds like focus is to identify good contributors and point them in the right direction

m: in the past reps have only focused on marketing, reps mobilize their local groups, reps council trains the reps, the reps have groups w.in countries that mobilize. Their mission is expanding - can't just have reps who only work on marketing campaigns, need to look at global Mozilla mission, can branch out and get involved w/technical aspects. - if you think of contributor pathways of funneling people into their interest areas, idea is to give reps enough info to talk about areas- why are open standards impt, and then send the people to US, to the QA team so we can shape their experience. Getting them to our doorstep.

discuss

r: we need to know our audience- sounds like they are not technical, or no expectation of being technical. we need to know what they want.

k: yes, we'll want to find non-technical folks a preview of our sessions to find out what people don't understand

r: we want technical contributors- because we let people down who wnat to learn and want to be lead through the how-tos of qa and development, we aren't a school

k: want people of a interested/curious mindset

m: webmaker does this well, need to clarify that we aren't a teaching org.

m: reps are good at getting people excited, as mhoye said it's enough to have people come by once, more important to teach these Reps how to tell our story

r: maybe focus more on non-technical or low technical presentations

k: impt to set expectations for Reps party, of 50-100 ppl, 45 may be good for a webmaker party, only 1-2 suitable QA candidates

r: are we going to sell webmaker more than QA? Are they doing their own sessions or not?

k: michelle would know

m: maybe send people to webmaker to get started, learn terminology, add to your own goals

r: spectrum: webmaker ---> manual testing ----> automation/development. Reps can identify where people are on that spectrum.

r: who is QA? What do the different teams do? we need to identify what teams the presenter is representing, be able to explain wha t they do, and how to get involved

r: would it be easier to make a handout of many resource links, or create a webpage?

k: easier to have one master link

r: lots of team info is spreadout between sources, good to have a master index

k: my idea is to match http://mozillapersona.info/

r: +11111

k: maybe add to qmo

Action items

• karl: email dev-quality to solicit session ideas
• matt: start initial conversation w/Tunisian Reps
• karl: Does Larissa have any Tunisian contacts?
• M: find out connection btw webmaker/mofo/moco
• karl: ask michelle: are webmaker going to be at the TTT event? are Reps the audience- or more than that? Is there a link to the event yet?