What is the status of MOSRS migration to GitHub? How can Partners help? #334
|
Are there any updates on the 2023 presentation on the Science Git Migration Project? I am especially interested in non-LFRic projects and |
Replies: 2 comments 4 replies
|
General update: we are still planning on widespread near-total migration before the end of March 2026, with LFRic etc expected to be fairly close up on that. There are some constraints e.g. forking the physics, and constraints on other areas such as e.g. Met Office parallel suite PS47 for workflow migration, GitHub changes, and allowing of changes to Met Office archiving that mean that we'd prefer to push most things to move around late 2025. We're working on a lot of the details as well including on workflows and preparing general advice documentation. However there are things like GC documentation that are aiming to move very soon, and the training rollout has started and will support earlier migration. The training is open to partners, but mostly in UK timezones - we are looking at wider partnership training outside those times. We are currently hung up on the creation of a new MetOfficeCollab GitHub organisation that we think will allow us to manage the external-collaborator-in-teams GitHub user management issue. Then effectively all the code.metoffice.gov.uk content partners can see will go there as a new home, including the workflows. Workflows specifically - I have a proposal that I would really like some feedback on, but I'm not sure of the best way to share it - can anyone here advise? It's currently a Word document - happy to convert it to any other format etc. Or I can post it here, but it's rather a lot... Generally, what can partners help with? We'd love feedback on proposals, the training, the migration advice, etc, as they get developed and if partners wanted to actively contribute to the drafting of those, that would be excellent. |
|
If its shareable just attaching the Word document as a file to this thread would be useful, and avoid the pain of SharePoint permissions. |
|
Hi Ben Fitzpatrick (@benfitzpatrick) , is there anywhere that timelines have been outlined for the migration to Github of the different codes (ie: LFRic_core, LFRic_apps, UM, etc) and suites (ie: Regional Nesting Suite, Regional Ensemble Suite, GC5LFRic, etc)? |
|
David Lee (@davelee2804) Please see /discussions/337 which covers the code repositories (stc). Current status: testing migration tool. |
|
Thanks for the link Yash! As to the suites I suppose that's a question for Ben Fitzpatrick (@benfitzpatrick) yes? |
|
We could do with more comms on suites and workflows. We are working out migration recommendations (e.g. how to suggest a first guess mapping from rosie id to shared GitHub repositories - maybe 100-200 of them, how to stand up e.g. MLFlow to replace rosie search capabilities). This is a bit of a Met Office answer, but we're blocked from moving away from Rosie ids by our archiving system until that's replaced and non-Rosie-ids configured in ~September/October 2025, so it depends on that delivery. I think the first workflows at the Met Office to migrate will be approximately then on current timescales, but we can do a lot of prep before then, and we could in theory support earlier migrations for others. |
General update: we are still planning on widespread near-total migration before the end of March 2026, with LFRic etc expected to be fairly close up on that. There are some constraints e.g. forking the physics, and constraints on other areas such as e.g. Met Office parallel suite PS47 for workflow migration, GitHub changes, and allowing of changes to Met Office archiving that mean that we'd prefer to push most things to move around late 2025. We're working on a lot of the details as well including on workflows and preparing general advice documentation.
However there are things like GC documentation that are aiming to move very soon, and the training rollout has started and will support e…