Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document Neuropoly's GitHub rules and etiquette #64

Open
jcohenadad opened this issue Jul 14, 2022 · 0 comments
Open

Document Neuropoly's GitHub rules and etiquette #64

jcohenadad opened this issue Jul 14, 2022 · 0 comments

Comments

@jcohenadad
Copy link
Member

Context

A student created a private GH repos under neuropoly's organization, with a size too large that it triggered git-lfs storage (and hence immediate cost for the lab)

Suggestion

  • Create a section 'GitHub' in the onboarding, right after 'Google drive'
  • In this section, explain that:
    • Neuropoly has a github organization (point to it)
    • the purpose of this organization is to host repos that are related to neuropoly's projects. Eg: if you publish a paper, you could put the code+data there and link to it in your paper.
    • the philosophy of neuropoly's lab is to do open science, which means that repos should be public. There are some exception: confidential data/credentials, highly-top-secret scientific research, etc.
    • IMPORTANT: if you decide to make your repos private, please make sure to not go above the total size and BW limits [LINK HERE TO GIT-LFS PRICES].
    • Please, always ask your supervisor before creating a repos.
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

No branches or pull requests

1 participant