New organization scheme #292

Open
piranna opened this Issue Aug 14, 2016 · 6 comments

Comments

Projects
None yet
2 participants
@piranna
Member

piranna commented Aug 14, 2016

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.

@lite20

This comment has been minimized.

Show comment
Hide comment
@lite20

lite20 Aug 18, 2016

Member

Ah this sounds excellent! Will allow for changes to progress quicker. +1

Member

lite20 commented Aug 18, 2016

Ah this sounds excellent! Will allow for changes to progress quicker. +1

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Aug 21, 2016

Member

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...

Member

piranna commented Aug 21, 2016

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...

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Aug 21, 2016

Member

there's no GitHub issues agregator (or does it?)

Ok, there is, but it's a SpringBoot app... Is it time to develop our own one? And maybe have a NodeOS instance running somewhere in the cloud? :-P

Member

piranna commented Aug 21, 2016

there's no GitHub issues agregator (or does it?)

Ok, there is, but it's a SpringBoot app... Is it time to develop our own one? And maybe have a NodeOS instance running somewhere in the cloud? :-P

@lite20

This comment has been minimized.

Show comment
Hide comment
@lite20

lite20 Aug 22, 2016

Member

Haha creative idea! It would be nice to have

Member

lite20 commented Aug 22, 2016

Haha creative idea! It would be nice to have

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Sep 15, 2016

Member

Since yesterday GitHub support projects! Didn't have the chance yet to read about it, but seems will help us to organice better NodeOS development :-) Can someone take a look on it?

Member

piranna commented Sep 15, 2016

Since yesterday GitHub support projects! Didn't have the chance yet to read about it, but seems will help us to organice better NodeOS development :-) Can someone take a look on it?

@lite20

This comment has been minimized.

Show comment
Hide comment
@lite20

lite20 Sep 15, 2016

Member

Doing that right now. It looks good!

Member

lite20 commented Sep 15, 2016

Doing that right now. It looks good!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment