P2PULearningChallenges/Hackjam

From MozillaWiki
Jump to: navigation, search

Agenda for Dec. 14 to 16th Hackasaurus Hackjam in Toronto

December 14 (Wednesday)

9am to 10am Arrive, get coffee, talk about how awesome it is to embark on a challenges experiment
10am Welcome from Skips
10:15ish Quickfire Presentations:

  • Jess (via Skype) to give quick rundown of where the Hackasaurus Content is 
  • Chloe to show and tell about Challenges 101
  • Zuzel to show and tell implemented functional improvements
  • Skips to talk briefly about evaluation goals

11ish Collaborative Hackjam Dev Goal Setting: Some goals will already be here, in this pad, others will be discovered during/after the presentations
  • Dev Goals - To be coded in the next couple of days
    • Challenge creation process UX
    • postMessage from embedded iFrame
    • Badges on Tasks UX
    • Grouping Challenges UX
  • Community tasks
12ish Eat Food.
1pm Community Arrival
  • Introductions and skill assessment Who wants to help with what?
    • Dev people to sit with Atul and Zuzel and begin planning which stand alone segments that Zuzel can then work into the interface or tickets (if they have Lernanta set up)
    • Chloe to test Challenges 101 with interested community. Will teach them how to make challenges and get feedback to streamline 101, introduce P2PU
    • Group SoW home page hack – Redesign discussion. Taking a page apart and putting it back together.
      • highlight hackasaurus
      • connect to Mozilla
      • point to badges
      • reword copy

3pm Prioritize dev goals
Division of tasks among Community (skill dependent)

3:30pm Shut up and hack!
5pm Closing circle – roundup what we did today

December 15 (Thursday)


9am to 10am Arrive, get coffee, and talk about previous night's debauchery
10am Shut up and hack (Break into Groups)
Collaborative Hackjam Hackasaurus Content Goal Setting: Some goals will already be here, in this pad, others will be discovered during/after the presentations

Dev

10:30am Task division - Figure out what can be given to the community
11am Hacking on Hackasaurus Challenges!
12ish Eat more food.
1pm Community Arrival

  • Development
  • Content/Curriculum
  • Evaluation Discussion
  • Finalize Wording for Challenges
    • What are Challenges in One Sentence?
    • Finalize Challenge description for users
    • Review Summary of Challenges
    • Potentially Rename Challenges 101
  • Finalize and Create Survey (and / or hack on metrics)

4:30pm Closing circle – roundup

7:00 Dinner @ Arisu http://www.yelp.ca/biz/arisu-toronto

December 16(Friday)


9am to 10am Arrive, get coffee, lament that it's the last day (i wish i could lament too - looks like you guys are having too much a lot of fun! - PS)

10:00am Organic Hacking discussion – Where have we gotten too, what's the scope of what we can get done today, and what will we do tomorrow and onward

10:15 Discuss Challenges promotion and create a plan
  • blog post planning 
  • how to promote the Hackasaurus challenges to teens
  • how to promote challenges to teachers

10:45am Task Division
  • Development
    • Hackasaurus modules
    • p2pu platform continuation
    • Content/Curriculum?????

2:00pm Platform Review & NEXT STEPS– Where we were two days ago, where we are now, where we need to be before the end of December, where we expect to be before launch.?

3pm Moar Hack

5pm See you later alligator

CoolKidsHack Etherpad

Links to Project Documents

Anyone  who wants some sort of specific information about this project, it's  metrics, legwork that exists - should probably ask LAURA where to look

https://etherpad.mozilla.org/coolkidshack

Open Items Parking Lot

  • Skips http://alpha.p2pu.org:8093/en/groups/first-challenge/ I wish "Learn Anything, With Your Peers" (intended for non-registered users, dissapears after you login/register and should not reappear after logout) was less promenant (that whole section) and more like a side bar.
  • Worthwhile Discussions to have in for Phase 2
    • About the differences in creating curriculum for different age groups (Jess)
    • Extending  the model for badges and functionality (Zuzel)
    • Integrating OBI (Laura and Steph)
    • Integrating Browser ID for talking b/w sites (implement the solution Atul and Zuzel discussed with OAuth)
  • the  logo/look of p2pu - networking engineers and others thought the look  and feel of the logo was geared towards highschoolers...confusion of  target audience

Next Steps

Dev Goals

  • Challenge creation process UX
  • postMessage from embedded iFrame - temp solution, with a cord or Atul puts JS directly into Lernanta
  • Badges on Tasks UX
  • Grouping Challenges UX - next step set page (chloe has assigned to Arlton)

Discuss Challenges promotion and create a plan
  • blog post planning 
    • Laura is Parking Lot
    • Laura and Steph to do artifact post
    • Michelle comparing learning goals between hackasaurus.org and p2pu challenges
    • Jess and Chloe doing a co blog post
    • Dev People (Zuzel, Luis, ...) Take Before and After Screenshots
  • how to promote the Hackasaurus challenges
    • launching to selected group, public launch after testing (TBD). 
    • Letting Moyo kids become mentors to issues badges.
    • Michelle starting a launch list (people to soft launch on)

What we did on Thursday
  • Dev Group
  • Curriculum Group
    • Defined the learning goals and challenge metas. 
  • Metrics Group
NOTES
  • Group SoW home page hack – Redesign discussion. Taking a page apart and putting it back together.
    • highlight hackasaurus (will be featured Challenges)
    • connect to Mozilla [DISCUSS: iFrame w/ Join Mozilla form?]
    • point to badges (done)
    • reword copy
    • Header suggestion: Learn to be a webmaker at School of Webcraft!
      • Can we get rid of the peer powered text? shorten? 
      • Images
  • Finalize Wording for Challenges
    • What are Challenges in One Sentence?
      • A challenge is a problem that you're asked to solve that will teach you some skills along the way. 
    • Finalize Challenge description for users
      • A Challenge  is a fun way to learn with your peers at your own pace. A Challenge  begins with a problem that you are asked to solve. In order to do so you  have to move through different tasks, work with your peers and "make  things" all while documenting triumphs with badges that highlight both  your technical and community super powers. 
    • Review Summary of Challenges
    • Potentially Rename Challenges 101

Wednesday People:


  • Greg Wilson (@gwilson)
  • Laura Hilliger (@epilepticrabbit)
  • Michelle Levesque (mlevesque@)
  • Stephanie Schipper (@stephschipper)
  • Zuzel Vera (@zuzelvp)
  • Atul Varma (@toolness)
  • Ryan Merkley (@ryanmerkley)
  • Chloe Varelidi (@varelidi)
  • Matt Price (matt.price@utoronto.ca)
    • digital humanities
    • teaches computer skills in elementary schools and social housing
  • Luis Zarrabeitia (@zarrabeitia)
  • Heather Payne
  • Sara Wigglesworth (sw999999999@hotmail.com)

What we did on Wednesday


  • Dev Group
    • Finished clarification of dev tasks 
    • decided on what goes into implementation
    • Divided tasks between Atul, Zuzel, Luis
    • Challenge Creation UX needs more work, mockups will be a challenge, but Chloe and Laura began the discussion and working on the copy.
    • Friday Goals
      • 1)Challenge Creation Process > 
      • 2) iframe implementation, phase 1, is already in programming (basically a call back)
      • 3) Skill badges integrated with tasks. 
      • 4) UI set of challenges

  • Second Group > testing 
    • a group went through the challenges 101 curriculum (that is just text) 
      • Big   takeaways were that it needs to be trimmed down into two paths, fast   and furious (1 -3 steps or a video) and one more involved where you   actually have to take the challenge and do the work. 
        • 3 ways to make a challenge;
        • 1) fast and furious version, watch a video and do it
        • 2) take challenges to learn how to make then (deeper involvement)
        • 3) make challenges during a jam
        • 4) hack a challenge
    • Having Heather with an actual real life example was really helpful. 
    • Add step zero to understand wether this type methodology is right for you. 

NOTES:



METRICS (notes from Michelle): https://etherpad.mozilla.org/p2pu-challenges-metrics
  • Is "abandon a challenge" an active or a passive action? (ie: never completed it)
  • "Users" = web hits or logged-in users?
  • It'd be useful, I bet, to have conditional metrics and divide users into "casual", "hardcore", etc. (This was one of the suggestions from my email - I started a (mind)draft of this. Then dropped it, maybe it's not useful but: https://docs.google.com/spreadsheet/ccc?key=0Aq_AA_zwu59sdG94UERFcnVMTzhWNGpxNDJIeC1ieWc&hl=en_US#gid=0)
  • Per challenge: time it take (average) to complete that challenge <-- and is this more often a function of challenge difficulty, or curriculum difficulty?
  • Per challenge-creator: time it take (average) to complete their  challenge <-- ie: is this person creating challenges that are too  easy/difficult?  Do we need to educate them about challenges?
  • Thresholds: "if a user completes 3 challenges, we're 80% certain they'll complete more"
  • Additional survey: x amount of time later, do they still retain the knowledge they "learned"?
  • Badge  hits off-site leading to that IP address then visiting the site (eg:  when I post my badge on my blog, how many people see that badge and then  indepdently choose to visit p2pu)
  • users who hit the site but are involved in learning about other topics 

DEV ISSUES and NOTES
  • Challenge creation process UX
  • postMessage from embedded iFrame/opened tab - Atul working on this one
    • Use Case: Hackasaurus - users not having to go through too many pages. 
    • Ok  the correct solution has been worked out between Atul and Zuzel, but  that solution is too complicated for January. Hence - Atul is working on  the postMessage solution.
    • A pad about past iframes discussions in p2pu: http://pad.p2pu.org/iframes
    • The last decisions were to white list the urls we allow in embeds:
      • Rellying on embed.ly for some of the whitelisting
      • Rellying in our own list to include other cases we want to support
      • An creating a role in p2pu for people who can contribute to this list.
        • We expect that this last via will be the one that could work with things like hackasaurus
        • This also applies to the postMessage source cheks.
    • We're   teaching them how the web works, but then using a confusing concept   like iFrames so they won't be able to do things like "view source" as   they're learning about these very concepts.
    • This is a really important point.
    • Initial implementation is at https://github.com/toolness/lernanta/commit/219b09b4cf808ecf89e57106d1e1799198a3bc28   It uses window.open() w/ postMessage instead of an iframe to get around  problems w/ whitelisting and inability to use goggles, view source etc.  on iframes.
  • Whitelisting domains isn't sustainable.
  • [embed:url] is how we currently go around including iframes in rich content areas
    • In   general translating iframes to wiki like syntaxt (with their   corresponding custom button in ckeditor and preview functionality to  see  how the tag will look like)
  • Badges on Tasks UX
  • Grouping Challenges UX

Notes from Greg
Retrieved from "https://wiki.mozilla.org/index.php?title=P2PULearningChallenges/Hackjam&oldid=382061"