---
# System prepended metadata

title: Github ideas
tags: [teaching]

---

---
tags: teaching
---
# Github ideas

## Repositories
We set up repos. 

We add one or more owners and let researchers manage access themselves. No AD integration, just standard GH accounts.

Three organisations:

`universityofleeds` a single organisation for anyone who wants a public repository. This can contain code and a github-pages site. Must have a README and a licence (minimum MIT) file, otherwise it will be toggled to a private repository.

Policies at org level:
* Cannot transfer repo elsewhere
* Cannot delete repo
* Cannot make someone an owner as default??

Can index this repo to act as a shopfront?

`universityofleeds-private` a single org in which anyone can request a private repository. Must be kept private and doesn't need to have a licence OR a readme.

Policies at org level:
* Cannot transfer repo elsewhere
* Cannot delete repo
* Cannot toggle to public repo
* Cannot make someone an owner as default!!

`universityofleeds-pages` a single org for those people who just want a pages site. No UoL domain name.

Policies at org level:
* Cannot transfer repo elsewhere
* Cannot delete repo
* Cannot make someone an owner as default!!

## Organisations:

Available on request BUT only to PIs/ Group Leads. Existing orgs can be transferred in via GH user support.

Policies:
* Assigned owner
    * Can create new repos in this org
    * Can delete repos in this org
    * Can assign new users
    * Cannot delete the org itself

## Accounts:

Github accounts only. No AD authentication.

## Guidance and support

* Training
    * What can/ cannot be stored in a GH repo
* Code/ repository lifecycle:
    * J-M-L

## Miscellaneous

* `Actions`: preferred model is to assign `azure devops` to manage actions.  Enterprise has limited actions-runner hours per month and we'd prefer that users can't use these?


