@bwk @FrailLeaf @LordMordred No idea what is that supposed to mean

for software engineering of a solution on an open-source projects the process is:
1. Abstract what you want to do and why (probably what google meant.. the term used in the computer science is "abstracting")
2. File a tracking and discuss the design with other developers
3. assign a developer to work on the issue or work on it yourself
4. work on implementation. This depends on the project e.g. sometimes it makes sense to first write the test before the code
5. Submit the solution for QA and discuss the design
5.1. In case the QA does not include it and the solution is projected to have such compatibility: Run it docker, VM, etc.. to ensure that it's cross-compatible
6. Make changes if any requested through collective research
7. Once approved make/polish tests and documentation
8. Merge

This is very watered-down and generic as it depends on the project and programming language used.