Notes from August 6th meeting

Attendees: Attendees: ctalbert, rpappalardo, michellemarovich, marcia, rbillings, lizzard

Planning documents for Grow Tunisia Event

• This info was taken from Kristin Baird's email
• --- gdocs version of Kristin's email (with links): https://docs.google.com/a/mozilla.com/document/d/1PCCLXGNa59fMj3M1EYg5M6FMMFhxat9ntXLsrZzMdWw/edit
• Dates of Event: September 26-28
• Location: Tunisia
• Presenters: marcia and lizzard, kthiessen backup
• Final chance to nominate community to attend: https://etherpad.mozilla.org/tunisiacommunityattendees
• Event Agenda: https://docs.google.com/drawings/d/1hImXOs3jDogtlT4n7zPMwHuP9NvvWcNyWKnajP4V11A/edit
• High Level Timeline: https://docs.google.com/drawings/d/1qAG2M8FVCNekiBEgeAHbjJJUAbC9CznVNg1AwyLv8l8/edit
• Content Development Flow: https://docs.google.com/document/d/1npxT7ID3VXCkFand8zdkcsUL_ZwqLDE57kKIw3SXpUo/edit#
• Deliverables for this week (week of August 4th):

• • Sign up for sessions here: https://docs.google.com/document/d/1Cw5y624RbE72rJ-KJwzlUEwHJ3bfYrO1DBfFUmSVG98/edit
  • Build a RASCII with your team (first cut done and saved in the folder below -- we can review/revise at this mtg if needed --kthiessen)
  • Template: https://docs.google.com/document/d/1PeUSAnjELfIK9UdqT5zJJxGHCCj-89LOMdJ7mvqVcZg/edit#heading=h.2dfjfbx08oc8
  • Template gets saved here: https://drive.google.com/folderview?id=0B9zaW1buOkBMV3liSkJUbmhrcjQ&usp=sharing

5 Strategic Questions are also done (to a first cut) and saved in the content folder. revisions/additions welcome. --kthiessen. [karl] Are we going to get Gaby as our community partner for this team, or do we need someone else?-- Gaby isn't eligible for Tunisia, unless she's based in Europe. [liz] How about Francesca? She is in Barcelona.

1. Outcomes

• Need measurable outcomes in the specific versus the abstract
  • Picking an outcome that we cannot measure sets us up for an inability to know whether we have been successful
  • If this event is a success, what outcome do we want?
    • We want more people doing tasks in One and Done
    • Local meetups, if these people are supposed to be growing their community
    • Regional community growth in QA measured by events held, tasks completed
  • We expect to see activity
  • Target areas, list of people who thought would attend -> having a measurable outcome - the people who attend the session are going to take on responsibility for events, One and Done, they also step into a leader role in taking those actions
    • Development of this area of the world for QA
    • Like to see people trained become more involved with the QA team - we are connected with them and they understand how to grow the community. They understand what they learn but they have a lifeline.
    • We want to know who are the people that are interested.

2. First Actions for a New Contributor

• Perform a task in One and Done
• Attend a test day on IRC
• Ask a question on the dev-quality mailing list.
• Report a bug
• Look over the documentation sources (MDN, MozillaWiki)

3. Audience

• Minimum viable level of technical ability
  • Students who are in active universities are the highest/valuable contributors identified in our exercise during Work Week.
  • High impact profile that we want them to focus on - what do they need to be able to do?
    • Tinkering with websites, computers, Linux users groups
      • Student Computer Club
      • Engineering
      • Web development
• This one can be refined over time.

4. Recruiting

• People attending the event
• Most effective things in terms of events and learning - their job to then think about how to get that information. Content -> what do they need to teach people at those events.
• We need to give them specific things
• How to set up an online event.
  • Register people for the event and track who they are.
  • Bug bash
  • Regional test events affiliated with our test events (Same theme, etc)
    • Localization QA is built for this type of things
  • Maker Party - they had it roll around the world...feeling connected to a bigger thing
  • Game aspect, hands on, interactive, people doing demos
• Host event competitions - how many regional areas in EMEA want to have a test day - set some criteria, the event that does this gets this type of recognition
  • Bragging rights that come with the competition
  • Regional Bug Bash competitions
    • Coming back on regular basis vs slogging thru lots of bugs

5. Enabling Content

• Lexicon of terminology
• Overview of Mozilla's QA teams.
• Tools we use on different teams.
• Overview of the Firefox release process.
• List of our main documentation sources.
• Willing to gather in small groups and practice with one another
• Temperament to work together
• Testing mindset. Explore, look for edge cases, break stuff
  • Looking for those people
  • Trainers -> list of resources -
  • Big Picture Ideas to understand how to get started. Approach this session about what QA is what we do
    • Overview - different functional areas of QA. Useful immediate engaging information
    • 80% case that is the same -
      • Think about what you want to test - error handling. how to file a decent bug.
      • Lingo - regression window, reproducible bug, STR

Kind of content, kind of people

• Why somebody might be interested in doing it?
• What is motivation?
• Getting on the cutting edge
• Consider using hardware as an example
• Thinking like a tester
  • Fun experiential stuff will be a part of the session
• Do we need to consider our appeal to them?
  • Do we need to develop 2 skill sets?
  • Think of it in terms of them helping them to recognize good contributors for the area