Transition To Workbench in May

[zkamvar]

@librarycarpentry/lc-data-intro-maintainers

As I hope you are already aware, we are rolling out the new lesson infrastructure, The Carpentries Workbench, across all of The Carpentries official lessons in early May 2023. This means that all Data Carpentry, Library Carpentry, and Software Carpentry lesson repositories will be modified to adopt the new infrastructure in the coming days.

You can follow the transition of this lesson repository at https://github.com/carpentries/lesson-transition/issues/60.

The transition has already taken place for several lessons, and so far the process has been running quite smoothly. You should see the transition take place with minimal disruption, but there are a few things that it is important for Maintainers to be aware of.

Here is what you can expect to happen next:

1. Any open pull requests on the repository will be closed with an automated message.
2. The repository will be set to read-only mode for a brief period while the transition occurs.
3. The new repository structure and lesson site layout will then be applied.
4. To avoid anyone accidentally pushing the old commit history back to the repository, after the transition Maintainers will need to delete and replace any existing forks and local clones they have of the lesson repository, and confirm that they have done so by replying to this issue.

I will reply here before and after the transition has taken place. If you have any questions in the meantime, please reach out to the Curriculum Team by tagging us here, e.g. @librarycarpentry/core-team-curriculum.

If you would like to read more about the new lesson infrastructure and the modified repository structure you can expect post-transition, I recommend the Infrastructure episode of the Maintainer Onboarding curriculum and the Workbench Transition Guide, which includes a side-by-side comparison of various elements of the old and new infrastructures.

[zkamvar]

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:

• [ ] @jt14den (admin)
• [ ] @ostephens (admin)
• [ ] @laufers (push)
• [x] @kevintfrench (push)
• [ ] @chennesy (push)
• [ ] @annajiat (push)
• [ ] @drjwbaker (push)
• [x] @sharilaster (push)
• [ ] @PhilReedData (push)
• [ ] @kekoziar (push)
• [ ] @ragamouf (push)

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

1. What you can expect from the transition 📹: https://carpentries.github.io/workbench/beta-phase.html#beta
2. How to update your local clone 💻: https://carpentries.github.io/workbench/beta-phase.html#updating-clone
3. 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]

technical issues, stand by.

[zkamvar]

The deed is done. The infrastructure takes a few minutes to bootstrap and cache the packages for the lesson build. Once the build is done, I will switch github pages to deploy from the gh-pages branch and you will have your workbench lesson.

Thank you all for your enthusiasm and your patience!

[zkamvar]

The Workbench version is now live: https://librarycarpentry.github.io/lc-data-intro/

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

[sharilaster]

I am ready for write access :rocket:

[zkamvar]

@sharilaster, access granted!

[zkamvar]

Note that @Freddy2304 will be joining on as a maintainer for this lesson, but has not yet accepted the invitation (see https://carpentries.org/blog/2023/05/welcome-new-lesson-maintainers/)

@Freddy2304, when you accept your invitation, please comment here with I am ready for write access :rocket: and I will grant you write access.

[PhilReedData]

I am ready for write access :rocket:

[zkamvar]

Hi @PhilReedData, thank you for following up. To shore up the security of the lesson repositories, the Curriculum Team would like to use this opportunity to tidy up the access levels we are providing to community members across the various repos. According to our records, you're not a Maintainer on this lesson, but I think you had previously been granted write access to the repository in your capacity as a LibraryCarpentry Curriculum Advisor.

For now, we are going to provide write access only to Maintainers---though that decision will be open to review, so please let us know (@ me or LibraryCarpentry/core-team-curriculum) if this interferes with the CAC's ability to perform their duties.

[kevintfrench]

I am ready for write access :rocket:

[zkamvar]

@kevintfrench access granted!

[Freddy2304]

I am ready for write access 🚀

[zkamvar]

Hello @Freddy2304, I have resent your invitation. You should see it in your inbox. When you accept it, you will have write access!

[Freddy2304]

Hi, I accept your invitation. Kindly grant me write access.

Best regards, freddy

---

From: Zhian N. Kamvar @.> Sent: Friday, June 23, 2023 1:01 AM To: LibraryCarpentry/lc-data-intro @.> Cc: Freddy @.>; Mention @.> Subject: Re: [LibraryCarpentry/lc-data-intro] Transition To Workbench in May (Issue #205)

Hello @Freddy2304https://github.com/Freddy2304, I have resent your invitation. You should see it in your inbox. When you accept it, you will have write access!

— Reply to this email directly, view it on GitHubhttps://github.com/LibraryCarpentry/lc-data-intro/issues/205#issuecomment-1603016061, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A7N2LBNA5IX2DBNMAMV2U2TXMR245ANCNFSM6AAAAAAXLMKEFI. You are receiving this because you were mentioned.Message ID: @.***>

[zkamvar]

Thank you for accepting! All maintainers now have Maintain access and this issue can be closed; congratulations!