Meego Wiki
Views

Web infrastructure/Processes

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(Services Definition)
(Services Definition)
Line 2: Line 2:
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.  
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.
+
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 ==
== Process for requesting a NEW service ==

Revision as of 11:08, 14 November 2010

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

  • 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
    • 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.

Personal tools