(Difference between revisions)
|
|
| Line 1: |
Line 1: |
| | + | == Services Definition == |
| | + | |
| | + | |
| | == Process for requesting a NEW service == | | == Process for requesting a NEW service == |
| | * 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) |
Revision as of 10:56, 14 November 2010
Services Definition
Process for requesting a NEW service
- 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
- estimate of 6 months userbase
- possible interdependencies between services
- urgency
- who needs admin access to the service
- Once the bug goes to assigned state this
- gets discussed at a technical level in MeegoIT team
- Implementation effort
- Maintenance effort
- gets sent to Community office for discussion and approval
- gets sent to TSG for budget approval if needed
If all of this pass we go to the implementation phase:
- Create a component in bugzilla
- define default CC
- define QA
- Creation of beta site
- Go live
Process for a Change Request
- Open a bug in the service component in bugs.meego.com
- Template:
- What change
- possible interdependencies between services
- urgency
- gets discussed at a technical level in MeegoIT team
- gets sent to Community office for discussion and approval
- gets sent to TSG for budget approval if needed
If all of this pass we go to the implementation phase.