View source for Drumbeat/p2pu/Summit2010brainstorm

= P2PU School of Webcraft Working Session =

== Session Overview ==

John & Pippa hosted a working session at the [[Summit2010|Mozilla Summit]]. The session started with a brief overview of P2PU, School of Webcraft, and Drumbeat. We asked four questions:

* How can P2PU School of Webcraft gain street-cred with employers?
* What are the soft-skills that a web developer should have?
* What are the technical skills that a web developer should have?
* What courses would you like to see at P2PU School of Webcraft?

== How can P2PU School of Webcraft gain street-cred with employers? ==

Present: Gunner, Adam Hyde, Richard , Gregorio?. Nathan, Pedro<br>

*Tell Stories showing success (eg employment offers, projects begun, internships, contracts received, use as prior learning in formal edu environments)<br>
*Be clear about how assessment works<br>
*Luddites within institutions – beware of these.<br>
*Admin / non teaching staff will be most resistant<br>
*Teachers will be supportive<br>
*Organise for formal mentoring (i.e. a dedicated mentor)<br>
*look at how Red Hat provide cert.<br>
*Primary target audience should be employers<br>
*Easy to show results with project based work, how to assess theory based learning??<br>
*Track people as a way of finding stories<br>
*extension of community of practice (community of success)<br>
*Look at Comptia?<br>
*Try to organise a jobs fair<br>
*Mozilla needs to hire alumni&nbsp; or Redhat – google, major company&nbsp; (eating the pudding we made)<br>
*Look at External Testers and proctor services<br>
*LPI.NET (dave sefry)<br>
*infrastructure<br>
*linux sys admin<br>
*Look at Free software – is the freeness of this going to affect our credibility?<br>
*Quality<br>
*economic transformation (focus on Nathan's audienc)<br>
*Need to be able to update their credentials<br>
*How do we encourage quality facilitators <br>
*measurement? Metrics?<br>
*Evaluation help?<br>
*Students need to be active about recording what they learn – reflective based practice<br>
*blog about it – hash tags<br><br>

== What are the soft-skills that a web developer should have? ==

present: <br>Xander, Noelle, Carlos?, Guillermo<br>

*Delegation<br>
*Community Engagement<br>
*Communication Skills<br>
*Bedside Manners<br>
*“onramping”<br>
*Managing the politics of a project<br>
*negotiation<br>
*tie breaking (moving out of deadlock)<br>
*Team building - ie the right people at the right place<br>
*Asynchronous tasking and communication (*SoW relies on this – they'll drop out otherwise*)<br>
*Blogging – evangalism and documentation<br>
*Passionate<br>
*Able to mentor others.<br>

=== Key Takeaways ===

*If someone has begun and run an open source project (with more than two people contributing) of their own they'll have done all of this<br>
*perhaps this can be a “graduate” course – something longer than 6 weeks which is mentored over 6 months or a year?<br>

== What are the technical skills that a web developer should have? ==

participants:&nbsp; Paul Osman, Tantek Çelik, (Didn't catch the names of other attendees, add yourself!)
*HTML<br>
*Microformats<br>
*Javascript (jquery, prototype)<br>
*CSS<br>
*Text Editors
*Server management
*Updating a server
*basic server administration (minimal)
**.htaccess (HTTP)
**Database Theory – to admin level
*Categories
**Client side
**Server Side
*UI Design
*ux / accessibility/ usability
*SVG
*Canvas
*OOP / Functional / Procedural / Layering Best practices
*Web Services
*Adaptive Media (Mobile and Print)<br>

=== Key Takeaways ===

The most important thing I took away from this was to filter courses that were based on dying technologies / poorly supported tech. eg SOAP, RSS<br>

== What courses would you like to see at P2PU School of Webcraft? ==

participants: Daniela, Austin... who else (hopefully they use the website) Atul<br>

*Web Service Dev w Python
**Entry level python – basic HTTP, request response 
**REST!
*How to make cool stuff on the web if you never programmed
**no complications
**big deal for nondev who need to know it
*Open Software Ethics
**Community Driven Process
**Openness all around
**Be Open Minded
*How to Design the Web – changing websites with stuff you create
**Photoshop
**Web Style
*User Experience / Interface
**The user is important!
**Happy Users
**More Users
**Wise
*Dive Deep into JS Jquery, Jetpack SDK
**Show what we (mozilla) can do
**powerful tech
**developers
**How to communicate with your manager about technical issues
**Effective change, less trouble at work
**Willing to collaborate

== Suggestions ==

We then split the room into four groups and worked on each question for about 20 minutes. After the session each group reported back, this is what they had to say.