ACCESS-NRI / team-meetings

Release management and coordination
Creative Commons Attribution 4.0 International
0 stars 0 forks source link

Release team meeting 2022-11-07 #4

Open aidanheerdegen opened 2 years ago

aidanheerdegen commented 2 years ago

ACCESS-NRI Release Meeting 07/11/2022

Time: 01.30p - 2.30p

Location: Teams and TBC (Boardroom unavailable this week)

Agenda

Item No. Topic Time (min)
1 Terms of Reference, role/purpose of these meetings 10
2 Team updates (i.e., achievements to highlight, information sharing across teams)
- Model Release
- MED
- Training
- Kelsey
10
3 Communications, Outreach & Engagement updates (Natalia)  5
4 Proposed topics (see below) 30
5 Any Other Business; record actions and decisions  5

2. Updates

3. Communications, Outreach & Engagement updates

4. Proposed topics

Definitions

Proposers: @aidanheerdegen @kdruken

Outcome: Inform team of current status and stimulate direct feedback offline

For this meeting to work effectively we need specific shared targets to focus activities and reporting. This requires good definitions of what constitutes products, releases, etc and their minimum viable products.

The intention is to give an overview of current thinking, with most feedback to be incorporated in a https://github.com/ACCESS-NRI/procedures-and-practices/issues/18

Roles/responsibilities

Proposer: @kdruken

Outcome: Review role and responsibilities for each team and what is in scope for the Release area.

Along with the definitions, these will help us work effectively and identify any gaps or highlight areas that are not immediately clear.

Useful links:

Style guide

Proposers: @rogeredberg @harshula

Outcome: Decide initial style guide to use as base and assign actions to start procedures and practices doc

A style guide obviates the need for tedious style choices, or worse taking extra time to check how this was done in the past (which is error prone and time consuming). We recognise there is a lot of legacy code and documentation with existing style conventions. The style guide should represent an ideal, recognising resource constraints will prevent this being universally retrospectively applied.

Some useful links:

Roadmap/goal tracking

Proposers: @kdruken

Outcome: Decide how best to track/monitor Release goals across the teams.

Team leads are reviewing the 2022-23 Target Milestones and looking to produce some implementation plans, so we can build some roadmaps. How can we best use ZenHub (or an alternative) in this space? New workspace: Release Meetings

Notes

Add meeting notes including links to action items (issues)

NBateman-bit commented 2 years ago

Hi, Not sure how I can add it to my section: but for this week the comms updates include: Icons, posters and cards, media release on the ACCESS-Hive launch and website update ready for the Launch (Code of Conduct, links , etc).

kdruken commented 1 year ago

Note carried the additional topics from this meeting over to next one (since we didn't have time to discuss).