Scheduling early transition to Workbench about lc-git HOT 16 CLOSED

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

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

from lc-git.

@tobyhodges and @zkamvar, we would like to go forward with the transition. I would like to get some help with the remaining PRs.
Also, what happens with issues that have not been resolved? (I am assuming they stay in place and can be addressed after the transition, but I just want to make sure).

from lc-git.

Yes, that's right @emcaulay: issues will be unaffected by the transition.

from lc-git.

I have reviewed the remaining open PR, and recommend that you go ahead and merge it.

from lc-git.

I have merged it. And I've entered a new one from myself. I'm going to merge it even though generally I prefer to have another reviewer.

from lc-git.

note: the transition of this lesson is tracked in carpentries/lesson-transition#63

from lc-git.

I apologise, I was unable to make the transition happen today. There is nothing impeding the transition itself, it's just a matter of a lot of outside factors coming together in ways that took away my time. The transition process itself takes ~ 5 minutes total, but as you can imagine, it's a very stressful transition on my part because I am changing something that a lot of people have put a lot of time an effort into. Thus, I like to give myself at least two hours for the transition to happen so that I can correct anything if it goes wrong.

I will try again tomorrow. Thank you for your patience.

from lc-git.

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)
• @jezcope (admin)
• @ostephens (admin)
• @emcaulay (push)
• @laufers (push)
• @cmacdonell (admin)
• @chennesy (push)
• @weaverbel (admin)
• @annajiat (push)
• @drjwbaker (admin)
• @r2c0der (push)
• @ccronje (admin)
• @U2NG (admin)
• @pitviper6 (admin)
• @PhilReedData (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

from lc-git.

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!

from lc-git.

I am ready for write access 🚀

from lc-git.

Hi @zkamvar ,
I am ready for write access 🚀

I have re-cloned this repo to my local machine.

from lc-git.

@emcaulay access granted!

@r2c0der, are you ready for write access?

from lc-git.

Hi @r2c0der - You have not yet responded here to report that you completed the steps listed by @zkamvar above to regain your Maintainer access to this repository. The lesson infrastructure transition required a second Maintainer team to be temporarily created for all lessons, which can only be removed when all Maintainers have confirmed that they are ready to have their access restored. Maintenance of both teams is not sustainable for The Carpentries in the long run. At the beginning of November 2023 (note the deadline has been extended) we will remove access for Maintainers who have not taken the necessary action to continue working on the repository.

The Curriculum Team is truly grateful for everything you have already done as a Maintainer and we do not want to lose you! But we also understand that circumstances change and you may no longer have capacity to continue in your role. If you wish to retain your access and keep supporting the community, please follow the steps above then confirm that you are ready by commenting I am ready for write access 🚀 on this thread before the end of your day on Wednesday 1st November.

from lc-git.

Assigning to @ErinBecker who will close this issue on 2023-11-01.

from lc-git.

@ErinBecker , reminder that I think this issue can now be closed?

from lc-git.

Hi @r2c0der - You no longer have Maintainer access to this repository. Please see the comment above for details. If you would like to restore your access, please re-clone the repository on your machine and then comment here with I am ready for write access 🚀 and the admin maintainer of this repository will restore your permissions. If you have any questions, please don’t hesitate to get in touch [email protected]

To the remaining Maintainers for this lesson - the Curriculum Team will be prioritizing onboarding of new Maintainers for lessons that have lost Maintainers in our next round of onboarding. Please don’t hesitate to reach out if your lesson needs additional support in the meantime - [email protected].

I will close this issue now but will still be notified of any replies on the thread in future.

from lc-git.