Developing Services

From Dark Peak
Revision as of 14:41, 11 November 2017 by Graphiclunarkid (talk | contribs) (From the 2017 AGM, added a section on a new approach to getting more people involved in developing and maintaining services)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Service development teams

Two people should be involved in developing a new User Service: someone who wants the service to exist and is keen to learn how to make it work; and another person with knowledge of how things work at present will be found to work with you on developing the alpha. They should arrange to get together in person to hack out the alpha version - our hack days are ideal for this purpose.

The benefits of this approach are that less experienced members can learn from those with more knowledge and skills; and we start to reduce the burden on our more knowledgeable members by bringing others up to speed on how to help them manage services.

Service production levels

  • Decide if your new service will be a User Service, Co-op Service or Infrastructure.
  • Work to reach Alpha level, this should take a few hours. This is about validating the idea and thinking through what you'll do and what you need to do it.
  • Ask the co-op to verify that you've achieved this
  • Work to reach Beta level. This should be the bulk of the deployment work, and involves finding some co-maintainers
  • Ask the co-op to verify that you've achieved this
  • Work to reach Live. This is mostly about simplifying future maintenance work and ensuring it will get done.
  • Ask the co-op to verify that you've achieved this

These levels exist so that users of your service are able to understand what they can expect from a service. There is no requirement that all services reach live, if all your users are happy with something less reliable you can remain at Beta indefinitely.

Running Services are expected to provide an annual at the AGM that indicates whether the service continues to meet the requirements for the maturity level it is operating at.

Services which start to fail to meet their requirements have until the next general meeting to correct the issues. If they continue to fail to meet the requirements means the service descends one maturity level. Such a degradation may place other services also under scrutiny; for example infrastructure being degraded would also affect any services consuming that infrastructure. In addition, live service maintainers have the responsibility to notify the co-op of a change which would mean that the service no longer meets its live requirements. The board should act on these notifications by following the same process as above (ie - entering the “reasonable” grace period of time to correct the deficiencies).

Level requirements will only change at the the AGM or an EGM. Services then have until the next AGM to meet these requirements. If that is failed then the above process is followed.


These definitions and processes attempt to keep things:

Avoid over specifying, set broad targets that a service can meet many ways
Limit special cases, these should be specific agreements at the service level rather than added to the requirements
Where possible, grant autonomy to the people responsible for the service.
Clarity of requirements to maintainers
What is required at each level
What is provided by the Co-op to help achieve these requirements.
Clarity of service to those outside the set of maintainers
What’s used to create the service
What’s provided to the users of the service
How the service aligns with co-op principles
End-user focused
what can the user of the service expect in terms of Service Quality and how likely the service is to still be available in the future.
Build only what’s needed, if indirectly, by the end user

Where we fail to meet these goals the relevant requirements should be updated.