From MozillaWiki
< Drumbeat‎ | p2pu
Jump to: navigation, search

Summit Roadmap


  1. Project logo
  2. "About": the overall project story or elevator pitch in 5 short, sharp story points.
  3. Progress. Where we stand. What has the project accomplished or built so far? What early successes / impact can we show off? (screen caps, demos, etc.)
  4. Roadmap: 18-month vision. What’s the utopic end state we want to reach? Describe perfect.
  5. Roadmap: end of 2010.
  6. Roadmap: end of September.
  7. Participation / ways to help. What are the top 3 ways people can help the project right now?

18 Month Vision

P2PU School of Webcraft is now being referred to as the "The grassroots Ivy League of Webcraft." Consistently, both large and small web organisations are recruiting employees and contractors using our Job Board. Webcraft alumni are referring to our Webcraft skill competencies and Hacker Attitudes in their CVs and these attributes are also being used in job descriptions that aren't even posted on our site.

Mozilla have been very successful in working on the certification process for the competencies. Mark / Ahrash - can we get feedback on what should be here?

Our roster of courses continues to feature the 10 core modules for all skill levels, however every round we're receiving offers of new courses. We're also happy to see alumni remaining in the community and beginning to organise courses based on topics that they had studied in earlier rounds.

The community of P2PU Webcraft is evolving into a community of practice for open webcraft professionals and amateurs. The competency maps are maintained and updated by members who also participate in the Web Standards Group and major open source projects like Drupal and Apache.

The global reach of the P2PU Webcraft community (particularly in Brazil, South Africa and the subcontinent) has led to the localisation of the School of Webcraft pages as well as the entire P2PU site. Our core courses are often taught in several languages besides English, primarily Portuguese, Spanish, Arabic and German. Where demand is high, we've had face to face courses are organised in libraries, media labs and co-working environments. Students from these groups continue to use the P2PU Webcraft site to manage their portfolios and connect with the community.


  • The key for the roadmap section is to stress ~nouns~ and changes of state. Not verbs or a list of tasks. We want to describe what the project looks like at that point. Not the set of tasks we need to get us there.
  • For the "progress" section, we can include screen grabs / demos / etc. We’re using Keynote, so video is ok here, too.
  • Keynote template attached. (And PDF version as well.) No design necessary at this point -- we can just stick with plain white, and then we'll put into a Drumbeat design template later.
  • Please include any images, artwork, etc that you feel could help tell the story. Don't have to be included on the slides -- feel free to just send as attachments.


Rough first draft based on conversation w. John Britton

P2PU Open Web Roadmap

  • Identify key dates and deliverables from now to end of 2010
  • Assign ownership / responsibilities for each
  • Identify questions, blanks & next steps

1) Complete Competency Map

DATE: July x

Identify and map what today's developers need to

  • get up to speed on the latest open web technologies & skills
  • develop a strong "hacker" attitude & open web values
  • get great jobs


  • How do we do a better job of publishing & sharing what we've already done on this? (e.g., digitize and publish John's flickr diagram)
  • How do we make it easy and compelling for people to contribute to the map? Could be as simple as leaving comments on the Drumbeat project page. Or as fancy as contributing to some sort of interactive map.
  • How do we effectively plug Mozilla Summit participation into this? Likely to be lots of opinions and expert knowledge there. Need to effectively capture it.
  • What's a sexier more intutive name for this than "competency map?"
  • How do we make the completed competency map cool, dynamic, and interactive? Instead of just a dry  document.

2) Establish Advisory Board


  • Gather a panel of 10 - 12 experts that can provide guidance, credibility and profile-raising
  • Use the process of shaping and developing the competency map to draw & identify these people.

  • This came out of conversation with John Britton. Is this an agreed on need / milestone?  '
  • What are the next steps?

3) Create template guides for course leaders


4) First "Open Web" courses begin

September x

  • GOAL: 5 - 10 courses
  • When does registration for classes start?

5) Courses end. Award badges / accreditation. Yay!!!

Date: when will courses end?

  • Let's think about how we can make this a success story. Photos of successful course graduates with their shiny "Open Web Developer" badges or accreditation
  • How will the accreditation process work? (Arash?)

6) Update Competency Map

  • Revise and expand competency map based on feedback from learners, mentors & community

7) Second semester of classes start 

DATE: November x

  • Goal: Grow to 10 - 15 classes

8) Second semester of classes end


  • Again, let's make this a success story