Today papiNet has assigned different permissons on papiNet.org and PMStage for papiNet members. I think it would also be good to set some rules how to manage papiNet-API in Github.
So far all people in the papiNet team on Github have by default been given the role owner.
New people are joining the papiNet team and some are leaving. Some of them would like to stay in the team as non active members.
I propose that papiNet assigns the role owner or the role member to people in the papiNet team and reviews and sets permissions for active members and non active members.
It would be good to have some rules how to manage settings on Github.
Who should be owners?
Who should be members?
- permissions for active members?
- permissions for non active members?
Who should be voting members? e.g. active owners and active members attending papiNet API meetings
papiNet has so far not used any “outside collaborators”.
Today papiNet has assigned different permissons on papiNet.org and PMStage for papiNet members. I think it would also be good to set some rules how to manage papiNet-API in Github.
So far all people in the papiNet team on Github have by default been given the role owner.
New people are joining the papiNet team and some are leaving. Some of them would like to stay in the team as non active members.
I propose that papiNet assigns the role owner or the role member to people in the papiNet team and reviews and sets permissions for active members and non active members.
It would be good to have some rules how to manage settings on Github.
Who should be owners?
Who should be members?
Who should be voting members? e.g. active owners and active members attending papiNet API meetings
papiNet has so far not used any “outside collaborators”.