WOW followup plan

[abbycabs]

I can own this if everyone is okay with that :construction_worker: :pencil2: :book:

owner: @acabunoc to consult: @zee-moz @auremoser

General ideas:

• [ ] set broad milestones (global sprint, run a local sprint, get on Collaborate) - cohort wide. Rough dates:
  • Collaborate launch: March 2016
  • Local event: March - April 2016
  • Global sprint: ~May 2016
• [ ] bi-weekly (every two weeks) check-ins with each project -- @acabunoc & @auremoser
  • we can divvy this up in the way that makes the most sense once we know what projects we have
• [ ] set individualized action items at each meeting
  • possible action items:
  • meet with this designer/project manager/other help we can provide
  • write contributor guidelines
  • submit a pull request for feature X to be reviewed by [mentor]
  • launch feature X
  • find X number of users to test out the feature / product
  • talk to X number of users - get input on your project
  • meet with X potential collaborators
  • book a location for the global sprint
  • meet with Arliss about your sprint
  • put together a communication plan to advertise sprint

• [ ] put together generic timeline of action items to work off of / create individualized goals

  • 12- 16 weeks of followup (depending on when global sprint is)
  • 6 - 8 check-ins + 1 post-global sprint check-in

  Etherpad: https://public.etherpad-mozilla.org/p/olc-plan

[abbycabs]

Requirements to get on Collaborate

Some of these documents will be constantly changing as you work on your project. Don't worry about having a perfect Roadmap or README before you launch on Collaborate!

1. project on GitHub
2. open LICENSE
3. readable README
4. Issues teased out in the issue tracker
   • Have "good first bugs"
5. CONTRIBUTING.md: contributor guidelines
   • with a way to get in touch with the team
   • and a Code of Conduct
6. Roadmap: development status
   • at least a stub
7. Mentorship: be ready to give quick feedback and engage with contributors

[auremoser]

Study Group Ideas

Some modifications here for study group projects, modeled after the "General Ideas" above and the issues in the WOW repo.

cc/ @acabunoc

• [ ] set broad milestones (global sprint, run a local sprint, get on Collaborate) - cohort wide. Rough dates:
  • Collaborate launch: March 2016
  • Local event: March - April 2016
  • Global sprint: ~May 2016
• [ ] bi-weekly (every two weeks) check-ins with each project -- @acabunoc & @auremoser
  • we can divvy this up in the way that makes the most sense once we know what projects we have
• [ ] set individualized action items at each meeting
  • possible action items:
  • meet with this designer/project manager/other help we can provide
  • complete tasks from their issues, template here
    • write README, LICENSE, Code of Conduct
    • write CONTRIBUTING.md
  • launch study group X
  • host a pilot event
  • talk to X number of attendees - get input on your project
  • meet with X potential collaborators
  • book a location for the global sprint
  • meet with Arliss about your sprint
  • put together a communication plan to advertise sprint
• [ ] put together generic timeline of action items to work off of / create individualized goals
  • 12- 16 weeks of followup (depending on when global sprint is)
  • 6 - 8 check-ins + 1 post-global sprint check-in

[stephwright]

Sounds like we need to review this in our Pathways discussion for WOWs, mentorship, OLTS. Shall I set up a mtg for us to discuss this? Anyone else need to be in on the discussion at this point?

[stephwright]

Just sent an invite for this mtg :)