---
# System prepended metadata

title: 'Maintainers Meeting, 14th December 2022'
tags: [maintainers]

---

---
title: "Maintainers Meeting, 14th December 2022"
tags: maintainers
datetime: 2022-14-09T{{time}}UTC
location: Online, Discord, the `#voice-meeting` voice channel
teams:
- maintainers
participants:
- Giovanni (GB)
- Nitinder (NM)
- Daniel (DM)
---

## 📋 Agenda
- Add Simon to HackMd, other repos(?)
- ToDos from last week
    - [ ] DM: Implement the sync in redux per component 
    - [x] DM: Create skeleton for design guideline.
    - [x] DM: Add image autobuilder to frontend repo
    - [ ] GB: Check the HPI resources and update the Google form. Email HPI to get new hostnames.
    - [ ] NM: Create a FrontendWG. Invite Daniel and Michael. First meeting in early.
- Next meeting

## 📢 Discussions

NM: FrontendWG in new year. Keep it pending

GB: Hostnames and IPs are same for previous ones. Need to send an email to ask for new hostnames and IPs.

GB: Shared disk is still there. Hooray!

GB: Check when you use a resource and wipe previous applications to not bother your results!

DM: Small problem in Autobuilder. Delete relevant package 

GB: Better if only Runner publishes the image.

DM: Looked at several style guidelines. Structure like this (https://www.familysearch.org/frontier/styleguide/). Something similar for Oakestra. The guide will be in HTML format.

DM. Wiki is not the best place for it. Can we create a seperate page?

GB: Wiki has contribution section. It can have external link.

NM: The contribution guide should be together. The wiki contribution guide stays high-level and has links to the guide as link.

GB: High-level guide might remain similar but code specific things will change frequently

DM: Read about redux. Small changes required. Will be pushed later.

NM: Going on vacation. Will be back on 11th Jan for Maintainers meeting.

GB: We will have meeting next week (last one before end of year).

DM: SLA error from backend. Need to check. 

GB: For new release, we need to figure out the changelog, whats needed to be tested. Plan to new release in early Jan.

NM: Will this be major release?

GB: Release will embed frontend. So likely major

GB: Current release tag `v0.4.2`

NM: We need to figure out a strategy for release numbers. How about changing to a scale of 100? So change `v0.4.2` to `v0.40.2`?

GB: Change the minor number on minor changes. Change the 10 count at major change. We need to pace ourseleves for road to v1

NM: Can we do minor release with bugfixes and release it with `v0.40.3`

GB: We need to keep everything on same number.

NM: Sync releases of all components to major release. So `v0.40.x` with `v0.40.y` of every other component.

GB: Add the * in the minor version of deployment descriptor will handle the major version mismatch between components

NM: Start creating small blogs (like in the wiki) with new release version details, naming schemes discussions. 

NM: We should start creating a blog with major release

NM: checkmarking on release and tasks. Assign stuff to people and signed by the person who checks. 

NM: maybe create guidelines 

## 🛠️ TODOs

NM: Create a FrontendWG. Invite Daniel and Michael. First meeting in early.

GB: Check the HPI resources and update the Google form. Email HPI to get new hostnames.

GB: Add a note in our Google spreadsheet about resources cleanup

DM: Create a Github page with guideline and add link to Wiki

DM: Implement the sync in redux per component

GB: Add task about automated develop images build

All: Discuss the major and minor release segment of the system. Figure out how to break it up and what the next immediate release should be. Also blogs for release.

NM: Figure out the HackMD GitHub push account





