Skip to content
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

Migrating to Workbench #35

Open
7 of 14 tasks
olexandr-konovalov opened this issue Aug 25, 2024 · 8 comments
Open
7 of 14 tasks

Migrating to Workbench #35

olexandr-konovalov opened this issue Aug 25, 2024 · 8 comments

Comments

@olexandr-konovalov
Copy link
Member

olexandr-konovalov commented Aug 25, 2024

This issue tracks migration to Workbench following instructions at https://carpentries.github.io/sandpaper-docs/migrating-from-styles.html

Update: migration completed, and now https://carpentries-incubator.github.io/gap-lesson/ already serves the Workbench-based version of the lesson. Remaining steps are to finish post-transition steps at https://carpentries.github.io/sandpaper-docs/migrating-from-styles.html#post-transition

The list of forks to check can be seen here:

Finally,

@olexandr-konovalov
Copy link
Member Author

olexandr-konovalov commented Aug 28, 2024

@rgaiacs in the past you have created a fork of this repository. Since I have updated this lesson to use the new Workbench platform, could you please delete (and re-create, if you want) your fork and all local clones of this repository. When done, please tick the box for your fork in the checklist above. Thanks!

@olexandr-konovalov
Copy link
Member Author

olexandr-konovalov commented Aug 28, 2024

@falque in the past you have created a fork of this repository. Since I have updated this lesson to use the new Workbench platform, could you please delete (and re-create, if you want) your fork and all local clones of this repository. Thanks!

@rgaiacs
Copy link

rgaiacs commented Aug 28, 2024

@olexandr-konovalov I archived my fork. I can't tick the box.

@olexandr-konovalov
Copy link
Member Author

Thanks @rgaiacs!

@olexandr-konovalov
Copy link
Member Author

@fingolfin @mtorpey @ChrisJefferson @james-d-mitchell - in the past you have created a fork of this repository. Since I have updated this lesson to use the new Workbench platform, could you please delete (and re-create, if you want) your fork and all local clones of this repository. Thanks!

@olexandr-konovalov
Copy link
Member Author

@dpshelio you have previously forked this repository to https://github.com/carpentries-i18n/gap-lesson. We need to decide what to do with that fork in the long perspective (it serves unapproved Ukrainian translation from Transifex for a preview, but it next version should appear in https://github.com/ukrainian-carpentries). Perhaps for now the right thing would be to at least archive it, to make it read-only. Could you do that, please?

@olexandr-konovalov
Copy link
Member Author

olexandr-konovalov commented Aug 28, 2024

@ssiccha @DominikBernhardt you and Christoph Schoennenbeck previously forked this repository to https://github.com/lbfm-rwth/gap-lesson, and intended to contribute it back to the main repository (lbfm-rwth#13) but this did not happen yet.

This is really unfortunate - you did a number of commits, and also have some open and closed issues with useful sugegstions. However, since I have now updated this lesson to use the new Workbench platform, it will not be straightforward to backport your changes to the lesson (the changes would have to be in another format in another files in another branch).

What are your plans regarding the https://github.com/carpentries-incubator/gap-lesson fork? If you don't intend to work with your fork in the nearest future, perhaps it would be useful to archive it, to make-read only and indicate that this fork is inactive? (You can later unarchive it, if needed). I would also recommend to delete all existing clones of this fork and of https://github.com/carpentries-incubator/gap-lesson. After that, if you'd like to contribute to the new version of the lesson, you can create new clones and new fork, and backport your changes there, in some small batches which can be easily reviewed. And if not, perhaps someone else may be interested to look at the changes and backport at least some of them.

@james-d-mitchell
Copy link
Contributor

@olexandr-konovalov I can't find a fork of this repo among my local repos or on github so I assume that I've deleted them already.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants