CloudServices/Roadmaps/Sagrada: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(17 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{draft}}


==Introduction==
== Prologue ==
Work up to this point has been focused on building out and refining our needs as they arise. While still maintaining a focus on products we support and products we are working towards launching (which will always have priority), our priorities in Q4 and beyond shift towards building generic support for applications that third parties may wish to build, both using our infrastructure and on our hardware. This can be done in pieces - most of them exist independently from each other, and have inherent value.


Each of the categories below represents a large project, and each of those projects will contain sequences of their own. The order is approximately in terms of importance and how well we are ready to take on the project, and the order may change as internal needs arise.
Project Sagrada is really a set of projects, tied together as a set of capabilities for an app platform.  For more on the project's initial goals, please see https://blog.mozilla.com/services/2011/09/15/introducing-project-sagrada/
 
'''Please Note:'''
 
In any project consisting of a large number of relatively orthogonal product areas, it's hard to build a useful single-timeline roadmap. Instead, we are working on breaking areas down into individual roadmaps covering specific elements of the platform.


==Sequence==
==Sequence==
This table has all the current planned products for Core Services.  The status field should be filled "Untriaged" for new items, "Not started", "In Progress", "Blocked", and "Completed". The owner can be TBD if no has claimed it.  
This table has all the current planned products that are a part of this project.  The status field should be filled "Untriaged" for new items, "Not started", "In Progress", "Blocked", and "Completed". The owner can be TBD if no has claimed it.  


{| class="fullwidth-table" style="width: 950px"
{| class="fullwidth-table" style="width: 950px"
Line 18: Line 22:
| 2011
| 2011
| Feature
| Feature
| Application Credentialing  
| [[Services/AppKeys|Application Credentialing]]
| Toby
| Toby
| In Progress
| In Progress
Line 24: Line 28:
| 2011
| 2011
| Feature
| Feature
| Deployment, Pipelining and Change Management
| [[Deployment, Pipelining and Change Management]]
| Tarek
| TBD
| In Progress
| Not Started
|-
|-
| 2011
| 2011
Line 32: Line 36:
| Logging and Metrics
| Logging and Metrics
| Rob
| Rob
| In Progress
|-
| 2011
| Feature
| Because Racecar
| Philipp
| In Progress
| In Progress
|-
|-
Line 48: Line 46:
| 2011
| 2011
| Feature
| Feature
| KV Storage
| [[Services/KeyValueStorage|KV Storage]]
| TBD
| TBD
| Not Started
| Not Started
Line 54: Line 52:
| 2011
| 2011
| Feature
| Feature
| Message Queueing
| [[Services/MessageQueuing|Message Queueing]]
| TBD
| Ben
| Not Started
| In Progress
|-
|-
| TBD
| TBD
Line 79: Line 77:
| Feature
| Feature
| Automated Caching
| Automated Caching
| TBD
| Not Started
|-
| TBD
| Feature
| Email
| TBD
| TBD
| Not Started
| Not Started

Latest revision as of 19:54, 19 November 2013

Draft-template-image.png THIS PAGE IS A WORKING DRAFT Pencil-emoji U270F-gray.png
The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly.
If you have any questions or ideas, please add them as a new topic on the discussion page.

Prologue

Project Sagrada is really a set of projects, tied together as a set of capabilities for an app platform. For more on the project's initial goals, please see https://blog.mozilla.com/services/2011/09/15/introducing-project-sagrada/

Please Note:

In any project consisting of a large number of relatively orthogonal product areas, it's hard to build a useful single-timeline roadmap. Instead, we are working on breaking areas down into individual roadmaps covering specific elements of the platform.

Sequence

This table has all the current planned products that are a part of this project. The status field should be filled "Untriaged" for new items, "Not started", "In Progress", "Blocked", and "Completed". The owner can be TBD if no has claimed it.

Goal Year Type Product Owner Status
2011 Feature Application Credentialing Toby In Progress
2011 Feature Deployment, Pipelining and Change Management TBD Not Started
2011 Feature Logging and Metrics Rob In Progress
2011 Feature Crypto Support TBD Not Started
2011 Feature KV Storage TBD Not Started
2011 Feature Message Queueing Ben In Progress
TBD Feature Permission Tokens TBD Not Started
TBD Feature Virtual Machines TBD Not Started
TBD Feature Advanced Storage Models TBD Not Started
TBD Feature Automated Caching TBD Not Started
TBD Feature Email TBD Not Started
TBD Feature Payment Processing TBD Not Started
TBD Feature DNS Management TBD Not Started
TBD Feature Social Graphs TBD Not Started
TBD Feature Phased Rollouts TBD Not Started
TBD Feature Multicolo Support TBD Not Started