Skip to content

3. 14th June 2023 (Wednesday)

Jump to bottom
Jasmeen Kaur edited this page Jun 22, 2023 · 3 revisions

14th June 2023 (Wednesday)

Meeting notes

Date: 14th June 2023, Wednesday

Target audience: ACCESS-Hive dev team

Goals/Agenda:

  • Quick check-in on scope/motivation for our work over the next 2 months (I'm getting a draft quickly together now for us to refer to and discuss -- this is in response to the really great feedback from last meeting on how it'd be good to confirm what we're aiming for in this timeframe, etc)

  • Go thru Zenhub issues - confirm what board we'll use, review the existing issues and create any new known ones needed, discuss how best to use the board/customise for our work.

  • Discuss best meeting frequency and do check on our roles in the project (e.g., is there benefit for having a subset meet at regular time do go thru the working issues and use Wednesdays for decisions or blockers? Roles - double check who wants to be involved or responsible for what parts)

Source: Kelsey (posted on slack)

Discussion Notes:

  • Ensure a smooth information flow between the main website and the hive page.
  • Have minimal duplication and maximal consistency between the two websites.
  • Users should be able to easily go to the hive page from the access-nri page and vice-versa.
  • Clear navigation of the ACCESS-NRI page.
  • Document internal development guide for contributing or modifying the access-hive page.
  • Hard deadline for the legacy release of the hive pages is before the september workshop and few review stages before that deadline.
  • Soft release is aimed at the end of July.
  • Use these Wednesday meetings for the overarching discussions, relating to what things have been done, and planning goals ahead.
  • Double check the OM2 content development on the hive website.
  • Possibly, have sprint meetings weekly to refine and discuss the issues being added to the hive zenhub.
  • Evaluate and brainstorm ways for evaluating and measuring success of the hive page, perhaps gathering user feedback after the soft release, or having a Mentimeter in the workshop for the feedback on new hive website.
  • Aiming what success factors we will use to measure the UI experience of the hive page by the end of July.
  • Ensure proper acknowledgements are displayed on the hive page (for instance, sources include - CSIRO, COSIMA etc.)
  • Brainstorming ways of how we can best support the needs of advanced user classes on the hive page.
  • Perhaps, also make it clear for the users to find how to contribute guides in case they want to make some suggestions or suggest edits on the hive page. Making videos/gifs for how to contribute is one suggestion, so users can visually follow the steps for contributing.
  • Brainstorm ways for encouraging end-users to raise issues on access-hive GitHub as it is very easy to create issues on GitHub.
  • Have a clear development workflow (ideally well-documented) of what best practices developers should follow to contribute to the hive page.
  • For creating the zenhub issues within dev team, any suggestions or bugs could be added to the new column in the kanban board.
  • In case, we plan to host sprint meetings in the future, these meetings could then be used to discuss these new issues found, and whether they could addressed in this sprint (in Ready column) or future sprints (backlog).

Action Items:

  • Decide upon the content of OM2 configuration on the hive page.

  • All old Hive content to be mapped/migrated across to the new hive page.

  • Ensure proper acknowledgements of all information sources, possibly on the hive website and repo READMEs.

  • Create a how to contribute video and add it on the hive page as required.

  • Update the README of this repository.

  • Brainstorm ways of encouraging users to raise issues on the hive page.

  • Remove ACCESS-S configuration from the hive page.

  • Add the getting started section to the ACCESS-CM2 configuration.

  • Add the development workflow guide.

  • Brainstorming ways of how we can best support the needs of advanced user classes on the hive page.

  • Ensure a smooth information flow between the main website and the hive page.

  • Clear navigation of the ACCESS-NRI page.

  • Add all of the above actions items as issues on zenhub ;)

Add the above items as issues to ZenHub.

Participants:

  • Kelsey
  • Romain
  • Heidi
  • Natalia (attended online)
  • Davide
  • Sven (attended online)
  • Jasmeen

ACCESS-Hive dev website - https://access-hive.org.au/development_site/

ACCESS-HIVE docs SharePoint - https://anu365.sharepoint.com/:w:/s/ACCESS-NRI/EawQ3lx_A-5JrJgtGT1CD2gBFU51LnD5w5TiAUfDvU4pkw?e=RdWQ4l

Clone this wiki locally