How to properly structure the logic of the web studio with github.com?

Question

git

Hello!
We are a small web studio (10 people) that develops websites using WordPress and Magento!
We want to move to github.com, now we are choosing the logic of how our projects work with github.com.
Here is what I managed to sketch, please write how you can improve the structure or what needs to be changed. If you need to change something - write why.
Thank you for your opinion.

Answer 1

Something in your diagram is all in the mess - both users and branches and environments.
My personal imho:
1) Read about git flow https://habrahabr.ru/post/106912/ - this is an extremely successful branching model
2) To use forks or not is a personal matter for everyone.
Someone likes the final repository to look simple and beautiful - and then forks with rebase before pull request will do everything well.
Someone (like me) likes to see the whole development process in realtime in the repository - we do not allow forks, developers explicitly make all commits to a common repository. But we have fairly detailed tasks, it never happens that more than 1 person works on a task. In this case, by the way, it's better to use mercurial, not git.

Answer 2

I'm curious, I didn't work in the studio, but I was always embarrassed that all the source code of the projects is available to everyone through google big query, doesn't it bother anyone?