Transition To Workbench in May about organization-genomics HOT 25 CLOSED

@ErinBecker and @zkamvar,
My sincere apologies. Life happens and I've not regained my full abilities since I was ill 18 months ago. I want to continue with Carpentries, but perhaps it's better to put me on "temporary leave" while I continue to heal (which is going, but going slow).

The transition to workbench simply came at a bad time when taking on new challenges is still difficult. I'm still myself (take that as good or bad), but getting caught up with home repairs and even trivial stuff is slow. Happy to speak more about it here, or by email, or phone. But I have to keep focus on my life.

I didn't make this decision until just today when I realized it was better for everyone for me to stay in touch, but let new, probably better people step up.

Please don't remove me from too many email lists (or slack channels, or whatever). I want to return as soon as possible. And I don't want to lose all the great friends and family in the Carpentries (I'd miss you all too much). I'll have to be the old uncle who "goes away" for a while.
Peter (@hoytpr)

from organization-genomics.

We are all set to transition this lesson tomorrow. I have fixed all the issues that were identified and you can see the preview here: https://fishtree-attempt.github.io/organization-genomics/

from organization-genomics.

The Workbench version is now live: https://datacarpentry.github.io/organization-genomics/

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

from organization-genomics.

Access granted @hidyverse (and hella props for the awesome handle)!

from organization-genomics.

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 organization-genomics.

@JCSzamosi, access granted 🎉

from organization-genomics.

Thanks for all your work and exceptionally clear communication throughout this process @zkamvar !

from organization-genomics.

@tobyhodges no worries! happy to have less to worry about 😅

from organization-genomics.

Thank you for asking this, @JCSzamosi

@hoytpr has Triage access, but he does not yet have Write access. He is able to merge pull requests, but he needs to use his own fork if he wants to make changes at the moment.

Once he says I am ready for write access :rocket:,then I will elevate his access.

from organization-genomics.

Hi @hoytpr - 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 organization-genomics.

Please don't worry too much @hoytpr ! I think @hidyverse and I can hold down the fort here while you take care of yourself. I hope to see you around elsewhere!

from organization-genomics.

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:

• @naupaka (push)
• @crazyhottommy (push)
• @JCSzamosi (push)
• @hoytpr (push)
• @ameynert (push)
• @JasonJWilliamsNY (push)
• @aschuerch (push)
• @elizabethmcd (push)
• @hidyverse (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 organization-genomics.

I am ready for write access 🚀

from organization-genomics.

It's my pleasure!

from organization-genomics.

It looks great. The primary actionable item might be that at the end of the lesson, the "next" arrow cycles back to what looks like the beginning of the workshop. The "Summary" starts the workshop again.

from organization-genomics.

I am ready for write access 🚀

from organization-genomics.

It looks great. The primary actionable item might be that at the end of the lesson, the "next" arrow cycles back to what looks like the beginning of the workshop. The "Summary" starts the workshop again.

@hoytpr, This is not something that can be fixed in individual lessons, it is an infrastructure issue. Could you open an issue in https://github.com/carpentries/workbench/issues ?

Additionally, would you say I am ready for write access :rocket: or do you still need to update your local clone?

from organization-genomics.

from organization-genomics.

I'm not ready for write access just yet. I have retired and the computer situation is in flux. I will see if my home setup still works ASAP.

No worries and no rush! The main concern is to prevent anyone who has an existing clone from accidentally force-pushing changes. If you are going to work from a fresh clone, you should be fine.

from organization-genomics.

I am ready for write access 🚀

from organization-genomics.

Hey @naupaka thanks 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 DC Genomics 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 datacarpentry/core-team-curriculum) if this interferes with the CAC's ability to perform their duties.

from organization-genomics.

Does anyone have any objection to closing this issue? It seems like @hoytpr has been granted write access and I don't see any obvious outstanding issues. @zkamvar @tobyhodges

from organization-genomics.

Hi @hoytpr - 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 organization-genomics.

Thanks @JCSzamosi, with a little luck, I'll be back here or somewhere around doing some good for data science education.

from organization-genomics.

You've nothing to apologise for, @hoytpr. I'm so sorry to hear you've been unwell and that the recovery is slow. Thank you for thinking it through, making a conscious decision to step back, and taking the time to update us here. We'll be delighted to welcome you back when you are ready, but until then look after yourself.

from organization-genomics.