Skip to content

Home

Jump to bottom
Jasmeen Kaur edited this page Jun 28, 2023 · 35 revisions

Welcome to the access-hive.github.io wiki!

Contents included in this wiki

Major Milestones

Date Description
21-Jun New Hive skeleton in place, main website linkages identified/tracked as issues
28-Jun All or close to all content in place (review in meeting), reviewing any major skeleton changes needed on main website
30-Jun Internal release and review
15-July External feedback
31-July Soft release (major update goes live)
15-Aug Release, advertise in mid-Aug newsletter and regular channels (social media, Forum?, main website)
4-8 Sep Actively being referenced during the Training and Workshop events

ACCESS-Hive docs and Legacy Release

Topic Description
Project ACCESS-Hive Docs & Legacy Release
Purpose To review and update our ACCESS-NRI websites (main website and ACCESS-Hive) to prepare for the release of the first round of ACCESS-NRI outputs.
Goals - Consistency and smooth information flow (with minimal duplication) between our main website and the ACCESS-Hive
- Success looks like: content on either main website OR Hive captures:
- What we offer
- How to run (or get started) supported models:
- CM2
- OM2
- ESM1.5
- How to run (or get started) on available MED tools
- The forum and how to get started
- How to find WG info and join
- ACCESS-NRI support information
- Contact info
- Community additional resources
- How to contribute to the Hive
- All old Hive content has been mapped/migrated across
- Nice to have:
- Something future focused – plans/goals/roadmap
- How to run AM3
- Clear and easy to follow information and navigation of ACCESS-NRI supported outputs
- Success looks like: External user feedback on how the user experience was (were the pathways for information organised in a useful way, clear, easy to follow)
- Documented internal development guide for contributing or modifying to the ACCESS-Hive
- Success looks like:
- Basic best practice guidelines, procedure on how submit changes, who approves what, etc.
- Develop release/deployment checklist
Audience ACCESS Community including new and existing users of ACCESS models, data and tools as well as funders and stakeholders.

Example users:
- New users (students, postdocs who have never run an ACCESS model or tool)
- Experienced users who need to reference/look up information on ACCESS modesl, tools, etc.
- Users only interested in working with ACCESS or other model output (I.e., MED focused)
- Users only interested in running ACCESS models (less interested in MED/data output tools)
- Funders/stakeholders (all the proper acknowledgements are clear, easy to find, link to main website if on the Hive, etc.)
- ACCESS user – if on main website, clear way to get to the Hive/user portal
- User who wants to contribute content to the Hive (direct and indirect, varying Github levels)
Story General agreement that the ACCESS-NRI material needs to be clearly presented and discoverable when users go to the Hive...

access-nri.org.au: This is our public-facing webpage which has recent news, job opportunities and static pages. It is designed for our funders and stakeholders to see what we are doing. (SEE COMMS plan – maybe refer/use same language)

access-hive.org.au: This is our user portal. It is designed for anyone who wants to use ACCESS-NRI outputs, including those who want to find data we have generated, those who want to use our tools to evaluate/analyse model output, those who want to run our model configurations and those who want to contribute to our model development. It includes both user-contributed and ACCESS-NRI-supported documentation.
Timeframe May – Sep 2023 (due by Community Workshop)
Team - Kelsey (lead/PM)
- Romain (MED content and Github management/deployment - Sven is delegate for MED things when Romain absent)
- Heidi (Model Development content – Davide is delegate for Heidi)
- Davide – primary on Hive design/restructure, Model Dev delegate
- Jasmeen – primary on Hive design/restructure, primary note taker 😊
- Sven – primary on Hive design/restructure, MED delegate
- Natalia – primary on branding, main website, linkages between websites
- Martin – oversee/technical advice and check point on model development
- Aidan - oversee/technical advice and check point on OM2 content
- Roger - oversee/technical advice and check point on training specifics
Meetings Weekly on Wednesdays at 12:00 (full team).
Smaller sprint meetings (Fridays - 14:30)

Source: ACCESS-Hive legacy release notes on sharepoint

Other Resources

  1. ACCESS-Hive development site (used as a staging branch for contributing to Hive) - https://access-hive.org.au/development_site/

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

  3. ACCESS-Hive home page - https://access-hive.org.au

  4. ACCESS-NRI home page - https://www.access-nri.org.au

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