As stated in Maintainers calls in late Feb '22 and early Mar '22 the quarterly rebasing/grooming/triage of issues in the Hypha OSS repo is due (well overdue technically!)
So I’ve created a new ‘stream’ in Zulip chat here where I’ll post conversation topics/updates: Zulip
I’ll also be doing the rebasing/grooming/triage of issues in google meet video room that act as ‘drop ins’ for anyone if they want to drop in and participate or see how it’s going for however long they want to.
On these days a times (GMT UK time):
April 6th 10.00 - 12.00
April 6th 13.00 - 14.00
April 7th 10.00 - 13.00
April 8th 10.00 - 13.00
I’ll also be posting ‘round ups’ of issues gone through in comments on this forum post as I go (e.g. numbers of issues covered, key actions, themes etc.) or edits to this main body of this post.
Rebasing/grooming/triage in an OSS project should (ideally) be a collective/collaborative affair and in my experience benefits from broad knowledge, context and understanding as issues are ‘gone through’, closed (with comments), updated, given better current context or similar and merging similar issues or collecting like issues in METAS/EPICS.
Given that the issues in the Hypha OSS repo are intended to meet the needs of both individual adopters and collectively adopters needs.
This does make rebasing an effort to understand the state of the repo from multiple adopter perspectives including adopters that may be future adopters.
Also remember, closing an issue or PR or similar doesn’t make is disappear forever, it can always be ‘reopened’.
I don’t expect i’ll get through everything in great detail during this time but it’ll be a start.
Y’all can find context of where this topic has originated from here: GitBook
and my follow up proposal here: 3 proposals for adopter and maintainer input: Open Roadmap, voting / 'wish list' and Quarterly Milestone Rebase process