Create `nasa-openscapes-workshops` github org

[jules32]

This was an idea from the first 2i2c Access Hackday: to create a separate org where more people have permission to add people to workshops. This is part of fledging

Starting steps:

• create https://github.com/nasa-openscapes-workshops
• follow up with Yuvi about how this works
• Create a new 2i2c ticket to show this. Won’t move the current 3 teams over there but can then start to add workshops in the new org

[stefaniebutland]

successfully used this Feb 13, 2024 for SWOT workshop at AGU Chapman (@cassienickles & @ScienceCat18 ). Added participants GitHub usernames to https://github.com/orgs/nasa-openscapes-workshops/teams/workshopaccess-2i2c to grant 2i2c Hub access

[ScienceCat18]

Yes, this worked beautifully. We get several comments after the workshop of how pleasantly surprised participants were on how smooth the hands-on onboarding and using the cloud hub was (vs as it is often the case people traditionally get stuck using a hands-on system during workshops). Thank you 2i2c, Openscapes and NASA DAAC mentors for building an amazingly efficient and helpful end-to-end system for the NASA DAACs and their data users. This makes getting to science and training with NASA data & tools that much easier. As a workshop co-host, I didn't have to spend my energy or time or worry on the cloud hub (and onboarding users), and instead focused on EO data content and tools, and other user engagement 🙌 CC: @stefaniebutland , @jules32 , @erinmr , @cassienickles

[stefaniebutland]

And thank you @yuvipanda!

[yuvipanda]

Yay, this made my day. So glad to hear, @ScienceCat18!

[jules32]

Keeping this open so to document this in the Cookbook

[stefaniebutland]

Starter documentation: https://nasa-openscapes.github.io/earthdata-cloud-cookbook/leading-workshops/add-folks-to-2i2c-github-teams.html, but process has evolved with creating one Team per workshop, and the possibility of avoiding GitHub login for some workshops (I think)