[p2pu-dev] Community Meeting Notes - 28 July 2011

Rebecca Kahn bekka at p2pu.org
Thu Jul 28 16:25:00 UTC 2011

Here are the notes from this week's community call. Thanks to all who
All notes (plus the chat transcripts, complete, this week, with sounds!) and
previous notes can be found here: http://pad.p2pu.org/community



   - Helping skill up learners so they can succeed in an environment like
   P2PU? [Pippa]

   - Is this something we can try to support in the helpdesk or does it
   belong somewhere else? Is it a course in itself?

   - Are the dev change lists useful to transform into documentation for
   users? [Zuzel]

   - Potential idea - Technical writing / documentation course (MDN and
   other contacts)

   - build their portfolio around P2PU documentation. [Pippa]

   - Survey: Results & purchasing data


   - Pippa

   - Jessica

   - Zuzel

   - Bekka

   - Artur

   - Erin

*Stand Ups*

   - drafting School of Webcraft Update

   - providing context and challenge document for Web Challenge Designer


   - Mocking up PD assessment/analytics to send to p2pu-dev list; will be in
   phases since integrating Google analytics will take a bit more research

   - Catching up as a new paid part-time staff member

   - Hope to have drag/drop tasks in before Monday's release -- if not, then
   next :) Hooray!


   - qa.p2pu.org is at the production server now

   - assessment design group call last Monday:

   - survey sent :)

   - dev meeting: https://github.com/p2pu/lernanta/wiki/Dev-Meetings-2011


   - Contracting admin

   - Preparing this week's featured courses and monthly update

   - General admin


   - New courses, handbook

   - Connecting local p2p groups w/ p2pu


   - Kicking off/managing the p2pu design group

   - Translating their initial design ideas into the badge integration plans

   - Buncha stuff for the Open Badge Infrastructure beta launch


*Helping Skill Up Learners*

   - Traditional graduate / undergraduate studies provide a great deal of
   material for helping students with stuff like writing good essays, study
   skills etc.

   - At P2PU we don't  provide a great deal of that kind of material

   - Should we be providing this kind of support to help people be better

   - Most of our users are not organisers, but participants, so it's
   important to provide them with support.

   - It's proably a good point to strat providing people with the support
   they need to know how to use P2PU, but not just in terms of the technology

   - What are the social permissions you/they have?

   - needs vary from course to course

   - but we should be looking at this

   - maybe this is related to a social contract

   - Or possibly badges

   - Something similar to the orientation that you get during orientation
   week as an undergraduate - eg.  here's the library

   - lots of things to learn in P2PU - eg. how to join the call

   - Documenting our processes

   - eg. Running great meetings

   - we have tools - but nothing about meetings

   - Useful inputs: Cathy Davidson (Duke/ Hastac) 21st literacies, learning

   - tech savviness, community savviness

   - http://hastac.org/blogs/cathy-davidson

   - collaboration as a literacy

   - users can be bewildered by the freedom of the P2PU model (Mentoring,
   deadlines, student engagement are important) (Artur, yes we !00% agree)

   - where's my organiser - No - we gave you a space, not an organiser. etc

   - How to _start_ implementing it?

   - small steps: eg. How to run (and participate) in a great meeting.

   - Follow up: List Discussions

*Communicating Dev Changes Documentation for Users*

   - Are people using the change list?

   - Is it valuable? YES, majorly

   - How do we transform this into documentation?

   - how do people figure out that something changed? Bekka willing to help
   with communicating this stuff

   - Technical writing and documentation course (MozDN and others can help)

   - tweeting, blog posts etc

   - anyone who gets messages - all help desk

   - John& alison are tweeting the changes, and blogging it would be

   - The change lost is part of the evolution of the site, and some stuff
   will change, or is in flux, and doesn't need explanation

   - Where does this information belong - in QA or in the handbook?

   - If stuff goes into QA we need to find a way to link to it from the
   course pages

   - Though I imagine the handbook will have to be updated based on some of
   the changes (e.g., video about how to start a study group/course)

   - Breakdown:

   - QA - answer questions

   - Handbook - longer processes - eg. create a course

   - Inline documentation - chat - how to use chat

   - coursename - how to write a good coursename

   - Some things are bigger than inline "?" documentation

   - inline documentation - add a LH tag

   - do users actually use the ? links

   - One thing we should probably do updates of what we are planning to
   change, so that people know what is coming, and what needs to be documented,
   or what not to worry about.

   - When we need to decide to make changes that make a difference to
   permissions for organisers and/or participants it is probably necessary to
   mention this kind of thing to the community.

   - Alison will update screencasts after next release

   - add help icons to features that link to screencasts

   - Also I think we should plan to add more documentation on the home page.
   Sites like https://plus.google.com add videos and hints so people get


   - over 450 responses

   - we've maximised our 100 free limit

   - Proposal: survey monkey much easier than limequery

   - $300 silver account - a year

   - payment - in pipeline

   - it will be good if we experiment with getting results from the 100 free
   response we see and then extent that after we can see all of them.

   - personal responses to ali's personal survey outreach

   - we love you, of course

   - i'm angry my organiser is gone!

   - can we get a discount?

   - John will do this.

   - Hack: add survey questions into user experience:

   - to other parts of Lernanta

   - leaving a course / group

   - as student / as organiser

   - opening a course for participating? (how was development process?)

   - refinements to main survey

Some data  from the first 100 answers - subject to change when we see the
whole data set

   - 70% signed up to P2PU to learn something relevant to their work

   - A majority feel that certification is pretty important

   - most of those would have certification from a leading org in their
   field than an institution or a badge (this may have something to do with how
   the question was framed) and some SoW folks might have been thinking of
   Mozilla as the leading org anyway

   - Erin: I think this response is expected since badges don't mean a whole
   lot to folks yet but also promising in that a credential from a
   discipline/industry leader is important to people (more so than a credit
   from a university, for example)

   - 20% wouldn't know where to start with running a course, and a majority
   say that they don't have time.

   - Ali sounds very professional

   - Alison sounds like a total sociologist.


*Potential idea - Technical writing / documentation course *

   - This has grown out of discussions Pippa has had with various technical

   - Technical writers in trainig need to develop portfolios, and the best
   way to do this is to contribute to open source projects

   - If we can sort out some of the details/strategy, it would be useful for
   P2PU and for them to develop a course around how to be a technical writer -
   suppling P2PU with the documentation that we need.

   - Follow examples from other highly used websites:

   - The other way to go it that the course participants propose how to go
   about this.

   - Pippa to blog.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.p2pu.org/pipermail/p2pu-dev/attachments/20110728/c7707153/attachment-0001.html>

More information about the p2pu-dev mailing list