This file shows the outline for a Green Guide. For illustration purposes I've refered to DevOps Engineers as an example persona.
- Explain the purpose of this guide
- Connect to the reduction of carbon emissions of software by applying a 'green lens' to existing your existing practises
- Refer to the course and recommend they complete it if they haven't already
- Explain what green software means in the context of [DevOps]
- Connect the 3 Principles from the course back to their role
- Introduce the GSF concept of "Learn > Measure > Reduce"
- What could this look like in DevOps?
- Mention finding proxy measures for carbon
- Recommend to start small
- e.g. Identify a suitable application or component of your systems that could be a good candidate for improvement
- 10 things you can do right now
- Mix of reflective questions and generic 'no regret moves'
- How might you reduce...?
- "Do we need that server?"
- "Do we need that feature?"
- Do X
- How might you reduce...?
- Mix of reflective questions and generic 'no regret moves'
- Talk more about Measurement (SCI & Impact Framework)
- Relevant GSF projects
- Additional learning resources (e.g. Building Green Sofware Book)