Skip to content
This repository has been archived by the owner on Oct 12, 2022. It is now read-only.

docs: add triage meeting notes #46

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
61 changes: 61 additions & 0 deletions community/minutes-of-meeting/triage-calls.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,61 @@
### Janssen issue triage (5th Jan 2022)
- Attendees:
- ossdhaval
- nynymike
- yuriyz
- yurem
- moabu
- hemantkmehta

#### Agenda
- Since this is initial triage meeting we quickly refreshed our understanding of three labels: `needs-triage`, `ready-for-triage`, `triaged`
- Went through current open issues
- priority-0, priority-1
- needs-discussion
- ready-for-triage (couldn't complete triage for all issues)
- we also discussed about having a label for issues which we don't want to take up immediately, but then we decided not to have additional label but let priority label decide when we take up issue in active development
- [dhaval] Code owners are requested to watch for issues labelled with their component label and `ready-for-triage`
- [Mike] Janssen should target weekly release cycle
- [Mike] Janssen releases automation and release notes creation needs to improve. Similar to [mod_auth_openidc](https://github.com/zmartzone/mod_auth_openidc/releases/tag/v2.4.10)
- [Moabu] Discussed monorepo
- [Mike] will discuss issues to get more clarity on business demand and priority.


- Messaging




#### Quick links:
- [Triage process document](https://github.com/JanssenProject/home/blob/main/triage.md)
- label for triaged but on hold `closed-wait`


### Janssen issue triage (21st Jan 2022)

- Attendees:
- ossdhaval
- nynymike
- yuriyz
- yurem
- moabu
- hemantkmehta

#### Agenda

- review action items
- Issues at high-level
- Total: 123 (triaged:15, ready-for-triage:25, needs-triage: 79)
- priority 0 or 1: 3
- needs-discussion: 0
- Need to identify `good first issue` and `help wanted`
- Discuss `ready-for-triage` issues


### Action items:
- `done` 5th Jan 2022 : Dhaval to setup follow up triage meeting
- 5th Jan 2022 : Dhaval to get back on whether we can host artifacts on maven central which are not released yet
- 5th Jan 2022 : Automation for `needs-triage` label (Dhaval/Mohammad)
- 5th Jan 2022 : Add PRs to triage
- `done` 5th Jan 2022 : Use github project boards or Projects (beta)
- 5th Jan 2022 : automation to add comment on issue when a label is added