11. 2nd August 2023 (Wednesday)

2nd Aug. 2023 (Wednesday)

Meeting notes

Date: 2nd Aug 2023, Wednesday

Target audience: ACCESS-Hive dev team

Goals/Agenda

Discuss how to place warnings on “not fully supported“ stuff
Hive purpose
Clear Home page introduction! (We need to decide on the exact words)
How to contribute page? Best structure for contribution (to be easy for people and useful for us)
Working Groups?? Discuss how to make it stand out
ACCESS-AM??
Model configuration/component pages. Need restructure/rewriting
Updates on the new icons
Discuss about the external review strategy by mid-August.

Discussion Notes

MED SUPPORT WARNINGS

How to display the warnings about the expectations for material on community resources.
We removed support icons from the hive and that could be something we could have just for the MED.
Support means on MED is that if people have any problems with the content, then MED team can help them running it GADI.
We can all the content in hive attributed and acknowledged.
May be instead of the warnings, we could have the status of the release of what is supported by ACCESS-NRI or NCI etc -- Kelsey.
Inverse of the warnings of what we not support, we could have warnings for the tools that we support.
Support levels could be indicator, if they are completely supported by us and this one is not that supported.
In the legacy release, and there are some things that we have to be careful about for the legacy release. The title of the warnings could be a bit catchy.
The three support levels could be demonstrated using the red light colours (traffic scheme).
The support icons could be something that we could discuss in the future, and they could definitely be reused.

HOW TO CONTRIBUTE

Some people might not contribute through GitHub, or some might just raise issues on github.
We might need a marketing "how to contribute" simple guide and should be flyer site. Contribute through GitHub - then raise an issue on github or clone the repository. Or have discussions on the forum.
Might need to think about watching all topics under the section "Hive suggestions" and dedicated topic and we can monitor the feedback.
We might capture some ideas on the forum - some people might have really good suggestions.
We might just have two categories - github and forum.
There is an issue with the footer on MED, might just need to think about the alignment for MED.

COMMS IMAGES COLLECTION

Natalia would be working on changing the logos and images on the hive.
The other images point is we need to have a shared folder for images for all websites on Sharepoint.

WORKING GROUPS

How the working groups should be displayed on the hive page.
Might just include it on the home page as a shortcut link.
On the working group page, we could have the working groups just on the ACCESS-NRI or ACCESS-Hive page.
For info on joining the working groups, we could just have on the main website or we could just rephrase the working groups page on the hive.

ACCESS-AM

We need to run the ACCESS-AM content and we need to take it out from the home page, and once it is complete we could add it back.

RESTRUCTURING OF THE MODEL-CONFIGURATIONS/COMPONENTS PAGES

For ACCESS-CM, and we could perhaps have the information in the table and Davide might just be working on improving the UI of the model configurations/components page.
The citation at the bottom could be improved perhaps.
For flagship releases which includes the configurations developed from ACCESS-NRI.
For aerosols and atmospheric chemistry, Martin suggested that they are often talked about together. Davide suggested that we might need to be bit more consistent with the images we use on the hive page.
The relationship between the atmospheric chemistry and aerosols could perhaps be bidirectional.

External reviewers

We might need to invite the external reviewers just now and if not the beginning the week after that.
Kelsey suggested - we could ask Aiden, Claire for the text they used to invite external reviewers at that time.
Martin suggested that he would be sharing the email addresses for the external reviewers with Heidi.
This week Thursday or Friday could prepare a draft for the external reviews email.
The home page could be left as it is for the external reviews, however, that could be improved progressively. The invitation could include a list of things that are still under development.
Might need another SkillShare for the user support model - related to the hive content, Aiden might just be working on that.

Action Items

Participants