To make the NodeOS organization easier to manage I've removed the teams and now will continue with fine-grain access control. Now instead of having direct access to the repo, anybody that wants to contribute to NodeOS I can be able to add him to the NodeOS organization and assign him (or her) the corresponding issue to work with, so there's no duplicated efforts. Due to that, they'll need to create a pull-request that will be merged with the reference repo on the NodeOS organization, and also you can be able to create new repos without needing to ask me first (as happened with the docs repo). I will be able to create new teams for specific repos like the website that work together and make sense to have access to all of them at once, but in general terms will not be anymore the "all or nothing" access control of before.
I will continue to use directly the NodeOS organization repos until 1.0 version, after that I'll protect the master branch of all of them and only it will be able to push and merge new commits the NodeOS-bot account managed by the CI server.
The text was updated successfully, but these errors were encountered:
I'm going to remove the issues tracker of the other projects and proxy all of them over this one, this way it will be possible to have all of them on a single place since there's no GitHub issues agregator (or does it?). When refering to a particular repo at its name between brackets on the issue title.
We should add this to the readme or a GitHub issues template...