Contribute/Systems: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Added systems and data principles)
Line 9: Line 9:
=== Goal ===
=== Goal ===
Make the business case and gather priorities for the systems to support the 1 Million Mozillians goal. In order to define the scope of the first iteration and deliver it in 2014.
Make the business case and gather priorities for the systems to support the 1 Million Mozillians goal. In order to define the scope of the first iteration and deliver it in 2014.
=== Principles ===
In order for Mozillians to easily access tools and contribute in a way that maximizes impact, we recommend these principles be adapted for all  tools used by Mozilla. This will be a long-term effort.
* '''Unified Identity'''
** Tools should have single source of truth for people data
*** Integration with HRIS
*** mozillians.org already has staff and volunteer information, so it is a good candidate at the single source of tr
** Tools should de-duplicate people information by integrating with a single source of truth
** e.g. Reps: Not integrated with Mozillians.org, lots of duplicate information on two profiles
* '''Unified Authentication and Authorization'''
** Tools should use a single identity platform that provides permissions-based access to tools (like Mozillians.org)
** e.g Reps: add people to the Reps group on mozillians.org to give them permission to use rep.mozilla.org as a Rep
* '''Accessible Metrics'''
** Tools should track each contribution a Mozillian makes and provide it in an accessible way to create a holistic view of contributions
* '''Localization'''
** Tools should be localized so they are accessible to our global community
* '''Education'''
** Tools should teach the user how to use the tool,  answer common usage questions, and have general documentation
* '''Recognition'''
** Tools should recognize the contributions that they enable
* '''Participation'''
** Tools should enable anyone to improve the tool by filing bugs, suggesting ideas and bringing those ideas to life
* '''Content de-duplication'''
** Tools should de-duplicate the content that is created in those tools, making it accessible to other systems
* '''Fun'''
** Tools should be personal and written in the Mozilla voice


==Status of Needed Systems==
==Status of Needed Systems==

Revision as of 09:35, 7 November 2014

Grow mozilla large.png Main | Resources | Working Groups | Get Involved Main Page | Team | Maturity Model | Build Principles


Intro

Community builders need data to measure growth, track volunteer contributions and measure success. The systems track will focus on how Mozilla can retool and instrument our efforts to provide efficient onboarding, management and reward systems as we aim for exponential community growth over the next decade.

Vision

Build the systems that support the growth of One Million Mozillians.

Goal

Make the business case and gather priorities for the systems to support the 1 Million Mozillians goal. In order to define the scope of the first iteration and deliver it in 2014.

Principles

In order for Mozillians to easily access tools and contribute in a way that maximizes impact, we recommend these principles be adapted for all tools used by Mozilla. This will be a long-term effort.

  • Unified Identity
    • Tools should have single source of truth for people data
      • Integration with HRIS
      • mozillians.org already has staff and volunteer information, so it is a good candidate at the single source of tr
    • Tools should de-duplicate people information by integrating with a single source of truth
    • e.g. Reps: Not integrated with Mozillians.org, lots of duplicate information on two profiles
  • Unified Authentication and Authorization
    • Tools should use a single identity platform that provides permissions-based access to tools (like Mozillians.org)
    • e.g Reps: add people to the Reps group on mozillians.org to give them permission to use rep.mozilla.org as a Rep
  • Accessible Metrics
    • Tools should track each contribution a Mozillian makes and provide it in an accessible way to create a holistic view of contributions
  • Localization
    • Tools should be localized so they are accessible to our global community
  • Education
    • Tools should teach the user how to use the tool, answer common usage questions, and have general documentation
  • Recognition
    • Tools should recognize the contributions that they enable
  • Participation
    • Tools should enable anyone to improve the tool by filing bugs, suggesting ideas and bringing those ideas to life
  • Content de-duplication
    • Tools should de-duplicate the content that is created in those tools, making it accessible to other systems
  • Fun
    • Tools should be personal and written in the Mozilla voice

Status of Needed Systems

System Priority Status Platform Owner Resourced Coordination Recommendation
Community Dashboards p1 Under deployment Contribution data source of truth will be Baloo Pierros(CBT) and Anurag(BIDW)
Events Manager p2 Proposal to make a general use version of the Reps events manager
Badge Issuer p3 Live at badges.mozilla.org Django-Badger Webdev Stewards No (Side project of lorchard) Contract with a django developer with some basic frontend skills to tackle redesign, Mozillians integration and a few top enhancements
Matching Service (by task, by project, by mentor, etc) p4 Prototypes live: Matching by project and Matching by task and another Matching by task and Matching by mentor https://github.com/jdm/asknot and https://github.com/jdm/bugsahoy/ Josh Matthews No (side project)
Volunteer Management p5 Exact Target (for communications) + something else to cover other pieces of this

Meetings

The Systems and Data group is regularly meeting to work on action items and advance the goals of the group.

Future meetings

Past meetings


Relevant Links

Retrieved from "https://wiki.mozilla.org/index.php?title=Contribute/Systems&oldid=1031388"