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.

Sign up for GitHub

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

Jump to bottom

what labels should we have? #5

Open
adagj opened this issue Jun 27, 2024 · 2 comments
Open

what labels should we have? #5

adagj opened this issue Jun 27, 2024 · 2 comments
Assignees
@gold2718 @matsbn @mvertens @JensBDebernard @oyvindseland @DirkOlivie @MichaelSchulzMETNO @hgoelzer @TomasTorsvik @kjetilaas

Comments

@adagj
Copy link
Contributor

adagj commented Jun 27, 2024

I suggest different (or additional) labels: Short compset names. We'll have N1850 for fully coupled piControl, NF1850 for amip style piControl, NHIST for fully coupled historical, NFHIST for amip style historical ect. I actually don't think NorESM is a good label. Feel free to think differently :)
@TomasTorsvik
Copy link

I would opt for additional labels, an issue can have multiple. Agree that NorESM is not very useful in this setting.

@oyvindseland
Copy link

I agree but it should not be overdone. There are very many compsets so they often have to be grouped together.

@mvertens mvertens changed the title Labels what labels should we have? Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gold2718 gold2718

@matsbn matsbn

@mvertens mvertens

@JensBDebernard JensBDebernard

@oyvindseland oyvindseland

@DirkOlivie DirkOlivie

@MichaelSchulzMETNO MichaelSchulzMETNO

@hgoelzer hgoelzer

@TomasTorsvik TomasTorsvik

@kjetilaas kjetilaas

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests