Mozillians/RoadMap: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
(rolled over Q4 to Q1)
 
(16 intermediate revisions by 2 users not shown)
Line 1: Line 1:
The site will be built over a series of phases. Our current thinking about milestones is below:
<section begin=summary />{{RoadmapSummary
|icon=Phonebook-114.png
|pagelocation=Mozillians/RoadMap
|pagetitle=Mozillians 2014 Strategy & Roadmap
|owner=Pierros Papadeas
|updated=January 10, 2014
|description=We amplify the ability for Mozillians to contribute and connect with each other through the use of tools. We're building tools to help all Mozillians grow the number of contributions and contributors in the project. [[Mozillians/Vision|Learn more]]
}}<section end=summary />


* <strike>[[Mozillians/Milestones/Phase1|Phase1 Roadmap]] (initial launch)</strike>
= Roadmap =
* [[Mozillians/Milestones/Phase2|Phase2 Roadmap]] (major enhancements and redesign)
* [[Mozillians/Milestones/Phase3|Phase3 Roadmap]] (features to better recognize Mozillians' efforts)


A full 2013 roadmap will be added soon.
== 2015Q1 ==
Mozillians.org moving forward needs to comply with Systems and Data principles as outlined by the Systems and Data working group. Those can be found [https://cbt.etherpad.mozilla.org/systemsdataprinciples here].
 
=== Mozillians.org as the source of truth about people data ===
Building on top of the core functionality of mozillians.org (phonebook) we need to make mozillians.org the one-stop place for all Mozillians to learn about fellow Mozillians.
* [P1] Multiple emails per profile
* [P2] Expose location information in search field
* [P3] People lists using language fields
 
=== Mozillians.org as a service to other Mozilla properties ===
Mozillians.org should be able to provide all people specific (identity) and discovery functionality to other Mozilla systems and websites in an easy, secure and documented way.
* [P1] Democratize API access, deploy API v2
* [P2] Use secondary emails on APIv2
* [P3] Ability to login using multiple emails.
 
=== Mozillians.org as a stable platform ===
Years of development of mozillians.org platform has created a considerable amount of development debt. In order to create a stable development environment we need to invest in updating our core libraries and apps to enable further development of features.
* [P1] Update to at least pyelasticsearch 0.6 and elasticutils 0.8
* [P2] Update documentation using docker
* [P3] Update factory fixtures to match production data types

Latest revision as of 13:54, 9 February 2015

Phonebook-114.png Mozillians 2014 Strategy & Roadmap
Owner: Pierros Papadeas Updated: 2015-02-9
We amplify the ability for Mozillians to contribute and connect with each other through the use of tools. We're building tools to help all Mozillians grow the number of contributions and contributors in the project. Learn more

Roadmap

2015Q1

Mozillians.org moving forward needs to comply with Systems and Data principles as outlined by the Systems and Data working group. Those can be found here.

Mozillians.org as the source of truth about people data

Building on top of the core functionality of mozillians.org (phonebook) we need to make mozillians.org the one-stop place for all Mozillians to learn about fellow Mozillians.

  • [P1] Multiple emails per profile
  • [P2] Expose location information in search field
  • [P3] People lists using language fields

Mozillians.org as a service to other Mozilla properties

Mozillians.org should be able to provide all people specific (identity) and discovery functionality to other Mozilla systems and websites in an easy, secure and documented way.

  • [P1] Democratize API access, deploy API v2
  • [P2] Use secondary emails on APIv2
  • [P3] Ability to login using multiple emails.

Mozillians.org as a stable platform

Years of development of mozillians.org platform has created a considerable amount of development debt. In order to create a stable development environment we need to invest in updating our core libraries and apps to enable further development of features.

  • [P1] Update to at least pyelasticsearch 0.6 and elasticutils 0.8
  • [P2] Update documentation using docker
  • [P3] Update factory fixtures to match production data types