Here the log of the meeting which is also posted @ https://github.com/supercollider/supercollider/wiki/Development-meetings:-minutes#2025-04-06
Thanks for everyone who showed up, it was great to see so many faces!
SuperCollider dev meeting - 2025-04-06
Present: MarcinP (dyfer), TedM, JamesS (jrsurge), Christophe, YannI, MikeMcC, DennisS (capital-g), JordanH, Tobias (HotwheelsSisyphus/girthrub), Gianluca (elgiano), MichaelW (cdbzb), ChristofR (Spacechild1), Simon
PRs/Issues discussed
- This procedure will take over from now on
- Dennis will post a finalized list on GitHub wiki
- We will try GitHub Code Owners to automatically figure out who needs to review PRs (see ToDos)
- Assigning PRs: We don’t assign to other people, but self assigning is welcome
- It is okay to ping people to get their attention, but teams should be pinged before people
- Merging procedure:
- currently: at least one approval, a different person merges
- current merge procedure can continue as-is - council people can step up if PR gets stalled or manage a discussion in case of conflicts.
- with the council structure:
- ppl responible for saying yay/nay on a give issue if the issue is stalled
- big changes still need to be discussed with community
- Marcin added Ted Moore to the SC GitHub team and added Tobias (HotwheelsSisyphus) and Ted (tedmoore) to the wiki team as well.
RFCs
We decided to deprecate this procedure - so please do not create or request any new RFCs from now on. The repo will be kept open for now in order to progress on the still open RFCs.
A proposal by James
I’d urge us to move towards Architectural Decision Records (ADR) coming out of the councils - “here’s what we’ve decided and why”, rather than “here’s what we might like to do”
Consensus that web browsers are a desirable “first party” platform. Although this is in an beta state (e.g. no file access yet) and using some deprecated API (which Dennis wants to rewrite at some point), this PR will move on by getting a review from James.
The docs team will finalize the styleguide with their preferences (e.g. there could be a dedicated meeting for this).
I final “go” for sticking to this from now on could be voted in the next dev meeting.
Christof requested a review as this is a crucial steps towards the resompling/reblocking feature (which will be part of a 3.15 release).
Has now already been merged.
The will be an upcoming release of 3.14 without any plugin api changes.
Afterwards, there will be a quick 3.15 release afterwards which will introduce changes to (break) the server API.
Forum / Wiki
We would like to rely more on the forum and move e.g. the GitHub wiki towards the discourse forum (see Editing and creating wiki posts - Using Discourse - Discourse Meta).
On the other hand there are concerns about the longevity of the forum regarding ownership, backups and financial resources - see If you value this site, please support it!.
Maybe some more transparency or some structure can help to share the responsibilities here.
Before there is a clearer picture about it the Wiki will stay at GitHub.
ToDos
- Dennis: Put James S and Marcin into GH organization structure
- Dennis: Write a final version about “council” structure, will be posted in the Wiki (maybe this will become obsolete once the codeowners thing is implemented?)
- Dennis: Create a CodeOwners file according to the council structure
- ?: Setup GitHub (sub)-teams according to the council structure document
- ?: Create a forum topic for each council?
- Dennis: Organize next meeting in around 2 weeks via the forum
Topics for next meetings
- Re-evaluate the permission structure of GitHub
- Should we look into creating some kind of legal entity? This would allow to share access to resources such as paying bills for domains, servers and dev certificates
