Adding releases for different versions of the tutorial to make sure older tutorials are available.

[negin513]

Hello everyone,
Since, I saw some recent changes in this repo, I wanted to follow up with an idea to make sure people have access to the older tutorials as well. I wanted to suggest to make releases/tags for each of the tutorials. For example, so far we had one tutorial (spring 2022) and we can create a tag for it. We can then add the list of all tags and corresponding tutorials in the readme. This will ensure the users can access older tutorials.
I also suggest changing the name of this repo to CTSM-Tutorials.

Please let me know your thoughts on this.
Cheers!
Negin

[wwieder]

we were thinking of creating branches for particular tutorials, but tags would be fine too (and maybe more permanent).

I really like the idea of renaming to CTSM-Tutorials, but couldn't see how to do this? Can you rename the repo, @negin513 ?

[wwieder]

@negin513 I think I lack admin access to change the repo name. Do you have this access? If so, can you give it to me, Danica and Teagan too?

[negin513]

@wwieder Thanks for your message.

I really like the idea of renaming to CTSM-Tutorials, but couldn't see how to do this? Can you rename the repo, @negin513 ?

I changed the name to CTSM-Tutorials. I have not created any tags yet but please feel free to do so.

@negin513 I think I lack admin access to change the repo name. Do you have this access? If so, can you give it to me, Danica and Teagan too?

you and @danicalombardozzi should have admin access and @TeaganKing is added as maintainer which has the write permissions. But I can add @TeaganKing as an admin as well.

Please see the attached screenshot:

Here is a description for permission levels allowed for each level:
https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/repository-roles-for-an-organization#permissions-for-each-role

[TeaganKing]

On a similar note, we might also think about versioned jupyterbooks. Separate jupyterbook pages for each of the various tutorial branches would allow users to continue to access a given tutorial at later dates, as well. At the moment, it is updated to NEON_Tutorial_2023; my understanding is that making any changes on either 'main' or 'NEON_Tutorial_2023' will overwrite the book and set the book to refer to that branch.