Skip to content

update most references to trac wiki - #487

Merged
Jenny Hickson (jennyhickson) merged 6 commits into
MetOffice:github_wpsfrom
james-bruten-mo:trac_wiki_pages
Oct 30, 2025
Merged

update most references to trac wiki#487
Jenny Hickson (jennyhickson) merged 6 commits into
MetOffice:github_wpsfrom
james-bruten-mo:trac_wiki_pages

Conversation

@james-bruten-mo

Copy link
Copy Markdown
Contributor

Update most of the references to code.metoffice.gov.uk/*
A couple of new wiki pages have been created

Remaining ones:

  • Need updating when the UM Docs have a new build location
  • Links to Ants team guidance - ask if they have a new location
  • Some wiki pages, eg bitcomp, standard_jobs etc. The wiki_pages release instructions
  • Some references to old tickets in the UM release instructions
  • Standard Suites locations
  • Release Notes template

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

trivial suggestions, but generally good and ready to go

Comment thread source/Development/planning_your_change.rst Outdated
Comment thread source/Development/planning_your_change.rst Outdated
Comment thread source/Development/rose_stem.rst Outdated
Comment thread source/FurtherDetails/coding_style.rst Outdated
Comment thread source/Reviewers/codereview.rst Outdated
Comment on lines +113 to +115
* :ref:`UMDP3 (UM and JULES FORTRAN) <umdp3>`
* `LFRic Coding Styles
<https://code.metoffice.gov.uk/trac/lfric/wiki/LFRicTechnical/CodingStandards>`__
* `PEP 8 (Python) <https://legacy.python.org/dev/peps/pep-0008/>`__

`This page
<https://code.metoffice.gov.uk/trac/um/wiki/CodeReviewCribSheet>`__
provides some common (though UM-centric) things to confirm and think
about. It is not an exhaustive list, just a starting point.
<https://metoffice.github.io/lfric_core/how_to_contribute/coding_standards/fortran_coding_standards.html>`__

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do the same here as above

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

<https://code.metoffice.gov.uk/doc/um/latest/papers/umdp_003.pdf>`__ or
`LFRic Coding Styles
<https://code.metoffice.gov.uk/trac/lfric/wiki/LFRicTechnical/CodingStandards>`__.
* Ensure that the code is written to the standards laid out in

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and again 😄

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I was anticipating that!

Comment on lines +61 to +63
<https://github.com/MetOffice/jules/wiki/sharing_jules_metadata>`__
and in `jules-standalone, jules-lfric or um-atmos
<https://code.metoffice.gov.uk/trac/jules/wiki/SharingJULESmetadata#Whatsinjules-standalonejules-lfricorum-atmos>`__.
<https://github.com/MetOffice/jules/wiki/sharing_jules_metadata>`__.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did these want to still be sublinks to different parts of the page?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah not sure why I didn't keep those

Co-authored-by: Jenny Hickson <61183013+jennyhickson@users.noreply.github.com>
Co-authored-by: Jenny Hickson <61183013+jennyhickson@users.noreply.github.com>
Co-authored-by: Jenny Hickson <61183013+jennyhickson@users.noreply.github.com>
Co-authored-by: Jenny Hickson <61183013+jennyhickson@users.noreply.github.com>

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cheers, all done

Comment on lines +61 to +63
<https://github.com/MetOffice/jules/wiki/sharing_jules_metadata>`__
and in `jules-standalone, jules-lfric or um-atmos
<https://code.metoffice.gov.uk/trac/jules/wiki/SharingJULESmetadata#Whatsinjules-standalonejules-lfricorum-atmos>`__.
<https://github.com/MetOffice/jules/wiki/sharing_jules_metadata>`__.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah not sure why I didn't keep those

Comment thread source/Reviewers/codereview.rst Outdated
Comment on lines +113 to +115
* :ref:`UMDP3 (UM and JULES FORTRAN) <umdp3>`
* `LFRic Coding Styles
<https://code.metoffice.gov.uk/trac/lfric/wiki/LFRicTechnical/CodingStandards>`__
* `PEP 8 (Python) <https://legacy.python.org/dev/peps/pep-0008/>`__

`This page
<https://code.metoffice.gov.uk/trac/um/wiki/CodeReviewCribSheet>`__
provides some common (though UM-centric) things to confirm and think
about. It is not an exhaustive list, just a starting point.
<https://metoffice.github.io/lfric_core/how_to_contribute/coding_standards/fortran_coding_standards.html>`__

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

<https://code.metoffice.gov.uk/doc/um/latest/papers/umdp_003.pdf>`__ or
`LFRic Coding Styles
<https://code.metoffice.gov.uk/trac/lfric/wiki/LFRicTechnical/CodingStandards>`__.
* Ensure that the code is written to the standards laid out in

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I was anticipating that!

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks

@jennyhickson
Jenny Hickson (jennyhickson) merged commit 827c03d into MetOffice:github_wps Oct 30, 2025
2 checks passed
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

Successfully merging this pull request may close these issues.

2 participants