Badges: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 239: Line 239:
[[Category:Badges]]
[[Category:Badges]]
[[Category:Drumbeat]]
[[Category:Drumbeat]]
SUMMARY
We recognize that assessments and certification/credentialing are important pieces of P2PU moving forward, so that learning is captured and made portable across other contexts. Creating an alternative assessment and certification path is important and critical for today's world where formal education options are limited and expensive, and where we see learning occurring outside of formal paths all the time.  Our current focus for this is using badges as the currency to capture and demonstrate learning, skills and reputation within the community.
There are two parallel tracks in motion: the badges/assessments for these courses and the open badge infrastructure.
TEAM
Erin Knight (Badge and Assessment Lead, P2PU and Mozilla Foundation)
Brian Brennan (Lead Developer, Open Badge Infrastructure)
Alan Webb (Badge Lead, SoSI)
Pippa Buchanan (Community Manager, SoW, advisory role)
Philipp Schmidt (Executive Director, P2PU, advisory role on assessments/badges)
Ahrash Bissell (did initial background work, now in an advisory role)
BADGES/ASSESSMENTS
BACKGROUND
Ahrash did some considerable work on the assessment background and frameworks.  His work is summarized here:
Starting point: http://wiki.mozilla.org/Drumbeat/p2pu/Assessment_and_Accreditation
Deep Dive on concrete examples: http://wiki.mozilla.org/Drumbeat/p2pu/Assessment_and_Accreditation/Webcraft_Assessments_-_detailed
BADGES - CONCEPTUAL FRAMEWORK
We have done considerable work and thinking around badges for learning contexts.  We are working on a foundational badge paper.  The latest version can be found here:  http://bit.ly/badgepaper3
JANUARY BADGES PILOT
We are running a pilot of assessments and badges in the January sessions of School of Webcraft and School of Social Innovation. Below are links to the various resources that we are building out as we go.
Summary (written for SoW course organizers):
http://wiki.p2pu.org/Webcraft-Assessment
SoW Badge/Assessment plan:
http://etherpad.mozilla.org:9000/webcraftassessment
SoSI Badge/Assessment plan:
http://etherpad.mozilla.org:9000/sosiassessments
TECHNICAL SUPPORT (aka - how to manage assessments and badge issuing)
We are going to use the OSQA environment to host the assessment challenges, manage the peer assessments and issue badges for all skill badges.
http://badges.p2pu.org/
PROJECT MANAGEMENT
Calls
We have a weekly SoW call where we discuss a number of SoW related issues, including updates on badges: http://pad.p2pu.org/community
BADGE INFRASTRUCTURE
DESCRIPTION
In order to enable people to earn badges from wherever they are learning across the web, there needs to be a way to allow for individual badge issuers.  Any learner could collect badges from multiple sites, tied to a single identity and then share them out with various sites like a personal blog or LinkedIn. This infrastructure should be open to allow anyone to issue badges, and each learner to carry the badges with them across the Web or other contexts.
BACKGROUND
Josh's work on badges infrastructure, which plays into assessments http://joshuagay.org/blog/
PROTOTYPE
A prototype of the infrastructure was built at Drumbeat Festival in Barcelona.  The prototype was updated and advanced in early January 2011. A more complete and working prototype will be used for the January badge pilot.
BADGE INFRASTRUCTURE
We are aiming to have a working badge infrastructure in late 2011 that will provide:
API/Metadata spec for independent badge issuers to use to issue badges, as well as for display sites to pull badges out
Data Wallet/Backpack - central collection of badges and associated metadata, tied to open identity

Revision as of 17:33, 8 March 2011

Hackasaur.jpg Badges
Owner: Mozilla Updated: 2011-03-8
Badges are awesome.

Project Tools

Get involved now

  1. Meet up with us at the Digital Media & Learning conference in Long Beach (Mar 3 - 5).
  2. Attend an upcoming hack jam. Or organize a hack jam in your community. We're looking to spread to new cities beyond New York and Chicago. Get in touch through our mailing list.
  3. Start hacking with Hackasaurus tools like HTML Pad or X-Ray Goggles.
  4. Share your own ideas, tools and resources. Through our mailing list or on twitter.
  5. Become a Hackasaurs partner. We're looking for learning centers, libraries, media centers and other partners to help design, develop and host Hackasaurus. Get in touch through our mailing list.
  6. Help develop the Hackasaurus tool set. Through our issue tracker and Github.

About this project

  • The project in 5 sentences:
    • Hackasaurus helps teens hack. Through tools that makes it easy for youth to explore, remix and redesign the web.
    • Plus local events or "hack jams" that make hacking and digital literacy easy, social and fun.
    • We're designing around the way kids learn technology, based on Mizuko Ito's concepts of hanging out, messing around and geeking out.
    • Tools in development so far include HTML Pad and X-Ray Goggles, with more on the way.
    • You can get involved by test-driving Hackasarus tools right now. Or attend an upcoming hack jam, organize your own event, help develop the Hackasaurus tool kit, or share your own ideas and tools.

Hackasaurus Hack Jams

  • Hack jams are one-day and weekend events that allow kids to test and help design Hackasaurus.
  • They're run through the New Youth City Learning Network in collaboration with Mozilla.
  • Hackasaurus jams are designed to be modular and self-organizing. So that any teen, parent or organization can organize their own.
  • Event curriculum and an organizing kit are under development.

Previous Hack Jams:

Upcoming Hack Jams:

  • 3/17 @ 4pm, YouMedia, Chicago
  • 3/23 @ 4pm, New York Public Libary, Grand Concourse (Bronx)
  • 3/24 @ 4pm, New York Public Library, 67th St (Manhattan)
  • 3/25 @ 3:30pm, New York Public Library, Battery Park City (Manhattan)


Experimental Hackasaurus Tools

These tools are still evolving and have rough edges, but their basic functionality is available now. They're also actively being used at jams.

X-Ray Goggles

Web X-Ray Goggles allow anyone to easily “see through the surface” of any Web page, and obtain an intuitive understanding of how pages are composed. They can be used anywhere on the Web one hangs out, and casual use of the tool enables one to gain a rudimentary grasp of HTML, CSS, and the Document Object Model.

You can try the prototype now at secure.toolness.com/webxray/.

HTMLPad

htmlpad.org is a simple website that allows anyone to easily create a Web page, collaborate on it in real-time with friends, and share it with the rest of the world.

More background for HTMLPad can be found in Atul's blog post entitled Prelude To Barcelona.

Ideas For Future Hackasaurus Tools

These tools don't actually exist yet. They also may never exist as independent products—for example, their functionality might be rolled into an existing tool instead.

Mixmaster

While goggles allow one to take apart a page and inspect its individual parts, the Mixmaster allows one to actually change parts to remix the page. For instance, the tool can be used to change the font that’s used on a page, or to hyperlink a word on a page to its entry on Wikipedia. Each alteration is called a hack and hacks can be easily shared with friends for any purpose—to make a page, a site, or even the entire Web more usable, more hilarious, or more meaningful. Experimenting with this tool engages people in writing short snippets of HTML, which provides scaffolding for future adventures in Web development.

Development on this tool has not yet started, though similar functionality has been added to the goggles as an experimental feature. Here's some wireframes to explain our thinking:

Wireframe: Boring Form

Boring Form
About this image

Magnetic Poetry

Magnetic Poetry
About this image
  • This mock-up explores how remixing code is like magnetic poetry.
  • Thinking of code this way allows users to define their own rules, rather than defining lines of sequential procedural code.
  • Some users might approach a sentence grammatically, others visually, and some might just cluster components together that they will eventually make sense of.
  • There's also an element of social collaborative mentoring, where users can help each other in developing code.

Next Steps:

  • Develop a functional prototype.
  • Consider integrating a gaming aspect.
  • Consider ways to include a mentoring/hint/bumper-bowling system that isn't as annoying as the MS Paper Clip.
  • Think about systems for users to define their own rules.
  • Think about social collaborative mentoring.
  • Think about social collaborative badging, karma for being helpful, etc.

Advanced Tools (coming soon)

  • The highest level of engagement are the “geeking out” tools.
  • These are for users with a serious interest in web design and development.
  • Ideas in development:


1) Creative Wireframing Tools

  • wireframing tools to allow teens to create new interfaces and interactions from scratch.
  • May involve pre-existing tools like OmniGraffle or developing our own from scratch.


2) "Build out" game

  • Players would use physical cards to trade with other kids, etc.
  • Maybe you need badges/achievements to trade or make certain kinds of content or code.


3) Super funked-out HTML editor

  • a super funked-out HTML editor would allow users to create a brand new page/website from scratch.
  • May build on some of Atul's HTMLPad work


Similar Tools

These could be used as inspiration for Hackasaurus tools. Or become part of the Hackasaurus toolkit itself:

Tutorials and reference materials:

Team




Welcome to the Badge Lab

Discuss and Brainstorm Badges

Help with Specs or Software

  • Github Repo for the Drumbeat Festival tech sprint code
  • Badge Specification -- Join the badge format specification draft process.
  • Badge Requirements -- let's convert our informal case studies into formal technical requirements for badges and the badge architecture.
  • Security Concern -- Open distributed architecture carries with it special security concerns.

Notices and notes

Questions? Feel free to email Joshua Gay or the public badge-lab mailing list with any questions you may have.


SUMMARY We recognize that assessments and certification/credentialing are important pieces of P2PU moving forward, so that learning is captured and made portable across other contexts. Creating an alternative assessment and certification path is important and critical for today's world where formal education options are limited and expensive, and where we see learning occurring outside of formal paths all the time. Our current focus for this is using badges as the currency to capture and demonstrate learning, skills and reputation within the community.

There are two parallel tracks in motion: the badges/assessments for these courses and the open badge infrastructure.

TEAM Erin Knight (Badge and Assessment Lead, P2PU and Mozilla Foundation) Brian Brennan (Lead Developer, Open Badge Infrastructure) Alan Webb (Badge Lead, SoSI) Pippa Buchanan (Community Manager, SoW, advisory role) Philipp Schmidt (Executive Director, P2PU, advisory role on assessments/badges) Ahrash Bissell (did initial background work, now in an advisory role)

BADGES/ASSESSMENTS

BACKGROUND Ahrash did some considerable work on the assessment background and frameworks. His work is summarized here: Starting point: http://wiki.mozilla.org/Drumbeat/p2pu/Assessment_and_Accreditation Deep Dive on concrete examples: http://wiki.mozilla.org/Drumbeat/p2pu/Assessment_and_Accreditation/Webcraft_Assessments_-_detailed

BADGES - CONCEPTUAL FRAMEWORK We have done considerable work and thinking around badges for learning contexts. We are working on a foundational badge paper. The latest version can be found here: http://bit.ly/badgepaper3

JANUARY BADGES PILOT We are running a pilot of assessments and badges in the January sessions of School of Webcraft and School of Social Innovation. Below are links to the various resources that we are building out as we go.

Summary (written for SoW course organizers): http://wiki.p2pu.org/Webcraft-Assessment

SoW Badge/Assessment plan: http://etherpad.mozilla.org:9000/webcraftassessment

SoSI Badge/Assessment plan: http://etherpad.mozilla.org:9000/sosiassessments

TECHNICAL SUPPORT (aka - how to manage assessments and badge issuing) We are going to use the OSQA environment to host the assessment challenges, manage the peer assessments and issue badges for all skill badges. http://badges.p2pu.org/

PROJECT MANAGEMENT Calls We have a weekly SoW call where we discuss a number of SoW related issues, including updates on badges: http://pad.p2pu.org/community

BADGE INFRASTRUCTURE

DESCRIPTION In order to enable people to earn badges from wherever they are learning across the web, there needs to be a way to allow for individual badge issuers. Any learner could collect badges from multiple sites, tied to a single identity and then share them out with various sites like a personal blog or LinkedIn. This infrastructure should be open to allow anyone to issue badges, and each learner to carry the badges with them across the Web or other contexts.

BACKGROUND Josh's work on badges infrastructure, which plays into assessments http://joshuagay.org/blog/

PROTOTYPE A prototype of the infrastructure was built at Drumbeat Festival in Barcelona. The prototype was updated and advanced in early January 2011. A more complete and working prototype will be used for the January badge pilot.


BADGE INFRASTRUCTURE We are aiming to have a working badge infrastructure in late 2011 that will provide: API/Metadata spec for independent badge issuers to use to issue badges, as well as for display sites to pull badges out Data Wallet/Backpack - central collection of badges and associated metadata, tied to open identity

Retrieved from "https://wiki.mozilla.org/index.php?title=Badges&oldid=289604"