Community Ops/Get Involved: Difference between revisions
Jump to navigation
Jump to search
(Draft : contribution info from project pages) |
(spacing) |
||
(2 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
{{draft}} | |||
Contributors can become involved in Community IT/Operations by following these possible entry pathways: | |||
== Pathways == | |||
===== Monitoring ===== | |||
* Handle victorops alerts | |||
* Provides an entry to resolve some problems | |||
===== Puppet Config Management ===== | |||
* Build new servers using existing puppet | |||
* Contribute code to our puppet repositories. | |||
===== Administer Wordpress Multisite ===== | |||
* Manage Wordpress | |||
* Work with communities to provide service for their site | |||
===== Software/Application Development Platform ===== | |||
[future, this is not started] | |||
== Next Steps == | |||
After following an entry pathway, we can discuss next steps in an individualised track for the contributor. A generic pathway isn't possible for us, due to the massive variation in work we do. |
Latest revision as of 17:31, 12 September 2015
Contributors can become involved in Community IT/Operations by following these possible entry pathways:
Pathways
Monitoring
- Handle victorops alerts
- Provides an entry to resolve some problems
Puppet Config Management
- Build new servers using existing puppet
- Contribute code to our puppet repositories.
Administer Wordpress Multisite
- Manage Wordpress
- Work with communities to provide service for their site
Software/Application Development Platform
[future, this is not started]
Next Steps
After following an entry pathway, we can discuss next steps in an individualised track for the contributor. A generic pathway isn't possible for us, due to the massive variation in work we do.