Contribute/Systems: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (update meetings)
(ck's name :))
 
(20 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<noinclude>
{{contribute_nav_bar}}
{{contribute_nav_bar}}


== Intro ==
== 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.
Community builders need data to measure growth, track volunteer contributions, measure success and enable participation. 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 ===
=== Vision ===
Line 8: 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==


{| class="wikitable sortable" border="1"
{| class="wikitable sortable" border="1"
! System !! Priority !! Status !! Platform !! Owner !! Resourced !! Coordination !! Recommendation
! System !! Priority !! Status !! Platform !! Owner !! Resourced
|-
| Community Metrics
| P1
| Under deployment
| Contribution data source of truth will be [[Baloo]]
| Pierros (CBT-MoCo) and Adam (Metrics-MoFo)
| BIDW team supporting integrations.
|-
| Community Dashboards
| P1
| Under deployment. Main dashboard live at http://areweamillionyet.org
| Building custom dashboards on top of Baloo data.
| Pierros (CBT-MoCo) and Adam (Metrics-MoFo)
| No resources assigned
|-
| Participation Tools Toolkit
| P2
| Planning phase.
| A toolkit to enable creation of participation tools by regional or functional communities
| No owner assigned
| No resources assigned
|-
| Leadership Platform
| P1
| Live at http://reps.mozilla.org
| Mozilla Reps Portal
| William Reynolds and Rosana Ardila
| Community Tools team
|-
| Community Discovery Platform
| P1
| Live at http://mozillians.org
| Mozillians.org
| Pierros Papadeas
| Community Tools team
|-
| Pathways Tool
| P2
| Planning phase
| A simple tool to map pathways across different contribution areas of Mozilla.
| Pierros Papadeas
| No resources assigned
|-
| Volunteer entry point
| P1
| Live at https://mozilla.org/contribute
| An common entry point for all contribution areas.
| Larissa Shapiro (CBT) & Jen Brench (Engagement)
| WebProd team
|-
|-
| Events Manager
| Events Manager
| p1
| P2
|  
| PoC deployed at http://events.mozspaces.org/
| Proposal to make a general use version of the [https://reps.mozilla.org/events/ Reps events manager]
| Proposal to make a general use version of the [https://reps.mozilla.org/events/ Reps events manager]
|
| William Quiviger and Pierros Papadeas
|
| No resources assigned
|
|
|-
|-
| Community Dashboards
| Content Platform
| p2
| P2
|
| Live at http://wiki.mozilla.org
| Contributor data source of truth will be Workday & Mozillians / Contribution data source of truth will be [[Blackhole]]
| Mediawiki public mozilla instance. Used by almost all projects within Mozilla.
|
| Christie Koehler
|
| Punctual IT support and CommunityIT
|
|-
|  
| Communications Tool
| P1
| Live at http://lists.mozilla.org
| Email Communications through mailing lists
| Gerv
| IT
|-
| Communications Tool
| P1
| Live at http://discourse.mozilla-community.org/
| Forum like communications open to all community
| Community IT
| Community IT
|-
|-
| Badge Issuer
| Recognition Platform
| p3
| P2
| Live at [http://badges.mozilla.org badges.mozilla.org]
| Live at [http://badges.mozilla.org badges.mozilla.org]
| [https://github.com/lmorchard/django-badger Django-Badger]
| [https://github.com/lmorchard/django-badger Django-Badger]
| Webdev Stewards
| None.
| No (Side project of lorchard)
| No resources assigned
|
| [https://etherpad.mozilla.org/badges-mozilla-org-enhancements 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)
| Matching Service
| p4
| P4
| Prototypes live: [http://whatcanidoformozilla.org/ Matching by project] and [http://www.joshmatthews.net/bugsahoy/ Matching by task] and another [http://oneanddone.balwiki.com/en-US/ Matching by task] and [https://gist.github.com/ygjb/4543418 Matching by mentor]
| Prototypes live: [http://whatcanidoformozilla.org/ Matching by project] and [http://www.joshmatthews.net/bugsahoy/ Matching by task] and another [http://oneanddone.balwiki.com/en-US/ Matching by task] and [https://gist.github.com/ygjb/4543418 Matching by mentor]
| https://github.com/jdm/asknot and https://github.com/jdm/bugsahoy/
| https://github.com/jdm/asknot and https://github.com/jdm/bugsahoy/
| Josh Matthews
| Josh Matthews
| No (side project)
| No resources assigned
|
|-
|
| Moderation Tool
| P3
| Live at http://moderator.mozilla.org
| [https://github.com/mozilla/mozmoderator Django app] with mozillians.org integration
| Pierros Papadeas
| No resources assigned
|-
| Mentoring Tool
| P2
| Under development
| Django app [https://github.com/ygjb/kitherder developed by security team].
| No one
| No resources assigned
|-
|-
| Volunteer Management
| Volunteer Management
| p5
| P3
| Exact Target (for communications) + something else to cover other pieces of this
| Planning phase
|
| Exact Target and possible CRM
|
| TBD
|
|  
|
|}
|}


== Meetings ==
== Meetings ==
The Systems and Data group is regularly meeting to work on action items and advance the goals of the group.
The Systems and Data group is regularly meeting to work on action items and advance the goals of the group.
 
</noinclude>
=== Future meetings ===
=== Future meetings ===
*  
* TBD
=== Past meetings ===
=== Past meetings ===
* [https://cbt.etherpad.mozilla.org/systemsdata-2014-10-03 2014-10-03]
* [https://cbt.etherpad.mozilla.org/systemsdata-2014-09-22 2014-09-22]
* [https://cbt.etherpad.mozilla.org/systemsdata-2014-09-05 2014-09-05]
* [https://cbt.etherpad.mozilla.org/systemsdata-2014-08-22 2014-08-22]
* [https://cbt.etherpad.mozilla.org/systemsdata-2014-08-08 2014-08-08]
* [https://cbt.etherpad.mozilla.org/systemsdata-2014-06-27 2014-06-27]
* [https://cbt.etherpad.mozilla.org/systemsdata-2014-06-13 2014-06-13]
* [https://cbt.etherpad.mozilla.org/systemsdata-2014-05-30 2014-05-30]
* [https://cbt.etherpad.mozilla.org/systemsdata-2014-05-16 2014-05-16]
* [https://cbt.etherpad.mozilla.org/systemsdata-2014-04-25 2014-04-25]
* [https://cbt.etherpad.mozilla.org/systemsdata-2014-04-11 2014-04-11]
* [https://cbt.etherpad.mozilla.org/systemsdata-2014-03-28 2014-03-28]
* [https://cbt.etherpad.mozilla.org/systemsdata-2014-03-14 2014-03-14]
* [https://cbt.etherpad.mozilla.org/systemsdata-2014-02-28 2014-02-28]
* [https://cbt.etherpad.mozilla.org/systemsdata-2014-02-14 2014-02-14]
* [https://cbt.etherpad.mozilla.org/systemsdata-2014-02-14 2014-02-14]
* [https://cbt.etherpad.mozilla.org/systemsdata-2014-01-31 2014-01-31]
* [https://cbt.etherpad.mozilla.org/systemsdata-2014-01-31 2014-01-31]
* [https://cbt.etherpad.mozilla.org/systemsdata-2014-01-17 2014-01-17]
* [https://cbt.etherpad.mozilla.org/systemsdata-2014-01-17 2014-01-17]
* [https://etherpad.mozilla.org/cbt-working-group-systems-data Notes from Working Group meetings in 2013]
* [https://etherpad.mozilla.org/cbt-working-group-systems-data Notes from Working Group meetings in 2013]
<noinclude>


==Relevant Links==
==Relevant Links==
Line 75: Line 185:


* https://etherpad.mozilla.org/volunteer-recruiting-recognition-requirements
* https://etherpad.mozilla.org/volunteer-recruiting-recognition-requirements
[[Category:Contribute]]
[[Category:Systems]]
</noinclude>

Latest revision as of 01:02, 4 December 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, measure success and enable participation. 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
Community Metrics P1 Under deployment Contribution data source of truth will be Baloo Pierros (CBT-MoCo) and Adam (Metrics-MoFo) BIDW team supporting integrations.
Community Dashboards P1 Under deployment. Main dashboard live at http://areweamillionyet.org Building custom dashboards on top of Baloo data. Pierros (CBT-MoCo) and Adam (Metrics-MoFo) No resources assigned
Participation Tools Toolkit P2 Planning phase. A toolkit to enable creation of participation tools by regional or functional communities No owner assigned No resources assigned
Leadership Platform P1 Live at http://reps.mozilla.org Mozilla Reps Portal William Reynolds and Rosana Ardila Community Tools team
Community Discovery Platform P1 Live at http://mozillians.org Mozillians.org Pierros Papadeas Community Tools team
Pathways Tool P2 Planning phase A simple tool to map pathways across different contribution areas of Mozilla. Pierros Papadeas No resources assigned
Volunteer entry point P1 Live at https://mozilla.org/contribute An common entry point for all contribution areas. Larissa Shapiro (CBT) & Jen Brench (Engagement) WebProd team
Events Manager P2 PoC deployed at http://events.mozspaces.org/ Proposal to make a general use version of the Reps events manager William Quiviger and Pierros Papadeas No resources assigned
Content Platform P2 Live at http://wiki.mozilla.org Mediawiki public mozilla instance. Used by almost all projects within Mozilla. Christie Koehler Punctual IT support and CommunityIT
Communications Tool P1 Live at http://lists.mozilla.org Email Communications through mailing lists Gerv IT
Communications Tool P1 Live at http://discourse.mozilla-community.org/ Forum like communications open to all community Community IT Community IT
Recognition Platform P2 Live at badges.mozilla.org Django-Badger None. No resources assigned
Matching Service 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 resources assigned
Moderation Tool P3 Live at http://moderator.mozilla.org Django app with mozillians.org integration Pierros Papadeas No resources assigned
Mentoring Tool P2 Under development Django app developed by security team. No one No resources assigned
Volunteer Management P3 Planning phase Exact Target and possible CRM TBD

Meetings

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

Future meetings

  • TBD

Past meetings


Relevant Links

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