Closed skcin closed 6 years ago
Comment by tomasbrod
Thursday Sep 07, 2017 at 18:20 GMT
Testing transfer of https://github.com/tomasbrod/transfer-org-test to community.
Settings -> transfer:
"Team access" dialog page comes up with checkbox near each team in the org.
I opened the transferred repo and inspect what is:
Comment by tomasbrod
Monday Sep 11, 2017 at 17:13 GMT
When the gridcoin repo is put under organization and the development team granted write access to it, protected branches must be set-up to protect master
, staging
and probably development
branches from unathorized modification by any team member.
I suggest creating another team "Executive team", for now containing only Rob @gridcoin and Marco @denravonska, which members only have permission to push or merge to master
.
Comment by tomasbrod
Tuesday Sep 12, 2017 at 08:59 GMT
I think this repository should go first to the organization, as en example. There already is already a Task maintainers team.
Comment by tomasbrod
Tuesday Sep 12, 2017 at 09:03 GMT
A issue-only repository should be created in the organization, for the purpose of collecting requests for team membership and repo settings changes. Such repo should be owned by "Executive team", which is also responsible for approving critical changes and releases.
Comment by grctest
Monday Sep 18, 2017 at 00:23 GMT
I think this repository should go first to the organization, as en example. There already is already a Task maintainers team.
https://github.com/Erkan-Yilmaz/Gridcoin-tasks/issues/150
Should be simple enough to do, just needs @Erkan-Yilmaz to click a couple buttons.
Tasks were copyied without interaction from erakn.
Gridcoin-Community Organization is on GitHub