NetBox maintainers meeting minutes, 21 Mar 2024

[jeffgdotorg]

NetBox maintainers meeting minutes, 21 Mar 2024

[Jeff] Reminder: Our second retrospective is next week

• Please think about your start / stop / continue items, and review our agreed outstanding actions.

[Jeff] Plugin certification is launched; now the hard part starts

• Massive thanks to all the plugin maintainers (including Abhi) who helped Jeff and the NetBox Labs team define and announce this program.
• Thanks in advance to the team for your future help making the program an ongoing success.

[Jeremy] New tooling for issue triage

• A GitHub action will be set up to automatically handle each new issue
• ↳ A "needs triage" label will be assigned per the issue template
• ↳ Assign the issue to a randomly-selected maintainer
• ↳ Ignores issues opened with an assigned owner
• Assignments will be weighted
• ↳ Jeremy: 40%
• ↳ Arthur: 40%
• ↳ Dan: 10%
• ↳ Abhi: 10%
• Triage assignment does not mean you must address the issue, just that you're responsible for triaging it per our intake policy
• I hope to have this set up next week

Further notes from Jeff

• We need to get better at issue triage. To date it's been just Jeremy doing it in his spare time.
• Jeremy found an action that auto-assigns issues or PRs to a pool of users. It supports up to 10 users, and we can get a weighting effect by putting Jeremy and Arthur in the rotation multiple times. We believe the rotation is random; still testing to be sure it does what we think and want.
• From looking at the current open issues, we're not being effective at this function. Some issues sit for weeks or months, which is going to create an unwieldy backlog, and that's not good for anybody.
• We get around 120 issues per month if we discount ones created by the team, so not a huge burden per maintainer.
• This feels to Jeremy like an equitable split. We'll try it and iterate as needed.

[Jeff] Off the record: impact of Redis license change

• The team discussed the implications of yesterday's announcement. No decisions or official response resulted.

[jeffgdotorg]

Following up the Redis license change agenda item: We've dug into this more deeply and concluded there's no impact to our users or customers.