8. 14th Jul. 2023 (Friday)

14th Jul. 2023 (Friday)

Meeting notes

Date: 14th July 2023, Friday

Target audience: ACCESS-Hive dev team

---

Goals/Agenda

• HOME page subsection #422
• Community resources subsection #425
• Working groups #424
• Quick workthrough MED (Sven)
• Things that should be moved to the main website and suggestions for images to go on Acknowledgement and Home page (Natalia)
• Revise introduction and other texts (Davide)
• Issue #420 what’s to come (Sven)
• Discuss which issues need to be prioritised (high priority mark on zenhub).
• What the user support page is gonna look like. User support should be on the same level on the hive and perhaps, it should not be inside the hive -- natalia.
• As the hive is the documentation place and forum is for discussion and we should not have user support on hive.

---

Discussion Notes

• Do we want to keep the navigation on the home page. One solution would be to render them as cards, not necessarily as important as the other cards.
• If we remove the community forum tab to some other place, we can include the about section in that place afterwards.
• After creating the about tab, we can discuss on what to include in that section.
• Contact should be included in the about page.
• The user support is to be discussed of how to go on the main website.
• Natalia suggested there should be a drop down menu linking where to ask for help.
• Have the user support on the home page and should be prominent on the home page.
• We could possibly include the user support card with the how to contribute card somewhere on the home page to be more prominent.
• Hive is the documentation the ACCESS-NRI is contributing to the community, and providing help to users for running their models.
• Training will go into the hive section.
• Hive forum is considered as any other forum or similar to StackOverflow forum. The idea is someone from the community to help with what we are working on.
• ACCESS-NRI is not providing a help-desk functionality and you ask questions from the community.
• Have a clear representation and link to the hive forum from the hive website.
• For the contribution part, we perhaps can create a separate page and if you have any suggestions, please indicate it on github.
• Have a template on the contribute page and you have the issue open with the template.
• Davide suggested we could possibly not have a navigation for the how to contribute page -- subject to discussion from the bigger team.
• There is no navigation for the how to contribute page.
• All the rest of things code of conduct, policies, and license could go in the about tab.
• Perhaps, hide the table of contents on the left and right from the home page.
• We might not need to have the images for the support and how to contribute buttons at all, might need to experiment with a little bit.
• Once we all agree, and the button could be more bigger and we could style it the way we want.

---

Action Items

• Include the about tab at the top right of the navigation bar (moving the community forum tab to somewhere else).

  • Include contact tab under about section.
  • Include code of conduct tab under about section.
  • Include policies tab under about section.
  • Include license tab under about section.

• Include the user support tab on the home page.

• Have a clear representation and link to the hive forum from the hive website.

• Restructure the contribute page to have clear instructions.

• Remove the how to contribute page from the home page.

---

Participants

• Sven
• Davide (online)
• Natalia (online)
• Jasmeen