Skip to content

add definitions box - #409

Merged
James Bruten (james-bruten-mo) merged 4 commits into
MetOffice:github_wpsfrom
jennyhickson:definitions
Jul 15, 2025
Merged

add definitions box#409
James Bruten (james-bruten-mo) merged 4 commits into
MetOffice:github_wpsfrom
jennyhickson:definitions

Conversation

@jennyhickson

Copy link
Copy Markdown
Collaborator

Making the definitions we're using easier to find and adding some initial things to this box. If it gets too big we might want to consider moving it.

Also deleting the files that have been made redundant so far.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Good shout adding this
A couple of comments...

@@ -59,14 +59,24 @@ the process is very comparable to that of the other repositories too.

To get started with the ``gh`` cli, see the `gh quickstart guide <https://docs.github.com/en/github-cli/github-cli/quickstart>`_

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Is it worth adding a link to the github glossary near this? Something like,

The github glossary https://docs.github.com/en/get-started/learning-about-github/github-glossary_ contains additional definitions to those below

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The mix of markdown and rst didn't work there! I had github glossary as a hyperlink!

Comment thread source/WorkingPractices/working_practices.rst Outdated
Comment thread source/WorkingPractices/working_practices.rst Outdated
All general development for Simulation Systems Github repos will take place on forks of that repository. It is the responsibility of the developer to maintain their own fork. See :ref:`forking` for advice on forking.
All general development for Simulation Systems Github repositories will take place on forks of that repository. It is the responsibility of the developer to maintain their own fork. See :ref:`forking` for advice on forking.

The development cycle can be seen below. ``Upstream`` (blue) refers to parent repository, owned by the MetOffice github organisation. ``Downstream`` (grey) refers to the forked repository, owned by the developer.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Do we want to remove the hinting of colours? Or am I getting ahead of myself given this is likely not the final flow design?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

I figured the flow design was likely to change and we can always include a key in the picture or add a note with it around colours once the final thing was sorted.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Yeah fair enough

Co-authored-by: James Bruten <109733895+james-bruten-mo@users.noreply.github.com>
Co-authored-by: James Bruten <109733895+james-bruten-mo@users.noreply.github.com>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Cheers, looks good

@james-bruten-mo
James Bruten (james-bruten-mo) merged commit ca0a785 into MetOffice:github_wps Jul 15, 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