🔥📄Refreshing the playbook #261
timburke-hackit
started this conversation in
Firebreak April 24
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
🌵What is the problem or issue we're trying to address?
The playbook has seen limited updates for a while now, the repo is poorly organised and I don't think the playbook itself is intuitive to navigate.
🎯How is this affecting producers, consumers or platform engineers?
Producers
Don't have a simple reference point for common generic tasks and usually require quite a lot of support from DAP even if they've used platform before
Consumers
Suffer from similar problems and it's maybe not the most easily accessible onboarding ramp
Platform Engineers
Sometimes need to refer to documentation of an implementation but find it is out of date and no longer as is on live.
Don't have an easy tutorial type resource to refer users who would otherwise be able to self serve their task
Find updating the playbook laborious
Find approving other people's entries laborious (or maybe that's just me)
📝What is the proposed task?
Review the playbook, its structure, content, how and when we update it, who updates it, etc
Come up with a plan to address the issues
🤔How might this work be carried out?
At one point I had a stickies exercise I'd thought up around this, but I'm pretty open to suggestions
⌛How urgent is this work?
It's a core piece of documentation that is no longer up to date / usesful - so quite?
💪How much effort do you think this will take?
M/L
it's an ongoing task but I think we can make some good headway fairly quickly and maybe agree to make time for it going forward?
🛠️What skills are needed?
Knowledge of platform
📃Additional Info:
No response
Beta Was this translation helpful? Give feedback.
All reactions