MozillaWiki - User contributions [en]

Foundation/2014Plans/OpenBadges

2014-01-08T03:49:47Z

Threeqube: /* Milestone Roadmap Q1 Q2 2014 */

<section begin=summary />{{RoadmapSummary
|icon=Mozilla webmaker logo-icon.png
|pagelocation=Foundation/2014Plans/OpenBadges
|pagetitle=Open Badges 2014 Plans
|owner=Mozilla Foundation
|updated=Jan 9, 2014
|description=Draft plans for the Open Badges project at the Mozilla Foundation
}}<section end=summary />

{{DoNotEdit}}

Open Badges is....

This collection of wiki pages outlines the high level 2014 - 2016 goals for Mozilla Foundation overall and for each of these programs. ''This is a draft version of the site'' -- it will evolve into a MoFO planning hub including goals, roadmaps and status updates starting in January 2014.

=== Open Badges Goals & Strategy ===
 
Open Badges re-imagines credentials to support a transformed culture of learning where skills,
interests and achievements are recognized and connected with digital badges to share across the
web, granting access to jobs, advancement and education.
 

Goals

2.1 Shape: A distributed credentialing system connects greater numbers of people to open technology
and makes learning, employment and identity on the web more interoperable. 
2.2 Teach: The Open Badge ecosystem has an abundance of quality opportunities to foster and
recognize learning and teaching experiences that align with Mozilla's values. 
2.3 Build: BadgeKit forms the core technical infrastructure of a vibrant and interoperable open
ecosystem of learning. 
2.4 Empower: A thriving community of issuers, endorsers and validators recognizes and reinforces
a culture of learning based on shared digital badges. 

=== Open Badges Story ===

1. What is Open Badges and why does it matter? 
Open Badges is a project that re-imagines credentials to support a transformed culture of learning - one
where all types of learning, skills, interests and achievements are recognized and connected using digital
badges that can be shared across the web to unlock access to relevant job opportunities and advancement.

2. How will it shape the world by 2016? 
Open Badges is dedicated to recognizing and connecting learning across all contexts, in and out of school,
allowing learners to gain insight into the skills they need in order to accomplish their goals, capture and
communicate those skills once they've been obtained, and unlock access to relevant jobs and opportunities
for advancement.

The Open Badges community has an audacious goal of a transformed culture of learning, employment and
identity across the web. Throughout 2014-2016, Open Badges will support thousands of issuers, endorsers
and validators in recognizing learning of all kinds through an open ecosystem of digital badges.
Subsequently, millions of learners will be able to build a collection of badges that truly represents their
lifelong learning and skills, and connects them to jobs, credit and other advancement opportunities. By the
end of 2016, we will see that new culture in action, with open badges issued by over 5,000 organizations,
impacting over 5 million learners and workers. Badges will be a key way that individuals represent
themselves online, and will be used in many hiring and admission decisions.

3. Why will people get involved in what we're doing? 
Mozilla Open Badges includes both an open standard for badges, as well as free software to make the
badging experience easy and personal. The shared standard enables openness and interoperability within
historically siloed credentialing systems. As a result, badges can operate as the key connector to ignite and
support a culture of learning that works like the web. Beyond the tools, Open Badges thrives on an active
and growing community who informs and drives this work forward with us.

4. Why will lead users or partners will get involved? 
The lead partners for Open Badges, including badge issuers, endorsers and validators, provide valuable
ways for learners to build upon and demonstrate what they know and can do. Issuers — often teaching
and learning organizations — benefit by plugging into a broader ecosystem of learning. Their learning
opportunities, recognition systems and brands will gain exposure beyond their networks, bringing more
learners, prestige and endorsement. Endorsers and validators have access to a connected ecosystem
where they support and promote specific skills, and exceptional learning opportunities for each skill.
Finally, badges are data, and privacy-friendly analytics around impact and outcomes are an attractive driver
for these contributors.

Employers will benefit from making hiring decisions based on verified skills instead of, or in addition to,
self-reported resumes. Learners will have the ability to stitch together their learning across multiple
experiences, access opportunities needed to reach their goals and easily communicate their skills to
employers.

5. What we're doing in 2014 to move towards this: 
Mozilla's role is to shepherd, protect and promote the open standard for badges, to ensure that badges are
interoperable and have currency in the ecosystem, as well as to build the scaffolding needed for a healthy,
open badging ecosystem to exist and thrive. This includes open tools to support critical elements of the
badging experience, and the common interfaces and channels to ensure that a connected ecosystem of
tools, support and services can exist. In 2014, the Open Badges team will build and release BadgeKit, an
open tool stack to support the entire badging experience, including defining and issuing badges. We will
also launch the Badge the World campaign to invite and support a wide diversity of organizations and
global communities into badging. Finally, we hope to engage more deeply with key global organizations like the United Nations, as well as the U.S. Department of Education, Office of Vocational and Adult Education, the Scottish Qualifications Authority, DigitalME, Statewide Afterschool Networks, and numerous K-12 schools, universities and community colleges to develop important badge systems.

6. Possible revenue opportunities: 
In addition to a large and growing community of contributors, the Open Badges work requires a solid set
of paid contributors as a means to further support the initiative. Revenue opportunities may include
offering badge system design services to new issuers, offering services on top of BadgeKit like metadata
caching, featured badges and employer tools, and additional philanthropic grants.

7. Why will Open Badges succeed? 
We will succeed with Open Badges because they are the credentials needed to meet a rapidly changing
world. Credentials have historically been siloed and owned by institutions. The Open Badges project,
through sound technology and an open web ethos, is well positioned to shift the learning and credentialing
paradigm towards an open ecosystem. In addition, we have the highest level of institutional knowledge and
experience with badging in the marketplace, which we can leverage to help organizations build exemplar
badge systems and educate the growing community on why open (learning, credentials, etc.) is critical to
our future and to posterity.

== Open Badges Roadmap ==
* n.b. This roadmap is a work in progress. Most updated version can be found on our github wiki: https://github.com/mozilla/openbadges-badgekit/wiki/Milestone-Roadmap-Q1-Q2-2014

=== Open Badges 2014 Product Priorities ===
Major product development priority for 2014 is BadgeKit. With BadgeKit, our goal is to:

* Improve the badging experience, making badging simple and easy to do
* Close the badging experience gaps by providing lightweight, free open badging tools
* Stoke the growth and development of the open badges ecosystem
* Build on our values of openness, interoperability, agency, choice and connectedness into the core and help shape emerging badge systems.

=== Milestone Roadmap Q1 Q2 2014 ===

==== Ducks in a Row: December 18 ====

Goal: complete prep work required prior to implementation
* product definition finalized
* architecture done
* all ux for MVP wireframed
* plan for UI
* plan for implementation

==== Preparing for Flight: January 22 ====

Goal: Pull together an instance suitable for user testing
* working app
** mockups / stubbed functionality for anything that isn't ready
* user testing sessions identified
* user tests planned
* federated city backpack requirements defined and wireframed

==== Take Off: February 5 ====

Goal: soft launch BadgeKit
* user interface applied to the site
* iterations based on user testing feedback incorporated
* functionality tweaked
* ready for 2nd round of user testing
* documentation docs drafted

==== Flying: February 19 ====

Goal: Put in the hands of real users (outside of the research cohort)
* Branding finalized
* Functionality and usability tweaks identified in testing, reconciled
* Documentation available on site
* Glossary and tool tips implemented
* Third round of user testing
* Marketing site content refreshed and designed
* Plan demo of badges.openbadges.org integration of BadgeKit

==== Soaring: March 6 ====

Goal: A (beta) release
* Documentation user tested and tweaked to include human - friendly language
* Glossary user tested and tweaked - all jargon is identified and explained
* A user can design and issue a badge on their site
* A developer can download the APIs codes
* Language on marketing site is tweaked to reflect a release
* Marketing site (badgekit.openbadges.org) implemented
* Demo of badges.openbadges.org integration of BadgeKit launched

==== Jetpack: March 27 ====

Goal: Federated city backpack release
* Deployed on CCOL
* federated
* seamless/fully integrated ux from BadgeKit to backpack

==== Orbit: May 14 ====

Goal: Federated Mozilla backpack release
* seamless/fully integrated ux from BadgeKit to Mozilla Backpack
* federated
* UX refined
* UI to match the Open Badges look and feel applied

Foundation/2014Plans/OpenBadges

2014-01-08T03:46:53Z

Threeqube: /* Open Badges Roadmap = */

<section begin=summary />{{RoadmapSummary
|icon=Mozilla webmaker logo-icon.png
|pagelocation=Foundation/2014Plans/OpenBadges
|pagetitle=Open Badges 2014 Plans
|owner=Mozilla Foundation
|updated=Jan 9, 2014
|description=Draft plans for the Open Badges project at the Mozilla Foundation
}}<section end=summary />

{{DoNotEdit}}

Open Badges is....

This collection of wiki pages outlines the high level 2014 - 2016 goals for Mozilla Foundation overall and for each of these programs. ''This is a draft version of the site'' -- it will evolve into a MoFO planning hub including goals, roadmaps and status updates starting in January 2014.

=== Open Badges Goals & Strategy ===
 
Open Badges re-imagines credentials to support a transformed culture of learning where skills,
interests and achievements are recognized and connected with digital badges to share across the
web, granting access to jobs, advancement and education.
 

Goals

2.1 Shape: A distributed credentialing system connects greater numbers of people to open technology
and makes learning, employment and identity on the web more interoperable. 
2.2 Teach: The Open Badge ecosystem has an abundance of quality opportunities to foster and
recognize learning and teaching experiences that align with Mozilla's values. 
2.3 Build: BadgeKit forms the core technical infrastructure of a vibrant and interoperable open
ecosystem of learning. 
2.4 Empower: A thriving community of issuers, endorsers and validators recognizes and reinforces
a culture of learning based on shared digital badges. 

=== Open Badges Story ===

1. What is Open Badges and why does it matter? 
Open Badges is a project that re-imagines credentials to support a transformed culture of learning - one
where all types of learning, skills, interests and achievements are recognized and connected using digital
badges that can be shared across the web to unlock access to relevant job opportunities and advancement.

2. How will it shape the world by 2016? 
Open Badges is dedicated to recognizing and connecting learning across all contexts, in and out of school,
allowing learners to gain insight into the skills they need in order to accomplish their goals, capture and
communicate those skills once they've been obtained, and unlock access to relevant jobs and opportunities
for advancement.

The Open Badges community has an audacious goal of a transformed culture of learning, employment and
identity across the web. Throughout 2014-2016, Open Badges will support thousands of issuers, endorsers
and validators in recognizing learning of all kinds through an open ecosystem of digital badges.
Subsequently, millions of learners will be able to build a collection of badges that truly represents their
lifelong learning and skills, and connects them to jobs, credit and other advancement opportunities. By the
end of 2016, we will see that new culture in action, with open badges issued by over 5,000 organizations,
impacting over 5 million learners and workers. Badges will be a key way that individuals represent
themselves online, and will be used in many hiring and admission decisions.

3. Why will people get involved in what we're doing? 
Mozilla Open Badges includes both an open standard for badges, as well as free software to make the
badging experience easy and personal. The shared standard enables openness and interoperability within
historically siloed credentialing systems. As a result, badges can operate as the key connector to ignite and
support a culture of learning that works like the web. Beyond the tools, Open Badges thrives on an active
and growing community who informs and drives this work forward with us.

4. Why will lead users or partners will get involved? 
The lead partners for Open Badges, including badge issuers, endorsers and validators, provide valuable
ways for learners to build upon and demonstrate what they know and can do. Issuers — often teaching
and learning organizations — benefit by plugging into a broader ecosystem of learning. Their learning
opportunities, recognition systems and brands will gain exposure beyond their networks, bringing more
learners, prestige and endorsement. Endorsers and validators have access to a connected ecosystem
where they support and promote specific skills, and exceptional learning opportunities for each skill.
Finally, badges are data, and privacy-friendly analytics around impact and outcomes are an attractive driver
for these contributors.

Employers will benefit from making hiring decisions based on verified skills instead of, or in addition to,
self-reported resumes. Learners will have the ability to stitch together their learning across multiple
experiences, access opportunities needed to reach their goals and easily communicate their skills to
employers.

5. What we're doing in 2014 to move towards this: 
Mozilla's role is to shepherd, protect and promote the open standard for badges, to ensure that badges are
interoperable and have currency in the ecosystem, as well as to build the scaffolding needed for a healthy,
open badging ecosystem to exist and thrive. This includes open tools to support critical elements of the
badging experience, and the common interfaces and channels to ensure that a connected ecosystem of
tools, support and services can exist. In 2014, the Open Badges team will build and release BadgeKit, an
open tool stack to support the entire badging experience, including defining and issuing badges. We will
also launch the Badge the World campaign to invite and support a wide diversity of organizations and
global communities into badging. Finally, we hope to engage more deeply with key global organizations like the United Nations, as well as the U.S. Department of Education, Office of Vocational and Adult Education, the Scottish Qualifications Authority, DigitalME, Statewide Afterschool Networks, and numerous K-12 schools, universities and community colleges to develop important badge systems.

6. Possible revenue opportunities: 
In addition to a large and growing community of contributors, the Open Badges work requires a solid set
of paid contributors as a means to further support the initiative. Revenue opportunities may include
offering badge system design services to new issuers, offering services on top of BadgeKit like metadata
caching, featured badges and employer tools, and additional philanthropic grants.

7. Why will Open Badges succeed? 
We will succeed with Open Badges because they are the credentials needed to meet a rapidly changing
world. Credentials have historically been siloed and owned by institutions. The Open Badges project,
through sound technology and an open web ethos, is well positioned to shift the learning and credentialing
paradigm towards an open ecosystem. In addition, we have the highest level of institutional knowledge and
experience with badging in the marketplace, which we can leverage to help organizations build exemplar
badge systems and educate the growing community on why open (learning, credentials, etc.) is critical to
our future and to posterity.

== Open Badges Roadmap ==
* n.b. This roadmap is a work in progress. Most updated version can be found on our github wiki: https://github.com/mozilla/openbadges-badgekit/wiki/Milestone-Roadmap-Q1-Q2-2014

=== Open Badges 2014 Product Priorities ===
Major product development priority for 2014 is BadgeKit. With BadgeKit, our goal is to:

* Improve the badging experience, making badging simple and easy to do
* Close the badging experience gaps by providing lightweight, free open badging tools
* Stoke the growth and development of the open badges ecosystem
* Build on our values of openness, interoperability, agency, choice and connectedness into the core and help shape emerging badge systems.

=== Milestone Roadmap Q1 Q2 2014 ===

==== Ducks in a Row: December 18 ====

Goal: complete prep work required prior to implementation
product definition finalized
architecture done
all ux for MVP wireframed
plan for UI
plan for implementation

==== Preparing for Flight: January 22 ====

Goal: Pull together an instance suitable for user testing
working app
mockups / stubbed functionality for anything that isn't ready
user testing sessions identified
user tests planned
federated city backpack requirements defined and wireframed

==== Take Off: February 5 ====

Goal: soft launch BadgeKit
user interface applied to the site
iterations based on user testing feedback incorporated
functionality tweaked
ready for 2nd round of user testing
documentation docs drafted

==== Flying: February 19 ====

Goal: Put in the hands of real users (outside of the research cohort)
Branding finalized
Functionality and usability tweaks identified in testing, reconciled
Documentation available on site
Glossary and tool tips implemented
Third round of user testing
Marketing site content refreshed and designed
Plan demo of badges.openbadges.org integration of BadgeKit

==== Soaring: March 6 ====

Goal: A (beta) release
Documentation user tested and tweaked to include human - friendly language
Glossary user tested and tweaked - all jargon is identified and explained
A user can design and issue a badge on their site
A developer can download the APIs codes
Language on marketing site is tweaked to reflect a release
Marketing site (badgekit.openbadges.org) implemented
Demo of badges.openbadges.org integration of BadgeKit launched

==== Jetpack: March 27 ====

Goal: Federated city backpack release
Deployed on CCOL
federated
seamless/fully integrated ux from BadgeKit to backpack

==== Orbit: May 14 ====

Goal: Federated Mozilla backpack release
seamless/fully integrated ux from BadgeKit to Mozilla Backpack
federated
UX refined
UI to match the Open Badges look and feel applied

Foundation/2014Plans/OpenBadges

2014-01-08T03:46:36Z

Threeqube: /* Open Badges Roadmap = */

<section begin=summary />{{RoadmapSummary
|icon=Mozilla webmaker logo-icon.png
|pagelocation=Foundation/2014Plans/OpenBadges
|pagetitle=Open Badges 2014 Plans
|owner=Mozilla Foundation
|updated=Jan 9, 2014
|description=Draft plans for the Open Badges project at the Mozilla Foundation
}}<section end=summary />

{{DoNotEdit}}

Open Badges is....

This collection of wiki pages outlines the high level 2014 - 2016 goals for Mozilla Foundation overall and for each of these programs. ''This is a draft version of the site'' -- it will evolve into a MoFO planning hub including goals, roadmaps and status updates starting in January 2014.

=== Open Badges Goals & Strategy ===
 
Open Badges re-imagines credentials to support a transformed culture of learning where skills,
interests and achievements are recognized and connected with digital badges to share across the
web, granting access to jobs, advancement and education.
 

Goals

2.1 Shape: A distributed credentialing system connects greater numbers of people to open technology
and makes learning, employment and identity on the web more interoperable. 
2.2 Teach: The Open Badge ecosystem has an abundance of quality opportunities to foster and
recognize learning and teaching experiences that align with Mozilla's values. 
2.3 Build: BadgeKit forms the core technical infrastructure of a vibrant and interoperable open
ecosystem of learning. 
2.4 Empower: A thriving community of issuers, endorsers and validators recognizes and reinforces
a culture of learning based on shared digital badges. 

=== Open Badges Story ===

1. What is Open Badges and why does it matter? 
Open Badges is a project that re-imagines credentials to support a transformed culture of learning - one
where all types of learning, skills, interests and achievements are recognized and connected using digital
badges that can be shared across the web to unlock access to relevant job opportunities and advancement.

2. How will it shape the world by 2016? 
Open Badges is dedicated to recognizing and connecting learning across all contexts, in and out of school,
allowing learners to gain insight into the skills they need in order to accomplish their goals, capture and
communicate those skills once they've been obtained, and unlock access to relevant jobs and opportunities
for advancement.

The Open Badges community has an audacious goal of a transformed culture of learning, employment and
identity across the web. Throughout 2014-2016, Open Badges will support thousands of issuers, endorsers
and validators in recognizing learning of all kinds through an open ecosystem of digital badges.
Subsequently, millions of learners will be able to build a collection of badges that truly represents their
lifelong learning and skills, and connects them to jobs, credit and other advancement opportunities. By the
end of 2016, we will see that new culture in action, with open badges issued by over 5,000 organizations,
impacting over 5 million learners and workers. Badges will be a key way that individuals represent
themselves online, and will be used in many hiring and admission decisions.

3. Why will people get involved in what we're doing? 
Mozilla Open Badges includes both an open standard for badges, as well as free software to make the
badging experience easy and personal. The shared standard enables openness and interoperability within
historically siloed credentialing systems. As a result, badges can operate as the key connector to ignite and
support a culture of learning that works like the web. Beyond the tools, Open Badges thrives on an active
and growing community who informs and drives this work forward with us.

4. Why will lead users or partners will get involved? 
The lead partners for Open Badges, including badge issuers, endorsers and validators, provide valuable
ways for learners to build upon and demonstrate what they know and can do. Issuers — often teaching
and learning organizations — benefit by plugging into a broader ecosystem of learning. Their learning
opportunities, recognition systems and brands will gain exposure beyond their networks, bringing more
learners, prestige and endorsement. Endorsers and validators have access to a connected ecosystem
where they support and promote specific skills, and exceptional learning opportunities for each skill.
Finally, badges are data, and privacy-friendly analytics around impact and outcomes are an attractive driver
for these contributors.

Employers will benefit from making hiring decisions based on verified skills instead of, or in addition to,
self-reported resumes. Learners will have the ability to stitch together their learning across multiple
experiences, access opportunities needed to reach their goals and easily communicate their skills to
employers.

5. What we're doing in 2014 to move towards this: 
Mozilla's role is to shepherd, protect and promote the open standard for badges, to ensure that badges are
interoperable and have currency in the ecosystem, as well as to build the scaffolding needed for a healthy,
open badging ecosystem to exist and thrive. This includes open tools to support critical elements of the
badging experience, and the common interfaces and channels to ensure that a connected ecosystem of
tools, support and services can exist. In 2014, the Open Badges team will build and release BadgeKit, an
open tool stack to support the entire badging experience, including defining and issuing badges. We will
also launch the Badge the World campaign to invite and support a wide diversity of organizations and
global communities into badging. Finally, we hope to engage more deeply with key global organizations like the United Nations, as well as the U.S. Department of Education, Office of Vocational and Adult Education, the Scottish Qualifications Authority, DigitalME, Statewide Afterschool Networks, and numerous K-12 schools, universities and community colleges to develop important badge systems.

6. Possible revenue opportunities: 
In addition to a large and growing community of contributors, the Open Badges work requires a solid set
of paid contributors as a means to further support the initiative. Revenue opportunities may include
offering badge system design services to new issuers, offering services on top of BadgeKit like metadata
caching, featured badges and employer tools, and additional philanthropic grants.

7. Why will Open Badges succeed? 
We will succeed with Open Badges because they are the credentials needed to meet a rapidly changing
world. Credentials have historically been siloed and owned by institutions. The Open Badges project,
through sound technology and an open web ethos, is well positioned to shift the learning and credentialing
paradigm towards an open ecosystem. In addition, we have the highest level of institutional knowledge and
experience with badging in the marketplace, which we can leverage to help organizations build exemplar
badge systems and educate the growing community on why open (learning, credentials, etc.) is critical to
our future and to posterity.

== Open Badges Roadmap ===
* n.b. This roadmap is a work in progress. Most updated version can be found on our github wiki: https://github.com/mozilla/openbadges-badgekit/wiki/Milestone-Roadmap-Q1-Q2-2014

=== Open Badges 2014 Product Priorities ===
Major product development priority for 2014 is BadgeKit. With BadgeKit, our goal is to:

* Improve the badging experience, making badging simple and easy to do
* Close the badging experience gaps by providing lightweight, free open badging tools
* Stoke the growth and development of the open badges ecosystem
* Build on our values of openness, interoperability, agency, choice and connectedness into the core and help shape emerging badge systems.

=== Milestone Roadmap Q1 Q2 2014 ===

==== Ducks in a Row: December 18 ====

Goal: complete prep work required prior to implementation
product definition finalized
architecture done
all ux for MVP wireframed
plan for UI
plan for implementation

==== Preparing for Flight: January 22 ====

Goal: Pull together an instance suitable for user testing
working app
mockups / stubbed functionality for anything that isn't ready
user testing sessions identified
user tests planned
federated city backpack requirements defined and wireframed

==== Take Off: February 5 ====

Goal: soft launch BadgeKit
user interface applied to the site
iterations based on user testing feedback incorporated
functionality tweaked
ready for 2nd round of user testing
documentation docs drafted

==== Flying: February 19 ====

Goal: Put in the hands of real users (outside of the research cohort)
Branding finalized
Functionality and usability tweaks identified in testing, reconciled
Documentation available on site
Glossary and tool tips implemented
Third round of user testing
Marketing site content refreshed and designed
Plan demo of badges.openbadges.org integration of BadgeKit

==== Soaring: March 6 ====

Goal: A (beta) release
Documentation user tested and tweaked to include human - friendly language
Glossary user tested and tweaked - all jargon is identified and explained
A user can design and issue a badge on their site
A developer can download the APIs codes
Language on marketing site is tweaked to reflect a release
Marketing site (badgekit.openbadges.org) implemented
Demo of badges.openbadges.org integration of BadgeKit launched

==== Jetpack: March 27 ====

Goal: Federated city backpack release
Deployed on CCOL
federated
seamless/fully integrated ux from BadgeKit to backpack

==== Orbit: May 14 ====

Goal: Federated Mozilla backpack release
seamless/fully integrated ux from BadgeKit to Mozilla Backpack
federated
UX refined
UI to match the Open Badges look and feel applied

Badges/roadmap

2013-12-17T23:02:46Z

Threeqube:

==2014 Roadmap==

BadgeKit roadmap: https://github.com/mozilla/openbadges-badgekit/wiki/Milestone-Roadmap-Q1-2014

== 2013 Roadmap ==

=== 2013 Highlights ===
* OBI v1.0+ release(s)
* Enhanced Backpack and OBI User Experience
* Exemplars, large-scale proofs of concept
* Open Badges issuing stack
* Community Platform
* Badge validation solution / APIs / frameworks

=== Q1: Ship OBI v1.0 ===
* '''OBI''' [https://github.com/mozilla/openbadges/issues?milestone=2&state=open Github 1.0 Milestone]
** v1.0 development and release
*** COPPA Stance
*** Extending metadata spec - a. standards alignment
*** Extending metadata spec - b. tags
*** 508 compliance
*** Signed badges
*** Backpack connect - autopush of badges from approved issuers
*** Revocation of badges
*** Badge expiration
*** user experience improvements

* '''Badge Validation'''
** [http://bit.ly/badgevalidation Publish paper]; get consensus on the solution we're working towards

=== Q2: Chicago, Issuing Tools, OBI v1.5 Development ===
* '''OBI'''
** Define, scope and start development on v1.5
** Backpack federation planning and development
** Define Endorsement specification

* '''Exemplars'''
** Chicago
*** Ship CSOL badges
*** Deliver issuing 'stack' and enhanced Backpacks for Chicago
** Mozilla badge system
*** Initial Mozilla-wide badges launched
*** Development of additional levels of webmaker badges and learning content

* '''Adoption'''
** Continued support and partnerships
** Strategic

* '''Community'''
** Community platform development and beta release

=== Q3: OBI v1.5 release ===

* '''OBI'''
** v1.5 release
** Fully federated OBI release
** Resume builder beta release

* '''Exemplars'''
** Chicago
*** Maintenance and additional features
** Mozilla Badge System
*** Multiple levels of badges and leveling up available for the Webmaker badges
*** Common issuing platform and experience for Mozilla badges
** San Francisco
*** Kick off work for SF badges

* '''Adoption'''
** Tools
*** Resume builder and other tool development
** Recruitment
*** Employer advisory board

* '''Community'''
** Working with community members to build out the knowledge base

* '''Foundational Frameworks and Practices'''
** Initial policy practices in place
** Community contribution to best practices

* '''Foundational Frameworks and Practices'''
** Publish badge system design best practices

== 2012 Roadmap ==

=== 2012 Must Haves ===
* <strike>New openbadges.org</strike>
* New, streamlined documentation
* <strike>Demo [by DML March 1]
** Available on new website
** Features:
*** Demo backpack interface and user flow
*** Demo pushing badges to display sites</strike> '''Completed 2/2012'''

* <strike>Ship OBI Beta by end of Q1 (*aiming for end of Q1 but may have issues with legal that push into Q2)
** Contributor engagement workflow
** Issuer API
** Displayer API</strike>
** Rough endorsement API
** <strike>Support around beta</strike> '''Completed 4/2012'''

* OBI 1.0 by end of year

=== Q1: Ship Beta ===

[https://github.com/mozilla/openbadges/issues?milestone=3&state=open Github Public Beta Milestone]
* <strike>Ship OBI beta by end of Q1 (aiming for end of Q1)</strike>
** <strike>Contributor engagement workflow improvement (Getting developer community to tap into OBI with facility)</strike>
** <strike>New issuer API - requiring user-initiated push to the OBI</strike>
** <strike>Displayer API</strike> '''low level, needs widgets and more detailed privacy controls'''

* Openbadges.org
** <strike>Website redesign
** Revised documentation
** Get Started on earning badges feature in website redesign
** OBI backpack and user mgmt demo</strike>

* Legal
** <strike>Initial terms of service and privacy policy FAQs</strike>

=== Q2 OBI UX Improvements ===
* OBI Features/Function Development
** Ux overhaul planning
*** Accessibility audit planning

* Adoption
** DML winner support (ongoing)
** Strategically recruit partner (ongoing)
** Onramping first wave of issuers/displayers (i.e. get people pushing badges in and out)

* <strike>Legal
** FAQs fully fleshed out</strike>

* <strike> Website planning
** Homepage revisions & updates
** Long term consideration of site updates
** Legal FAQs icon w/ own page or reconsideration of all nav
** How to highlight items on site
** Research area</strike>

=== Q3 Open Badger development ===

* OBI
** UX improvements for backpack log in and authentication
** Displayer integration
*** Fb
*** Wordpress
** Update spec to account for "Pie" badges (i.e. badges that comprise pieces of a pie)

* Open Badger Beta
** Proposed API spec: https://github.com/mozilla/openbadger/wiki/api
** Ongoing development

* Community
** Create step by step onboarding documentation and supporting material for new entrants.

* Adoption
** DML ongoing outreach to 30 funded winners

=== Q4 Open Badger beta release and OBI v1.0 development ===
[https://github.com/mozilla/openbadges/issues?milestone=2&state=open Github 1.0 Milestone]

* OBI
** v1.0 ongoing development
*** Accessibility: 508 compliance
*** COPPA compliant backpack or parallel < 13 backpack development
*** Global badge directory
*** Privacy, data, security review and vetting
*** Operational requirements review for productization

*Open Badger
** Privacy, data, security review and vetting
** Operational requirements review for beta public release
** Beta release

* Adoption
** DML first round of outreach to 60 unfunded winners
** Identify key partners to onboard
** Develop strategy map for recruitment
** Scope and model a distributed support system

* Foundational Frameworks & Practices
** Draft Badge Validation white paper

* Mozilla badge system
** Release initial round of webmaker badges system

Badges/About

2013-10-15T20:12:34Z

Threeqube: /* Open Badge Infrastructure */

__NOTOC__
= Mozilla Open Badges =

==Get recognition for new skills and achievements ...==
The web and other new learning spaces provide exciting ways to gain skills and experience -- from online courses, learning networks and mentorship to peer learning, volunteering and after-school programs. Badges provide a way for learners to get recognition for these skills, and display them to potential employers, schools, colleagues and their community.

==...through a simple framework that's open to all... ==
Using Mozilla’s Open Badges infrastructure, any organization or community can issue badges backed by their own seal of approval. Learners can then collect badges from different sources and display them across the web -- on their resumes, websites, social networking profiles, job sites and more.

==...to unlock new career and learning opportunities!==
 By displaying skills and achievements that traditional degrees and transcripts often leave out, badges can help lead to jobs, community recognition, and new learning opportunities.

[[Image:Open_Badges_one_sheet_copy.jpg|800px]]
*[https://www.dropbox.com/s/spa6r08bo3irahu/Open%20Badges%20one%20sheet.pdf PDF version is here]

== How does it work? ==

Any [http://www.openbadges.org/participating-issuers/ '''badge issuer'''] (for example, an after-school program, free online course, or vocational institute) can award certified badges to learners like you. Learners can then collect and manage their badges in a [https://backpack.openbadges.org/ '''badge backpack''']. This makes it easy to display your skills and achievements across a range of different display sites -- from your personal résumé or web site, to social networking profiles, to employment sites.

'''The result?''' Jobs, new learning opportunities and unlocked privileges.

[[Image:Open_Badges_napkin_sketch.png|800px]]

=== Open Badge Infrastructure ===

Mozilla's Open Badge infrastructure provides the open, core technology to support an ecosystem of badges. It is designed to support a broad range of different badge issuers, and allow any user to earn badges across different issuers, web sites and experiences, then combine them into a single collection tied to their identity. This collection of badges can then be shared out to various audiences across the web, resulting in real-world results like jobs or formal credit. 

*'''Open Badge Infrastructure status''': 1.0, released March 14, 2013 ([https://github.com/mozilla/openbadges/ '''source code'''])

Summit2013/Sessions

2013-09-18T17:29:48Z

Threeqube: /* Badges: How to Encourage Engagement */

=What are Supporting Sessions?=

[https://wiki.mozilla.org/Summit2013/FAQ#What_are_.E2.80.9CSupporting_Sessions.E2.80.9D_and_how_did_they_get_on_the_agenda.3F Link to the general FAQ]

=Call for Facilitators=

We need facilitators for the supporting sessions! Anyone can be a facilitator. Here is the list of sessions currently on the agenda for the Mozilla Summit 2013, with facilitators at each location. More information on expectations of facilitators can be found on the [https://wiki.mozilla.org/Summit2013/Sessionfacilitators Session Facilitators wiki].

Each proposed session has its own etherpad for discussion and description, if you click through to it. Please add to that pad if you want to suggest specific questions to be addressed within the session.

Also note there will be open sessions on site which can be signed up for when we are at the summit, "Unconference" style. For more information about how to sign-up to host an open session, please see our [https://wiki.mozilla.org/Summit2013/FAQ FAQ].

=How to Sign-up?=

See a session that you would like to facilitate? If so, please place your name by the appropriate location next to the session (listed below) on this wiki page.

'''Please note that the deadline to sign-up has now passed. If you would like to help facilitate a session, please reach out directly to the named session facilitator.'''

=Can I Co-facilitate?=

In general, if you want to Co-facilitate a session, it is frequently possible, reach out to the track owner or to the facilitators themselves.

=Who are the Track Owners?=

[[https://wiki.mozilla.org/Summit2013/TrackOwners Track Owners]] for the Summit Are:

:Mike Hoye (irc: mhoye), People and Process Track, office hours: 2-3 PM Eastern (6-7 PM UTC)
:[[https://mozillians.org/en-US/u/lmandel/ Lawrence Mandel]] (irc: lmandel), Purpose and Strategy Track, office hours: Monday and Tuesday 11-12am Eastern Time.
:[[https://mozillians.org/en-US/u/lshapiro/ Larisa Shapiro]] (irc: lshapiro), Product and Technology Track (and the Innovation Fair) office hours: M-W-F 9-10am Pacific Time

You can also reach us at:
:IRC: #mozsummit
:Vidyo (during office hours): Summit Track Owners room

Can't meet during the designated office hours? No problem. Just ping us and we'll set up an alternate time just for you. :)

Don't know who to reach out to? [https://etherpad.mozilla.org/2013supportingsessions Here] is a list of sessions as they align with the Tracks.

=Deadline to Sign-up=

'''Please note that the deadline to sign-up has now passed. If you would like to help facilitate a session, please reach out directly to the named session facilitator.'''

=Any Questions?=

If you have any additional questions, please feel free to reach out to a Track Owner or read through our [https://wiki.mozilla.org/Summit2013/FAQ FAQ].

==Friday==

===Ecosystems in our Image===

Friday, 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Track: Purpose and Strategy

Put practically and short term: how our values show up in the app ecosystem or social network (where the users are now). And, in the long term, how do our values show up in big data, internet of things and other upcoming ecosystems.
What would it look like to build a mobile apps and content ecosystem based literally on the ideas in the Nature of Mozilla? What features and marketing approaches would you include? How would we most effectively balance building, teaching and shaping markets? Where do local communities fit in as part of building this? Can they help build a long tail app ecosystem where we really see local diversity?

Facilitators:
:Brussels: David Ascher, Bill Maggs
:Toronto: Chris Lawrence, Ben Moskowitz
:Santa Clara: Alina Mierlus, Erika Owens

Session Etherpad: http://mzl.la/1ent7a9

===The Web We Want===

Friday, 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Track: Purpose and Strategy

A large, interactive session to explore the web we're championing.What do we mean by "the web"? Is it a technology? A set of values? (also, how is it different from the Internet?) What are the baseline design principles we value most? Privacy? Creativity? User freedom? User Control? Data ownership? Something else? How is the web part of our identity? How do we use our products and our voice to help the broader world--including users--understand the web and become champions with us?

Facilitators:
:Santa Clara: Asa Dotzler, [[User:Tantek|Tantek Çelik]]
:Brussels: [https://mozillians.org/en-US/u/lco/ Larissa Co], [[User:Aking|Ozten]], [[User:AlisonW|AlisonW]]
:Toronto: Potch, [https://mozillians.org/en-US/u/firetoad/ Mike Collins], Dan Sinker

Session Etherpad: http://mzl.la/15nyhNz

Afterwards:
* I've proposed an [[IndieWeb]] Hackspace on the [[Summit2013/Experiences#HackSpaces|Summit2013 Experiences]] wiki page for those that want to actively hack on their own websites and create the web we want by example. - [[User:Tantek|Tantek]] ([[User talk:Tantek|talk]])

===Building a Web Literate World===

Friday, 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Track: Purpose and Strategy

Why the large majority of people on the web should understand how the web works and how are we going to empower them to make it. How we can teach the everyday internet users more skills to improve their online experience and understand how the web works.

Facilitators:
*Toronto: Julia Vallera, Emma Irwin, Lawrence Kisuuki
*Santa Clara, Sandraghassen Subbaraya Pillai, Ankit Gadgil, Vineel Reddy Pindi, Benny Chandra, Faye Tandog
*Brussels: Christos Bacharakis, Ibrahima SARR, [https://mozillians.org/en-US/u/LauraHilliger/ Laura Hilliger]

Session Etherpad: http://mzl.la/17ZwqNo

===What does "Mozillian" mean?===

Friday, 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Track: Purpose and Strategy

A hands-on session to define the identity of Mozillians, historically and as we evolve. Towards building scope and identity as a community. Consider new domains, like news and science. Do partners count? Who do we count? What are we trying to build? Who are we inviting?

Facilitators:
:Brussels: Gervase Markham, Wilson Guaraca, Ioana Chiorean
:Toronto: Guillermo Movia, [https://mozillians.org/en-US/u/feer56/ Andrew (feer56)- Will do second session @2:45]
:Santa Clara: Sujith Reddy (would like co facilitator), Alex Lakatos

Session Etherpad: http://mzl.la/15nymAM

===Firefox OS in 2014 and Beyond===

Friday, 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Track: Product and Technology

The strategy and vision for what Firefox OS is trying to accomplish, what markets it's heading for, as well as showcasing the technology and features.

Facilitators:
:Brussels: Chris Lee, Bill Maggs
:Toronto: [https://mozillians.org/en-US/u/pdolanjski/ Peter Dolanjski], Vik Iya
:Santa Clara: Sandip Kamat, Christian Heilmann

Session Etherpad: http://mzl.la/17Zws7Y

===Privacy, Security, and Data: Pragmatic Innovations for Users and the Web===

Friday, 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Track: Product and Technology

A discussion on how we combine our desire for excellent products, services and UX with leading privacy and security characteristics that advance trust, sustainability and safety for people.

Facilitators:
:Brussels: Stacy Martin / Garrett Robinson / Simon Bennetts
:Toronto: Alex Fowler / Monica Chew / Yvan Boily
:Santa Clara: Alina Hua / Sid Stamm / Joe Stevenson

Session Etherpad: http://mzl.la/17Zwvki

===Building through Brand===

Friday, 1:00 - 2:15pm, 2:45 - 4:00pm

Track: Purpose and Strategy

NEED DESCRIPTION

Facilitators (Pete Scanlon to coordinate):
:Brussels: Ioana Chiorean, {{NeedCoFacilitator}}
:Toronto: Winston Bowden, {{NeedCoFacilitator}}
:Santa Clara: Sakina Groth, Alex Lakatos

Session Etherpad: http://mzl.la/17ZwzR0

==Saturday==

===Practicing Open===

Saturday, 1:30-3:30 pm

Track: Purpose and Strategy

When there's a conflict between openness and bushinesses requirements, how should we, as individuals, navigate that? What resources do we have available for guidance and help?

Facilitators:
:Toronto: Lawrence Kissuki, David Humphrey, Matthew Thompson
:Brussels: Ioana Chiorean
:Santa Clara: Sakina Groth

Session Etherpad: http://mzl.la/17ZwUmQ

===Mozilla: Winning the Next Three Years===

Saturday, 1:30-3:30pm (yes, this one is longer, co-facilitators encouraged)

Track: Purpose and Strategy

What does Mozilla need to be doing right now, to move the web forward, to do right by our users, and what are the most important factors to consider in planning the next three years?

Facilitators:
:Brussels: David Ascher
:Toronto: Mark Surman
:Santa Clara: Brendan Eich

Session Etherpad: http://mzl.la/17ZwWuP

===Building a Framework to enable Mozilla to effectively communicate across our community===

Saturday, 1:30-3:30pm (yes, this one is longer, co-facilitators encouraged)

Track: People and Process

How does Mozilla hold a discussion on a particular topic that allows expression of positives and negatives in a productive way? This session will build the Mozilla Framework for how to invite feedback, manage the conversation and ensure all parties are acknowledged regardless of their view of the issue.

Facilitators:
:Brussels:Gervase Markham
:Toronto: Lainie Delcoursy,[https://mozillians.org/en-US/u/feer56/ Andrew (feer56)], Majken Connor
:Santa Clara: {{NeedFacilitator}}

Session Etherpad: http://mzl.la/17ZwWeu

===Defining and Packaging a Mozilla Core experience for onboarding===

Saturday, 1:30-3:30pm (yes, this one is longer)

Track: People & Process

How do we create an experience that captures the history of Mozilla, our values, and what makes us unique in a way that we can transfer these items to new Mozillians and even our partners?

Facilitators:
:Brussels: Rubén Martín [:Nukeador] (one of the Mozilla Hispano mentors that runs the onboarding process for new contributors), Tobias Leingruber
:Toronto: Amie Tyrrel, Amira Dhalla, Lainie DeCoursy
:Santa Clara: Ankit Gadgil {{NeedCoFacilitator}}

Session Etherpad: http://mzl.la/17Zx1Pf

===What would a million Mozillians do?===

Saturday, 1:30-3:30pm (yes, this is a longer session)

Track: Purpose & Strategy

Working Narrative: A creative, "blue sky" session to imagine new kinds of contributors

Facilitators:
:Brussels: [https://mozillians.org/u/kinger/ Brian King] (Community Manager for Europe), [https://mozillians.org/u/henx/ Henrik Mitsch], [https://mozillians.org/u/nethahussain/ Netha Hussain], [https://mozillians.org/u/thornet/ Michelle Thorne], [https://mozillians.org/u/FuzzyFox/ William Duyck]
:Toronto: Marc Lesser, Margaret Schroeder
:Santa Clara: David Boswell and William Quiviger

Session Etherpad:http://mzl.la/1enxmmc

===Developing empathy for your users===

Saturday, 1:30-3:30 (yes, this one is longer)

Track: Product & Technology

A workshop where you learn how to easily make sure that the products you make are as appreciated as you think they should be.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/lco/ Larissa Co] , Maureen Hanratty
:Toronto: Cori Schauer
:Santa Clara: Lindsay Kenzig, Maria Sandberg

Session Etherpad: http://mzl.la/1enxqlU

===Understanding the Servo strategy===

Saturday, 1:30 - 3:30pm

Track: Product & Technology

Web browsers were designed around yesterday's reality of computer hardware. Servo is a rethinking of the architecture of browsers to accommodate the hardware of today and tomorrow: multiple CPU's and powerful GPU's, and with limited power consumption. What's more, Servo is being built in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust], a new programming language designed to support faster and safer development practices.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/jdm/ Josh Matthews]
:Toronto: Jack Moffitt
:Santa Clara: Patrick Walton

Session Etherpad: http://mzl.la/17Zx5yz

===Growing Stakeholders in the Web===

Saturday, 1:30 - 3:30pm

Track: Product & Technology

The success of the internet depends on commercial activity as well as individual self-expression. To make that work means that we need to understand the perspectives of different stakeholders, from phone manufacturers, to phone companies, to media companies, to consumers.

Facilitators:
:Brussels: Kat Braybrooke, Patrick Finch can co-facilitate
:Toronto: Marc Lesser
:Santa Clara: Geoffrey MacDougall, Need Co-Facilitator: Irina Sandu?

Session Etherpad: http://mzl.la/1enxPVs

===Who are our users in 2018 and where are they?===

Saturday, 4:00 - 6:00pm

Track: Product & Technology

Alternate title: What's not going to change in 2018? What motivations our users will still hold in 10-15 years?

The world is changing, and we need to build products that work for the next billion users. Who are they, and what are they like?

Facilitators:
:Brussels: Yuan Wang, Mary Trombley
:Toronto: Cori Schauer
:Santa Clara: Jinghua Zhang, Bill Selman,

Session Etherpad: http://mzl.la/1enxKkH

===Designing for our users not ourselves===

Saturday, 4:00 - 6:00pm (yes, this one is longer)

Track: Product & Technology

Introduction to our users - who they are, what they do, what they need, and how Mozilla can do this.

Facilitators:
:Cori Schauer will be main facilitator for this, and will coordinate the other facilitators.
:Brussels: Gemma & Madhava Zhenshuo & Dominik?
:Toronto: Cori & Bryan Clark (possibly Gregg Lind)
:Santa Clara: Bill Selman

Session Etherpad: http://mzl.la/1enxtOr

===How people see our markets and how we compete effectively in them===

Saturday, 4:00 - 6:00pm

Track: Product & Technology

Powerful interests are creating silos of content and private walled gardens on the web. What can Mozilla do to open these silos up or create new more open alternatives? How do we need to understand how these competitors work for markets and consumers?

Facilitators:
:Brussels: Patrick Finch {{NeedCoFacilitator}}
:Toronto: Kev Needham, John Jensen
:Santa Clara: Irina Sandu, Sandip Kamat

Session Etherpad:http://mzl.la/1enxOko

===Understanding web developers===

Saturday, 4:00 - 6:00pm

Track: Product & Technology

Web developers are a key community for Mozilla. Our competitors are building sophisticated developer tools, API's, and platform technologies. How can we maintain a close and symbiotic relationship with web developers? How do we meet their needs, and how do we get them signed up for Mozilla's mission?

Facilitators:
:Brussels: Jeff Griffiths
:Toronto: Stormy Peters
:Santa Clara: Christian Heilmann

Session Etherpad: http://mzl.la/1enxVMI

===The Petri Dish required by scaling innovation===

Saturday, 4-6pm

Track: Product and Technology

If we're to have the kind of massive impact on the internet that we hope to, we have to ask ourselves whether our structure and processes will get us there. If we want to facilitate innovation at the edges and focus on recognizing good ideas rather than having them, how should we relate to web innovators around the world?

Facilitators:
:Brussels: David Ascher
:Toronto: Simon Wex
:Santa Clara: Robert Richter

Session Etherpad: http://mzl.la/1enxJ00

===WebMaker: Getting People to Take Back The Web===

Saturday, 4-6 pm

Track: Product and Technology

Webmaker is the brand that we're using to tell a new generation of web citizens that the web is theirs to grab, shape and remix. We'll show you what that looks like, and get you activated to help in that effort!

Facilitators:

:Brussels: Kat Braybrooke, Henrik Mitsch, Michelle Thorne
:Toronto: Chris Lawrence, Amira Dhalla, Lyre Calliope, Matt Thompson
:Santa Clara: Brett Gaylor, Ankit Gadgil, Jacob Caggiano, Yoe One Ariestya Niovitta

Session Etherpad:http://mzl.la/1enxYYR

==Sunday==

===Distributed Leadership and decision making===

Sunday, 1:15-2:30 pm

Track: Purpose and Strategy

A well-facilitated inquiry and skillshare on distributed leadership. Skills Learned: Leadership, Conflict Resolution, Facilitating distributed meetings/planning/group actions. Potential Outline of Session:
# Nature of Mozilla -- one pillar is human capability; more mozillians moving the mission forward
# history of the huge chunks of mozilla that people made up on on their own and we incorporated into the centralized piece
# Some issues with distributed decision-mkaing: risk, mistakes, surprise, messiness
# What do we do now: how we build more APIs to the centralized part of mozilla?

Facilitators:
:Brussels: Laura Thomson, Ioana Chiorean
:Toronto: [https://mozillians.org/en-US/u/regnard/ Regnard Raquedan], Lukas Blakk
:Santa Clara: Alina Mierlus, Vineel Reddy Pindi

Session Etherpad: http://mzl.la/17Zxktf

===Ideas into Action: Next steps for me and my team===

Sunday, 1:15-2:30

Track: Purpose and Strategy

Four breakout sessions with a joint shareback round. Determine what winning looks like as measured by Mozilla's four pillars of activity. Tools, roadmap and things you can do when you return home. How you can adapt the 3-year plan to your local context and the projects you care about. How you can multiply the mission. Skills Learned: Metrics, Building Open into your Project, How to Identify the NoM in your ideas & highlight/promote/grow those

Facilitators:
:Brussels: Karen Rudnitski
:Toronto: Larissa Shapiro, Selena Deckelmann
:Santa Clara: Ernest Chiang

Session Etherpad: http://mzl.la/1enyki5

===Designing your project for participation===

Sunday, 1:15-2:30 pm

Track: People and Process

Nearly all projects will benefit from community involvement; however, there are different approaches and best practices that can better enable a project for wider contributions. This session will capture best practices and challenges to build a project with community involvement.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/LauraHilliger/ Laura Hilliger] (working with Mozilla Reps to help them deliver #teachtheweb professional development content)
:Toronto: David Eaves (creator of the community building workshops that includes a 'Designing your project for participation' module) or Emma Irwin (One of the Mozilla Reps who will be delivering the community building workshop content), Jess Klein
:Santa Clara: Benjamin Kerensa (One of the Mozilla Reps who will be delivering the community building workshop content)

Session Etherpad: http://mzl.la/17Zxm4A

===Community tools - what do we currently have===

Sunday, 1:15-2:30 pm

Track: People and Process

The topic of tooling seems to be a frequent one. Let's discuss the needs of the various members of the community and determine if there are shared tools in which we as a community should invest.

Facilitators:
:Brussels: [https://mozillians.org/u/jdm/ Josh Matthews], [https://mozillians.org/u/williamr/ William Reynolds] (members of the Community Building Systems Working Group)
:Toronto: [https://mozillians.org/u/mhoye/ Michael Hoye], [https://mozillians.org/u/r1cky/ Ricky Rosario] (members of the Community Building Systems Working Group)
:Santa Clara: [https://mozillians.org/u/pierros/ Pierros Papadeas] (members of the Community Building Systems Working Group)

Session Etherpad: http://mzl.la/1enyrua

===Working with corporate (closed) partners===

Sunday, 1:15-2:30 pm

Track: People and Process

How to stay open at Mozilla while meeting our needs: Creating a shared understanding of how Mozilla can work in a closed environment and a roadmap for introducing open concepts to our partners.

Facilitators:
*Toronto: Lawrence Mandel, Lukas Blakk, Bhavana Bajaj
*Brussels: Dietrich Ayala, [https://mozillians.org/en-US/u/mcote/ Mark Côté], Chris Lee
*Santa Clara: [https://mozillians.org/en-US/u/cpeterson/ Chris Peterson], Alex Keybl

Session Etherpad: http://mzl.la/1enywhl

===Workshop on Contributor recognition guide===

Sunday, 1:15-2:30 pm

Track: People and Process

Workshop to share tips and tricks for how recognize contributors to your project that would cover badges, swag, events and more. Also hack on the draft Recognition Guide at https://wiki.mozilla.org/Contribute/Recognition

Facilitator:
:Brussels: Michelle Marovich (Lead Recruiter) and Lizz Noonan (Brand Campaign Coordinator/Creative Contribute Community Co-manager)
:Toronto: Jeff Beatty (Community Building for l10n)
:Santa Clara: Rosana Ardila (Community Builder for SUMO)

Session Etherpad: http://mzl.la/17ZxsJo

===Moderated discussion on how we will think about product opportunities in the cloud===

Sunday, 1:15-2:30 pm

Track: Product and Technology

Mozilla has a proud history of championing user control of data, but there are both huge user benefits and competitive pressures to having some cloud-enabled data and services. How should Mozilla approach this problem in a way that pushes the mission forward while being pragmatic to the needs of the market?

Facilitators:
:Brussels: Lloyd Hilaiel
:Toronto: John Jensen
:Santa Clara: Toby Elliott

Session Etherpad: http://mzl.la/17ZxrFk

===The future of web gaming===

Sunday, 1:15-2:30 pm

Track: Product and Technology

The web is poised to become a platform for games, which opens up opportunities for new markets and independent developers. With WebGL, asm.js, and key web API's like Pointer Lock, audio, and video, Mozilla is making the future of web gaming a reality, and creating an open alternative to proprietary technologies like Google's NaCl and Chrome.

Facilitators:
:Brussels: Vlad Vukicevic
:Toronto: Martin Best
:Santa Clara: Marco Mucci

Session Etherpad: http://mzl.la/17Zxu3U

===Open Badges: How to Encourage Engagement===

Sunday, 1:15-2:30 pm

Track: Product and Technology

Working Narrative: With OpenBadges, Mozilla has a combination of technology and market-shaping partners which could shift how people engage, get recognized for their skills and contributions, and unlock new opportunities. Learn about OpenBadges and what it's shooting for.

Facilitators:
:Brussels: Tim Riches, Emily Goligoski
:Toronto: Meg Cole, Kerrie Lemoie, Damian Ewens
:Santa Clara: Sunny Lee, Carla Casilli

Session Etherpad:http://mzl.la/1enyN3W

Summit2013/Sessions

2013-09-18T17:23:58Z

Threeqube: /* Badges and how they can help rethink education */

=What are Supporting Sessions?=

[https://wiki.mozilla.org/Summit2013/FAQ#What_are_.E2.80.9CSupporting_Sessions.E2.80.9D_and_how_did_they_get_on_the_agenda.3F Link to the general FAQ]

=Call for Facilitators=

We need facilitators for the supporting sessions! Anyone can be a facilitator. Here is the list of sessions currently on the agenda for the Mozilla Summit 2013, with facilitators at each location. More information on expectations of facilitators can be found on the [https://wiki.mozilla.org/Summit2013/Sessionfacilitators Session Facilitators wiki].

Each proposed session has its own etherpad for discussion and description, if you click through to it. Please add to that pad if you want to suggest specific questions to be addressed within the session.

Also note there will be open sessions on site which can be signed up for when we are at the summit, "Unconference" style. For more information about how to sign-up to host an open session, please see our [https://wiki.mozilla.org/Summit2013/FAQ FAQ].

=How to Sign-up?=

See a session that you would like to facilitate? If so, please place your name by the appropriate location next to the session (listed below) on this wiki page.

'''Please note that the deadline to sign-up has now passed. If you would like to help facilitate a session, please reach out directly to the named session facilitator.'''

=Can I Co-facilitate?=

In general, if you want to Co-facilitate a session, it is frequently possible, reach out to the track owner or to the facilitators themselves.

=Who are the Track Owners?=

[[https://wiki.mozilla.org/Summit2013/TrackOwners Track Owners]] for the Summit Are:

:Mike Hoye (irc: mhoye), People and Process Track, office hours: 2-3 PM Eastern (6-7 PM UTC)
:[[https://mozillians.org/en-US/u/lmandel/ Lawrence Mandel]] (irc: lmandel), Purpose and Strategy Track, office hours: Monday and Tuesday 11-12am Eastern Time.
:[[https://mozillians.org/en-US/u/lshapiro/ Larisa Shapiro]] (irc: lshapiro), Product and Technology Track (and the Innovation Fair) office hours: M-W-F 9-10am Pacific Time

You can also reach us at:
:IRC: #mozsummit
:Vidyo (during office hours): Summit Track Owners room

Can't meet during the designated office hours? No problem. Just ping us and we'll set up an alternate time just for you. :)

Don't know who to reach out to? [https://etherpad.mozilla.org/2013supportingsessions Here] is a list of sessions as they align with the Tracks.

=Deadline to Sign-up=

'''Please note that the deadline to sign-up has now passed. If you would like to help facilitate a session, please reach out directly to the named session facilitator.'''

=Any Questions?=

If you have any additional questions, please feel free to reach out to a Track Owner or read through our [https://wiki.mozilla.org/Summit2013/FAQ FAQ].

==Friday==

===Ecosystems in our Image===

Friday, 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Track: Purpose and Strategy

Put practically and short term: how our values show up in the app ecosystem or social network (where the users are now). And, in the long term, how do our values show up in big data, internet of things and other upcoming ecosystems.
What would it look like to build a mobile apps and content ecosystem based literally on the ideas in the Nature of Mozilla? What features and marketing approaches would you include? How would we most effectively balance building, teaching and shaping markets? Where do local communities fit in as part of building this? Can they help build a long tail app ecosystem where we really see local diversity?

Facilitators:
:Brussels: David Ascher, Bill Maggs
:Toronto: Chris Lawrence, Ben Moskowitz
:Santa Clara: Alina Mierlus, Erika Owens

Session Etherpad: http://mzl.la/1ent7a9

===The Web We Want===

Friday, 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Track: Purpose and Strategy

A large, interactive session to explore the web we're championing.What do we mean by "the web"? Is it a technology? A set of values? (also, how is it different from the Internet?) What are the baseline design principles we value most? Privacy? Creativity? User freedom? User Control? Data ownership? Something else? How is the web part of our identity? How do we use our products and our voice to help the broader world--including users--understand the web and become champions with us?

Facilitators:
:Santa Clara: Asa Dotzler, [[User:Tantek|Tantek Çelik]]
:Brussels: [https://mozillians.org/en-US/u/lco/ Larissa Co], [[User:Aking|Ozten]], [[User:AlisonW|AlisonW]]
:Toronto: Potch, [https://mozillians.org/en-US/u/firetoad/ Mike Collins], Dan Sinker

Session Etherpad: http://mzl.la/15nyhNz

Afterwards:
* I've proposed an [[IndieWeb]] Hackspace on the [[Summit2013/Experiences#HackSpaces|Summit2013 Experiences]] wiki page for those that want to actively hack on their own websites and create the web we want by example. - [[User:Tantek|Tantek]] ([[User talk:Tantek|talk]])

===Building a Web Literate World===

Friday, 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Track: Purpose and Strategy

Why the large majority of people on the web should understand how the web works and how are we going to empower them to make it. How we can teach the everyday internet users more skills to improve their online experience and understand how the web works.

Facilitators:
*Toronto: Julia Vallera, Emma Irwin, Lawrence Kisuuki
*Santa Clara, Sandraghassen Subbaraya Pillai, Ankit Gadgil, Vineel Reddy Pindi, Benny Chandra, Faye Tandog
*Brussels: Christos Bacharakis, Ibrahima SARR, [https://mozillians.org/en-US/u/LauraHilliger/ Laura Hilliger]

Session Etherpad: http://mzl.la/17ZwqNo

===What does "Mozillian" mean?===

Friday, 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Track: Purpose and Strategy

A hands-on session to define the identity of Mozillians, historically and as we evolve. Towards building scope and identity as a community. Consider new domains, like news and science. Do partners count? Who do we count? What are we trying to build? Who are we inviting?

Facilitators:
:Brussels: Gervase Markham, Wilson Guaraca, Ioana Chiorean
:Toronto: Guillermo Movia, [https://mozillians.org/en-US/u/feer56/ Andrew (feer56)- Will do second session @2:45]
:Santa Clara: Sujith Reddy (would like co facilitator), Alex Lakatos

Session Etherpad: http://mzl.la/15nymAM

===Firefox OS in 2014 and Beyond===

Friday, 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Track: Product and Technology

The strategy and vision for what Firefox OS is trying to accomplish, what markets it's heading for, as well as showcasing the technology and features.

Facilitators:
:Brussels: Chris Lee, Bill Maggs
:Toronto: [https://mozillians.org/en-US/u/pdolanjski/ Peter Dolanjski], Vik Iya
:Santa Clara: Sandip Kamat, Christian Heilmann

Session Etherpad: http://mzl.la/17Zws7Y

===Privacy, Security, and Data: Pragmatic Innovations for Users and the Web===

Friday, 1-2:15, 2:45-4:00 (please note these sessions are run twice, therefore co-facilitation is recommended)

Track: Product and Technology

A discussion on how we combine our desire for excellent products, services and UX with leading privacy and security characteristics that advance trust, sustainability and safety for people.

Facilitators:
:Brussels: Stacy Martin / Garrett Robinson / Simon Bennetts
:Toronto: Alex Fowler / Monica Chew / Yvan Boily
:Santa Clara: Alina Hua / Sid Stamm / Joe Stevenson

Session Etherpad: http://mzl.la/17Zwvki

===Building through Brand===

Friday, 1:00 - 2:15pm, 2:45 - 4:00pm

Track: Purpose and Strategy

NEED DESCRIPTION

Facilitators (Pete Scanlon to coordinate):
:Brussels: Ioana Chiorean, {{NeedCoFacilitator}}
:Toronto: Winston Bowden, {{NeedCoFacilitator}}
:Santa Clara: Sakina Groth, Alex Lakatos

Session Etherpad: http://mzl.la/17ZwzR0

==Saturday==

===Practicing Open===

Saturday, 1:30-3:30 pm

Track: Purpose and Strategy

When there's a conflict between openness and bushinesses requirements, how should we, as individuals, navigate that? What resources do we have available for guidance and help?

Facilitators:
:Toronto: Lawrence Kissuki, David Humphrey, Matthew Thompson
:Brussels: Ioana Chiorean
:Santa Clara: Sakina Groth

Session Etherpad: http://mzl.la/17ZwUmQ

===Mozilla: Winning the Next Three Years===

Saturday, 1:30-3:30pm (yes, this one is longer, co-facilitators encouraged)

Track: Purpose and Strategy

What does Mozilla need to be doing right now, to move the web forward, to do right by our users, and what are the most important factors to consider in planning the next three years?

Facilitators:
:Brussels: David Ascher
:Toronto: Mark Surman
:Santa Clara: Brendan Eich

Session Etherpad: http://mzl.la/17ZwWuP

===Building a Framework to enable Mozilla to effectively communicate across our community===

Saturday, 1:30-3:30pm (yes, this one is longer, co-facilitators encouraged)

Track: People and Process

How does Mozilla hold a discussion on a particular topic that allows expression of positives and negatives in a productive way? This session will build the Mozilla Framework for how to invite feedback, manage the conversation and ensure all parties are acknowledged regardless of their view of the issue.

Facilitators:
:Brussels:Gervase Markham
:Toronto: Lainie Delcoursy,[https://mozillians.org/en-US/u/feer56/ Andrew (feer56)], Majken Connor
:Santa Clara: {{NeedFacilitator}}

Session Etherpad: http://mzl.la/17ZwWeu

===Defining and Packaging a Mozilla Core experience for onboarding===

Saturday, 1:30-3:30pm (yes, this one is longer)

Track: People & Process

How do we create an experience that captures the history of Mozilla, our values, and what makes us unique in a way that we can transfer these items to new Mozillians and even our partners?

Facilitators:
:Brussels: Rubén Martín [:Nukeador] (one of the Mozilla Hispano mentors that runs the onboarding process for new contributors), Tobias Leingruber
:Toronto: Amie Tyrrel, Amira Dhalla, Lainie DeCoursy
:Santa Clara: Ankit Gadgil {{NeedCoFacilitator}}

Session Etherpad: http://mzl.la/17Zx1Pf

===What would a million Mozillians do?===

Saturday, 1:30-3:30pm (yes, this is a longer session)

Track: Purpose & Strategy

Working Narrative: A creative, "blue sky" session to imagine new kinds of contributors

Facilitators:
:Brussels: [https://mozillians.org/u/kinger/ Brian King] (Community Manager for Europe), [https://mozillians.org/u/henx/ Henrik Mitsch], [https://mozillians.org/u/nethahussain/ Netha Hussain], [https://mozillians.org/u/thornet/ Michelle Thorne], [https://mozillians.org/u/FuzzyFox/ William Duyck]
:Toronto: Marc Lesser, Margaret Schroeder
:Santa Clara: David Boswell and William Quiviger

Session Etherpad:http://mzl.la/1enxmmc

===Developing empathy for your users===

Saturday, 1:30-3:30 (yes, this one is longer)

Track: Product & Technology

A workshop where you learn how to easily make sure that the products you make are as appreciated as you think they should be.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/lco/ Larissa Co] , Maureen Hanratty
:Toronto: Cori Schauer
:Santa Clara: Lindsay Kenzig, Maria Sandberg

Session Etherpad: http://mzl.la/1enxqlU

===Understanding the Servo strategy===

Saturday, 1:30 - 3:30pm

Track: Product & Technology

Web browsers were designed around yesterday's reality of computer hardware. Servo is a rethinking of the architecture of browsers to accommodate the hardware of today and tomorrow: multiple CPU's and powerful GPU's, and with limited power consumption. What's more, Servo is being built in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust], a new programming language designed to support faster and safer development practices.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/jdm/ Josh Matthews]
:Toronto: Jack Moffitt
:Santa Clara: Patrick Walton

Session Etherpad: http://mzl.la/17Zx5yz

===Growing Stakeholders in the Web===

Saturday, 1:30 - 3:30pm

Track: Product & Technology

The success of the internet depends on commercial activity as well as individual self-expression. To make that work means that we need to understand the perspectives of different stakeholders, from phone manufacturers, to phone companies, to media companies, to consumers.

Facilitators:
:Brussels: Kat Braybrooke, Patrick Finch can co-facilitate
:Toronto: Marc Lesser
:Santa Clara: Geoffrey MacDougall, Need Co-Facilitator: Irina Sandu?

Session Etherpad: http://mzl.la/1enxPVs

===Who are our users in 2018 and where are they?===

Saturday, 4:00 - 6:00pm

Track: Product & Technology

Alternate title: What's not going to change in 2018? What motivations our users will still hold in 10-15 years?

The world is changing, and we need to build products that work for the next billion users. Who are they, and what are they like?

Facilitators:
:Brussels: Yuan Wang, Mary Trombley
:Toronto: Cori Schauer
:Santa Clara: Jinghua Zhang, Bill Selman,

Session Etherpad: http://mzl.la/1enxKkH

===Designing for our users not ourselves===

Saturday, 4:00 - 6:00pm (yes, this one is longer)

Track: Product & Technology

Introduction to our users - who they are, what they do, what they need, and how Mozilla can do this.

Facilitators:
:Cori Schauer will be main facilitator for this, and will coordinate the other facilitators.
:Brussels: Gemma & Madhava Zhenshuo & Dominik?
:Toronto: Cori & Bryan Clark (possibly Gregg Lind)
:Santa Clara: Bill Selman

Session Etherpad: http://mzl.la/1enxtOr

===How people see our markets and how we compete effectively in them===

Saturday, 4:00 - 6:00pm

Track: Product & Technology

Powerful interests are creating silos of content and private walled gardens on the web. What can Mozilla do to open these silos up or create new more open alternatives? How do we need to understand how these competitors work for markets and consumers?

Facilitators:
:Brussels: Patrick Finch {{NeedCoFacilitator}}
:Toronto: Kev Needham, John Jensen
:Santa Clara: Irina Sandu, Sandip Kamat

Session Etherpad:http://mzl.la/1enxOko

===Understanding web developers===

Saturday, 4:00 - 6:00pm

Track: Product & Technology

Web developers are a key community for Mozilla. Our competitors are building sophisticated developer tools, API's, and platform technologies. How can we maintain a close and symbiotic relationship with web developers? How do we meet their needs, and how do we get them signed up for Mozilla's mission?

Facilitators:
:Brussels: Jeff Griffiths
:Toronto: Stormy Peters
:Santa Clara: Christian Heilmann

Session Etherpad: http://mzl.la/1enxVMI

===The Petri Dish required by scaling innovation===

Saturday, 4-6pm

Track: Product and Technology

If we're to have the kind of massive impact on the internet that we hope to, we have to ask ourselves whether our structure and processes will get us there. If we want to facilitate innovation at the edges and focus on recognizing good ideas rather than having them, how should we relate to web innovators around the world?

Facilitators:
:Brussels: David Ascher
:Toronto: Simon Wex
:Santa Clara: Robert Richter

Session Etherpad: http://mzl.la/1enxJ00

===WebMaker: Getting People to Take Back The Web===

Saturday, 4-6 pm

Track: Product and Technology

Webmaker is the brand that we're using to tell a new generation of web citizens that the web is theirs to grab, shape and remix. We'll show you what that looks like, and get you activated to help in that effort!

Facilitators:

:Brussels: Kat Braybrooke, Henrik Mitsch, Michelle Thorne
:Toronto: Chris Lawrence, Amira Dhalla, Lyre Calliope, Matt Thompson
:Santa Clara: Brett Gaylor, Ankit Gadgil, Jacob Caggiano, Yoe One Ariestya Niovitta

Session Etherpad:http://mzl.la/1enxYYR

==Sunday==

===Distributed Leadership and decision making===

Sunday, 1:15-2:30 pm

Track: Purpose and Strategy

A well-facilitated inquiry and skillshare on distributed leadership. Skills Learned: Leadership, Conflict Resolution, Facilitating distributed meetings/planning/group actions. Potential Outline of Session:
# Nature of Mozilla -- one pillar is human capability; more mozillians moving the mission forward
# history of the huge chunks of mozilla that people made up on on their own and we incorporated into the centralized piece
# Some issues with distributed decision-mkaing: risk, mistakes, surprise, messiness
# What do we do now: how we build more APIs to the centralized part of mozilla?

Facilitators:
:Brussels: Laura Thomson, Ioana Chiorean
:Toronto: [https://mozillians.org/en-US/u/regnard/ Regnard Raquedan], Lukas Blakk
:Santa Clara: Alina Mierlus, Vineel Reddy Pindi

Session Etherpad: http://mzl.la/17Zxktf

===Ideas into Action: Next steps for me and my team===

Sunday, 1:15-2:30

Track: Purpose and Strategy

Four breakout sessions with a joint shareback round. Determine what winning looks like as measured by Mozilla's four pillars of activity. Tools, roadmap and things you can do when you return home. How you can adapt the 3-year plan to your local context and the projects you care about. How you can multiply the mission. Skills Learned: Metrics, Building Open into your Project, How to Identify the NoM in your ideas & highlight/promote/grow those

Facilitators:
:Brussels: Karen Rudnitski
:Toronto: Larissa Shapiro, Selena Deckelmann
:Santa Clara: Ernest Chiang

Session Etherpad: http://mzl.la/1enyki5

===Designing your project for participation===

Sunday, 1:15-2:30 pm

Track: People and Process

Nearly all projects will benefit from community involvement; however, there are different approaches and best practices that can better enable a project for wider contributions. This session will capture best practices and challenges to build a project with community involvement.

Facilitators:
:Brussels: [https://mozillians.org/en-US/u/LauraHilliger/ Laura Hilliger] (working with Mozilla Reps to help them deliver #teachtheweb professional development content)
:Toronto: David Eaves (creator of the community building workshops that includes a 'Designing your project for participation' module) or Emma Irwin (One of the Mozilla Reps who will be delivering the community building workshop content), Jess Klein
:Santa Clara: Benjamin Kerensa (One of the Mozilla Reps who will be delivering the community building workshop content)

Session Etherpad: http://mzl.la/17Zxm4A

===Community tools - what do we currently have===

Sunday, 1:15-2:30 pm

Track: People and Process

The topic of tooling seems to be a frequent one. Let's discuss the needs of the various members of the community and determine if there are shared tools in which we as a community should invest.

Facilitators:
:Brussels: [https://mozillians.org/u/jdm/ Josh Matthews], [https://mozillians.org/u/williamr/ William Reynolds] (members of the Community Building Systems Working Group)
:Toronto: [https://mozillians.org/u/mhoye/ Michael Hoye], [https://mozillians.org/u/r1cky/ Ricky Rosario] (members of the Community Building Systems Working Group)
:Santa Clara: [https://mozillians.org/u/pierros/ Pierros Papadeas] (members of the Community Building Systems Working Group)

Session Etherpad: http://mzl.la/1enyrua

===Working with corporate (closed) partners===

Sunday, 1:15-2:30 pm

Track: People and Process

How to stay open at Mozilla while meeting our needs: Creating a shared understanding of how Mozilla can work in a closed environment and a roadmap for introducing open concepts to our partners.

Facilitators:
*Toronto: Lawrence Mandel, Lukas Blakk, Bhavana Bajaj
*Brussels: Dietrich Ayala, [https://mozillians.org/en-US/u/mcote/ Mark Côté], Chris Lee
*Santa Clara: [https://mozillians.org/en-US/u/cpeterson/ Chris Peterson], Alex Keybl

Session Etherpad: http://mzl.la/1enywhl

===Workshop on Contributor recognition guide===

Sunday, 1:15-2:30 pm

Track: People and Process

Workshop to share tips and tricks for how recognize contributors to your project that would cover badges, swag, events and more. Also hack on the draft Recognition Guide at https://wiki.mozilla.org/Contribute/Recognition

Facilitator:
:Brussels: Michelle Marovich (Lead Recruiter) and Lizz Noonan (Brand Campaign Coordinator/Creative Contribute Community Co-manager)
:Toronto: Jeff Beatty (Community Building for l10n)
:Santa Clara: Rosana Ardila (Community Builder for SUMO)

Session Etherpad: http://mzl.la/17ZxsJo

===Moderated discussion on how we will think about product opportunities in the cloud===

Sunday, 1:15-2:30 pm

Track: Product and Technology

Mozilla has a proud history of championing user control of data, but there are both huge user benefits and competitive pressures to having some cloud-enabled data and services. How should Mozilla approach this problem in a way that pushes the mission forward while being pragmatic to the needs of the market?

Facilitators:
:Brussels: Lloyd Hilaiel
:Toronto: John Jensen
:Santa Clara: Toby Elliott

Session Etherpad: http://mzl.la/17ZxrFk

===The future of web gaming===

Sunday, 1:15-2:30 pm

Track: Product and Technology

The web is poised to become a platform for games, which opens up opportunities for new markets and independent developers. With WebGL, asm.js, and key web API's like Pointer Lock, audio, and video, Mozilla is making the future of web gaming a reality, and creating an open alternative to proprietary technologies like Google's NaCl and Chrome.

Facilitators:
:Brussels: Vlad Vukicevic
:Toronto: Martin Best
:Santa Clara: Marco Mucci

Session Etherpad: http://mzl.la/17Zxu3U

===Badges: How to Encourage Engagement===

Sunday, 1:15-2:30 pm

Track: Product and Technology

Working Narrative: With OpenBadges, Mozilla has a combination of technology and market-shaping partners which could shift how people learn, get recognized for their skills, and level up in the game of life. Learn about the OpenBadges project and what it's shooting for.

Facilitators:
:Brussels: Tim Riches, Emily Goligoski
:Toronto: Jess Klein, Meg Cole, Kerrie Lemoie, Damian Ewens
:Santa Clara: Sunny Lee, Carla Casilli

Session Etherpad:http://mzl.la/1enyN3W

Badges/About

2013-09-10T14:49:14Z

Threeqube: /* Open Badge Infrastructure */

__NOTOC__
= Mozilla Open Badges =

==Get recognition for new skills and achievements ==
The web and other new learning spaces provide exciting ways to gain skills and experience -- from online courses, learning networks and mentorship to peer learning, volunteering and after-school programs. Badges provide a way for learners to get recognition for these skills, and display them to potential employers, schools, colleagues and their community.

==Through a simple framework that's open to all ==
Using Mozilla’s Open Badges infrastructure, any organization or community can issue badges backed by their own seal of approval. Learners can then collect badges from different sources and display them across the web -- on their resumes, websites, social networking profiles, job sites and more.

==Unlocking new career and learning opportunities==
 By displaying skills and achievements that traditional degrees and transcripts often leave out, badges can help lead to jobs, community recognition, and new learning opportunities.

[[Image:OpenBadges -- one-pager -- DRAFT ONLY -- version 1.4.jpg|800px]]
*[https://wiki.mozilla.org/images/6/64/OpenBadges_--_one-pager_--_DRAFT_ONLY_--_version_1.4.pdf PDF version is here]

== How does it work? ==

[[Image:Open_Badges_napkin_sketch.png|800px]]

'''''How does it work?''''' Any '''BADGE ISSUER '''(for example, an after-school programs, free online course, or vocational institute) can award certified '''BADGES''' to learners like you. Learners can then collect and manage their badges in a '''BADGE BACKPACK'''. This makes it easy to display your skills and achievements across a range of different '''DISPLAY SITES''' -- from your personal resume or web site, to social networking profiles, to employment sites. The result? Jobs, new learning opportunities and unlocked privileges.

The project consists of several parts:

=== Open Badge Infrastructure ===

Mozilla's Open Badge infrastructure provides the open, core technology to support an ecosystem of badges. It is designed to support a broad range of different badge issuers, and allow any user to earn badges across different issuers, web sites and experiences, then combine them into a single collection tied to their identity. This collection of badges can then be shared out to various audiences across the web, resulting in real-world results like jobs or formal credit. 

*'''Open Badge Infrastructure status''': 1.0, released March 14, 2013 ([https://github.com/mozilla/openbadges/ '''source code'''])

=== Conceptual framework and innovation in assessment and credentials ===

Mozilla is collaborating with thought leaders and innovators in assessment and credentials to inform wider efforts.

*'''STATUS''': current version of the working badge paper ([https://wiki.mozilla.org/File:OpenBadges-Working-Paper_092011.pdf '''Download'''])

Badges/About

2013-09-10T14:48:22Z

Threeqube: /* Badge system prototypes and pilot programs */

__NOTOC__
= Mozilla Open Badges =

==Get recognition for new skills and achievements ==
The web and other new learning spaces provide exciting ways to gain skills and experience -- from online courses, learning networks and mentorship to peer learning, volunteering and after-school programs. Badges provide a way for learners to get recognition for these skills, and display them to potential employers, schools, colleagues and their community.

==Through a simple framework that's open to all ==
Using Mozilla’s Open Badges infrastructure, any organization or community can issue badges backed by their own seal of approval. Learners can then collect badges from different sources and display them across the web -- on their resumes, websites, social networking profiles, job sites and more.

==Unlocking new career and learning opportunities==
 By displaying skills and achievements that traditional degrees and transcripts often leave out, badges can help lead to jobs, community recognition, and new learning opportunities.

[[Image:OpenBadges -- one-pager -- DRAFT ONLY -- version 1.4.jpg|800px]]
*[https://wiki.mozilla.org/images/6/64/OpenBadges_--_one-pager_--_DRAFT_ONLY_--_version_1.4.pdf PDF version is here]

== How does it work? ==

[[Image:Open_Badges_napkin_sketch.png|800px]]

'''''How does it work?''''' Any '''BADGE ISSUER '''(for example, an after-school programs, free online course, or vocational institute) can award certified '''BADGES''' to learners like you. Learners can then collect and manage their badges in a '''BADGE BACKPACK'''. This makes it easy to display your skills and achievements across a range of different '''DISPLAY SITES''' -- from your personal resume or web site, to social networking profiles, to employment sites. The result? Jobs, new learning opportunities and unlocked privileges.

The project consists of several parts:

=== Open Badge Infrastructure ===

Mozilla's Open Badge infrastructure provides the open, core technology to support an ecosystem of badges. It is designed to support a broad range of different badge issuers, and allow any user to earn badges across different issuers, web sites and experiences, then combine them into a single collection tied to their identity. This collection of badges can then be shared out to various audiences across the web, resulting in real-world results like jobs or formal credit. 

*'''Open Badge Infrastructure status''': 1.0, released March 14, 2013 ([https://wiki.mozilla.org/Badges/infrastructure-tech-docs '''documentation'''], [https://github.com/mozilla/openbadges/ '''source code'''])

=== Conceptual framework and innovation in assessment and credentials ===

Mozilla is collaborating with thought leaders and innovators in assessment and credentials to inform wider efforts.

*'''STATUS''': current version of the working badge paper ([https://wiki.mozilla.org/File:OpenBadges-Working-Paper_092011.pdf '''Download'''])

Badges/About

2013-09-10T14:47:55Z

Threeqube: /* Open Badge Infrastructure */

__NOTOC__
= Mozilla Open Badges =

==Get recognition for new skills and achievements ==
The web and other new learning spaces provide exciting ways to gain skills and experience -- from online courses, learning networks and mentorship to peer learning, volunteering and after-school programs. Badges provide a way for learners to get recognition for these skills, and display them to potential employers, schools, colleagues and their community.

==Through a simple framework that's open to all ==
Using Mozilla’s Open Badges infrastructure, any organization or community can issue badges backed by their own seal of approval. Learners can then collect badges from different sources and display them across the web -- on their resumes, websites, social networking profiles, job sites and more.

==Unlocking new career and learning opportunities==
 By displaying skills and achievements that traditional degrees and transcripts often leave out, badges can help lead to jobs, community recognition, and new learning opportunities.

[[Image:OpenBadges -- one-pager -- DRAFT ONLY -- version 1.4.jpg|800px]]
*[https://wiki.mozilla.org/images/6/64/OpenBadges_--_one-pager_--_DRAFT_ONLY_--_version_1.4.pdf PDF version is here]

== How does it work? ==

[[Image:Open_Badges_napkin_sketch.png|800px]]

'''''How does it work?''''' Any '''BADGE ISSUER '''(for example, an after-school programs, free online course, or vocational institute) can award certified '''BADGES''' to learners like you. Learners can then collect and manage their badges in a '''BADGE BACKPACK'''. This makes it easy to display your skills and achievements across a range of different '''DISPLAY SITES''' -- from your personal resume or web site, to social networking profiles, to employment sites. The result? Jobs, new learning opportunities and unlocked privileges.

The project consists of several parts:

=== Open Badge Infrastructure ===

Mozilla's Open Badge infrastructure provides the open, core technology to support an ecosystem of badges. It is designed to support a broad range of different badge issuers, and allow any user to earn badges across different issuers, web sites and experiences, then combine them into a single collection tied to their identity. This collection of badges can then be shared out to various audiences across the web, resulting in real-world results like jobs or formal credit. 

*'''Open Badge Infrastructure status''': 1.0, released March 14, 2013 ([https://wiki.mozilla.org/Badges/infrastructure-tech-docs '''documentation'''], [https://github.com/mozilla/openbadges/ '''source code'''])

=== Badge system prototypes and pilot programs ===

Mozilla and Peer 2 Peer University are also building a pilot badge system for the School of Webcraft, offering free, open, peer-based training for web developers.

*'''STATUS''': pilot, planning for phase 2 ([https://wiki.mozilla.org/Badges/Pilot_programs '''Learn More'''])

=== Conceptual framework and innovation in assessment and credentials ===

Mozilla is collaborating with thought leaders and innovators in assessment and credentials to inform wider efforts.

*'''STATUS''': current version of the working badge paper ([https://wiki.mozilla.org/File:OpenBadges-Working-Paper_092011.pdf '''Download'''])

Badges/About

2013-06-25T00:53:33Z

Threeqube: /* How does it work? */

__NOTOC__
= Mozilla Open Badges =

==Get recognition for new skills and achievements ==
The web and other new learning spaces provide exciting ways to gain skills and experience -- from online courses, learning networks and mentorship to peer learning, volunteering and after-school programs. Badges provide a way for learners to get recognition for these skills, and display them to potential employers, schools, colleagues and their community.

==Through a simple framework that's open to all ==
Using Mozilla’s Open Badges infrastructure, any organization or community can issue badges backed by their own seal of approval. Learners can then collect badges from different sources and display them across the web -- on their resumes, websites, social networking profiles, job sites and more.

==Unlocking new career and learning opportunities==
 By displaying skills and achievements that traditional degrees and transcripts often leave out, badges can help lead to jobs, community recognition, and new learning opportunities.

[[Image:OpenBadges -- one-pager -- DRAFT ONLY -- version 1.4.jpg|800px]]
*[https://wiki.mozilla.org/images/6/64/OpenBadges_--_one-pager_--_DRAFT_ONLY_--_version_1.4.pdf PDF version is here]

== How does it work? ==

[[Image:Open_Badges_napkin_sketch.png|800px]]

'''''How does it work?''''' Any '''BADGE ISSUER '''(for example, an after-school programs, free online course, or vocational institute) can award certified '''BADGES''' to learners like you. Learners can then collect and manage their badges in a '''BADGE BACKPACK'''. This makes it easy to display your skills and achievements across a range of different '''DISPLAY SITES''' -- from your personal resume or web site, to social networking profiles, to employment sites. The result? Jobs, new learning opportunities and unlocked privileges.

The project consists of several parts:

=== Open Badge Infrastructure ===

Mozilla's Open Badge infrastructure provides the open, core technology to support an ecosystem of badges. It is designed to support a broad range of different badge issuers, and allow any user to earn badges across different issuers, web sites and experiences, then combine them into a single collection tied to their identity. This collection of badges can then be shared out to various audiences across the web, resulting in real-world results like jobs or formal credit. 

*'''Open Badge Infrastructure status''': beta1, released September 14, 2011 ([https://wiki.mozilla.org/Badges/infrastructure-tech-docs '''documentation'''], [https://github.com/mozilla/openbadges/ '''source code'''])

=== Badge system prototypes and pilot programs ===

Mozilla and Peer 2 Peer University are also building a pilot badge system for the School of Webcraft, offering free, open, peer-based training for web developers.

*'''STATUS''': pilot, planning for phase 2 ([https://wiki.mozilla.org/Badges/Pilot_programs '''Learn More'''])

=== Conceptual framework and innovation in assessment and credentials ===

Mozilla is collaborating with thought leaders and innovators in assessment and credentials to inform wider efforts.

*'''STATUS''': current version of the working badge paper ([https://wiki.mozilla.org/File:OpenBadges-Working-Paper_092011.pdf '''Download'''])

Badges

2013-06-25T00:51:28Z

Threeqube: /* What is Mozilla's Open Badges project? */

<section begin=summary />{{RoadmapSummary
|icon=3ea2d817e92ac6e2e4e69bf9e9290d4f bigger.png
|pagelocation=Open Badges
|pagetitle=Mozilla Open Badges
|owner=Erin Knight, Carla Casilli, Sunny Lee, Emily Goligoski, Chris McAvoy, Brian Brennan, Mike Larsson, Doug Belshaw, Jess Klein, Chloe Varelidi, Atul Varma, Meg Cole, Jade Forester
|updated=June 2013
|description=Mozilla's Open Badges make it easy for anyone to issue, earn and display badges across the web through a shared infrastructure that's free and open to all.
}}<section end=summary />

__NOTOC__

== What is Mozilla's Open Badges project? ==

Learning today happens everywhere, not just in the classroom. But it's often difficult to get recognition for skills and achievements that happen outside of school. '''Mozilla's Open Badges project''' is working to solve that problem, making it easy for anyone to issue, earn and display badges across the web through a shared technical infrastructure. '''The result:''' helping people of all ages gain and display 21st century skills and unlock new career and educational opportunities.

[[Image:Open_Badges_napkin_sketch.png|800px]]

== Get involved with Open Badges ==

;Check out our site
:http://openbadges.org

;Create your Backpack
:https://backpack.openbadges.org

;Join our weekly community calls
:Our [https://openbadges.etherpad.mozilla.org/openbadges-community Open Badges community calls] are held weekly on Wednesdays at 9am PT (-8 UTC) and are open to the public. During these hour-long calls we share our progress and encourage you to share your Open Badges work, questions, and comments. They're fun and we encourage you to join them.

;Subscribe to our mailing list
:Subscribe to the [https://groups.google.com/d/forum/openbadges Open Badges learning group] and [https://groups.google.com/forum/#!forum/openbadges-dev development group] to take part in ongoing conversations about badges in the wild.

;Find others ways to join the community
:Check out [http://community.openbadges.org/ learning, design and technical themes] being explored by people like you.

;Read our whitepaper
:We wrote a whitepaper on some of the initial thinking and framing about badges. [https://wiki.mozilla.org/File:OpenBadges-Working-Paper_012312.pdf Check it out!]

;Check out our code
:Visit our [https://github.com/mozilla/openbadges Open Badges github repository] where you can see our [https://github.com/mozilla/openbadges/wiki technical wiki], view our outstanding and closed issues, and submit bugs. You can also find [https://github.com/mozilla/openbadges/wiki/Open-Badges-related-widgets Open Badges related widgets].

;View our roadmap
:We're continually updating the [https://wiki.mozilla.org/Badges/roadmap Open Badges roadmap] with new features.

;Learn about the Digital Media and Learning Competition
:Go read about the [http://dmlcompetition.net DML competition: Badges for LifeLong Learning] (administered by HASTAC and funded by MacArthur).

;Read the Open Badges blog
:Read [http://openbadges.tumblr.com/ our blog] for regular posts about badges news and thinking.

;Follow us on Twitter
:Our Twitter handle: [http://twitter.com/#!/openbadges @OpenBadges]
:Hashtags to follow include<nowiki> #OpenBadges and #CSOL2013 (for the Chicago Summer of Learning)</nowiki>.

;IRC (Chat)
:Reach us on IRC at irc.mozilla.org, #badges

;Open Badges Definition of Terms
:Help us to build [https://docs.google.com/document/d/1aTAP04N9dAuSGv71tWOUA1iqYxWWTA4dlQIyP-7WT0E/edit a common lexicon of digital badge terms].

;Presentation resources
:Want to give an Open Badges presentation? To get you started, here's a [[Media:Open_Badges_Presentation_-_General.pdf‎| PDF]]. Please note that all of these documents are [https://creativecommons.org/licenses/by-sa/2.0/ CC by SA].

;Press inquiries
:Please contact [mailto:press@mozilla.com press@mozilla.com].

== Learn more ==

*[https://wiki.mozilla.org/Badges/About '''About Open Badges'''] -- What are badges? How does it all work?
*[https://wiki.mozilla.org/Badges/GetStarted '''How to get started'''] -- Onboarding information for Issuer, Displayer and Earner
*[http://delicious.com/mozilladrumbeat/press+badges '''Press coverage'''] -- Up-to-date news coverage on the project
*[https://wiki.mozilla.org/File:OpenBadges-Working-Paper_012312.pdf '''White Paper'''] -- An in-depth look at how badges can reinvent 21st century learning. 
*[http://openmatt.wordpress.com/2011/03/17/badges-in-the-real-world/ '''User stories'''] -- Everyday examples of badges in the real world. 
*[https://wiki.mozilla.org/Badges/Technology '''Technology'''] -- Documentation and resources on how the underlying technology works. 
*[https://wiki.mozilla.org/Badges/FAQs '''Frequently Asked Questions'''] (F.A.Q.) -- Got questions? Start here. 
*[https://wiki.mozilla.org/Badges/Pilot_programs '''Pilot badge program'''] -- Mozilla and P2PU's School of Webcraft badge program. 
*[http://openbadges.tumblr.com// '''Open Badges Blog'''] -- Blog posts about Open Badges from a variety of sources 
*[https://wiki.mozilla.org/Badges/Team_and_Tools '''Project team and tools'''] -- Open Badges source code, issue tracker and communications tools. 



== Get involved with Mozilla ==

*[http://join.mozilla.org '''Join Mozilla''']
*[http://www.mozilla.org/about/mission.html '''Mozilla's mission''']
*[http://twitter.com/mozilla '''Follow Mozilla on Twitter''']
*[https://www.facebook.com/mozilladrumbeat '''Like Mozilla on Facebook''']
*[https://donate.mozilla.org/Sign-Up '''Get updates from Mozilla''']

WeeklyUpdates/2013-06-10

2013-06-10T15:41:52Z

Threeqube: /* Speakers */

[[WeeklyUpdates/{{#time:Y-m-d|{{SUBPAGENAME}} -1 week}}|« previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/{{#time:Y-m-d|{{SUBPAGENAME}} +1 week}}|next week »]]

{{conf|8600}}

__TOC__

= All-hands Status Meeting Agenda =

Items in this section will be shared during the live all-hand status meeting.

== Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] ==

Fear56 for doing the agenda and notes of meetings from when I have been away from Mozilla. Satdav
== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===
* 13:00 PST: [https://wiki.mozilla.org/Security/Champions Security Champions] / [https://v.mozilla.com/flex.html?roomdirect.html&key=5XEMsG1ApA4b Vidyo 624] (see curtisk for more info if needed)

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===

The Mobile meeting for sumo has moved to SFO319 its 3pm PST https://etherpad.mozilla.org/mobile-2013-06-12

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===

Today is knowledge base day, we are looking for people to write brand new knowledgebase articles for the following, Firefox OS, mobile and Firefox for desktop

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===

It's ask a question day in sumo

== Product Status Updates (voice updates) ==

=== Firefox Desktop ===
''Speaker Location:''

=== Firefox Mobile ===
''Speaker Location:''

=== Thunderbird ===
''Speaker Location:''

=== Older Branch Work ===
''Speaker Location:''

=== Webmaker ===
''Speaker Location:''

=== Identity ===
''Speaker Location:''

=== Services ===
''Speaker Location:''

=== Firefox OS ===
''Speaker Location:''

=== Grow Mozilla ===
''Speaker Location:''

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table"
|-
! Presenter
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
| Alfredo Coh
| Year Up Intern
| Next Around the Campfire Event
| Mountain View
| No
| None
| https://intranet.mozilla.org/Interns_YearUp
|-
| Sunny Lee
| Open Badges, Product Lead
| Chicago Summer of Learning
| remotely
| No
| None
| http://chicagosummeroflearning.org/
|}

== Introducing New Hires ==
{| class="fullwidth-table"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Terra Jones''
| ''Ronald Piovesan''
| ''Mountain View''
| ''Mountain View''
| ''Business Development''
|-
| ''Angela Fabbro''
| ''Mark Coggins''
| ''Vancouver''
| ''Vancouver''
| ''Evangelism''
|-
| ''Patrick Hundal''
| ''Mark Crandon''
| ''San Francisco''
| ''San Francisco''
| ''Business Development''
|-
|}

== Introducing New Interns ==
{| class="fullwidth-table"
|-
! New Intern
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| Eric Reed
| Dave Herman/Brian Anderson
| MV
| MV
| Research
|-
| Jonathan Wilde
| Mark Finkle/Frank Yan
| MV
| SF
| FFX Eng/Mobile UI
|-
| Shilpan Bhagat
| Mark Finkle/Wes Johnston
| MV
| SF
| Mobile
|-
| Stefan Mirea
| Mike Connor/Greg Szorc
| MV
| SF
| FFX Services Eng
|-
| Alexander Wafula
| David Boswell
| MV
| SF
| People People
|-
| Eric Zounes
| Jake Maul/Dumitru Gherman
| MV
| MV
| Web Ops
|-
|}

== Roundtable ==

= <meta> =

Notes and non-voice status updates that aren't part of the live meeting go here.

== Status Updates By Team (*non-voice* updates) ==

=== Firefox ===

=== Platform ===

=== Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

==== PR ====

==== Events ====

==== Creative Team ====

==== Community Marketing ====

=== Support ===

=== Metrics ===

=== Evangelism ===

=== Labs ===

=== Apps ===

=== Developer Tools ===

=== Add-ons ===

=== Webdev ===

=== L10n ===

=== People Team ===

=== WebFWD ===

== Foundation Updates ==

Badges/chicago/org

2013-06-10T12:58:15Z

Threeqube:

<div style="border: thin dotted #aaa; padding:5px;">
'''Welcome to the Organization page. This is where you'll find a list of resources to help you, as an instructor of an organization, issue badges to learners as part of the Chicago Summer of Learning.'''</div> 

== The Role of the Instructor of an Organization ==
You are in the line of duty, ensuring Chicago youth have engaging and rewarding experiences through participation in your organization's programs. You will be the one providing the activities and learning opportunities, assessing whether a learner has done what it takes to earn badges that are part of your program and issuing them on-site or shortly after.

== Instructions ==

Please follow the instructions provided on this slide deck to get started: https://www.dropbox.com/s/sofra9xk29r4l1t/csol-training-org_v2.5.pdf

== How to use excel to roster and issue badges on the CSOL badge issuing tool ==

Video: http://vimeo.com/68021640#

Excel doc: https://www.dropbox.com/s/agu2ixe33unu3a5/MYCSOLRoster.xlsx

Badges/chicago/org

2013-06-08T19:01:11Z

Threeqube:

Badges/chicago/org

2013-06-08T18:18:52Z

Threeqube: Created page with "<div style="border: thin dotted #aaa; padding:5px;"> '''Welcome to the Organization page. This is where you'll find a list of resources to help you, as an instructor of an org..."

Badges/chicago/mentor

2013-06-08T18:04:39Z

Threeqube:

<div style="border: thin dotted #aaa; padding:5px;">
'''Welcome to the Mentor page. This is where you'll find a list of resources to help you review, evaluate and asses badge applications that come through from learners all over Chicago as part of the Chicago Summer of Learning.'''</div> 

== The Role of the Mentor ==
Mentors have been pre-selected by Digital Youth Network. We are so happy you are here to help Chicago youth explore and engage in learning opportunities all throughout the summer.

== Instructions ==

Please follow the instructions provided on this slide deck to get started: https://www.dropbox.com/s/2bdbgiu8xbumar2/csol-training-assessor_v2.pdf

Badges/chicago/mentor

2013-06-08T18:04:09Z

Threeqube:

<div style="border: thin dotted #aaa; padding:5px;">
'''Welcome to the Mentor page. This is where you'll find a list of resources to help you review, evaluate and asses badge applications that come through from learners all over Chicago as part of the Chicago Summer of Learning.'''</div> 

=== The Role of the Mentor ===
Mentors have been pre-selected by Digital Youth Network. We are so happy you are here to help Chicago youth explore and engage in learning opportunities all throughout the summer.

=== Instructions ===

Please follow the instructions provided on this slide deck to get started: https://www.dropbox.com/s/2bdbgiu8xbumar2/csol-training-assessor_v2.pdf

File:Csol-training-assessor v2.pdf

2013-06-08T17:46:19Z

Threeqube:

Badges/chicago/mentor

2013-06-08T17:06:57Z

Threeqube:

Badges/chicago/mentor

2013-06-07T16:13:30Z

Threeqube:

<div style="border: thin dotted #aaa; padding:5px;">
'''Welcome to the Mentor page. This is where you'll find a list of resources to help you with review, evaluate and asses badge applications that come through from learners all over Chicago as part of the Chicago Summer of Learning.'''</div>

Badges/chicago/mentor

2013-06-07T16:13:12Z

Threeqube: Created page with "<div style="border: thin dotted #aaa; padding:5px;"> '''Welcome to the Mentor page. This is where you'll find a list of resources to help you with review, evaluate and asses b..."

Badges/chicago

2013-06-07T16:08:19Z

Threeqube:

<section begin="summary" />{{RoadmapSummary
|icon=CSOL-Logo.png
|pagelocation=Open Badges
|pagetitle=Chicago Summer of Learning Badges
|owner=City of Chicago, MacArthur, Mozilla, DYN
|updated=June 2013
|description=Youth in Chicago learning all summer and getting recognition for that learning.
}}<section end="summary" />

__NOTOC__

== Chicago Summer of Learning Badges Program ==
Mozilla is advising the city of Chicago and Chicago-based organizations to design and implement badges to capture various forms of learning throughout the summer in order to make their Summer of Learning program awesome.

For the Chicago Summer of Learning, Mozilla is playing the following roles:

* Advising on overall campaign design.
* Supporting the organizations on badge design and implementation.
* Building and hosting the badge-issuing platform.
* Celebrating with the rest of Chicago this summer!

=== What is Chicago Summer of Learning? ===
Mayor Rahm Emanuel has announced an ambitious initiative to ensure that youth across the city of Chicago will have access to high-quality learning opportunities over the summer. Beginning in the summer of 2013, private and public summer programs will provide educational experiences to youth across the city, recognize that learning and skill development through digital badges, and then connect youth to opportunities for jobs, internships and credit in the school year.

=== How will badges in the Summer of Learning work? ===
This summer, private and public organizations will offer learning programs for youth and issue badges to recognize the learning and skill development that occurs. Youth will earn badges as they participate and complete various programs and learning experiences. These organizational badges will accumulate to city-level badges that will unlock access to special projects and events for youth that span organizations and skill areas, providing exciting and inspiring pathways to continued learning and leveling up. Youth will also have an online profile to track their progress and get recommendations for additional learning options and badges to earn.

=== Napkin Sketch ===
[[Image: ChicagoBadgeDeck1.3.001.png|800px]]
[[Image: ChicagoBadgeDeck1.3.002.png|800px]]

== Important Dates ==
==== February 5, 2013 - Kick off meeting ====
Many of the participating orgs gathered on Feb 5th to learn about badges and start planning badges for their summer programs.

Slides downloadable here: http://dl.dropbox.com/u/1605183/chicagobadges_febmtg.pdf
Worksheet: Downloadable here: https://wiki.mozilla.org/images/2/22/CSOLWorksheet.pdf

==== February 18, 2013 – Badge Submissions Due ====
Badge idea submissions due – please submit your ideas for 1-5 badges* for your program through the form here: http://openbadges.org/chicago
Note: If you’d like to have more than 5 badges, let us know at support@openbadges.org and we’ll work with you on the best solution.

Badge submission form: http://openbadges.org/chicago

==== March 7th, 2013 – Program Meeting ====
Chicago Summer of Learning Organizations will partake in a CSOL Badge Make-up Workshop on March 7, 2013 from 9-11 am to plan for the issuing of badges. The workshop will take place at DePaul University - College of Computing and Digital Media on the 9th Floor, room 924.

==== March 14, 2013 – Program Meeting ====
1-5pm CT, Sheraton Towers Hotel, Chicago
Please send 1-2 reps from your organization to this meeting to discuss the badges and opportunities for cross-organization connections and projects.
Stick around after the meeting for the DML Conference Science Fair (6-8pm), where you’ll see examples of badge systems from other organizations like yours around the country!

Slides downloadable here: https://www.dropbox.com/sh/lipl7hkqok9swgx/qMpZjT0q7I

== General Roadmap ==

==== FEBRUARY 2013 ====
* Badges definition and submission

==== MARCH - APRIL 2013 ====
* Badges iteration and finalization, with support of Mozilla

==== MAY 2013 ====
* Testing and Prep

==== JUNE - AUGUST 2013 ====
* Issuing and Awarding in your summer programs

==== SEPTEMBER 2013 ====
* Reflections

== Other Resources ==

* Technical FAQ: https://wiki.mozilla.org/Badges/chicago/techFAQ

Badges/chicago

2013-06-07T16:07:52Z

Threeqube:

<section begin=summary />{{RoadmapSummary
|icon=101badge.png
|pagelocation=Open Badges
|pagetitle=Chicago Summer of Learning Badges
|owner=City of Chicago, MacArthur, Mozilla, DYN
|updated=Mar 2013
|description=Youth in Chicago learning all summer and getting recognition for that learning.
}}<section end=summary />

<section begin="summary" />{{RoadmapSummary
|icon=CSOL-Logo.png
|pagelocation=Open Badges
|pagetitle=Chicago Summer of Learning Badges
|owner=City of Chicago, MacArthur, Mozilla, DYN
|updated=June 2013
|description=Youth in Chicago learning all summer and getting recognition for that learning.
}}<section end="summary" />

__NOTOC__

== Chicago Summer of Learning Badges Program ==
Mozilla is advising the city of Chicago and Chicago-based organizations to design and implement badges to capture various forms of learning throughout the summer in order to make their Summer of Learning program awesome.

For the Chicago Summer of Learning, Mozilla is playing the following roles:

* Advising on overall campaign design.
* Supporting the organizations on badge design and implementation.
* Building and hosting the badge-issuing platform.
* Celebrating with the rest of Chicago this summer!

=== What is Chicago Summer of Learning? ===
Mayor Rahm Emanuel has announced an ambitious initiative to ensure that youth across the city of Chicago will have access to high-quality learning opportunities over the summer. Beginning in the summer of 2013, private and public summer programs will provide educational experiences to youth across the city, recognize that learning and skill development through digital badges, and then connect youth to opportunities for jobs, internships and credit in the school year.

=== How will badges in the Summer of Learning work? ===
This summer, private and public organizations will offer learning programs for youth and issue badges to recognize the learning and skill development that occurs. Youth will earn badges as they participate and complete various programs and learning experiences. These organizational badges will accumulate to city-level badges that will unlock access to special projects and events for youth that span organizations and skill areas, providing exciting and inspiring pathways to continued learning and leveling up. Youth will also have an online profile to track their progress and get recommendations for additional learning options and badges to earn.

=== Napkin Sketch ===
[[Image: ChicagoBadgeDeck1.3.001.png|800px]]
[[Image: ChicagoBadgeDeck1.3.002.png|800px]]

== Important Dates ==
==== February 5, 2013 - Kick off meeting ====
Many of the participating orgs gathered on Feb 5th to learn about badges and start planning badges for their summer programs.

Slides downloadable here: http://dl.dropbox.com/u/1605183/chicagobadges_febmtg.pdf
Worksheet: Downloadable here: https://wiki.mozilla.org/images/2/22/CSOLWorksheet.pdf

==== February 18, 2013 – Badge Submissions Due ====
Badge idea submissions due – please submit your ideas for 1-5 badges* for your program through the form here: http://openbadges.org/chicago
Note: If you’d like to have more than 5 badges, let us know at support@openbadges.org and we’ll work with you on the best solution.

Badge submission form: http://openbadges.org/chicago

==== March 7th, 2013 – Program Meeting ====
Chicago Summer of Learning Organizations will partake in a CSOL Badge Make-up Workshop on March 7, 2013 from 9-11 am to plan for the issuing of badges. The workshop will take place at DePaul University - College of Computing and Digital Media on the 9th Floor, room 924.

==== March 14, 2013 – Program Meeting ====
1-5pm CT, Sheraton Towers Hotel, Chicago
Please send 1-2 reps from your organization to this meeting to discuss the badges and opportunities for cross-organization connections and projects.
Stick around after the meeting for the DML Conference Science Fair (6-8pm), where you’ll see examples of badge systems from other organizations like yours around the country!

Slides downloadable here: https://www.dropbox.com/sh/lipl7hkqok9swgx/qMpZjT0q7I

== General Roadmap ==

==== FEBRUARY 2013 ====
* Badges definition and submission

==== MARCH - APRIL 2013 ====
* Badges iteration and finalization, with support of Mozilla

==== MAY 2013 ====
* Testing and Prep

==== JUNE - AUGUST 2013 ====
* Issuing and Awarding in your summer programs

==== SEPTEMBER 2013 ====
* Reflections

== Other Resources ==

* Technical FAQ: https://wiki.mozilla.org/Badges/chicago/techFAQ

File:CSOL-Logo.png

2013-06-07T16:05:43Z

Threeqube:

Badges/Badge Specification

2013-04-04T04:27:15Z

Threeqube:

==Current Specification==

The latest badge specification can be found here: https://github.com/mozilla/openbadges/wiki/Assertions

Below you can see the evolution of our thinking.

== Goals ==
'''Goal 1:''' Gather possible fields a badge could have.

'''Goal 2:''' Determine the minimum set of required fields that a badge should have.

== Required Fields ==

;Name of badge
:This is simply a UTF-8 String.

;Who earned the badge
:Not all children and youth are able to something like OpenID accounts, particularly with COPAA requirements. Perhaps site-user-name and/or email address could be used for some badge providers?

=== Optional Fields ===

;What does the badge signify
:Is this different than '''why was it awarded'''? There should be minimally descriptive metadata on what the badge represents and optionally any detailed requirements for receiving the badge and who can award (if there are any restrictions) the specific badge. Perhaps permitted issuer(s) or open should be a separate field?

;When was the badge acquired
:TIMESTAMP?

;Where was it given
:URI?

;What does it look like?
:Dimensions? Description? Caption? Accessibility description?

;Multimedia properties?
:E.g., Image-type, Video, Interactive SVG, JavaScript, Is it a video, embedded JavaScript, SVG, Canvas, etc. -- HTML5 Canvas since declining support for SVG (thoughts?)

;Insignia or device
:Sometimes badges can be modified with additional insignia over time. For example, this could be adding stripes to indicate a "level" (or counter) at which you have earned a given rank or badge, to indicate that you've earned a badge more than once, etc. Accessibility description concerns?

;Associated Value
:This could be a numeric value of what this is ''worth'', e.g., points, karma, etc. This value may be used to distinguish the relative "worth" of badges or the aggregate worth of your badges may unlock certain activities or be used as a way to compare members of a group.

;Version
:Some badges are part of version control systems and come with a release number.

;External URLs
:Sometimes a badge may link to URLs to show exactly where or for what you earned a badge.

;Dependencies
:What badges are first required before you can earn this badge?

;Groups
:Is this badge part of a larger group of badges?

;Unlocked properties
:Often when you earn a badge it unlocks the ability to pursue other badges or partake in other activities in an organization or on a given system.

== Notes, Concerns, Thoughts ==

== References ==

=== Related Specifications ===

*[http://www.w3.org/TR/rdfa-syntax/ http://www.w3.org/TR/rdfa-syntax/]
*[http://microformats.org/ http://microformats.org/]
*[http://www.w3.org/WAI/ W3C Web Accessibility Initiative]

=== Other References ===

*[http://joshuagay.org/blog/?p=32 ''Badges, badges, everywhere!'', joshuagay.org/blog]
*[http://en.wikipedia.org/wiki/Awards_and_decorations_of_the_United_States_military Awards_and_decorations_of_the_United_States_military]
**[http://en.wikipedia.org/wiki/Category:Devices_and_accouterments_of_United_States_military_awards Devices_and_accouterments_of_United_States_military_awards]
**[http://en.wikipedia.org/wiki/United_States_military_award_devices United_States_military_award_devices]

== Acknowledgments ==

Community:SummerOfCode13:Brainstorming

2013-04-01T17:15:44Z

Threeqube: /* Mozilla Open Badges */

Mozilla community members - submit proposals here for 2013 Google Summer of Code projects with Mozilla. (If this page looks empty, it's because accepted ideas have already been transferred to the [[Community:SummerOfCode13|official list]].) The absolute last deadline for submitting ideas in time to help us get accepted by Google is March 29th.

Are you a students looking to apply to SoC with Mozilla? Your first stop should be the [[Community:SummerOfCode13|official list of ideas]]. This page is full of weird and whacky ideas, some of which are still on here for a reason - it could be that they are not properly defined, the wrong size, or don't have a mentor. That makes them less likely to get accepted. You can, of course, also submit your own ideas - you don't have to put an idea on this page and get it 'made official' in order to send in a proposal for it.

==How To Write A Good Project Proposal==

Before adding an proposal to this list, please consider the following:

* '''Be specific'''. It's hard to understand the impact of, or the size of, vague proposals.
* '''Consider size'''. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.
* '''Do your research'''. Support the idea with well-researched links.
* '''Don't morph other people's ideas'''. If you have a related idea, place it next to the existing one, or add a comment.
* '''Insert only your own name into the Mentor column''', and then only if you are willing to take on the responsibility. If you think the SoC admins won't know who you are, leave contact details.
* '''Check back regularly'''. The administrators may have questions about your idea that you will need to answer.
* '''Know when to give up'''. If you've added the same idea for the last three years and it hasn't made it to the official page, perhaps you can predict what will happen this time.

==Suggestion List==

[[SummerOfCode|Here are the ideas lists from previous years]].

Proposals can be in almost any part of the Mozilla project - don't be fooled by the "Code" in "Summer of Code". If there is no category below for your part of Mozilla, add one!

== Mozilla Platform (Gecko) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Firefox for Android ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox OS / Boot2Gecko ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Mozilla Open Badges ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Open Badge Infrastructure
| OBI is Mozilla's response to the growing badges in learning movement. The OBI allows learners to collect badges from a variety of badge issuers, and display them wherever they'd like. We need help building additional display widgets, developing an endorsement specification that allows for organizations and individuals to endorse a badge class or badge instance and further build out the functionalities of the badge management tool, ie the Backpack in addition to Backpack federation. There's lots of work to be done, so we're pretty open to ideas you have. Contact Chris for more information.
| The OBI is written in Javascript, and runs on Node.js, so Javascript knowledge is a big plus.
| Chris McAvoy
| Chris McAvoy
|
|}

== Calendar ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Thunderbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Utilize capability attributes of nsIMsgIncomingServer and nsIMsgFolder
| Remove hard-coded checks through-out the comm-central codebase where a simple check of the server (nsIMsgIncomingServer) capability can be used.

Example:
: if (server.type == "nntp" || server.type == "rss") { enableSubscribe(); }
Change to:
: if (server.canSubscribe) { enableSubscribe(); }

For this to work, the student has to see if the server types return the proper value for the capability (some may be unimplemented yet) and may have to add some new attributes where needed.
Hard-coded checks are bad because they do not pick up new server types automatically even if they would have the capability. Extension authors have a hard time plugging into these hard-coded spots. Often they have to duplicate the whole function from TB to add their new server type to it.
The same can be done with folders, i.e. nsIMsgFolder.

Starting point: [https://bugzilla.mozilla.org/show_bug.cgi?id=63369 bug 63369].
| C++, Javascript
| aceman
|
|-
| Rewrite our database code to be asynchronous when database if huge.
| This would help us in improving the start-up time of Thunderbird. Main idea is splitting the database in chunks and then loading it, if the database is quite big. I guess related bug would be: {{bug|588952}}.
Difficulty: Medium to hard depending on how far we go.
| C++ mainly
| atuljangra
| ?anyone?
| jcranmer - Mork database async opening needs to be completed, and we would probably also need nsIMsgDBHdr instances to become "dead" (cached copies of the database or newer changes).
|-
| Open ended project to solve several critical bugs
| My idea for this project is that we can have a student solve various bugs that are arising in Thunderbird which are makin users unhappy. For example Bug 516222, Bug 803921, Bug 618553 and many others. We can utilize this to solve such critical bugs. This would be some kind of open ended bug. Main area of concern would be Mailnews core.
| C/C++ mostly, Js for testing
| atuljangra
| ?anyone from Mailnews core?
| atuljangra- Do we need to prioritise the ideas?
|-
| Make OS X users happier
| Something from [https://bugzilla.mozilla.org/show_bug.cgi?id=728438 Bug 728438] to integrate Thunderbird better into OS X would be good. This includes interesting Bugs like the Quickloock integration [https://bugzilla.mozilla.org/show_bug.cgi?id=457546 Bug 457546], which was already a student project, but needs to be finished, integrated into Thunderbird and some tests. The same is true for [https://bugzilla.mozilla.org/show_bug.cgi?id=465257 Bug 465257] to support multi-touch gestures. It also includes Bugs to improve the addressbook behaviour for OS X users (write support, [https://bugzilla.mozilla.org/show_bug.cgi?id=391057 Bug 391057] and picture support, [https://bugzilla.mozilla.org/show_bug.cgi?id=496789 Bug 496789]).
| You need to know about C++, JS and OS X APIs.
| ?
| ?
|
|-
|}

== SeaMonkey ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

==NSS (Network Security Services)==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Bugzilla ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Firefox Support (SUMO) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== QA ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Automation & Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Documentation ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Mozilla Developer Network ==

{| class="standard-table" border="1" style="border-collapse: collapse"
{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Localization Dashboard
| Build a Localization Dashboard for the Mozilla Developer Network (MDN) to help contribuors view localization progress and find articles that need to be localized. The dashboard should be somewhat similar to the existing [https://developer.mozilla.org/dashboards/revisions Revision Dashboard]. Over the course of the summer, the student should build a [https://en.wikipedia.org/wiki/Minimum_viable_product minimum viable product] and work with the MDN team to iterate on it, making as many improvements as time allows.
| HTML, CSS, JavaScript, Python
| John Karahalis (openjck)
| John Karahalis (openjck)
|
|}

== Mozilla IT and Infrastructure ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Persona / BrowserID ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Sync / Services ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Developer Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Add-on SDK ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Foundation ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Release Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Instantbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Emscripten ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Rust ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Security Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Security Report
| It can be tricky for a developer to cover all their bases when it comes to security. Moreover, information about the security of a website can be difficult for advanced users to find without searching through multiple data sources in the browser (error console, cookie manager, certificate manager, etc.) This project is to build a firefox addon that reports all of this data in one place. Developers can then view the report for their websites or pre-production pages and quickly identify their security issues. Advanced users can quickly learn about a websites security before deciding whether or not they want to enter sensitive information on the page.

Here are some examples of what the security report could include:
* information about network requests that have been blocked by the browser for security reasons (e.g. mixed content, CSP, CORS)
* information about the cookies on the site (are they marked secure, do they have the httponly attribute?)
* security related headers (does the site set STS, CSP, or X-Frame-Options headers?)
* SSL information (is the websites ssl certficate about to expire?)

| JavaScript, Add-on SDK, some platform knowledge.
| Mark Goodwin (mgoodwin), Tanvi Vyas (tanvi)
| Mark Goodwin (mgoodwin), Tanvi Vyas (tanvi)
|-
|}

== Open(Art) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

Community:SummerOfCode13:Brainstorming

2013-04-01T17:13:11Z

Threeqube: /* Mozilla Open Badges */

Mozilla community members - submit proposals here for 2013 Google Summer of Code projects with Mozilla. (If this page looks empty, it's because accepted ideas have already been transferred to the [[Community:SummerOfCode13|official list]].) The absolute last deadline for submitting ideas in time to help us get accepted by Google is March 29th.

Are you a students looking to apply to SoC with Mozilla? Your first stop should be the [[Community:SummerOfCode13|official list of ideas]]. This page is full of weird and whacky ideas, some of which are still on here for a reason - it could be that they are not properly defined, the wrong size, or don't have a mentor. That makes them less likely to get accepted. You can, of course, also submit your own ideas - you don't have to put an idea on this page and get it 'made official' in order to send in a proposal for it.

==How To Write A Good Project Proposal==

Before adding an proposal to this list, please consider the following:

* '''Be specific'''. It's hard to understand the impact of, or the size of, vague proposals.
* '''Consider size'''. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.
* '''Do your research'''. Support the idea with well-researched links.
* '''Don't morph other people's ideas'''. If you have a related idea, place it next to the existing one, or add a comment.
* '''Insert only your own name into the Mentor column''', and then only if you are willing to take on the responsibility. If you think the SoC admins won't know who you are, leave contact details.
* '''Check back regularly'''. The administrators may have questions about your idea that you will need to answer.
* '''Know when to give up'''. If you've added the same idea for the last three years and it hasn't made it to the official page, perhaps you can predict what will happen this time.

==Suggestion List==

[[SummerOfCode|Here are the ideas lists from previous years]].

Proposals can be in almost any part of the Mozilla project - don't be fooled by the "Code" in "Summer of Code". If there is no category below for your part of Mozilla, add one!

== Mozilla Platform (Gecko) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Firefox for Android ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox OS / Boot2Gecko ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Mozilla Open Badges ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Open Badge Infrastructure
| OBI is Mozilla's response to the growing badges in learning movement. The OBI allows learners to collect badges from a variety of badge issuers, and display them wherever they'd like. We need help building additional display widgets, developing an endorsement specification that allows for organizations and individuals to endorse a badge class or badge instance and further build out the functionalities of the badge management tool, ie the Backpack. There's lots of work to be done, so we're pretty open to ideas you have. Contact Chris for more information.
| The OBI is written in Javascript, and runs on Node.js, so Javascript knowledge is a big plus.
| Chris McAvoy
| Chris McAvoy
|
|}

== Calendar ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Thunderbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Utilize capability attributes of nsIMsgIncomingServer and nsIMsgFolder
| Remove hard-coded checks through-out the comm-central codebase where a simple check of the server (nsIMsgIncomingServer) capability can be used.

Example:
: if (server.type == "nntp" || server.type == "rss") { enableSubscribe(); }
Change to:
: if (server.canSubscribe) { enableSubscribe(); }

For this to work, the student has to see if the server types return the proper value for the capability (some may be unimplemented yet) and may have to add some new attributes where needed.
Hard-coded checks are bad because they do not pick up new server types automatically even if they would have the capability. Extension authors have a hard time plugging into these hard-coded spots. Often they have to duplicate the whole function from TB to add their new server type to it.
The same can be done with folders, i.e. nsIMsgFolder.

Starting point: [https://bugzilla.mozilla.org/show_bug.cgi?id=63369 bug 63369].
| C++, Javascript
| aceman
|
|-
| Rewrite our database code to be asynchronous when database if huge.
| This would help us in improving the start-up time of Thunderbird. Main idea is splitting the database in chunks and then loading it, if the database is quite big. I guess related bug would be: {{bug|588952}}.
Difficulty: Medium to hard depending on how far we go.
| C++ mainly
| atuljangra
| ?anyone?
| jcranmer - Mork database async opening needs to be completed, and we would probably also need nsIMsgDBHdr instances to become "dead" (cached copies of the database or newer changes).
|-
| Open ended project to solve several critical bugs
| My idea for this project is that we can have a student solve various bugs that are arising in Thunderbird which are makin users unhappy. For example Bug 516222, Bug 803921, Bug 618553 and many others. We can utilize this to solve such critical bugs. This would be some kind of open ended bug. Main area of concern would be Mailnews core.
| C/C++ mostly, Js for testing
| atuljangra
| ?anyone from Mailnews core?
| atuljangra- Do we need to prioritise the ideas?
|-
| Make OS X users happier
| Something from [https://bugzilla.mozilla.org/show_bug.cgi?id=728438 Bug 728438] to integrate Thunderbird better into OS X would be good. This includes interesting Bugs like the Quickloock integration [https://bugzilla.mozilla.org/show_bug.cgi?id=457546 Bug 457546], which was already a student project, but needs to be finished, integrated into Thunderbird and some tests. The same is true for [https://bugzilla.mozilla.org/show_bug.cgi?id=465257 Bug 465257] to support multi-touch gestures. It also includes Bugs to improve the addressbook behaviour for OS X users (write support, [https://bugzilla.mozilla.org/show_bug.cgi?id=391057 Bug 391057] and picture support, [https://bugzilla.mozilla.org/show_bug.cgi?id=496789 Bug 496789]).
| You need to know about C++, JS and OS X APIs.
| ?
| ?
|
|-
|}

== SeaMonkey ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

==NSS (Network Security Services)==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Bugzilla ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Firefox Support (SUMO) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== QA ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Automation & Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Documentation ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Mozilla Developer Network ==

{| class="standard-table" border="1" style="border-collapse: collapse"
{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Localization Dashboard
| Build a Localization Dashboard for the Mozilla Developer Network (MDN) to help contribuors view localization progress and find articles that need to be localized. The dashboard should be somewhat similar to the existing [https://developer.mozilla.org/dashboards/revisions Revision Dashboard]. Over the course of the summer, the student should build a [https://en.wikipedia.org/wiki/Minimum_viable_product minimum viable product] and work with the MDN team to iterate on it, making as many improvements as time allows.
| HTML, CSS, JavaScript, Python
| John Karahalis (openjck)
| John Karahalis (openjck)
|
|}

== Mozilla IT and Infrastructure ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Persona / BrowserID ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Sync / Services ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Developer Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Add-on SDK ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Foundation ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Release Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Instantbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Emscripten ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Rust ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Security Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Security Report
| It can be tricky for a developer to cover all their bases when it comes to security. Moreover, information about the security of a website can be difficult for advanced users to find without searching through multiple data sources in the browser (error console, cookie manager, certificate manager, etc.) This project is to build a firefox addon that reports all of this data in one place. Developers can then view the report for their websites or pre-production pages and quickly identify their security issues. Advanced users can quickly learn about a websites security before deciding whether or not they want to enter sensitive information on the page.

Here are some examples of what the security report could include:
* information about network requests that have been blocked by the browser for security reasons (e.g. mixed content, CSP, CORS)
* information about the cookies on the site (are they marked secure, do they have the httponly attribute?)
* security related headers (does the site set STS, CSP, or X-Frame-Options headers?)
* SSL information (is the websites ssl certficate about to expire?)

| JavaScript, Add-on SDK, some platform knowledge.
| Mark Goodwin (mgoodwin), Tanvi Vyas (tanvi)
| Mark Goodwin (mgoodwin), Tanvi Vyas (tanvi)
|-
|}

== Open(Art) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

Community:SummerOfCode13:Brainstorming

2013-04-01T17:09:33Z

Threeqube: /* Mozilla Open Badges */

Mozilla community members - submit proposals here for 2013 Google Summer of Code projects with Mozilla. (If this page looks empty, it's because accepted ideas have already been transferred to the [[Community:SummerOfCode13|official list]].) The absolute last deadline for submitting ideas in time to help us get accepted by Google is March 29th.

Are you a students looking to apply to SoC with Mozilla? Your first stop should be the [[Community:SummerOfCode13|official list of ideas]]. This page is full of weird and whacky ideas, some of which are still on here for a reason - it could be that they are not properly defined, the wrong size, or don't have a mentor. That makes them less likely to get accepted. You can, of course, also submit your own ideas - you don't have to put an idea on this page and get it 'made official' in order to send in a proposal for it.

==How To Write A Good Project Proposal==

Before adding an proposal to this list, please consider the following:

* '''Be specific'''. It's hard to understand the impact of, or the size of, vague proposals.
* '''Consider size'''. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.
* '''Do your research'''. Support the idea with well-researched links.
* '''Don't morph other people's ideas'''. If you have a related idea, place it next to the existing one, or add a comment.
* '''Insert only your own name into the Mentor column''', and then only if you are willing to take on the responsibility. If you think the SoC admins won't know who you are, leave contact details.
* '''Check back regularly'''. The administrators may have questions about your idea that you will need to answer.
* '''Know when to give up'''. If you've added the same idea for the last three years and it hasn't made it to the official page, perhaps you can predict what will happen this time.

==Suggestion List==

[[SummerOfCode|Here are the ideas lists from previous years]].

Proposals can be in almost any part of the Mozilla project - don't be fooled by the "Code" in "Summer of Code". If there is no category below for your part of Mozilla, add one!

== Mozilla Platform (Gecko) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Firefox for Android ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox OS / Boot2Gecko ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Mozilla Open Badges ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title: Open Badges
! Details: OBI is Mozilla's response to the growing badges in learning movement. The OBI allows learners to collect badges from a variety of badge issuers, and display them wherever they'd like. We need help building additional display widgets, developing an endorsement specification that allows for organizations and individuals to endorse a badge class or badge instance and further build out the functionalities of the badge management tool, ie the Backpack. There's lots of work to be done, so we're pretty open to ideas you have. Contact Chris for more information.
! Skills Needed: The OBI is written in Javascript, and runs on Node.js, so Javascript knowledge is a big plus.
! Reporter
! Mentor(s)
! Comments
|-
|}

== Calendar ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Thunderbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Utilize capability attributes of nsIMsgIncomingServer and nsIMsgFolder
| Remove hard-coded checks through-out the comm-central codebase where a simple check of the server (nsIMsgIncomingServer) capability can be used.

Example:
: if (server.type == "nntp" || server.type == "rss") { enableSubscribe(); }
Change to:
: if (server.canSubscribe) { enableSubscribe(); }

For this to work, the student has to see if the server types return the proper value for the capability (some may be unimplemented yet) and may have to add some new attributes where needed.
Hard-coded checks are bad because they do not pick up new server types automatically even if they would have the capability. Extension authors have a hard time plugging into these hard-coded spots. Often they have to duplicate the whole function from TB to add their new server type to it.
The same can be done with folders, i.e. nsIMsgFolder.

Starting point: [https://bugzilla.mozilla.org/show_bug.cgi?id=63369 bug 63369].
| C++, Javascript
| aceman
|
|-
| Rewrite our database code to be asynchronous when database if huge.
| This would help us in improving the start-up time of Thunderbird. Main idea is splitting the database in chunks and then loading it, if the database is quite big. I guess related bug would be: {{bug|588952}}.
Difficulty: Medium to hard depending on how far we go.
| C++ mainly
| atuljangra
| ?anyone?
| jcranmer - Mork database async opening needs to be completed, and we would probably also need nsIMsgDBHdr instances to become "dead" (cached copies of the database or newer changes).
|-
| Open ended project to solve several critical bugs
| My idea for this project is that we can have a student solve various bugs that are arising in Thunderbird which are makin users unhappy. For example Bug 516222, Bug 803921, Bug 618553 and many others. We can utilize this to solve such critical bugs. This would be some kind of open ended bug. Main area of concern would be Mailnews core.
| C/C++ mostly, Js for testing
| atuljangra
| ?anyone from Mailnews core?
| atuljangra- Do we need to prioritise the ideas?
|-
| Make OS X users happier
| Something from [https://bugzilla.mozilla.org/show_bug.cgi?id=728438 Bug 728438] to integrate Thunderbird better into OS X would be good. This includes interesting Bugs like the Quickloock integration [https://bugzilla.mozilla.org/show_bug.cgi?id=457546 Bug 457546], which was already a student project, but needs to be finished, integrated into Thunderbird and some tests. The same is true for [https://bugzilla.mozilla.org/show_bug.cgi?id=465257 Bug 465257] to support multi-touch gestures. It also includes Bugs to improve the addressbook behaviour for OS X users (write support, [https://bugzilla.mozilla.org/show_bug.cgi?id=391057 Bug 391057] and picture support, [https://bugzilla.mozilla.org/show_bug.cgi?id=496789 Bug 496789]).
| You need to know about C++, JS and OS X APIs.
| ?
| ?
|
|-
|}

== SeaMonkey ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

==NSS (Network Security Services)==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Bugzilla ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Firefox Support (SUMO) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== QA ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Automation & Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Documentation ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Mozilla Developer Network ==

{| class="standard-table" border="1" style="border-collapse: collapse"
{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Localization Dashboard
| Build a Localization Dashboard for the Mozilla Developer Network (MDN) to help contribuors view localization progress and find articles that need to be localized. The dashboard should be somewhat similar to the existing [https://developer.mozilla.org/dashboards/revisions Revision Dashboard]. Over the course of the summer, the student should build a [https://en.wikipedia.org/wiki/Minimum_viable_product minimum viable product] and work with the MDN team to iterate on it, making as many improvements as time allows.
| HTML, CSS, JavaScript, Python
| John Karahalis (openjck)
| John Karahalis (openjck)
|
|}

== Mozilla IT and Infrastructure ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Persona / BrowserID ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Sync / Services ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Developer Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Add-on SDK ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Foundation ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Release Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Instantbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Emscripten ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Rust ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Security Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Security Report
| It can be tricky for a developer to cover all their bases when it comes to security. Moreover, information about the security of a website can be difficult for advanced users to find without searching through multiple data sources in the browser (error console, cookie manager, certificate manager, etc.) This project is to build a firefox addon that reports all of this data in one place. Developers can then view the report for their websites or pre-production pages and quickly identify their security issues. Advanced users can quickly learn about a websites security before deciding whether or not they want to enter sensitive information on the page.

Here are some examples of what the security report could include:
* information about network requests that have been blocked by the browser for security reasons (e.g. mixed content, CSP, CORS)
* information about the cookies on the site (are they marked secure, do they have the httponly attribute?)
* security related headers (does the site set STS, CSP, or X-Frame-Options headers?)
* SSL information (is the websites ssl certficate about to expire?)

| JavaScript, Add-on SDK, some platform knowledge.
| Mark Goodwin (mgoodwin), Tanvi Vyas (tanvi)
| Mark Goodwin (mgoodwin), Tanvi Vyas (tanvi)
|-
|}

== Open(Art) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

Badges

2013-03-07T13:59:12Z

Threeqube: /* What is Mozilla's Open Badges project? */

<section begin=summary />{{RoadmapSummary
|icon=101badge.png
|pagelocation=Open Badges
|pagetitle=Mozilla Open Badges
|owner=Erin Knight, Carla Casilli, Sunny Lee, Emily Goligoski, Chris McAvoy, Brian Brennan, Mike Larsson, Doug Belshaw
|updated=January 2013
|description=Mozilla's Open Badges is working to make it easy for anyone to issue, earn and display badges across the web—through a shared infrastructure that's free and open to all.
}}<section end=summary />

__NOTOC__

== What is Mozilla's Open Badges project? ==

Learning today happens everywhere, not just in the classroom. But it's often difficult to get recognition for skills and achievements that happen outside of school. '''Mozilla's Open Badges project''' is working to solve that problem, making it easy for anyone to issue, earn and display badges across the web -- through a shared infrastructure that's free and open to all. '''The result:''' helping people of all ages learn and display 21st century skills, unlock career and educational opportunities, and find new life pathways.

[[Image:Badge-diagram-2.2.jpg]]

Localized Spanish badge diagram: http://www.flickr.com/photos/alvarmaciel/8536933804/in/photostream/lightbox/

== Get involved with Open Badges ==

;Check out our site
:http://openbadges.org

;Join our weekly community calls
:Our [https://openbadges.etherpad.mozilla.org/openbadges-community Open Badges community calls] are held weekly on Wednesdays at 9am PT (-8 UTC) and are open to the public. During these hour long calls we share our progress and encourage you to share your Open Badges work, questions, and comments. They're fun and we encourage you to join them.

;Subscribe to our mailing list
:Subscribe to our [https://groups.google.com/d/forum/openbadges Open Badges google group]. This is where you'll find active discussion of technical questions, philosophical conversation about badges, and badge-interested folks.

;Read our Whitepaper
:We wrote a whitepaper on some of the initial thinking and framing about badges. [https://wiki.mozilla.org/File:OpenBadges-Working-Paper_012312.pdf Check it out!]

;Check out our code
:Visit our [https://github.com/mozilla/openbadges Open Badges github repository] where you can see our [https://github.com/mozilla/openbadges/wiki technical wiki], view our outstanding and closed issues, and submit bugs. You can also find [https://github.com/mozilla/openbadges/wiki/Open-Badges-related-widgets Open Badges related widgets].

;View our roadmap
:We're continually updating the [https://wiki.mozilla.org/Badges/roadmap Open Badges roadmap] with new features.

;Learn about the Digital Media and Learning Competition
:Go read about the [http://dmlcompetition.net DML competition: Badges for LifeLong Learning] (administered by HASTAC and funded by MacArthur).

;Read the Open Badges blog
:Read [http://openbadges.tumblr.com/ our blog] for regular posts about badges news and thinking.

;Follow us on Twitter
:Our Twitter handle: [http://twitter.com/#!/openbadges @OpenBadges]
:Hashtags to follow include<nowiki> #openbadges and #dmlbadges </nowiki>

;IRC (Chat)
:Reach us on IRC at irc.mozilla.org, #badges

;Open Badges Definition of Terms
:Help us to build [https://docs.google.com/document/d/1aTAP04N9dAuSGv71tWOUA1iqYxWWTA4dlQIyP-7WT0E/edit a common lexicon of digital badge terms]

;Presentation resources
:Want to give an Open Badges presentation? To get you started, here's a [[Media:Mozilla-OpenBadges-presentation.pdf‎ | PDF]]. (Still working on uploading the PPT deck and a Keynote deck.) Please note that all of these documents are [https://creativecommons.org/licenses/by-sa/2.0/ CC by SA].

;Press & Research
:Help us to track press articles, blog posts, research, white papers, etc. on this [https://docs.google.com/document/d/1DgR0-cUsDmJ0E7yRSMrIZVQJ5JLW4d8BoZ04HQwM8Ro/edit Open Badges Communications] google doc

;Press inquiries
:Contact [mailto:press@mozilla.com press@mozilla.com]

== Learn more ==

*[https://wiki.mozilla.org/Badges/About '''About Open Badges'''] -- What are badges? How does it all work?
*[https://wiki.mozilla.org/Badges/GetStarted '''How to get started'''] -- Onboarding information for Issuer, Displayer and Earner
*[http://delicious.com/mozilladrumbeat/press+badges '''Press coverage'''] -- Up-to-date news coverage on the project
*[https://wiki.mozilla.org/File:OpenBadges-Working-Paper_012312.pdf '''White Paper'''] -- An in-depth look at how badges can reinvent 21st century learning. 
*[http://openmatt.wordpress.com/2011/03/17/badges-in-the-real-world/ '''User stories'''] -- Everyday examples of badges in the real world. 
*[https://wiki.mozilla.org/Badges/Technology '''Technology'''] -- Documentation and resources on how the underlying technology works. 
*[https://wiki.mozilla.org/Badges/FAQs '''Frequently Asked Questions'''] (F.A.Q.) -- Got questions? Start here. 
*[https://wiki.mozilla.org/Badges/Pilot_programs '''Pilot badge program'''] -- Mozilla and P2PU's School of Webcraft badge program. 
*[http://openbadges.tumblr.com// '''Open Badges Blog'''] -- Blog posts about Open Badges from a variety of sources 
*[https://wiki.mozilla.org/Badges/Team_and_Tools '''Project team and tools'''] -- Open Badges source code, issue tracker and communications tools. 



== Get involved with Mozilla ==

*[http://join.mozilla.org '''Join Mozilla''']
*[http://www.mozilla.org/about/mission.html '''Mozilla's mission''']
*[http://twitter.com/mozilla '''Follow Mozilla on Twitter''']
*[https://www.facebook.com/mozilladrumbeat '''Like Mozilla on Facebook''']
*[https://donate.mozilla.org/Sign-Up '''Get updates from Mozilla''']

Badges/Issuers

2013-02-26T19:17:33Z

Threeqube:

This page includes information about some organizations that are currently issuing badges. Badge issuing organizations are groups or individuals who have content to share and/or contributions and skills that they want to recognize. They determine the criteria and system design behind their badges, and they align those badges with the Open Badges Infrastructure. This benefits earners whose portable badges can then tell robust stories about what they're capable of.

Organizations that issue badges come from various sectors and sizes. They include formal and informal educational institutions; multinational corporations; industry associations; non-profits; and groups interested in professional development. They share a common interest in making their badges shareable and interoperable in alignment with the OBI.

This list includes badge issuers who have chosen to share their badges here. If you're interested in having your organization and badges listed, please log into the wiki and click "Edit" (top middle of this page). You can then list your organization's name and any links to the badges that you've made available.

 

ORGANIZATIONS CURRENTLY ISSUING BADGES:

- Cybersociety Observatory (http://cibersociedad.net/)

- OpenBadgesUA (http://openbadges.es/en/index)

- UniMOOC aemprende (http://unimooc.com/)

- PASA - The Hub (http://hubprov.com/)

- Codery (http://gocodery.com/)

- workforce.io (http://workforce.io/)

- DigitalMe (http://www.digitalme.co.uk)

- Sweet Water Foundation (http://sweetwaterfoundation.com/)

- David Wiley, Introduction to Open Education course (https://learn.canvas.net/courses/4)

- IPT EdTec - Using Technology In Teaching (http://iptedtec.org)

- coderbits - Knowledge portfolio for developers and designers (https://coderbits.com/)

- Open University / Cloudworks - Repository of educational ideas and experiences (http://cloudworks.ac.uk/badge/badge_list)

- EDUCAUSE (http://www.educause.edu/eli/events/eli-annual-meeting/innovation-and-networking/badging)

- Training Magazine (https://credly.com/u/trainingmag)

- Smithsonian Center for Education and Museum Studies (http://smithsonianeducationconferences.org/)

- HIVE NYC (https://credly.com/u/hivenyc)

- Museum Computer Network - MCN Pro Workshop Series (http://mcnpro.org/)

- Museums & Mobile (http://www.museums-mobile.org/)

- Smithsonian American Art Museum (https://credly.com/u/americanart)

- NYC Department of Education (http://www.learningtimes.com/news/nycdoe-digit/)

- YMCA of Greater New York (http://www.ymcanyc.org/association/pages/y-mvp)

- Dallas Museum of Art (http://dma.org/Visit/Friends)

- Peer to Peer University (https://p2pu.org)

- NOAA Planet Stewards (http://noaaplanetstewards.org)

- 3D GameLab (http://3dgamelab.com)

- Mozilla Webmaker (https://badges.webmaker.org/)

- ADD YOUR ORGANIZATION HERE

 
ORGANIZATIONS CURRENTLY DESIGNING BADGES:

- Cybersociety Observatory (http://cibersociedad.net/)

- OpenBadgesUA (http://openbadges.es/en/index)

- UniMOOC aemprende (http://unimooc.com/)

- workforce.io (http://workforce.io/)

- OhioCreditFlexibility.org: For OH K12 students

- Sweet Water Foundation (http://sweetwaterfoundation.com/)

- Tamritz (http://www.tamritz.org)

- SUNY Empire State College (http://esc.edu/)

- IPT EdTec - Using Technology In Teaching (http://iptedtec.org)

- coderbits - Knowledge portfolio for developers and designers (https://coderbits.com/)

- Center for Educational Technologies at Wheeling Jesuit University - Home of the NASA-sponsored Classroom of the Future (http://www.cet.edu)

- DigitalMe (http://www.digitalme.co.uk)

- Makewaves (https://www.makewav.es/)

- GoGo Labs (http://gogolabs.net)

- ADD YOUR ORGANIZATION HERE

 
ORGANIZATIONS EXPLORING BADGES FOR THEIR COMMUNITIES:

- John Henry Newman Catholic College

- Cybersociety Observatory (http://cibersociedad.net/)

- Appleby College (http://www.appleby.on.ca)

- workforce.io (http://workforce.io/)

- Sweet Water Foundation (http://sweetwaterfoundation.com/)

- Tamritz (http://www.tamritz.org)

- Makewaves (https://www.makewav.es/)

- WICHE Cooperative for Educational Technologies (http://wcet.wiche.edu)

- NOAA Planet Stewards (http://noaaplanetstewards.org)

- ADD YOUR ORGANIZATION HERE

 
ORGANIZATIONS DISPLAYING BADGES:

- Badge Bingo by Codery (http://badgebingo.com)

- DigitalMe (http://www.digitalme.co.uk)

- Makewaves (https://www.makewav.es/)

- Credly (https://credly.com)

- 3D GameLab (http://3dgamelab.com)

Badges/roadmap

2013-02-12T13:55:36Z

Threeqube: /* Q2 OBI v1.5 development, Open Badger v1.0 release */

== 2013 Roadmap ==

=== 2013 Highlights ===
* OBI v1.0 release
* Enhanced Backpack and OBI User Experience
* Open Badger v1.0 release
* Community Platform
* Badge validation solution / APIs / frameworks
* Large-scale proofs of concept

=== Q1: Ship OBI v1.0 ===
* '''OBI''' [https://github.com/mozilla/openbadges/issues?milestone=2&state=open Github 1.0 Milestone]
** v1.0 development and release
*** COPPA Stance
*** Extending metadata spec - a. standards alignment
*** Extending metadata spec - b. tags
*** 508 compliance
*** Signed badges
*** Backpack connect - autopush of badges from approved issuers
*** Revocation of badges
*** Badge expiration
*** user experience improvements

* '''Badge Validation'''
** [http://bit.ly/badgevalidation Publish paper]; get consensus on the solution we're working towards

=== Q2 OBI v1.5 development, Open Badger v1.0 release ===
* OBI
** Define, scope and start development on v1.5
** Backpack federation planning and development
** Define Endorsement specification

* Adoption
** Tools
*** Open Badger
**** v1.0 release
*** Resume Builder development
** Recruitment
*** Work with targeted job sites or job relevant badge issuers to onramp
*** Hold events with targeted groups of partners
** Support
*** Develop distributed support system

* Community
** Community platform development and beta release

* Foundational Frameworks and Practices
** Publish badge system design best practices
** Distribute badge risk analysis and sustainability reports

* Mozilla badge system
** Mozilla-wide badges added in
** Development of additional levels of webmaker badges and learning content

=== Q3 OBI v1.5 release ===

* OBI
** v1.5 release
** Fully federated OBI release
** Resume builder beta release

* Adoption
** Tools
*** Resume builder launch
** Recruitment
*** Launch of big issuer and displayer
** Support
*** Iterative development of distributed support platform

* Community
** Working with community members to build out the knowledge base

* Foundational Frameworks and Practices
** Initial policy practices in place
** Community contribution to best practices

* Mozilla Badge System
** Multiple levels of badges and leveling up available for the Webmaker badges
** Common issuing platform and experience for Mozilla badges

== 2012 Roadmap ==

=== 2012 Must Haves ===
* <strike>New openbadges.org</strike>
* New, streamlined documentation
* <strike>Demo [by DML March 1]
** Available on new website
** Features:
*** Demo backpack interface and user flow
*** Demo pushing badges to display sites</strike> '''Completed 2/2012'''

* <strike>Ship OBI Beta by end of Q1 (*aiming for end of Q1 but may have issues with legal that push into Q2)
** Contributor engagement workflow
** Issuer API
** Displayer API</strike>
** Rough endorsement API
** <strike>Support around beta</strike> '''Completed 4/2012'''

* OBI 1.0 by end of year

=== Q1: Ship Beta ===
[[Badges/PublicBeta]]

[https://github.com/mozilla/openbadges/issues?milestone=3&state=open Github Public Beta Milestone]

* <strike>Ship OBI beta by end of Q1 (aiming for end of Q1)</strike>
** <strike>Contributor engagement workflow improvement (Getting developer community to tap into OBI with facility)</strike>
** <strike>New issuer API - requiring user-initiated push to the OBI</strike>
** <strike>Displayer API</strike> '''low level, needs widgets and more detailed privacy controls'''

* Openbadges.org
** <strike>Website redesign
** Revised documentation
** Get Started on earning badges feature in website redesign
** OBI backpack and user mgmt demo</strike>

* Legal
** <strike>Initial terms of service and privacy policy FAQs</strike>

=== Q2 OBI UX Improvements ===
* OBI Features/Function Development
** Ux overhaul planning
*** Accessibility audit planning

* Adoption
** DML winner support (ongoing)
** Strategically recruit partner (ongoing)
** Onramping first wave of issuers/displayers (i.e. get people pushing badges in and out)

* <strike>Legal
** FAQs fully fleshed out</strike>

* <strike> Website planning
** Homepage revisions & updates
** Long term consideration of site updates
** Legal FAQs icon w/ own page or reconsideration of all nav
** How to highlight items on site
** Research area</strike>

=== Q3 Open Badger development ===

* OBI
** UX improvements for backpack log in and authentication
** Displayer integration
*** Fb
*** Wordpress
** Update spec to account for "Pie" badges (i.e. badges that comprise pieces of a pie)

* Open Badger Beta
** Proposed API spec: https://github.com/mozilla/openbadger/wiki/api
** Ongoing development

* Community
** Create step by step onboarding documentation and supporting material for new entrants.

* Adoption
** DML ongoing outreach to 30 funded winners

=== Q4 Open Badger beta release and OBI v1.0 development ===
[https://github.com/mozilla/openbadges/issues?milestone=2&state=open Github 1.0 Milestone]

* OBI
** v1.0 ongoing development
*** Accessibility: 508 compliance
*** COPPA compliant backpack or parallel < 13 backpack development
*** Global badge directory
*** Privacy, data, security review and vetting
*** Operational requirements review for productization

*Open Badger
** Privacy, data, security review and vetting
** Operational requirements review for beta public release
** Beta release

* Adoption
** DML first round of outreach to 60 unfunded winners
** Identify key partners to onboard
** Develop strategy map for recruitment
** Scope and model a distributed support system

* Foundational Frameworks & Practices
** Draft Badge Validation white paper

* Mozilla badge system
** Release initial round of webmaker badges system

Badges/roadmap

2013-02-12T13:54:34Z

Threeqube: /* Q2 OBI v1.5 development, Open Badger v1.0 release */

== 2013 Roadmap ==

=== 2013 Highlights ===
* OBI v1.0 release
* Enhanced Backpack and OBI User Experience
* Open Badger v1.0 release
* Community Platform
* Badge validation solution / APIs / frameworks
* Large-scale proofs of concept

=== Q1: Ship OBI v1.0 ===
* '''OBI''' [https://github.com/mozilla/openbadges/issues?milestone=2&state=open Github 1.0 Milestone]
** v1.0 development and release
*** COPPA Stance
*** Extending metadata spec - a. standards alignment
*** Extending metadata spec - b. tags
*** 508 compliance
*** Signed badges
*** Backpack connect - autopush of badges from approved issuers
*** Revocation of badges
*** Badge expiration
*** user experience improvements

* '''Badge Validation'''
** [http://bit.ly/badgevalidation Publish paper]; get consensus on the solution we're working towards

=== Q2 OBI v1.5 development, Open Badger v1.0 release ===
* OBI
** Define, scope and start development on v1.5
** Federation planning and development
** Endorsement API definition

* Adoption
** Tools
*** Open Badger
**** v1.0 release
*** Resume Builder development
** Recruitment
*** Work with targeted job sites or job relevant badge issuers to onramp
*** Hold events with targeted groups of partners
** Support
*** Develop distributed support system

* Community
** Community platform development and beta release

* Foundational Frameworks and Practices
** Publish badge system design best practices
** Distribute badge risk analysis and sustainability reports

* Mozilla badge system
** Mozilla-wide badges added in
** Development of additional levels of webmaker badges and learning content

=== Q3 OBI v1.5 release ===

* OBI
** v1.5 release
** Fully federated OBI release
** Resume builder beta release

* Adoption
** Tools
*** Resume builder launch
** Recruitment
*** Launch of big issuer and displayer
** Support
*** Iterative development of distributed support platform

* Community
** Working with community members to build out the knowledge base

* Foundational Frameworks and Practices
** Initial policy practices in place
** Community contribution to best practices

* Mozilla Badge System
** Multiple levels of badges and leveling up available for the Webmaker badges
** Common issuing platform and experience for Mozilla badges

== 2012 Roadmap ==

=== 2012 Must Haves ===
* <strike>New openbadges.org</strike>
* New, streamlined documentation
* <strike>Demo [by DML March 1]
** Available on new website
** Features:
*** Demo backpack interface and user flow
*** Demo pushing badges to display sites</strike> '''Completed 2/2012'''

* <strike>Ship OBI Beta by end of Q1 (*aiming for end of Q1 but may have issues with legal that push into Q2)
** Contributor engagement workflow
** Issuer API
** Displayer API</strike>
** Rough endorsement API
** <strike>Support around beta</strike> '''Completed 4/2012'''

* OBI 1.0 by end of year

=== Q1: Ship Beta ===
[[Badges/PublicBeta]]

[https://github.com/mozilla/openbadges/issues?milestone=3&state=open Github Public Beta Milestone]

* <strike>Ship OBI beta by end of Q1 (aiming for end of Q1)</strike>
** <strike>Contributor engagement workflow improvement (Getting developer community to tap into OBI with facility)</strike>
** <strike>New issuer API - requiring user-initiated push to the OBI</strike>
** <strike>Displayer API</strike> '''low level, needs widgets and more detailed privacy controls'''

* Openbadges.org
** <strike>Website redesign
** Revised documentation
** Get Started on earning badges feature in website redesign
** OBI backpack and user mgmt demo</strike>

* Legal
** <strike>Initial terms of service and privacy policy FAQs</strike>

=== Q2 OBI UX Improvements ===
* OBI Features/Function Development
** Ux overhaul planning
*** Accessibility audit planning

* Adoption
** DML winner support (ongoing)
** Strategically recruit partner (ongoing)
** Onramping first wave of issuers/displayers (i.e. get people pushing badges in and out)

* <strike>Legal
** FAQs fully fleshed out</strike>

* <strike> Website planning
** Homepage revisions & updates
** Long term consideration of site updates
** Legal FAQs icon w/ own page or reconsideration of all nav
** How to highlight items on site
** Research area</strike>

=== Q3 Open Badger development ===

* OBI
** UX improvements for backpack log in and authentication
** Displayer integration
*** Fb
*** Wordpress
** Update spec to account for "Pie" badges (i.e. badges that comprise pieces of a pie)

* Open Badger Beta
** Proposed API spec: https://github.com/mozilla/openbadger/wiki/api
** Ongoing development

* Community
** Create step by step onboarding documentation and supporting material for new entrants.

* Adoption
** DML ongoing outreach to 30 funded winners

=== Q4 Open Badger beta release and OBI v1.0 development ===
[https://github.com/mozilla/openbadges/issues?milestone=2&state=open Github 1.0 Milestone]

* OBI
** v1.0 ongoing development
*** Accessibility: 508 compliance
*** COPPA compliant backpack or parallel < 13 backpack development
*** Global badge directory
*** Privacy, data, security review and vetting
*** Operational requirements review for productization

*Open Badger
** Privacy, data, security review and vetting
** Operational requirements review for beta public release
** Beta release

* Adoption
** DML first round of outreach to 60 unfunded winners
** Identify key partners to onboard
** Develop strategy map for recruitment
** Scope and model a distributed support system

* Foundational Frameworks & Practices
** Draft Badge Validation white paper

* Mozilla badge system
** Release initial round of webmaker badges system

Badges/roadmap

2013-02-12T13:52:27Z

Threeqube: /* Q1: Ship OBI v1.0 */

== 2013 Roadmap ==

=== 2013 Highlights ===
* OBI v1.0 release
* Enhanced Backpack and OBI User Experience
* Open Badger v1.0 release
* Community Platform
* Badge validation solution / APIs / frameworks
* Large-scale proofs of concept

=== Q1: Ship OBI v1.0 ===
* '''OBI''' [https://github.com/mozilla/openbadges/issues?milestone=2&state=open Github 1.0 Milestone]
** v1.0 development and release
*** COPPA Stance
*** Extending metadata spec - a. standards alignment
*** Extending metadata spec - b. tags
*** 508 compliance
*** Signed badges
*** Backpack connect - autopush of badges from approved issuers
*** Revocation of badges
*** Badge expiration
*** user experience improvements

* '''Badge Validation'''
** [http://bit.ly/badgevalidation Publish paper]; get consensus on the solution we're working towards

=== Q2 OBI v1.5 development, Open Badger v1.0 release ===
* OBI
** v1.5 development
** Federation planning and development
** Endorsement API definition

* Adoption
** Tools
*** Open Badger
**** v1.0 release
*** Resume Builder development
** Recruitment
*** Work with targeted job sites or job relevant badge issuers to onramp
*** Hold events with targeted groups of partners
** Support
*** Develop distributed support system

* Community
** Community platform development and beta release

* Foundational Frameworks and Practices
** Publish badge system design best practices
** Distribute badge risk analysis and sustainability reports

* Mozilla badge system
** Mozilla-wide badges added in
** Development of additional levels of webmaker badges and learning content

=== Q3 OBI v1.5 release ===

* OBI
** v1.5 release
** Fully federated OBI release
** Resume builder beta release

* Adoption
** Tools
*** Resume builder launch
** Recruitment
*** Launch of big issuer and displayer
** Support
*** Iterative development of distributed support platform

* Community
** Working with community members to build out the knowledge base

* Foundational Frameworks and Practices
** Initial policy practices in place
** Community contribution to best practices

* Mozilla Badge System
** Multiple levels of badges and leveling up available for the Webmaker badges
** Common issuing platform and experience for Mozilla badges

== 2012 Roadmap ==

=== 2012 Must Haves ===
* <strike>New openbadges.org</strike>
* New, streamlined documentation
* <strike>Demo [by DML March 1]
** Available on new website
** Features:
*** Demo backpack interface and user flow
*** Demo pushing badges to display sites</strike> '''Completed 2/2012'''

* <strike>Ship OBI Beta by end of Q1 (*aiming for end of Q1 but may have issues with legal that push into Q2)
** Contributor engagement workflow
** Issuer API
** Displayer API</strike>
** Rough endorsement API
** <strike>Support around beta</strike> '''Completed 4/2012'''

* OBI 1.0 by end of year

=== Q1: Ship Beta ===
[[Badges/PublicBeta]]

[https://github.com/mozilla/openbadges/issues?milestone=3&state=open Github Public Beta Milestone]

* <strike>Ship OBI beta by end of Q1 (aiming for end of Q1)</strike>
** <strike>Contributor engagement workflow improvement (Getting developer community to tap into OBI with facility)</strike>
** <strike>New issuer API - requiring user-initiated push to the OBI</strike>
** <strike>Displayer API</strike> '''low level, needs widgets and more detailed privacy controls'''

* Openbadges.org
** <strike>Website redesign
** Revised documentation
** Get Started on earning badges feature in website redesign
** OBI backpack and user mgmt demo</strike>

* Legal
** <strike>Initial terms of service and privacy policy FAQs</strike>

=== Q2 OBI UX Improvements ===
* OBI Features/Function Development
** Ux overhaul planning
*** Accessibility audit planning

* Adoption
** DML winner support (ongoing)
** Strategically recruit partner (ongoing)
** Onramping first wave of issuers/displayers (i.e. get people pushing badges in and out)

* <strike>Legal
** FAQs fully fleshed out</strike>

* <strike> Website planning
** Homepage revisions & updates
** Long term consideration of site updates
** Legal FAQs icon w/ own page or reconsideration of all nav
** How to highlight items on site
** Research area</strike>

=== Q3 Open Badger development ===

* OBI
** UX improvements for backpack log in and authentication
** Displayer integration
*** Fb
*** Wordpress
** Update spec to account for "Pie" badges (i.e. badges that comprise pieces of a pie)

* Open Badger Beta
** Proposed API spec: https://github.com/mozilla/openbadger/wiki/api
** Ongoing development

* Community
** Create step by step onboarding documentation and supporting material for new entrants.

* Adoption
** DML ongoing outreach to 30 funded winners

=== Q4 Open Badger beta release and OBI v1.0 development ===
[https://github.com/mozilla/openbadges/issues?milestone=2&state=open Github 1.0 Milestone]

* OBI
** v1.0 ongoing development
*** Accessibility: 508 compliance
*** COPPA compliant backpack or parallel < 13 backpack development
*** Global badge directory
*** Privacy, data, security review and vetting
*** Operational requirements review for productization

*Open Badger
** Privacy, data, security review and vetting
** Operational requirements review for beta public release
** Beta release

* Adoption
** DML first round of outreach to 60 unfunded winners
** Identify key partners to onboard
** Develop strategy map for recruitment
** Scope and model a distributed support system

* Foundational Frameworks & Practices
** Draft Badge Validation white paper

* Mozilla badge system
** Release initial round of webmaker badges system

Badges/chicago

2013-02-08T12:37:19Z

Threeqube:

Badges/chicago

2013-02-05T15:35:56Z

Threeqube: /* Roadmap */

Badges/chicago

2013-02-05T15:31:16Z

Threeqube: /* Roadmap */

Badges/chicago

2013-02-05T15:29:34Z

Threeqube: /* Roadmap */

Badges/chicago

2013-02-05T14:24:55Z

Threeqube: /* February 18, 2013 – Badge Submissions Due */

== Chicago Summer of Learning Badges Program ==
Mozilla is advising the city of Chicago and Chicago-based organizations to design and implement badges to capture various forms of learning throughout the summer in order to make their Summer of Learning program awesome.

For the Chicago Summer of Learning, Mozilla is playing the following roles:

* Advising on overall campaign design.
* Supporting the organizations on badge design and implementation.
* Building and hosting the badge-issuing platform.
* Celebrating with the rest of Chicago this summer!

=== What is Chicago Summer of Learning? ===
Mayor Rahm Emanuel has announced an ambitious initiative to ensure that youth across the city of Chicago will have access to high-quality learning opportunities over the summer. Beginning in the summer of 2013, private and public summer programs will provide educational experiences to youth across the city, recognize that learning and skill development through digital badges, and then connect youth to opportunities for jobs, internships and credit in the school year.

=== How will badges in the Summer of Learning work? ===
This summer, private and public organizations will offer learning programs for youth and issue badges to recognize the learning and skill development that occurs. Youth will earn badges as they participate and complete various programs and learning experiences. These organizational badges will accumulate to city-level badges that will unlock access to special projects and events for youth that span organizations and skill areas, providing exciting and inspiring pathways to continued learning and leveling up. Youth will also have an online profile to track their progress and get recommendations for additional learning options and badges to earn.

=== Napkin Sketch ===
[[Image: ChicagoBadgeDeck1.3.001.png|800px]]
[[Image: ChicagoBadgeDeck1.3.002.png|800px]]

=== Program Workshop ===

Downloadable here: https://wiki.mozilla.org/images/2/22/CSOLWorksheet.pdf

=== Roadmap ===

In progress roadmap can be found here: https://openbadges.etherpad.mozilla.org/chicago-badges-roadmap

==== JANUARY 2013 ====
* Badges - Programmatic Design / Recruitment (Erin)
** Recruit orgs
** Define categories and top level badges
** Develop the framework / model for the badge system
*** Agree on highlevel set of badges and 'flow'
*** Decide if we are capping org badges or allowing more flexibility for them to create more badges

* Tech - Requirements (Chris McAvoy)
** Summer of Learning site:
*** Decide on ownership and objectives
** OpenBadger:
*** Gather tech requirements
** Data Integration Implementation
*** Planning / Requirements (Akili, Melissa)

* Communications - Mayor's office working on a
* Partners - for challenges, funding) (Connie)

==== FEBRUARY 2013 ====
* Badges - Org Specific Badge Build out
** Feb 5th meeting with the organizations to kick off the badge design
** Org submissions of their badges are due mid Feb
** Review of the badges, sorting against the categories
** Design the games, pathways and artifacts
*** Work with orgs to determine the challenges / artifacts
*** Plug in additional online opportunities for learning (i.e. Mozilla Webmaker, Girl Scouts, etc.)
*** Hire and onramp Chicago-based Badge system designer
*** Finalize the top city-level badges (criteria and design)

* Tech - Wireframing and Initial Development
** Summer of Learning site:
***Hire firm / developer to build the site (if needed)
***Wireframing and initial designs
*** Begin website development
** OpenBadger:
*** Hire Open Badger developer
*** Break tech requirements into discreet tasks
*** Define development sprint cycle workflow

==== MARCH 2013 ====
2nd meeting: March 14th, 1pm-5pm CT, Sheraton
Connie request: invited to DML conference, too

* Badges - Badge Design and Finalization
** Finalize the org-specific badges, or the framework to support them on design
** Finalize the challenges / artifacts
** Finalize the pathways (how badges will hook together)
** Badge graphic design
* Tech - Development
** Summer of Learning site:
*** Website development
**** Several reviews/iteration
** OpenBadger:
*** Continued development
*** Staging launch (end of month)
*** QA / Testing

==== APRIL 2013 ====

* Badges - Badge Creation and Build Out
** Build out badges in OpenBadger
** Integration of badges into program websites
** Production of offline badges

* Tech - Staging / production launches
** Summer of Learning site:
*** Staging launch early in the month
*** Production launch of site end of the month
** OpenBadger:
*** Continued development
***Bug fixing / final QA
*** Production Launch (end of month)

==== MAY 2013 ====
* Badges - QA and testing
**Delivery of offline badges
** Testing / QA of badges
** Planning for end of summer showcase events
** Communication campaign to youth and parents
*** Pathcrafting in schools?

* Tech
** Maintenance / Bug fixing

==== JUNE 2013 ====

* Badges - Launch, first earners
** LAUNCH, people earning badges

* Tech:
** Maintenance / Bug fixing

=== Badge submission form ===

http://openbadges.org/chicago

=== Technical FAQ ===

Can be found here: https://wiki.mozilla.org/Badges/chicago/techFAQ

=== Important Dates ===

==== February 18, 2013 – Badge Submissions Due ====
Badge idea submissions due – please submit your ideas for 1-5 badges* for your program through the form here: http://openbadges.org/chicago
Note: If you’d like to have more than 5 badges, let us know at support@openbadges.org and we’ll work with you on the best solution.

==== March 14, 2013 – Program Meeting ====
1-5pm CT, Sheraton Towers Hotel, Chicago
Please send 1-2 reps from your organization to this meeting to discuss the badges and opportunities for cross-organization connections and projects.
Stick around after the meeting for the DML Conference Science Fair (6-8pm), where you’ll see examples of badge systems from other organizations like yours around the country!

Badges/chicago

2013-02-05T14:24:18Z

Threeqube: /* Napkin Sketch */

== Chicago Summer of Learning Badges Program ==
Mozilla is advising the city of Chicago and Chicago-based organizations to design and implement badges to capture various forms of learning throughout the summer in order to make their Summer of Learning program awesome.

For the Chicago Summer of Learning, Mozilla is playing the following roles:

* Advising on overall campaign design.
* Supporting the organizations on badge design and implementation.
* Building and hosting the badge-issuing platform.
* Celebrating with the rest of Chicago this summer!

=== What is Chicago Summer of Learning? ===
Mayor Rahm Emanuel has announced an ambitious initiative to ensure that youth across the city of Chicago will have access to high-quality learning opportunities over the summer. Beginning in the summer of 2013, private and public summer programs will provide educational experiences to youth across the city, recognize that learning and skill development through digital badges, and then connect youth to opportunities for jobs, internships and credit in the school year.

=== How will badges in the Summer of Learning work? ===
This summer, private and public organizations will offer learning programs for youth and issue badges to recognize the learning and skill development that occurs. Youth will earn badges as they participate and complete various programs and learning experiences. These organizational badges will accumulate to city-level badges that will unlock access to special projects and events for youth that span organizations and skill areas, providing exciting and inspiring pathways to continued learning and leveling up. Youth will also have an online profile to track their progress and get recommendations for additional learning options and badges to earn.

=== Napkin Sketch ===
[[Image: ChicagoBadgeDeck1.3.001.png|800px]]
[[Image: ChicagoBadgeDeck1.3.002.png|800px]]

=== Program Workshop ===

Downloadable here: https://wiki.mozilla.org/images/2/22/CSOLWorksheet.pdf

=== Roadmap ===

In progress roadmap can be found here: https://openbadges.etherpad.mozilla.org/chicago-badges-roadmap

==== JANUARY 2013 ====
* Badges - Programmatic Design / Recruitment (Erin)
** Recruit orgs
** Define categories and top level badges
** Develop the framework / model for the badge system
*** Agree on highlevel set of badges and 'flow'
*** Decide if we are capping org badges or allowing more flexibility for them to create more badges

* Tech - Requirements (Chris McAvoy)
** Summer of Learning site:
*** Decide on ownership and objectives
** OpenBadger:
*** Gather tech requirements
** Data Integration Implementation
*** Planning / Requirements (Akili, Melissa)

* Communications - Mayor's office working on a
* Partners - for challenges, funding) (Connie)

==== FEBRUARY 2013 ====
* Badges - Org Specific Badge Build out
** Feb 5th meeting with the organizations to kick off the badge design
** Org submissions of their badges are due mid Feb
** Review of the badges, sorting against the categories
** Design the games, pathways and artifacts
*** Work with orgs to determine the challenges / artifacts
*** Plug in additional online opportunities for learning (i.e. Mozilla Webmaker, Girl Scouts, etc.)
*** Hire and onramp Chicago-based Badge system designer
*** Finalize the top city-level badges (criteria and design)

* Tech - Wireframing and Initial Development
** Summer of Learning site:
***Hire firm / developer to build the site (if needed)
***Wireframing and initial designs
*** Begin website development
** OpenBadger:
*** Hire Open Badger developer
*** Break tech requirements into discreet tasks
*** Define development sprint cycle workflow

==== MARCH 2013 ====
2nd meeting: March 14th, 1pm-5pm CT, Sheraton
Connie request: invited to DML conference, too

* Badges - Badge Design and Finalization
** Finalize the org-specific badges, or the framework to support them on design
** Finalize the challenges / artifacts
** Finalize the pathways (how badges will hook together)
** Badge graphic design
* Tech - Development
** Summer of Learning site:
*** Website development
**** Several reviews/iteration
** OpenBadger:
*** Continued development
*** Staging launch (end of month)
*** QA / Testing

==== APRIL 2013 ====

* Badges - Badge Creation and Build Out
** Build out badges in OpenBadger
** Integration of badges into program websites
** Production of offline badges

* Tech - Staging / production launches
** Summer of Learning site:
*** Staging launch early in the month
*** Production launch of site end of the month
** OpenBadger:
*** Continued development
***Bug fixing / final QA
*** Production Launch (end of month)

==== MAY 2013 ====
* Badges - QA and testing
**Delivery of offline badges
** Testing / QA of badges
** Planning for end of summer showcase events
** Communication campaign to youth and parents
*** Pathcrafting in schools?

* Tech
** Maintenance / Bug fixing

==== JUNE 2013 ====

* Badges - Launch, first earners
** LAUNCH, people earning badges

* Tech:
** Maintenance / Bug fixing

=== Badge submission form ===

http://openbadges.org/chicago

=== Technical FAQ ===

Can be found here: https://wiki.mozilla.org/Badges/chicago/techFAQ

=== Important Dates ===

==== February 18, 2013 – Badge Submissions Due ====
Badge idea submissions due – please submit your ideas for 1-5 badges* for your program through the form here: http://openbadges.org/chicago
Note: If you’d like to have more than 5 badges, let us know at badges@mozillafoundation.org and we’ll work with you on the best solution.

==== March 14, 2013 – Program Meeting ====
1-5pm CT, Sheraton Towers Hotel, Chicago
Please send 1-2 reps from your organization to this meeting to discuss the badges and opportunities for cross-organization connections and projects.
Stick around after the meeting for the DML Conference Science Fair (6-8pm), where you’ll see examples of badge systems from other organizations like yours around the country!

Badges/chicago

2013-02-05T14:23:46Z

Threeqube: /* Napkin Sketch */

== Chicago Summer of Learning Badges Program ==
Mozilla is advising the city of Chicago and Chicago-based organizations to design and implement badges to capture various forms of learning throughout the summer in order to make their Summer of Learning program awesome.

For the Chicago Summer of Learning, Mozilla is playing the following roles:

* Advising on overall campaign design.
* Supporting the organizations on badge design and implementation.
* Building and hosting the badge-issuing platform.
* Celebrating with the rest of Chicago this summer!

=== What is Chicago Summer of Learning? ===
Mayor Rahm Emanuel has announced an ambitious initiative to ensure that youth across the city of Chicago will have access to high-quality learning opportunities over the summer. Beginning in the summer of 2013, private and public summer programs will provide educational experiences to youth across the city, recognize that learning and skill development through digital badges, and then connect youth to opportunities for jobs, internships and credit in the school year.

=== How will badges in the Summer of Learning work? ===
This summer, private and public organizations will offer learning programs for youth and issue badges to recognize the learning and skill development that occurs. Youth will earn badges as they participate and complete various programs and learning experiences. These organizational badges will accumulate to city-level badges that will unlock access to special projects and events for youth that span organizations and skill areas, providing exciting and inspiring pathways to continued learning and leveling up. Youth will also have an online profile to track their progress and get recommendations for additional learning options and badges to earn.

=== Napkin Sketch ===
[[Image: ChicagoBadgeDeck1.3.001.png|800px]]

=== Program Workshop ===

Downloadable here: https://wiki.mozilla.org/images/2/22/CSOLWorksheet.pdf

=== Roadmap ===

In progress roadmap can be found here: https://openbadges.etherpad.mozilla.org/chicago-badges-roadmap

==== JANUARY 2013 ====
* Badges - Programmatic Design / Recruitment (Erin)
** Recruit orgs
** Define categories and top level badges
** Develop the framework / model for the badge system
*** Agree on highlevel set of badges and 'flow'
*** Decide if we are capping org badges or allowing more flexibility for them to create more badges

* Tech - Requirements (Chris McAvoy)
** Summer of Learning site:
*** Decide on ownership and objectives
** OpenBadger:
*** Gather tech requirements
** Data Integration Implementation
*** Planning / Requirements (Akili, Melissa)

* Communications - Mayor's office working on a
* Partners - for challenges, funding) (Connie)

==== FEBRUARY 2013 ====
* Badges - Org Specific Badge Build out
** Feb 5th meeting with the organizations to kick off the badge design
** Org submissions of their badges are due mid Feb
** Review of the badges, sorting against the categories
** Design the games, pathways and artifacts
*** Work with orgs to determine the challenges / artifacts
*** Plug in additional online opportunities for learning (i.e. Mozilla Webmaker, Girl Scouts, etc.)
*** Hire and onramp Chicago-based Badge system designer
*** Finalize the top city-level badges (criteria and design)

* Tech - Wireframing and Initial Development
** Summer of Learning site:
***Hire firm / developer to build the site (if needed)
***Wireframing and initial designs
*** Begin website development
** OpenBadger:
*** Hire Open Badger developer
*** Break tech requirements into discreet tasks
*** Define development sprint cycle workflow

==== MARCH 2013 ====
2nd meeting: March 14th, 1pm-5pm CT, Sheraton
Connie request: invited to DML conference, too

* Badges - Badge Design and Finalization
** Finalize the org-specific badges, or the framework to support them on design
** Finalize the challenges / artifacts
** Finalize the pathways (how badges will hook together)
** Badge graphic design
* Tech - Development
** Summer of Learning site:
*** Website development
**** Several reviews/iteration
** OpenBadger:
*** Continued development
*** Staging launch (end of month)
*** QA / Testing

==== APRIL 2013 ====

* Badges - Badge Creation and Build Out
** Build out badges in OpenBadger
** Integration of badges into program websites
** Production of offline badges

* Tech - Staging / production launches
** Summer of Learning site:
*** Staging launch early in the month
*** Production launch of site end of the month
** OpenBadger:
*** Continued development
***Bug fixing / final QA
*** Production Launch (end of month)

==== MAY 2013 ====
* Badges - QA and testing
**Delivery of offline badges
** Testing / QA of badges
** Planning for end of summer showcase events
** Communication campaign to youth and parents
*** Pathcrafting in schools?

* Tech
** Maintenance / Bug fixing

==== JUNE 2013 ====

* Badges - Launch, first earners
** LAUNCH, people earning badges

* Tech:
** Maintenance / Bug fixing

=== Badge submission form ===

http://openbadges.org/chicago

=== Technical FAQ ===

Can be found here: https://wiki.mozilla.org/Badges/chicago/techFAQ

=== Important Dates ===

==== February 18, 2013 – Badge Submissions Due ====
Badge idea submissions due – please submit your ideas for 1-5 badges* for your program through the form here: http://openbadges.org/chicago
Note: If you’d like to have more than 5 badges, let us know at badges@mozillafoundation.org and we’ll work with you on the best solution.

==== March 14, 2013 – Program Meeting ====
1-5pm CT, Sheraton Towers Hotel, Chicago
Please send 1-2 reps from your organization to this meeting to discuss the badges and opportunities for cross-organization connections and projects.
Stick around after the meeting for the DML Conference Science Fair (6-8pm), where you’ll see examples of badge systems from other organizations like yours around the country!

File:ChicagoBadgeDeck1.3.002.png

2013-02-05T14:22:43Z

Threeqube:

Badges/chicago

2013-02-05T14:22:01Z

Threeqube: /* Napkin Sketch */

== Chicago Summer of Learning Badges Program ==
Mozilla is advising the city of Chicago and Chicago-based organizations to design and implement badges to capture various forms of learning throughout the summer in order to make their Summer of Learning program awesome.

For the Chicago Summer of Learning, Mozilla is playing the following roles:

* Advising on overall campaign design.
* Supporting the organizations on badge design and implementation.
* Building and hosting the badge-issuing platform.
* Celebrating with the rest of Chicago this summer!

=== What is Chicago Summer of Learning? ===
Mayor Rahm Emanuel has announced an ambitious initiative to ensure that youth across the city of Chicago will have access to high-quality learning opportunities over the summer. Beginning in the summer of 2013, private and public summer programs will provide educational experiences to youth across the city, recognize that learning and skill development through digital badges, and then connect youth to opportunities for jobs, internships and credit in the school year.

=== How will badges in the Summer of Learning work? ===
This summer, private and public organizations will offer learning programs for youth and issue badges to recognize the learning and skill development that occurs. Youth will earn badges as they participate and complete various programs and learning experiences. These organizational badges will accumulate to city-level badges that will unlock access to special projects and events for youth that span organizations and skill areas, providing exciting and inspiring pathways to continued learning and leveling up. Youth will also have an online profile to track their progress and get recommendations for additional learning options and badges to earn.

=== Napkin Sketch ===
[[Image: ChicagoBadgeDeck1.3.001.png]]

=== Program Workshop ===

Downloadable here: https://wiki.mozilla.org/images/2/22/CSOLWorksheet.pdf

=== Roadmap ===

In progress roadmap can be found here: https://openbadges.etherpad.mozilla.org/chicago-badges-roadmap

==== JANUARY 2013 ====
* Badges - Programmatic Design / Recruitment (Erin)
** Recruit orgs
** Define categories and top level badges
** Develop the framework / model for the badge system
*** Agree on highlevel set of badges and 'flow'
*** Decide if we are capping org badges or allowing more flexibility for them to create more badges

* Tech - Requirements (Chris McAvoy)
** Summer of Learning site:
*** Decide on ownership and objectives
** OpenBadger:
*** Gather tech requirements
** Data Integration Implementation
*** Planning / Requirements (Akili, Melissa)

* Communications - Mayor's office working on a
* Partners - for challenges, funding) (Connie)

==== FEBRUARY 2013 ====
* Badges - Org Specific Badge Build out
** Feb 5th meeting with the organizations to kick off the badge design
** Org submissions of their badges are due mid Feb
** Review of the badges, sorting against the categories
** Design the games, pathways and artifacts
*** Work with orgs to determine the challenges / artifacts
*** Plug in additional online opportunities for learning (i.e. Mozilla Webmaker, Girl Scouts, etc.)
*** Hire and onramp Chicago-based Badge system designer
*** Finalize the top city-level badges (criteria and design)

* Tech - Wireframing and Initial Development
** Summer of Learning site:
***Hire firm / developer to build the site (if needed)
***Wireframing and initial designs
*** Begin website development
** OpenBadger:
*** Hire Open Badger developer
*** Break tech requirements into discreet tasks
*** Define development sprint cycle workflow

==== MARCH 2013 ====
2nd meeting: March 14th, 1pm-5pm CT, Sheraton
Connie request: invited to DML conference, too

* Badges - Badge Design and Finalization
** Finalize the org-specific badges, or the framework to support them on design
** Finalize the challenges / artifacts
** Finalize the pathways (how badges will hook together)
** Badge graphic design
* Tech - Development
** Summer of Learning site:
*** Website development
**** Several reviews/iteration
** OpenBadger:
*** Continued development
*** Staging launch (end of month)
*** QA / Testing

==== APRIL 2013 ====

* Badges - Badge Creation and Build Out
** Build out badges in OpenBadger
** Integration of badges into program websites
** Production of offline badges

* Tech - Staging / production launches
** Summer of Learning site:
*** Staging launch early in the month
*** Production launch of site end of the month
** OpenBadger:
*** Continued development
***Bug fixing / final QA
*** Production Launch (end of month)

==== MAY 2013 ====
* Badges - QA and testing
**Delivery of offline badges
** Testing / QA of badges
** Planning for end of summer showcase events
** Communication campaign to youth and parents
*** Pathcrafting in schools?

* Tech
** Maintenance / Bug fixing

==== JUNE 2013 ====

* Badges - Launch, first earners
** LAUNCH, people earning badges

* Tech:
** Maintenance / Bug fixing

=== Badge submission form ===

http://openbadges.org/chicago

=== Technical FAQ ===

Can be found here: https://wiki.mozilla.org/Badges/chicago/techFAQ

=== Important Dates ===

==== February 18, 2013 – Badge Submissions Due ====
Badge idea submissions due – please submit your ideas for 1-5 badges* for your program through the form here: http://openbadges.org/chicago
Note: If you’d like to have more than 5 badges, let us know at badges@mozillafoundation.org and we’ll work with you on the best solution.

==== March 14, 2013 – Program Meeting ====
1-5pm CT, Sheraton Towers Hotel, Chicago
Please send 1-2 reps from your organization to this meeting to discuss the badges and opportunities for cross-organization connections and projects.
Stick around after the meeting for the DML Conference Science Fair (6-8pm), where you’ll see examples of badge systems from other organizations like yours around the country!

Badges/chicago

2013-02-05T14:21:39Z

Threeqube: /* Napkin Sketch */

== Chicago Summer of Learning Badges Program ==
Mozilla is advising the city of Chicago and Chicago-based organizations to design and implement badges to capture various forms of learning throughout the summer in order to make their Summer of Learning program awesome.

For the Chicago Summer of Learning, Mozilla is playing the following roles:

* Advising on overall campaign design.
* Supporting the organizations on badge design and implementation.
* Building and hosting the badge-issuing platform.
* Celebrating with the rest of Chicago this summer!

=== What is Chicago Summer of Learning? ===
Mayor Rahm Emanuel has announced an ambitious initiative to ensure that youth across the city of Chicago will have access to high-quality learning opportunities over the summer. Beginning in the summer of 2013, private and public summer programs will provide educational experiences to youth across the city, recognize that learning and skill development through digital badges, and then connect youth to opportunities for jobs, internships and credit in the school year.

=== How will badges in the Summer of Learning work? ===
This summer, private and public organizations will offer learning programs for youth and issue badges to recognize the learning and skill development that occurs. Youth will earn badges as they participate and complete various programs and learning experiences. These organizational badges will accumulate to city-level badges that will unlock access to special projects and events for youth that span organizations and skill areas, providing exciting and inspiring pathways to continued learning and leveling up. Youth will also have an online profile to track their progress and get recommendations for additional learning options and badges to earn.

=== Napkin Sketch ===
[[Image: https://wiki.mozilla.org/images/3/3a/ChicagoBadgeDeck1.3.001.png]]

=== Program Workshop ===

Downloadable here: https://wiki.mozilla.org/images/2/22/CSOLWorksheet.pdf

=== Roadmap ===

In progress roadmap can be found here: https://openbadges.etherpad.mozilla.org/chicago-badges-roadmap

==== JANUARY 2013 ====
* Badges - Programmatic Design / Recruitment (Erin)
** Recruit orgs
** Define categories and top level badges
** Develop the framework / model for the badge system
*** Agree on highlevel set of badges and 'flow'
*** Decide if we are capping org badges or allowing more flexibility for them to create more badges

* Tech - Requirements (Chris McAvoy)
** Summer of Learning site:
*** Decide on ownership and objectives
** OpenBadger:
*** Gather tech requirements
** Data Integration Implementation
*** Planning / Requirements (Akili, Melissa)

* Communications - Mayor's office working on a
* Partners - for challenges, funding) (Connie)

==== FEBRUARY 2013 ====
* Badges - Org Specific Badge Build out
** Feb 5th meeting with the organizations to kick off the badge design
** Org submissions of their badges are due mid Feb
** Review of the badges, sorting against the categories
** Design the games, pathways and artifacts
*** Work with orgs to determine the challenges / artifacts
*** Plug in additional online opportunities for learning (i.e. Mozilla Webmaker, Girl Scouts, etc.)
*** Hire and onramp Chicago-based Badge system designer
*** Finalize the top city-level badges (criteria and design)

* Tech - Wireframing and Initial Development
** Summer of Learning site:
***Hire firm / developer to build the site (if needed)
***Wireframing and initial designs
*** Begin website development
** OpenBadger:
*** Hire Open Badger developer
*** Break tech requirements into discreet tasks
*** Define development sprint cycle workflow

==== MARCH 2013 ====
2nd meeting: March 14th, 1pm-5pm CT, Sheraton
Connie request: invited to DML conference, too

* Badges - Badge Design and Finalization
** Finalize the org-specific badges, or the framework to support them on design
** Finalize the challenges / artifacts
** Finalize the pathways (how badges will hook together)
** Badge graphic design
* Tech - Development
** Summer of Learning site:
*** Website development
**** Several reviews/iteration
** OpenBadger:
*** Continued development
*** Staging launch (end of month)
*** QA / Testing

==== APRIL 2013 ====

* Badges - Badge Creation and Build Out
** Build out badges in OpenBadger
** Integration of badges into program websites
** Production of offline badges

* Tech - Staging / production launches
** Summer of Learning site:
*** Staging launch early in the month
*** Production launch of site end of the month
** OpenBadger:
*** Continued development
***Bug fixing / final QA
*** Production Launch (end of month)

==== MAY 2013 ====
* Badges - QA and testing
**Delivery of offline badges
** Testing / QA of badges
** Planning for end of summer showcase events
** Communication campaign to youth and parents
*** Pathcrafting in schools?

* Tech
** Maintenance / Bug fixing

==== JUNE 2013 ====

* Badges - Launch, first earners
** LAUNCH, people earning badges

* Tech:
** Maintenance / Bug fixing

=== Badge submission form ===

http://openbadges.org/chicago

=== Technical FAQ ===

Can be found here: https://wiki.mozilla.org/Badges/chicago/techFAQ

=== Important Dates ===

==== February 18, 2013 – Badge Submissions Due ====
Badge idea submissions due – please submit your ideas for 1-5 badges* for your program through the form here: http://openbadges.org/chicago
Note: If you’d like to have more than 5 badges, let us know at badges@mozillafoundation.org and we’ll work with you on the best solution.

==== March 14, 2013 – Program Meeting ====
1-5pm CT, Sheraton Towers Hotel, Chicago
Please send 1-2 reps from your organization to this meeting to discuss the badges and opportunities for cross-organization connections and projects.
Stick around after the meeting for the DML Conference Science Fair (6-8pm), where you’ll see examples of badge systems from other organizations like yours around the country!

Badges/chicago

2013-02-05T14:20:31Z

Threeqube: /* Napkin Sketch */

== Chicago Summer of Learning Badges Program ==
Mozilla is advising the city of Chicago and Chicago-based organizations to design and implement badges to capture various forms of learning throughout the summer in order to make their Summer of Learning program awesome.

For the Chicago Summer of Learning, Mozilla is playing the following roles:

* Advising on overall campaign design.
* Supporting the organizations on badge design and implementation.
* Building and hosting the badge-issuing platform.
* Celebrating with the rest of Chicago this summer!

=== What is Chicago Summer of Learning? ===
Mayor Rahm Emanuel has announced an ambitious initiative to ensure that youth across the city of Chicago will have access to high-quality learning opportunities over the summer. Beginning in the summer of 2013, private and public summer programs will provide educational experiences to youth across the city, recognize that learning and skill development through digital badges, and then connect youth to opportunities for jobs, internships and credit in the school year.

=== How will badges in the Summer of Learning work? ===
This summer, private and public organizations will offer learning programs for youth and issue badges to recognize the learning and skill development that occurs. Youth will earn badges as they participate and complete various programs and learning experiences. These organizational badges will accumulate to city-level badges that will unlock access to special projects and events for youth that span organizations and skill areas, providing exciting and inspiring pathways to continued learning and leveling up. Youth will also have an online profile to track their progress and get recommendations for additional learning options and badges to earn.

=== Napkin Sketch ===
[[Image: ChicagoBadgeDeck1.3.001.png]]

=== Program Workshop ===

Downloadable here: https://wiki.mozilla.org/images/2/22/CSOLWorksheet.pdf

=== Roadmap ===

In progress roadmap can be found here: https://openbadges.etherpad.mozilla.org/chicago-badges-roadmap

==== JANUARY 2013 ====
* Badges - Programmatic Design / Recruitment (Erin)
** Recruit orgs
** Define categories and top level badges
** Develop the framework / model for the badge system
*** Agree on highlevel set of badges and 'flow'
*** Decide if we are capping org badges or allowing more flexibility for them to create more badges

* Tech - Requirements (Chris McAvoy)
** Summer of Learning site:
*** Decide on ownership and objectives
** OpenBadger:
*** Gather tech requirements
** Data Integration Implementation
*** Planning / Requirements (Akili, Melissa)

* Communications - Mayor's office working on a
* Partners - for challenges, funding) (Connie)

==== FEBRUARY 2013 ====
* Badges - Org Specific Badge Build out
** Feb 5th meeting with the organizations to kick off the badge design
** Org submissions of their badges are due mid Feb
** Review of the badges, sorting against the categories
** Design the games, pathways and artifacts
*** Work with orgs to determine the challenges / artifacts
*** Plug in additional online opportunities for learning (i.e. Mozilla Webmaker, Girl Scouts, etc.)
*** Hire and onramp Chicago-based Badge system designer
*** Finalize the top city-level badges (criteria and design)

* Tech - Wireframing and Initial Development
** Summer of Learning site:
***Hire firm / developer to build the site (if needed)
***Wireframing and initial designs
*** Begin website development
** OpenBadger:
*** Hire Open Badger developer
*** Break tech requirements into discreet tasks
*** Define development sprint cycle workflow

==== MARCH 2013 ====
2nd meeting: March 14th, 1pm-5pm CT, Sheraton
Connie request: invited to DML conference, too

* Badges - Badge Design and Finalization
** Finalize the org-specific badges, or the framework to support them on design
** Finalize the challenges / artifacts
** Finalize the pathways (how badges will hook together)
** Badge graphic design
* Tech - Development
** Summer of Learning site:
*** Website development
**** Several reviews/iteration
** OpenBadger:
*** Continued development
*** Staging launch (end of month)
*** QA / Testing

==== APRIL 2013 ====

* Badges - Badge Creation and Build Out
** Build out badges in OpenBadger
** Integration of badges into program websites
** Production of offline badges

* Tech - Staging / production launches
** Summer of Learning site:
*** Staging launch early in the month
*** Production launch of site end of the month
** OpenBadger:
*** Continued development
***Bug fixing / final QA
*** Production Launch (end of month)

==== MAY 2013 ====
* Badges - QA and testing
**Delivery of offline badges
** Testing / QA of badges
** Planning for end of summer showcase events
** Communication campaign to youth and parents
*** Pathcrafting in schools?

* Tech
** Maintenance / Bug fixing

==== JUNE 2013 ====

* Badges - Launch, first earners
** LAUNCH, people earning badges

* Tech:
** Maintenance / Bug fixing

=== Badge submission form ===

http://openbadges.org/chicago

=== Technical FAQ ===

Can be found here: https://wiki.mozilla.org/Badges/chicago/techFAQ

=== Important Dates ===

==== February 18, 2013 – Badge Submissions Due ====
Badge idea submissions due – please submit your ideas for 1-5 badges* for your program through the form here: http://openbadges.org/chicago
Note: If you’d like to have more than 5 badges, let us know at badges@mozillafoundation.org and we’ll work with you on the best solution.

==== March 14, 2013 – Program Meeting ====
1-5pm CT, Sheraton Towers Hotel, Chicago
Please send 1-2 reps from your organization to this meeting to discuss the badges and opportunities for cross-organization connections and projects.
Stick around after the meeting for the DML Conference Science Fair (6-8pm), where you’ll see examples of badge systems from other organizations like yours around the country!

Badges/chicago

2013-02-05T14:19:42Z

Threeqube: /* Napkin Sketch */

== Chicago Summer of Learning Badges Program ==
Mozilla is advising the city of Chicago and Chicago-based organizations to design and implement badges to capture various forms of learning throughout the summer in order to make their Summer of Learning program awesome.

For the Chicago Summer of Learning, Mozilla is playing the following roles:

* Advising on overall campaign design.
* Supporting the organizations on badge design and implementation.
* Building and hosting the badge-issuing platform.
* Celebrating with the rest of Chicago this summer!

=== What is Chicago Summer of Learning? ===
Mayor Rahm Emanuel has announced an ambitious initiative to ensure that youth across the city of Chicago will have access to high-quality learning opportunities over the summer. Beginning in the summer of 2013, private and public summer programs will provide educational experiences to youth across the city, recognize that learning and skill development through digital badges, and then connect youth to opportunities for jobs, internships and credit in the school year.

=== How will badges in the Summer of Learning work? ===
This summer, private and public organizations will offer learning programs for youth and issue badges to recognize the learning and skill development that occurs. Youth will earn badges as they participate and complete various programs and learning experiences. These organizational badges will accumulate to city-level badges that will unlock access to special projects and events for youth that span organizations and skill areas, providing exciting and inspiring pathways to continued learning and leveling up. Youth will also have an online profile to track their progress and get recommendations for additional learning options and badges to earn.

=== Napkin Sketch ===
[[Image: ChicagoBadgeDeck1.3.001.png]

=== Program Workshop ===

Downloadable here: https://wiki.mozilla.org/images/2/22/CSOLWorksheet.pdf

=== Roadmap ===

In progress roadmap can be found here: https://openbadges.etherpad.mozilla.org/chicago-badges-roadmap

==== JANUARY 2013 ====
* Badges - Programmatic Design / Recruitment (Erin)
** Recruit orgs
** Define categories and top level badges
** Develop the framework / model for the badge system
*** Agree on highlevel set of badges and 'flow'
*** Decide if we are capping org badges or allowing more flexibility for them to create more badges

* Tech - Requirements (Chris McAvoy)
** Summer of Learning site:
*** Decide on ownership and objectives
** OpenBadger:
*** Gather tech requirements
** Data Integration Implementation
*** Planning / Requirements (Akili, Melissa)

* Communications - Mayor's office working on a
* Partners - for challenges, funding) (Connie)

==== FEBRUARY 2013 ====
* Badges - Org Specific Badge Build out
** Feb 5th meeting with the organizations to kick off the badge design
** Org submissions of their badges are due mid Feb
** Review of the badges, sorting against the categories
** Design the games, pathways and artifacts
*** Work with orgs to determine the challenges / artifacts
*** Plug in additional online opportunities for learning (i.e. Mozilla Webmaker, Girl Scouts, etc.)
*** Hire and onramp Chicago-based Badge system designer
*** Finalize the top city-level badges (criteria and design)

* Tech - Wireframing and Initial Development
** Summer of Learning site:
***Hire firm / developer to build the site (if needed)
***Wireframing and initial designs
*** Begin website development
** OpenBadger:
*** Hire Open Badger developer
*** Break tech requirements into discreet tasks
*** Define development sprint cycle workflow

==== MARCH 2013 ====
2nd meeting: March 14th, 1pm-5pm CT, Sheraton
Connie request: invited to DML conference, too

* Badges - Badge Design and Finalization
** Finalize the org-specific badges, or the framework to support them on design
** Finalize the challenges / artifacts
** Finalize the pathways (how badges will hook together)
** Badge graphic design
* Tech - Development
** Summer of Learning site:
*** Website development
**** Several reviews/iteration
** OpenBadger:
*** Continued development
*** Staging launch (end of month)
*** QA / Testing

==== APRIL 2013 ====

* Badges - Badge Creation and Build Out
** Build out badges in OpenBadger
** Integration of badges into program websites
** Production of offline badges

* Tech - Staging / production launches
** Summer of Learning site:
*** Staging launch early in the month
*** Production launch of site end of the month
** OpenBadger:
*** Continued development
***Bug fixing / final QA
*** Production Launch (end of month)

==== MAY 2013 ====
* Badges - QA and testing
**Delivery of offline badges
** Testing / QA of badges
** Planning for end of summer showcase events
** Communication campaign to youth and parents
*** Pathcrafting in schools?

* Tech
** Maintenance / Bug fixing

==== JUNE 2013 ====

* Badges - Launch, first earners
** LAUNCH, people earning badges

* Tech:
** Maintenance / Bug fixing

=== Badge submission form ===

http://openbadges.org/chicago

=== Technical FAQ ===

Can be found here: https://wiki.mozilla.org/Badges/chicago/techFAQ

=== Important Dates ===

==== February 18, 2013 – Badge Submissions Due ====
Badge idea submissions due – please submit your ideas for 1-5 badges* for your program through the form here: http://openbadges.org/chicago
Note: If you’d like to have more than 5 badges, let us know at badges@mozillafoundation.org and we’ll work with you on the best solution.

==== March 14, 2013 – Program Meeting ====
1-5pm CT, Sheraton Towers Hotel, Chicago
Please send 1-2 reps from your organization to this meeting to discuss the badges and opportunities for cross-organization connections and projects.
Stick around after the meeting for the DML Conference Science Fair (6-8pm), where you’ll see examples of badge systems from other organizations like yours around the country!

File:ChicagoBadgeDeck1.3.001.png

2013-02-05T14:13:46Z

Threeqube:

Badges/chicago/techFAQ

2013-02-04T22:54:14Z

Threeqube: /* Will my organization have to host anything? */

== Technical FAQ ==

=== What is this? ===
This is a list of frequently asked questions about the technical requirements for the Chicago Summer of Learning badging program.

=== Who is this for? ===
This is for organizations that are planning on issuing badges along with their program this summer. It is written with a non-technical user in mind, but can act as a solid jumping off point for a more technical user. Additional deeper technical documents are referenced in the “where do I go from here?” question.

=== Who is Mozilla? ===
Mozilla is a non-profit company that cares about protecting the open Web and helping people benefit from it. You might know us from our open source browser, Firefox. Mozilla is leading the Open Badges project, which is exploring an alternative credentialing system through digital badges. We’ve built the standard and technical plumbing to allow badges to work together for the learner. For the Chicago Summer of Learning, Mozilla is playing the following roles:

* Advising on overall campaign design.
* Supporting the organizations on badge design and implementation.
* Building and hosting the badge-issuing platform.
* Celebrating with the rest of Chicago this summer!

=== Help me with definitions... ===

There’s a handful of words that will come up often in the technical implementation of an open badge system,
# Issuer - the issuer is the organization that awards a badge. Each participating organization in the summer of learning will be considered an open badge issuer.
# Learner - the person that earns the open badge.
# Open Badge - a 90x90 PNG graphic, and set of metadata that aligns with the Open Badge specification. The technical requirements of the badge will be taken care of by Mozilla, unless an open badge issuer wants to build their own issuing platform.
# Open Badge Issuing Platform - software that allows an issuer to issue an open badge to a learner. Mozilla’s open badge issuing platform is called OpenBadger. All participating organizations in the Summer of Learning will have access to OpenBadger.
# Open Badges Infrastructure (OBI) - The OBI is the ‘plumbing’ that allows badges to be interoperable, and us to build an alternative credentialing system at an ecosystem level. It includes the badge metadata specification, APIs for pushing badges in and pulling badges out and a set of badge repositories called the Badge Backpacks. It is an open source project, hosted at http://github.com/mozilla/openbadges
# Badge Backpack - A repository and management interface for each learner to use to collect open badges from multiple issuers, create and publish groups of badges, and share badges. The Mozilla hosted Badge Backpacks are at http://beta.openbadges.org
# Displayer - A website that allows their users to display badges they’ve earned and collected in their backpack.
# Criteria Page - A web page that describes what a learner needs to do to earn a particular badge. For more information, see the question below, “How do I create a Criteria Page?”

=== Will my organization have to host anything? ===
No, Mozilla will coordinate hosting open badge issuing platforms. However, if you’re capable of hosting an open badge issuing platform, and want the flexibility that provides, there’s no reason not to. Talk to us: support@openbadges.org

=== How will badges be delivered or issued? ===
Using the OpenBadger issuing platform, badges can be be delivered in one of three ways,
# Through your website. We can support online-issued badges through a web API that can integrate with your existing website. The API has existing javascript libraries that make it easy to integrate. (Don’t worry, we’ll help you with this)
# Through your own email system using a claim code. The learner will receive an email from you with a web location to visit and a claim code to enter on the site to claim a badge.
# A printed paper with a web location to visit and a claim code to enter to claim a badge.

=== What data can be collected? ===
Each badge has a defined set of metadata with it that communicates who issued it, when it was issued, what the earner had to do to get the badge, and optional evidence. The Open Badge Infrastructure stores this information with the badge, as well as a minimum amount of personally identifiable information (a verified email address) to verify their identity. There are opportunities to collect additional data from learners through deeper integration with the OpenBadger API, but will have to be worked out on a case by case basis.

=== What’s the badge metadata specification? ===
The Open Badge specification is simply a set of required and optional information that is included with every badge issued. It includes issuer, issue date, criteria URL, evidence URL, expiration, and other information. It is an open standard for badges that ensures that all badges, regardless of type or issuer, are interoperable.

=== What information do I need to include with my badge? ===
You don’t need to worry about this yet, we’ll help you, but eventually you are going to define the criteria information for the badge (i.e. what someone has to do to earn the badge), as well as decide if there is an expiration date on the badge and if you’d like the badge to link to particular artifacts for evidence or not. Again, we’ll help you.

=== How do I create a criteria page? ===
OpenBadger, the issuing tool we’ll be using for the Chicago badges, will generate and host the criteria page for you based on the criteria information you will provide us over the next couple of months. If your organization has a website and you’d like to host your own criteria pages, talk to us: support@openbadges.org

=== What does the Issuer API do? ===
Let’s you connect your website to the Open Badge Infrastructure so that your users can push their badges to their Badge Backpacks. If your organization has a website, we’ll help you work with the API. If you don’t have a website and just plan to use offline or email issuing, you won’t need to use the Issuer API.

=== How do earners display their badges? ===
Earners can view their badges in their Badge Backpack and share out individual or groups of badges from there. There will also be a Summer of Learning website, where earners can see and share their badges and find additional badges to earn.

=== Where will I go for technical support? ===
Mozilla is helping to drive the technical components of this campaign. We will help you get your badges created and up and running over the coming months. You can always reach us at support@openbadges.org or on the #badges channel of irc.mozilla.org.

=== Where do I go from here? ===
==== General Information & Community Involvement ====

*Open Badges website: http://openbadges.org/en-US/
* Open Badges wiki: https://wiki.mozilla.org/Badges
* All things badges blog: http://openbadges.tumblr.com/
* Weekly Wednesday community calls: https://openbadges.etherpad.mozilla.org/openbadges-community-2
* Google group for dialogue: https://groups.google.com/forum/?fromgroups#!forum/openbadges

==== Technical Resources ====
* Open Badges github repository: https://github.com/mozilla/openbadges
* README: https://github.com/mozilla/openbadges#mozilla-open-badges
* Badge assertion / metadata specification: https://github.com/mozilla/openbadges/wiki/Assertions
* Issuer API: https://github.com/mozilla/openbadges/wiki/Issuer-API
* Two articles on issuing a minimal badge
** http://weblog.lonelylion.com/2012/03/22/earn-a-badge-issue-a-badge/
** http://billymeinke.wordpress.com/2012/05/24/open-badges-want-to-make-your-own-badges-by-hand-heres-how/
* Google group for developers: https://groups.google.com/forum/#!forum/openbadges-dev

Badges/chicago/techFAQ

2013-02-04T22:53:39Z

Threeqube: /* Where will I go for technical support? */

== Technical FAQ ==

=== What is this? ===
This is a list of frequently asked questions about the technical requirements for the Chicago Summer of Learning badging program.

=== Who is this for? ===
This is for organizations that are planning on issuing badges along with their program this summer. It is written with a non-technical user in mind, but can act as a solid jumping off point for a more technical user. Additional deeper technical documents are referenced in the “where do I go from here?” question.

=== Who is Mozilla? ===
Mozilla is a non-profit company that cares about protecting the open Web and helping people benefit from it. You might know us from our open source browser, Firefox. Mozilla is leading the Open Badges project, which is exploring an alternative credentialing system through digital badges. We’ve built the standard and technical plumbing to allow badges to work together for the learner. For the Chicago Summer of Learning, Mozilla is playing the following roles:

* Advising on overall campaign design.
* Supporting the organizations on badge design and implementation.
* Building and hosting the badge-issuing platform.
* Celebrating with the rest of Chicago this summer!

=== Help me with definitions... ===

There’s a handful of words that will come up often in the technical implementation of an open badge system,
# Issuer - the issuer is the organization that awards a badge. Each participating organization in the summer of learning will be considered an open badge issuer.
# Learner - the person that earns the open badge.
# Open Badge - a 90x90 PNG graphic, and set of metadata that aligns with the Open Badge specification. The technical requirements of the badge will be taken care of by Mozilla, unless an open badge issuer wants to build their own issuing platform.
# Open Badge Issuing Platform - software that allows an issuer to issue an open badge to a learner. Mozilla’s open badge issuing platform is called OpenBadger. All participating organizations in the Summer of Learning will have access to OpenBadger.
# Open Badges Infrastructure (OBI) - The OBI is the ‘plumbing’ that allows badges to be interoperable, and us to build an alternative credentialing system at an ecosystem level. It includes the badge metadata specification, APIs for pushing badges in and pulling badges out and a set of badge repositories called the Badge Backpacks. It is an open source project, hosted at http://github.com/mozilla/openbadges
# Badge Backpack - A repository and management interface for each learner to use to collect open badges from multiple issuers, create and publish groups of badges, and share badges. The Mozilla hosted Badge Backpacks are at http://beta.openbadges.org
# Displayer - A website that allows their users to display badges they’ve earned and collected in their backpack.
# Criteria Page - A web page that describes what a learner needs to do to earn a particular badge. For more information, see the question below, “How do I create a Criteria Page?”

=== Will my organization have to host anything? ===
No, Mozilla will coordinate hosting open badge issuing platforms. However, if you’re capable of hosting an open badge issuing platform, and want the flexibility that provides, there’s no reason not to. Talk to us: badges@mozillafoundation.org

=== How will badges be delivered or issued? ===
Using the OpenBadger issuing platform, badges can be be delivered in one of three ways,
# Through your website. We can support online-issued badges through a web API that can integrate with your existing website. The API has existing javascript libraries that make it easy to integrate. (Don’t worry, we’ll help you with this)
# Through your own email system using a claim code. The learner will receive an email from you with a web location to visit and a claim code to enter on the site to claim a badge.
# A printed paper with a web location to visit and a claim code to enter to claim a badge.

=== What data can be collected? ===
Each badge has a defined set of metadata with it that communicates who issued it, when it was issued, what the earner had to do to get the badge, and optional evidence. The Open Badge Infrastructure stores this information with the badge, as well as a minimum amount of personally identifiable information (a verified email address) to verify their identity. There are opportunities to collect additional data from learners through deeper integration with the OpenBadger API, but will have to be worked out on a case by case basis.

=== What’s the badge metadata specification? ===
The Open Badge specification is simply a set of required and optional information that is included with every badge issued. It includes issuer, issue date, criteria URL, evidence URL, expiration, and other information. It is an open standard for badges that ensures that all badges, regardless of type or issuer, are interoperable.

=== What information do I need to include with my badge? ===
You don’t need to worry about this yet, we’ll help you, but eventually you are going to define the criteria information for the badge (i.e. what someone has to do to earn the badge), as well as decide if there is an expiration date on the badge and if you’d like the badge to link to particular artifacts for evidence or not. Again, we’ll help you.

=== How do I create a criteria page? ===
OpenBadger, the issuing tool we’ll be using for the Chicago badges, will generate and host the criteria page for you based on the criteria information you will provide us over the next couple of months. If your organization has a website and you’d like to host your own criteria pages, talk to us: support@openbadges.org

=== What does the Issuer API do? ===
Let’s you connect your website to the Open Badge Infrastructure so that your users can push their badges to their Badge Backpacks. If your organization has a website, we’ll help you work with the API. If you don’t have a website and just plan to use offline or email issuing, you won’t need to use the Issuer API.

=== How do earners display their badges? ===
Earners can view their badges in their Badge Backpack and share out individual or groups of badges from there. There will also be a Summer of Learning website, where earners can see and share their badges and find additional badges to earn.

=== Where will I go for technical support? ===
Mozilla is helping to drive the technical components of this campaign. We will help you get your badges created and up and running over the coming months. You can always reach us at support@openbadges.org or on the #badges channel of irc.mozilla.org.

=== Where do I go from here? ===
==== General Information & Community Involvement ====

*Open Badges website: http://openbadges.org/en-US/
* Open Badges wiki: https://wiki.mozilla.org/Badges
* All things badges blog: http://openbadges.tumblr.com/
* Weekly Wednesday community calls: https://openbadges.etherpad.mozilla.org/openbadges-community-2
* Google group for dialogue: https://groups.google.com/forum/?fromgroups#!forum/openbadges

==== Technical Resources ====
* Open Badges github repository: https://github.com/mozilla/openbadges
* README: https://github.com/mozilla/openbadges#mozilla-open-badges
* Badge assertion / metadata specification: https://github.com/mozilla/openbadges/wiki/Assertions
* Issuer API: https://github.com/mozilla/openbadges/wiki/Issuer-API
* Two articles on issuing a minimal badge
** http://weblog.lonelylion.com/2012/03/22/earn-a-badge-issue-a-badge/
** http://billymeinke.wordpress.com/2012/05/24/open-badges-want-to-make-your-own-badges-by-hand-heres-how/
* Google group for developers: https://groups.google.com/forum/#!forum/openbadges-dev

Badges/chicago/techFAQ

2013-02-04T22:52:03Z

Threeqube: /* How do I create a criteria page? */

== Technical FAQ ==

=== What is this? ===
This is a list of frequently asked questions about the technical requirements for the Chicago Summer of Learning badging program.

=== Who is this for? ===
This is for organizations that are planning on issuing badges along with their program this summer. It is written with a non-technical user in mind, but can act as a solid jumping off point for a more technical user. Additional deeper technical documents are referenced in the “where do I go from here?” question.

=== Who is Mozilla? ===
Mozilla is a non-profit company that cares about protecting the open Web and helping people benefit from it. You might know us from our open source browser, Firefox. Mozilla is leading the Open Badges project, which is exploring an alternative credentialing system through digital badges. We’ve built the standard and technical plumbing to allow badges to work together for the learner. For the Chicago Summer of Learning, Mozilla is playing the following roles:

* Advising on overall campaign design.
* Supporting the organizations on badge design and implementation.
* Building and hosting the badge-issuing platform.
* Celebrating with the rest of Chicago this summer!

=== Help me with definitions... ===

There’s a handful of words that will come up often in the technical implementation of an open badge system,
# Issuer - the issuer is the organization that awards a badge. Each participating organization in the summer of learning will be considered an open badge issuer.
# Learner - the person that earns the open badge.
# Open Badge - a 90x90 PNG graphic, and set of metadata that aligns with the Open Badge specification. The technical requirements of the badge will be taken care of by Mozilla, unless an open badge issuer wants to build their own issuing platform.
# Open Badge Issuing Platform - software that allows an issuer to issue an open badge to a learner. Mozilla’s open badge issuing platform is called OpenBadger. All participating organizations in the Summer of Learning will have access to OpenBadger.
# Open Badges Infrastructure (OBI) - The OBI is the ‘plumbing’ that allows badges to be interoperable, and us to build an alternative credentialing system at an ecosystem level. It includes the badge metadata specification, APIs for pushing badges in and pulling badges out and a set of badge repositories called the Badge Backpacks. It is an open source project, hosted at http://github.com/mozilla/openbadges
# Badge Backpack - A repository and management interface for each learner to use to collect open badges from multiple issuers, create and publish groups of badges, and share badges. The Mozilla hosted Badge Backpacks are at http://beta.openbadges.org
# Displayer - A website that allows their users to display badges they’ve earned and collected in their backpack.
# Criteria Page - A web page that describes what a learner needs to do to earn a particular badge. For more information, see the question below, “How do I create a Criteria Page?”

=== Will my organization have to host anything? ===
No, Mozilla will coordinate hosting open badge issuing platforms. However, if you’re capable of hosting an open badge issuing platform, and want the flexibility that provides, there’s no reason not to. Talk to us: badges@mozillafoundation.org

=== How will badges be delivered or issued? ===
Using the OpenBadger issuing platform, badges can be be delivered in one of three ways,
# Through your website. We can support online-issued badges through a web API that can integrate with your existing website. The API has existing javascript libraries that make it easy to integrate. (Don’t worry, we’ll help you with this)
# Through your own email system using a claim code. The learner will receive an email from you with a web location to visit and a claim code to enter on the site to claim a badge.
# A printed paper with a web location to visit and a claim code to enter to claim a badge.

=== What data can be collected? ===
Each badge has a defined set of metadata with it that communicates who issued it, when it was issued, what the earner had to do to get the badge, and optional evidence. The Open Badge Infrastructure stores this information with the badge, as well as a minimum amount of personally identifiable information (a verified email address) to verify their identity. There are opportunities to collect additional data from learners through deeper integration with the OpenBadger API, but will have to be worked out on a case by case basis.

=== What’s the badge metadata specification? ===
The Open Badge specification is simply a set of required and optional information that is included with every badge issued. It includes issuer, issue date, criteria URL, evidence URL, expiration, and other information. It is an open standard for badges that ensures that all badges, regardless of type or issuer, are interoperable.

=== What information do I need to include with my badge? ===
You don’t need to worry about this yet, we’ll help you, but eventually you are going to define the criteria information for the badge (i.e. what someone has to do to earn the badge), as well as decide if there is an expiration date on the badge and if you’d like the badge to link to particular artifacts for evidence or not. Again, we’ll help you.

=== How do I create a criteria page? ===
OpenBadger, the issuing tool we’ll be using for the Chicago badges, will generate and host the criteria page for you based on the criteria information you will provide us over the next couple of months. If your organization has a website and you’d like to host your own criteria pages, talk to us: support@openbadges.org

=== What does the Issuer API do? ===
Let’s you connect your website to the Open Badge Infrastructure so that your users can push their badges to their Badge Backpacks. If your organization has a website, we’ll help you work with the API. If you don’t have a website and just plan to use offline or email issuing, you won’t need to use the Issuer API.

=== How do earners display their badges? ===
Earners can view their badges in their Badge Backpack and share out individual or groups of badges from there. There will also be a Summer of Learning website, where earners can see and share their badges and find additional badges to earn.

=== Where will I go for technical support? ===
Mozilla is helping to drive the technical components of this campaign. We will help you get your badges created and up and running over the coming months. You can always reach us at badges@mozillafoundation.org or on the #badges channel of irc.mozilla.org.

=== Where do I go from here? ===
==== General Information & Community Involvement ====

*Open Badges website: http://openbadges.org/en-US/
* Open Badges wiki: https://wiki.mozilla.org/Badges
* All things badges blog: http://openbadges.tumblr.com/
* Weekly Wednesday community calls: https://openbadges.etherpad.mozilla.org/openbadges-community-2
* Google group for dialogue: https://groups.google.com/forum/?fromgroups#!forum/openbadges

==== Technical Resources ====
* Open Badges github repository: https://github.com/mozilla/openbadges
* README: https://github.com/mozilla/openbadges#mozilla-open-badges
* Badge assertion / metadata specification: https://github.com/mozilla/openbadges/wiki/Assertions
* Issuer API: https://github.com/mozilla/openbadges/wiki/Issuer-API
* Two articles on issuing a minimal badge
** http://weblog.lonelylion.com/2012/03/22/earn-a-badge-issue-a-badge/
** http://billymeinke.wordpress.com/2012/05/24/open-badges-want-to-make-your-own-badges-by-hand-heres-how/
* Google group for developers: https://groups.google.com/forum/#!forum/openbadges-dev