I have been using and coaching teams on using Git since 2009 - and in this particular summer of 2020, my experience has made me as if pregnant with a change work gospel (centered around Git). I intend this as a brief draft of what I want to achieve.
You are very welcome to get in touch, contribute to or collaborate on this. Many parts I would like to make Open Source - though this is also my profession and I intend to sell coaching in this area. Find me here on GitHub, twitter or email: cj.sveningsson@gmail.com
Some perspectives I'd like to address:
- Developers must have effective paths to progress from inexperienced to craftsperson
- The crucial role of change work in systems development should be connected with adjacent fields such as lean, agile, clean code, architecture etc.
- Change work must be described in the modern contexts and tools people recognize
- Jargon and references to Git-specific concepts should be minimized, and the topic be as inclusive and open to entry as possible
- Details should be described on a need-basis (or otherwise provided by the plentiful reference documentation), as well as contextualized to mitigate the common issues users face
- Inaccessible topics normally addressed by someone in a "configuration manager" role should be described, for instance:
- Knowledge sharing, code review and maintainability
- Collaboration, reusability and dependency management
- "Workflows" - including templates and contribution guidelines
- Repository layout and strategies
- Validation, analysis, lint and CI
- Versioning, releasing and communication (change logs / release notes)
- Development environment setup and user introduction