AMC2010 Report Back 2: School of Webcraft Workshop

Peer2Peer University WorkshopOn Sunday morning, I led a workshop on the Mozilla Drumbeat project Peer 2 Peer University School of Webcraft.  I was very pleased to have 20+ attendees show up to the AMC Media Lab bright and early on the last day of the conference.  Below are some highlights from the workshop, including questions and critiques, course suggestions and an early start on a new course called Open Web Toolkit.

After a round of introductions and ice breakers (“What’s your favorite thing that you can do with the web – your web super power?”), I started us off with a brief description Mozilla Drumbeat, and then we dug in to discuss the School of Webcraft and begin to brainstorm the kinds of courses and other support that the School will need to be successful.

For the uninitiated, Mozilla Drumbeat is supporting a new Peer 2 Peer University (P2PU) project, the School of Webcraft.  While anyone can use P2PU to organize a course on any topic, we are working with them to create their first comprehensive set of courses that will allow anyone (with the connection and bandwidth) to study web development and become proficient in open web technology.

After introducing the concept, I asked the participants to brainstorm potential challenges for this model.  Here are a few main questions that came up:

  • Why should people trust the course content?  I think that once people get used to working through P2PU, they will see that the course content is transparent and open to review and improvement (a little like Wikipedia), and every course organizer(P2PU-speak for “teacher”) will be open to improvements as their courses develop.
  • What about accessibility?  People wondered about issues like basic web access, disabilities, different learning styles, and the range of potential learners’ starting points (think prerequisites).  In that order, I suggested that P2PU won’t solve the web access problem, but that I hope in the long run that we can partner with community technology centers and libraries to provide the necessary connectivity.  I wasn’t aware of P2PU’s strategy for supporting people with disabilities, but would check into it (starting with this blog post, which is going to the P2PU team).  I believe that P2PU course organizers will get better over time at working with diverse learning styles; as a volunteer effort (course organizers are unpaid, co-learners with the other participants), we will probably struggle with this for a while.  Finally, I mentioned that P2PU course descriptions give a pretty clear indication of previous knowledge participants will need to be successful in a course.  Questions around language and culture differences came up, too.  I know that the P2PU team is working hard on these issues, and that we should see courses in Spanish and Portuguese pretty early on.
  • Are P2PU courses focused on book learning or hands-on experience?  Definitely, the latter.  Participants should finish all School of Webcraft courses with at least one project they built for every course and leave the program with a portfolio, a key piece for moving from education to employment.
  • Is the School of Webcraft accredited?  This is a big, big question in the open education movement – how do we compete with the traditional institutions that have a kind of monopoly on accreditation.  It’s also one of the main reasons that Mozilla Drumbeat is investing in Webcraft – we believe that we can organize all the big players in the open source space to create a peer-recognized certification that anyone should be proud to put on their resume.  Apparently, we aren’t without precedent in this area.  One workshop participant pointed out that CompTIA’s certification services began in a similar, peer-driven manner.  If you are interested in the accreditation question, please leave a comment or contact me, as that conversation is ongoing.

Then, with just a little time left, we got onto the really good stuff: brainstorming the kinds of things people wanted to see offered through the School of Webcraft.

We got a few suggestions, namely:

  • Design for Developers: one participant said that a major trend in hiring for web development is that clients are expecting developers to have an eye for design and the ability to design something beautiful in addition to building something functional.
  • Developer Lingo 101: A course to ease the pain we get when bombarded with techno-speak.  I mentioned that I think this will be covered in the Web 101 course, and someone else offered that the School could have an online glossary that everyone in all the courses could use and improve.
  • Open Web Security: ’nuff said.  Good idea.
  • Open Web Toolkit: this is the one where I thought there was the most potential for building out some course content…

Open Web Toolkit Brainstorm

This course suggestion came from one participant recalling the pain of acquiring a toolkit for web development without any clear recommendations.  Basic web development tools include: text editors (you just should NOT use a word processor to write code), version control systems (like Subversion and Mercurial), FTP clients, IRC clients, and Firefox plugins like Greasemonkey.  Clients, and plugins, and bears, oh my!  This could definitely make a new learner’s head spin.  I can really see the value of a course dedicate to a peer review of all these options, where the participants each leave with a toolkit of their choice.

The P2PU team agrees, so we will be following up with the participants and seeing who wants to get involved in shaping that course up for the September course cycle.

Thank you so much to those who participated.  We will be following up soon.

Share

3 Responses to “AMC2010 Report Back 2: School of Webcraft Workshop”

  1. Atul says:

    Hey Nathaniel,

    Really cool ideas! We’re actually working on some new in-browser tools for developers to use in Firefox 4, and it would be great to get feedback on them from anyone in your program.

    One of the tools is called Inspector:

    https://wiki.mozilla.org/Firefox/Projects/Inspector

    And the other is Console:

    https://wiki.mozilla.org/Firefox/Projects/Console

    With respect to web security, Ian Bicking (also of Mozilla) had an interesting thought about how to go about teaching this recently:

    http://www.google.com/buzz/ianbicking/LKiQedT8eDP/I-feel-like-writing-something-along-the-lines-of

    I can see if he’d be interested in helping with something like this at P2PU if you like.

    Finally, regarding the Open Web Toolkit, one big decision that even experienced professionals have a lot of difficulty making is choosing a client-side JS library to be the foundation of their web app–such as JQuery, MooTools, Prototype, and so forth. On the server side, there’s a vast plethora of languages and web frameworks to use too, of course. Would these fit into the Open Web Toolkit, or would they be covered somewhere else?

  2. Hi Nathaniel,

    Thanks for writing this up and to Atul for pointing me to it.

    Regarding the text editor, version control, FTP and possibly even IRC, this is the kind of thing we’re hoping to make easy and “zero install” with Bespin in a few months. We’re redoing our server to make it possible to do a lot more and a lot more quickly. It would be great if new developers could just sit down at any random computer and start creating beautiful things for the web :)

    For now, though, you’re right that a new developer needs to figure out their way through a huge maze of tools that they need to find and install.

    Kevin

  3. … trackback …..

    Fascinant doudoune moncler http://www.myscenespace.ca/blogs_view.php?id=2364 doudoune moncler pas cher et dispara?tre m’un commentaire pour me dire ce que vous pensez…

Leave a Reply