Open jules32 opened 3 months ago
We've scheduled a 2 hour coworking for April 10 where we can tackle some of these things together once you're a bit more familiar with the things above
This issue also seems relevant here: https://github.com/NASA-Openscapes/earthdata-cloud-cookbook/issues/316
A thought about the ChampionsAccess-2i2c team... is the intention to have one team, and on-board and off-board members at the start/end of each cohort? Or do we want a team for each cohort? I wonder where the cost/benefit falls of administering multiple teams vs potential overlap in access between one team and the next?
Progress today: @ateucher created a draft PR to 2i2c/infrastructure to update the teams access: https://github.com/2i2c-org/infrastructure/pull/3930
We stopped before adding mentors (using kyber) to nasa-openscapes-workshops:: AdminTeam, thinking that we will do that for upcoming workshops when we onboard specific mentors to this process (with some of this documentation in the Cookbook)
Next steps for Andy:
We also created a new (empty) team for the 2024 champions cohort nasa-openscapes-workshops:champions-access-2i2c-2024
Hi Andy! Great job today with presenting these slides with the Champions Cohort. I think we're ready to add to Cookbook:
Could you please:
Hi Andy!
We can use this issue to help overall progress/coordination. This will start off by reading and getting familiar with the following documentation and Issues, with an eye towards having all updated policies and process documented in the Cloud Cookbook (likely in the Leading Workshops section). We can track specific issues in the NASA-Openscapes GitHub organization.
Policy documentation and issues:
nasa-openscapes-workshops
repo where we will have a separate GitHub Team for each workshop. We can bulk-add GitHub usernames with kyber; note this is something that Stef/Julie/Erin currently do for Champions and we're just starting to use for NASA JupyterHub; but hasn't been taught/established as practice for MentorsMoving towards automating more workshop processes:
kyber
R package.