Confirmed users, Bureaucrats and Sysops emeriti
812
edits
User:Mconnor/Past/Services Beta Channel: Difference between revisions
Jump to navigation
Jump to search
User:Mconnor/Past/Services Beta Channel (view source)
Revision as of 17:00, 2 June 2011
, 2 June 2011no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
In order to move faster and prove out new ideas, we will create | In order to move faster and prove out new ideas, we will create an environment for both beta features and experimental ideas, consisting of both new client features as well as new server-side offerings. This will be a superset of our current production offerings, with no overlap between the environments. Users will need to explicitly create accounts with revised Terms of Service to join the early access program. We will ship an add-on which makes this action easier for existing users, but the requirement for isolation is to allow us more freedom to deploy new services quicker, and opt into even earlier access to experimental services. | ||
== Server Environment == | == Server Environment == | ||
| Line 7: | Line 7: | ||
This will be a new set of infrastructure, starting with a deployment of all of the current Services apps (excluding KeyEx, which is account-agnostic). We will treat this as an explicit opt-in sandbox, with a fully separate set of accounts, user data, and servers. It will be isolated from the production environment, and carry different Terms of Service, Privacy Policy, and SLA requirements. | This will be a new set of infrastructure, starting with a deployment of all of the current Services apps (excluding KeyEx, which is account-agnostic). We will treat this as an explicit opt-in sandbox, with a fully separate set of accounts, user data, and servers. It will be isolated from the production environment, and carry different Terms of Service, Privacy Policy, and SLA requirements. | ||
Experimental services will require an explicit user opt-in before use. Whether this is a single opt-in, or a per-experiment opt-in, will be determined by the product driver for those releases. | |||
Mozilla Services will use the same architecture as LabKit to create a client feature beta channel independent of the Firefox beta channel. This means that we will build new features as restartless add-ons first, and roll them out to users of the beta channel. Users of this channel will need to have an account on our beta infrastructure to make use of any client features dependent on new services or service features. | == Client Feature Channels == | ||
The Mozilla Services beta channel will use the same architecture as LabKit to create a client feature beta channel independent of the Firefox beta channel. This means that we will build new features as restartless add-ons first, and roll them out to users of the beta channel. Users of this channel will need to have an account on our beta infrastructure to make use of any client features dependent on new services or service features. | |||
The Mozilla Labs experimental channel user experience is still TBD, but is expected to require a more explicit opt-in. | |||
== Beta Channel Process == | == Beta Channel Process == | ||
| Line 18: | Line 22: | ||
* The core concept has been prototyped and evolved to the point where we think it's a compelling enough feature/service to start accelerating | * The core concept has been prototyped and evolved to the point where we think it's a compelling enough feature/service to start accelerating | ||
* If there is a user data component, we've gone through the initial iteration/refinement/assessment phases and have | * If there is a user data component, we've gone through the initial iteration/refinement/assessment phases and have preliminary sign-offs | ||
* There is a clear Product desire to move the feature towards Firefox inclusion | * There is a clear Product desire to move the feature towards Firefox inclusion | ||
* We have defined UX and Product requirements for a beta-quality feature, and we've built that | * We have defined UX and Product requirements for a beta-quality feature, and we've built that | ||
| Line 42: | Line 46: | ||
* This environment will not be able to share account information or data with production services. | * This environment will not be able to share account information or data with production services. | ||
* Initial signoffs will still be required from Security/Privacy/Product before deploying to this environment. These signoffs will apply a looser standard than for production-level signoffs. | * Initial signoffs will still be required from Security/Privacy/Product before deploying to this environment. These signoffs will apply a looser standard than for production-level signoffs. | ||
* There will be two SLA levels, one for "beta" services and one for "experimental" services. | |||
=== Legal === | === Legal === | ||
* New ToS/PP | * New ToS/PP | ||
** Must be open-ended enough to allow for future products. No guarantees of encryption/data protection should be made here. | ** Must be open-ended enough to allow for future products. No guarantees of encryption/data protection should be made here. | ||
** There will be an additional opt-in Terms of Service for experimental options, including consent to automatic user tracking | |||
=== Product === | === Product === | ||
* Need to define branding for this channel | * Need to define branding for this channel | ||
* Need to define "beta-quality" more concretely | * Need to define "beta-quality" more concretely | ||
* Need to define sufficient uptake to move to production | * Need to define sufficient uptake to move to production | ||
=== Engineering === | === Engineering === | ||
* We will need to develop the client add-on and get that channel ready for use. | * We will need to develop the client add-on and get that channel ready for use. | ||
** Ideally this will modify the existing account sign-up process to make it trivial to move to the beta channel | ** Ideally this will modify the existing account sign-up process to make it trivial to move to the beta channel. | ||