(→Services Definition) |
(→Process for requesting a NEW service) |
||
| Line 4: | Line 4: | ||
It's important to review the existing services list on [[Web infrastructure]] before submitting a NEW request. Duplication of services will be highly discouraged. | It's important to review the existing services list on [[Web infrastructure]] before submitting a NEW request. Duplication of services will be highly discouraged. | ||
| - | == | + | == Requesting a NEW service == |
| + | * Review [[Web infrastructure]] list | ||
* Open a bug in 'General Requests' in bugs.meego.com (http://bugs.meego.com/enter_bug.cgi?product=General%20Requests) | * Open a bug in 'General Requests' in bugs.meego.com (http://bugs.meego.com/enter_bug.cgi?product=General%20Requests) | ||
| - | + | ||
| - | + | === Template === | |
| - | + | # What service (link to tarball, package, webpage or so) | |
| - | + | # Service description | |
| - | + | # Purpose of service | |
| - | + | # Estimate of 6 month user base | |
| - | + | # Possible interdependencies between services | |
| - | + | # Urgency | |
| + | # Service owner | ||
| + | # Service admin(s) | ||
| + | |||
| + | === Workflow === | ||
* Once the bug goes to assigned state this | * Once the bug goes to assigned state this | ||
** gets discussed at a technical level in MeegoIT team | ** gets discussed at a technical level in MeegoIT team | ||
Contents |
A service for MeeGo is defined as a specific project that provides some type of useful function within the community. Not all services will be user facing or be accessible by all meego.com users, but the project should be valuable to the entire MeeGo project.
It's important to review the existing services list on Web infrastructure before submitting a NEW request. Duplication of services will be highly discouraged.
If all of this pass we go to the implementation phase:
If all of this pass we go to the implementation phase.