Transition to The Carpentries Workbench

ErinBecker commented 1 year ago

Hi @datacarpentry/geospatial-workshop-maintainers

The Curriculum Team is preparing to transition all of the workshop/curriculum overview sites to the Workbench. @zkamvar has set a tentative migration date of Monday 18th September. This change will bring all of the overview sites, including this one, back in line with all of the official lessons that were transitioned to the new infrastructure in May.

What do you need to do?

To help us prepare for a smooth transition, we invite you to:

explore the preview of the transitioned version of the overview site: https://fishtree-attempt.github.io/geospatial-workshop/
- if you find any problems with formatting, missing content, etc, please post a comment on https://github.com/carpentries/lesson-transition/issues/27 to give us the details
process any pull requests made to the repository, ensuring that they are all merged or closed before the transition takes place. Any open pull requests on this repository will be invalidated by the transition. There are currently 2 open pull requests on the repository.
post the questions and concerns you have about the transition here, tagging @tobyhodges.

What happens next?

After the transition, Maintainers will temporarily lose their write access to the repository as a safety measure, ensuring that the old project history cannot be accidentally pushed back into the repository. The steps to restore access are relatively straightforward (see an example from the completed transition of another lesson) and you can expect detailed instructions and further support from the Curriculum Team when the transition takes place.

Beyond that, you can expect to continue maintaining the repository as you were before, while taking advantage of the simplified layout and syntax that the new infrastructure offers. main will become the default branch of the repository (currently gh-pages), and files currently located in _extras/ will be divided between two new folders: learners/ and instructors/. You can read more about the changes to repository structure/organisation and source file syntax in the Workbench Transition Guide.

zkamvar commented 1 year ago

This lesson will be converted to use The Carpentries Workbench To prevent accidental reversion of the changes, we are temporarily revoking write access for all collaborators on this lesson:

[x] @albhasan (push)
[x] @HaoZeke (push)
[ ] @jhollist (push)
[ ] @marissablock23 (push)
[ ] @jsta (push)
[x] @tobyhodges (push)
[ ] @tyson-swetnam (push)
[ ] @srappel (push)
[ ] @arreyves (push)
[ ] @aranganath24 (push)
[x] @likeajumprope (push)
[x] @mikemahoney218 (push)
[x] @drakeasberry (push)
[x] @misgna3 (push)

If you no longer wish to have write access to this repository, you do not need to do anything further.

What you can expect from the transition 📹: https://carpentries.github.io/workbench/beta-phase.html#beta
How to update your local clone 💻: https://carpentries.github.io/workbench/beta-phase.html#updating-clone
How to update (delete) your fork (if you have one) 📹: https://carpentries.github.io/workbench/faq.html#update-fork-from-styles

If you wish to regain write access, please re-clone the repository on your machine and then comment here with I am ready for write access :rocket: and the admin maintainer of this repository will restore your permissions.

If you have any questions, please reply here and tag @zkamvar

zkamvar commented 1 year ago

The Workbench version is now live: https://datacarpentry.github.io/geospatial-workshop/

In addition, here is map of commits that were changed during the transition

albhasan commented 1 year ago

I am ready for write access :rocket:

HaoZeke commented 1 year ago

I'm ready for write access 🚀

On Sep 18 2023, at 7:30 pm, Alber Sánchez @.***> wrote:

I am ready for write access 🚀 — Reply to this email directly, view it on GitHub @./0?redirect=https%3A%2F%2Fgithub.com%2Fdatacarpentry%2Fgeospatial-workshop%2Fissues%2F66%23issuecomment-1724245370&recipient=cmVwbHkrYWJiY3V0N3NrcGt6Z2NneXU3b3RsdmdkY3hsNTVldmJuaGhnN3VhN3VxQHJlcGx5LmdpdGh1Yi5jb20%3D), or unsubscribe @./1?redirect=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABBCUT4MR53DETKZHXWX35TX3CON5ANCNFSM6AAAAAA4GLZX7A&recipient=cmVwbHkrYWJiY3V0N3NrcGt6Z2NneXU3b3RsdmdkY3hsNTVldmJuaGhnN3VhN3VxQHJlcGx5LmdpdGh1Yi5jb20%3D). You are receiving this because you were mentioned.