More DevOps engineers outside of Skyline are starting to contribute to our community and will start to create their own Automation scripts, drivers, Visuals, ...
Starting Devops engineers do not yet have the same experience and are as aware of the best practices as some experienced Devops engineers. So they might want their work to be reviewed by more experienced engineers. They might also be interested to make amendments to solutions already provided by Skyline (e.g. enhancing Visuals, Scripts, ...).
If we want to set up a (private) shared repository where both Skyline employees and user DevOps engineers from the user can contribute together (to avoid that we are overwriting each other's work), what is the best way to do this?
If Skyline employees work on a public repository within the SkylineCommunications Github organization, DevOps engineers should be able to fork on that same repository and make pull requests for changes. The Skyline Employees can then review pull requests and commit them to the main fork, eventually deploying the changes to the catalog.
This is the most logical solution I see with the system we already have in place.