Skip to content

New organisation policies#3

Open
micaeljtoliveira wants to merge 3 commits intomainfrom
new_admin_policies
Open

New organisation policies#3
micaeljtoliveira wants to merge 3 commits intomainfrom
new_admin_policies

Conversation

@micaeljtoliveira
Copy link

This PR adds new policies regarding:

  • repository administration and membership
  • roles and responsabilities of repository and organisation administrators

Closes #2

chrisb13 and others added 3 commits February 10, 2026 09:22
As discussed with  @ccarouge @aidanheerdegen this afternoon, this text is currently misleading as a mixed approach is being used where eventually the plan is to move to a per repository access basis. Perhaps text like I've suggested could be used eventually? 

Alternatively, can this text please be updated to reflect the current suggested approach? Have admins of all the current organisation's repos been informed of the change / update of the READMEs as appropriate?
Co-authored-by: Micael Oliveira <micael.oliveira@anu.edu.au>
@micaeljtoliveira
Copy link
Author

@chrisb13 @aekiss @Whyborn @atteggiani @blimlim @helenmacdonald @phellipecouto @paolap @matlipson @georgyfalster @penguian @greensh16 @heidinett @KAUR1984 @aidanheerdegen @ccarouge @rbeucher

Dear all, I'm tagging you in this PR because you are listed as being an administrator of one or more repositories in the ACCESS-Community-Hub organisation and Github does not provide any better way of contacting people. At the end of this month ACCESS-NRI will be enforcing new policies regarding the repositories in this organisation. You can read all the details here. One important change that I want to draw your attention to is this one:

  • No special access is granted at the organisation level to members. This means that organisation members:
    • cannot write to repositories unless they have been granted explicit write access at the repository level or are part of a team that has such permissions
    • cannot read private repositories unless they have been granted explicit read access at the repository level or are part of a team that has such permissions.

This means that your collaborators will lose write access to any repositories that they are not direct members when this change is implemented. Therefore, I recommend you check that every person that needs write access is a direct member of the repository and, if they are not, please add them.

Let me know if you have any questions.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Proposed changes to how repositories in this org are managed

2 participants