Meego Wiki
Views

Web infrastructure/Processes

From MeeGo wiki
< Web infrastructure(Difference between revisions)
Jump to: navigation, search
(→Request Workflow)
 
(5 intermediate revisions not shown)
Line 1: Line 1:
== Services Definition ==
== Services Definition ==
 +
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.
-
== Process for requesting a NEW service ==
+
== 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)
+
=== Request Template ===
-
** Service description  
+
# What service  (link to tarball, package, webpage or so)
-
*** purpose
+
# Service description  
-
*** estimate of 6 months userbase
+
# Purpose of service
-
*** possible interdependencies between services
+
# Estimate of 6 month user base
-
*** urgency
+
# Possible interdependencies between services
-
*** who needs admin access to the service
+
# Urgency
 +
# Service owner
 +
# Service admin(s)
 +
 
 +
=== Request 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  
Line 24: Line 31:
** define default CC  
** define default CC  
** define QA
** define QA
 +
* Add service to list on [[Web infrastructure]]
* Creation of beta site
* Creation of beta site
** testing
** testing

Latest revision as of 11:34, 14 November 2010

Contents

Services Definition

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.

Requesting a NEW service

Request Template

  1. What service (link to tarball, package, webpage or so)
  2. Service description
  3. Purpose of service
  4. Estimate of 6 month user base
  5. Possible interdependencies between services
  6. Urgency
  7. Service owner
  8. Service admin(s)

Request Workflow

  • 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
  • Add service to list on Web infrastructure
  • Creation of beta site
    • testing
  • 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
    • Implementation 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.

Retrieved from "http://wiki.meego.com/Web_infrastructure/Processes"
Personal tools