Service Catalogue
Purpose
This site records the IT-related services provided by or for Leicester Hackspace, along with whether or not they are currently live, and whether or not they are supported - and if so, who is responsible for seeing that an adequate standard of maintained is done to them. Not all services listed here will be user-facing, some will be services that are "underpinnings" for other services.
List of services
| Service | Description | Service Owner | Deployment Status | Support Status |
|---|
| Website | Leicester Hackspace's main website | Jacob Lucas/Daniel Warren | Live | Supported by Web Team |
| HMIS | Hackspace membership records system | John P | Live | Supported |
| Forum | phpBB discussion forum | No service owner | Live | Not Supported |
| Wiki | MediaWiki installation | No service owner | Live | Not Supported |
| Bitbucket team | Repository hosting service for Git and Mercurial | None | Live | Not Supported |
| GitHub organisation | Repository hosting service for Git | Jacob Lucas | Live | Supported - contact Jacob Lucas/IT Team for assistance |
| Email forwarding | Email forwarding service is used to distribute emails sent to addresses such as it@, directors@, etc. | Brett Howard | Live | Supported |
| Discord | Instant messaging service used for communication between teams and members within the Hackspace | Jacob Lucas/Daniel Warren | Live | Supported |
Glossary of terms
- Service
- A Service is something IT-related, which the IT Team might be expected to maintain, upgrade, change, fix, commission, decommission or otherwise be responsible for.
- Service Catalogue
- The official record of Services which are Supported by the Hackspace IT Team, and have a Service Owner.
This list may also contain services which are not currently supported, if they were previously supported, if it is thought that a Service Owner should be sought as the service is in some way worthwhile or necessary, or if the service is currently In Development, and is expected to become a Supported service in the future.
- Service Owner
- The single point of ultimate responsibility for a service.
This must be a single person for the service to be considered Supported, as something which is everybody's responsibility is nobody's responsibility. The Service Owner is responsible for maintaining the Service to the standards agreed with the organisation. Whether they do the technical work themselves or co-ordinate the work of others is immaterial, but they must be confident that they have the people/resources/support they need in order to fulfil their responsibility to see that the work is done.
The Service Owner has a certain degree of latitude to act as a "gatekeeper" of changes to their Service, in so far as those changes impact their ability to support the service.
- Supported
- A supported service is one which has a Service Owner, and therefore has a single point of responsibility.
How to update this page
This page is served by GitHub Pages, and is stored in a private GitHub repository. If you don't have access to update this page, but think you should, please contact the Hackspace IT Team.