Account confirmers, Anti-spam team, Bureaucrats, canmove, Confirmed users, Module owners and peers, smwadministrator, smwcurator, Administrators, MozillaWiki team, Widget editors
734
edits
Petri: Difference between revisions
+Obsolete flag
(+Obsolete flag) |
|||
| (7 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{RELEASE_MANAGEMENT_OBSOLETE}} | |||
== Synopsis == | == Synopsis == | ||
| Line 50: | Line 52: | ||
* After 1 year, evaluate whether to evolve, grow, change, or wind down the offering. | * After 1 year, evaluate whether to evolve, grow, change, or wind down the offering. | ||
Driver | {| | ||
Approvers | | Driver || David Ascher (dascher@ mozilla dot com) | ||
Contributors | |- | ||
Informed | | Approvers || Jim Cook; mrz; Todd Simpson, Mark Mayo | ||
|- | |||
| Contributors || Gozer, MCoates, others TBD | |||
|- | |||
| Informed || everyone who cares, in particular: directors, labs, research, engineering, webdev, people-who-sign-up, + public posts along the way | |||
|} | |||
=== Status === | |||
Ongoing (just starting, actually) | |||
Draft Schedule | == Draft Schedule == | ||
{| | {| | ||
| | | -Dec 12 || Proposal Discussion / Editing / Establish Schedule | ||
|- | |- | ||
| Dec 5 || Survey of Mozilla developers to understand current behaviors and which platforms/IaaS systems they'd be able to use | | Dec 5 || Survey of Mozilla developers to understand current behaviors and which platforms/IaaS systems they'd be able to use | ||
| Line 106: | Line 115: | ||
* Eucalyptus (note: CEO is a friend of Mozilla) | * Eucalyptus (note: CEO is a friend of Mozilla) | ||
* OpenStack | * OpenStack | ||
* OpenNebula | |||
* Nimbula | * Nimbula | ||
* Ganeti | * Ganeti | ||
| Line 113: | Line 123: | ||
* Open source or not, what license, what contribution model | * Open source or not, what license, what contribution model | ||
* Can run inside firewall | * Can we run it ourselves inside the firewall? | ||
* Are there commercial service providers? Could we pay someone else to run it? | |||
* Current capabilities (e.g. supports Django or not, etc) | * Current capabilities (e.g. supports Django or not, etc) | ||
* Known roadmaps/plans (e.g. "doesn't do HBase today, but planned for 2013") | * Known roadmaps/plans (e.g. "doesn't do HBase today, but planned for 2013") | ||
* | * Developer ergonomics: how good is the fit with what our developers need? | ||
* IT/Ops ergonomics: how good is the fit with what IT/Ops need? | * IT/Ops ergonomics: how good is the fit with what IT/Ops need? | ||
* Cost | * Cost | ||
| Line 159: | Line 170: | ||
There's nothing about this project that warrants secrecy, so the project will be run like a traditional Mozilla project: | There's nothing about this project that warrants secrecy, so the project will be run like a traditional Mozilla project: | ||
* Weekly meetings with public minutes | * [[/WeeklyMeeting|Weekly meetings with public minutes]] | ||
* Mailing list | * [https://mail.mozilla.org/listinfo/petri-users Mailing list] | ||
* Public artifacts | * Public artifacts as they are created. | ||
We should be careful to explain in the project descriptions that we're starting by tackling the problem for internal users, but we should also explore the issues preventing us from making the platform available to trusted Mozillians who aren't paid. I expect there are legal issues there worth exploring. | We should be careful to explain in the project descriptions that we're starting by tackling the problem for internal users, but we should also explore the issues preventing us from making the platform available to trusted Mozillians who aren't paid. I expect there are legal issues there worth exploring. | ||