-
-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transition To Workbench in May #283
Comments
@datacarpentry/core-team-curriculum I'm working on updating the new version of the lesson (as well as general cleanup of the repo) before the deployment of Workbench. I'm planning on completing this by mid-May, if not earlier. I'll add another comment here when the repo is ready for the transition. Please let me know if there are any concerns or timeline issues. |
Thank you for letting me know. I will update the timeline. |
The new version of the lesson has been deployed, so it can go back to the path of migration. |
I've put a tentative date for 09 May, but that may move to the week after |
I am planning on performing the transition today. Please let me know if you would like me to delay |
I'm good with proceeding. Crossing fingers! |
This lesson will be converted to use The Carpentries Workbench
If you no longer wish to have write access to this repository, you do not
If you wish to regain write access, please re-clone the repository on your machine and If you have any questions, please reply here and tag @zkamvar |
technical issues standby |
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 Thank you all for your enthusiasm and your patience! |
The Workbench version is now live: https://datacarpentry.github.io/OpenRefine-ecology-lesson/ In addition, here is map of commits that were changed during the transition |
I am ready for write access 🚀 @villanueval if you're okay with it, I can be a co-maintainer more officially, to match the responsibility of push access. |
@bencomp access granted! |
Yeah, no objections from me. |
I am ready for write access 🚀 |
@villanueval access granted! All of the maintainers now have write access! |
@datacarpentry/OpenRefine-ecology-lesson-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 carpentries/lesson-transition#53.
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:
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. @datacarpentry/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.
The text was updated successfully, but these errors were encountered: