Development meetings: minutes

2023-12-17

People in meeting: Dennis, Michael W, Eduard F, Mike M, Marcin P, Christof R.

PRs to discuss

Qt5 -> Qt6 transition
- 2 Steps
wiki migration
- The current wiki will be replaced/updated by Mike during the holidays
clang-format update
- tag this commit
- contact Moss?
- pre-commit additional PR
SC domain
- Contact Josh/James about
Updating plugin interface / Moving Plugin Interface C++ -> C, making it extendable etc
WebAssembly - discussion on maintainability etc

Meta topics

Where to focus our limited resources; how to prioritize what to work on?

Larger issues to tackle

for the longevity of the project

lang
- garbage collerctor bugs...
server
- plugin interface updates
- wasm?
IDE
other aspects
- Qt6 update
- package manager with binaries (Quarks2 etc)
dev
- provide a list of "who-to-contact" for what regarding develoment on the forum/github (e.g. having a PR for scsynth, who can I contact to obtain a final(?) word on a problem)

2023-10-14

Planned as the "Server group" meeting

In the meeting: James S, Marcin P

Discussing the “Keeping SC evolving with minimal impact (…)” thread on the forum JS points out:

lack of a roadmap
there needs to be leadership within groups
Need to modernize code >> needs tests
Development is too scattered

Ideas on how to come up with a roadmap:

Everybody gathers every X months
Prioritize all tasks
Choose something from the top
Work on that task
Check in about the progress at the next meeting

2023-10-08

In the meeting: Simon, Marcin P, Michael W, James S, Mike M

macOS build issues - discussing libsndfile from homebrew; Marcin will investigate
Discussion on qt6 port and webengine hurdle; last work of was done here
Discussion on pushing the project forward:
- desire to create explicit policies for breaking changes that can't be easily deprecated (like fixing long-standing DSP bugs)
- consideration on backwards compatibility when discussion changes
- can we guarantee to the users:
  - your code should work X years down the line
  - SC works on the newest machines
- need to balance between SC being a lively tool vs a museum for old pieces We might need to be more careful on how we deprecate things; but we shouldn't hesitate to deprecate Automated tooling

Discussed PRs

changing the posting format PR
- Probably this is a good change, in accordance with our code style guide
  - Marcin will review
    - Make a point about storeOn being a breaking change, but probably okay
    - Mention in the review that this should be considered for Event and other classes; reference code formatting
Multiple config files
- Boost testing - James would prefer to use a different test framework
  - Adding test framework should become a separate PR
- Renaming the sclang folder - a separate PR
- Whith the above changes in place, create and review just the configuration file loading change

TODOs and other matters:

Marcin: check macOS CI building
The need for a roadmap for bigger tasks like Qt5 -> Qt6
The need to keep discussions on few features etc. on track, so that we can move forward
Future on GUI framework and Qt6 licensing
Marcin: make a clean Qt6 branch
Consider the need to redo our CMake files

2023-10-01

"Class library" group meeting

In the meeting: James S, Marcin P, Simon D, Michael W, PyoungRyang K

discussion on rebranding the developer tracks as proposed by Mike McCrea
- too soon to change the name
- table the discussion until another meeting
From the previous meeting:
- idea of trimming down class library
- would need package management system
  - various proposals floated before
    - sharing the whole class library
    - search paths
  - new package management system
- musical notation
Discussion on package management
- two separate features:
  - package managemen
  - session management
- the packer manager needs to provide:
  - conflict resolution
  - binary files
  - searchability
    - classes
    - help files
  - versioning!
    - SC compatibility
    - OS compatibility
  - additive configuration - installing requested extensions on top of "home" extensions (e.g. for local hardware etc)
  - need to solve the patch management between sclang and scsynth
- the session manager needs to provide:
  - transferring project to another machine
  - switching extension sets (overlap with package manager?)
  - need a format to combine sc code and requirements
  - "lock" file that lists extensions
  - discussion on how to store that data
    - change .scd format to include metadata
    - or use multiple files in a particular directory structure
  - save/recall the current state of the project
- discussion on existing solutions: deken
- security concerns of a possible solution
- what are the bedrock improvements
- note Josh's the idea of using quarks as a surrogate for the project
- Class library not booting when conflicts are countered - could this be addressed regardless of the package manager solution? e.g. "safe mode" boot with basic class library if that happens
- Order of actions: discuss search paths > package manager > session manager
  - ref. Nathan's wiki page https://github.com/supercollider/supercollider/wiki/Path-searching
Discussion on Piping functions
Note names
- discussion on Lilypond syntax not applicable
- PyoungRyang describes their system that also generates MusicXML: https://github.com/prko/Notator
- note name shouldn't just be a map to the midi note name

2023-09-24

8 People showed up! 👍

In the meeting: MarcinP, DennisS, MaximilianR, EduardF, MichaelW, ThalesR, MikeM, JamesS

Update by sclang dev group

Modularization
Quark/package manager System
Pitch class representation

Meta discussion about developer groups

Discussion about the communication about the publication about events within the forum - maybe it needs some improvement in regards of people who want to be notified.

There are 3 threads:

Subscribe to the the Developer meeting polls thread to keep track of future meetings and their planning. Use the bell icon to receive updates via Mail.

JamesS: One proposal / original idea of the splitting of the dev groups: Should the sub-groups still meet within the main-dev meeting and go into break-out rooms, so an communication between the teams can established, but also a focussed discussion would be possible. Yet, additional meetings within the team is still encouraged. One idea of sub-groups is/was to give the authority about decissions to a group of people which can be adressed.

=> General meeting with breakout rooms

Related discussion on code of conduct and safety for participants.

Maybe founding a SC-Mod/Awarness team to have the possibility to adress Code of Conduct violations and try to resolve the issue. The resolution could/should be handled first privately via a PM.

One way to resolve this could be a sticky post which covers a small introduction and the "who-is-who" within the community like release-manager, moderators.

How should a bespoke person for groups emerge? Naturally or "enforce" it?

Questions

Should focus group happen within the "core"-meetings or should they have meetings on their own?

Core meetings focus on meta-discussion (but still PR discussion possible).

Actions

Create stickies on scsynth.org
- Introduction to the forum
  - link to the dev-threads
  - explain procedure about meetings
  - state moderators and release-managers
  - state actions for violation of Code of Conduct)
  - Add links to other ways of communication like Telegram group, Matrix room
- All meetings are anounced unified in a single thread (sticky)
- Polls are announcemed in the poll thread (make sticky also)
Communicate on the class library and synth focus group that the meetings will be announcement on the main poll/announcement threads
- Marcin will make a poll for the class lib meeting next week
James will look into moderating interactions in the SC community

Discussed PRs

https://github.com/supercollider/supercollider/pull/6068 - needs more eyes
https://github.com/supercollider/supercollider/pull/6073
https://github.com/supercollider/supercollider/pull/5974 / https://github.com/supercollider/supercollider/issues/5973
https://github.com/supercollider/qpm/pull/14 => Will be archived by Marcin with a small note on why at the top of the README

2023-08-06 (sclang sub-group)

Attendees: Josh, Michael, Mike, Mike, Stefaan, Jordan

Started out discussing the Dev process.

At a high level, we’d like to see:

Clear development cadence for a sense of momentum and that SC is a live project.
Communicate the dev process more clearly so people new to contributing have a sense of the process, and where they can start.
Focal “projects” to rally around, that can also drive release milestones.

Focal projects

Ideally these would consist of small working groups (or very motivated individuals) that do the varied work of large changes:

E.g. state the problem clearly to the community, field their ideas in response, triage and prioritize requests, set the milestones and provide periodic summaries to keep the community updated and solicit targeted feedback.
A couple examples of focal projects might be ():
- Cleaning up the quark system: systematically identifying and removing pain points
- Refactoring the class library
- Outreach and documentation around dev processes
An example of a project suited for a personal initiative:
- Make the Quark library more deeply searchable (keywords, class names, etc.)
Not everyone wants or has time to be involved with larger focal projects, we should still be actively supporting individual initiatives for those with passion projects (more exploratory, open-ended, or less deadline-driven)

Refactoring the Class Library

Some initial discussion took place...

The existing directory structure in SCClassLibrary already suggests what might stay and what might better be a Quark, e.g. “Core” should obviously be kept.
Interestingly, any group implementing this would, in the course of testing, come up with a “Vanilla SC install”, akin to pd-vanilla. This is essentially the goal of the project: to make SC itself “vanilla”.
- So as a thought experiment: in lieu of consensus or of a successful refactor, what about the possibility of an officially maintained fork: sc-vanilla.
- - there were murmurs of skepticism, w.r.t. counterproductively growing the maintenance base, but… worth considering?

Low-hanging fruit

How do we move through “low-hanging fruit” on the ever-growing Issues list?

Meanwhile we have people eager to become new contributors!

New Contributors are confused on how to get started and on the review process.
- What’s the review process? Who are reviewers?
  - Related resources:
  - Reviewer instructions
  - Creating-pull-requests
  - git-workflow-and-guidelines
  - It could be worth refreshing/reorganizing these. And should they be cross-posted elsewhere?
- How do we get more people to join the review process?
  - We have “good first issue” for contributors, how about a “good first review” for reviewers?
We can try to make more effort to usher in and follow through with “Good first issue” contributors.
This has been discussed many times on various forums, it’s worth revisiting those posts...

Documentation

The never-ending Project

It’s a common complaint, and a #goodFirstIssue
Related resources:
- contributing-helpfiles
- Setting-up-the-IDE-for-easy-contribution (this could use improvement)
Recommend: a SCDoc Style Guide, akin to SuperCollider Style Guide https://github.com/supercollider/supercollider/wiki/Code-style-guidelines -This would make the those good-first-issues related to Docs much smoother!

Self-advocacy

We recognize dev efforts are spread thin, if you have an open issue or PR, you may need to follow through with pings/reminders.

Don’t be afraid of being annoying, showing enthusiasm and commitment is generally a good thing ;)

“Projects” as swappable quark packages

A kind of meta quark that would install all required quarks for your project

Temporarily remove non-project quarks?
Would help when sharing/migrating your project to new systems.
There is partial support for this already, but could definitely be smoothed out.
Examples:
- Your art project has x, y, z dependencies. You sit down to work on it, when opening that project you can expect all the quarks to be loaded/pulled down, and none you didn’t need.
- For contributing to the SC, you want to make sure you’re not accidentally including Quark-dependent methods, so you load “SC Dev” Project that removes/disconnects all quarks so you can be sure you’re just compiling the default classlib.

Namespaces

…aren’t technically supported (maybe SC 4 X-P), but for Quark authors, a prefix on class names is helpful. Ex: Josh’s CTK quark.

keep in mind that if you modify your existing quarks, it can break that for users that already use it. Make use of the quarks versioning feature so users can check out old versions!

This brings up the question: do we have a Tutorial on publishing quarks?

Does it highlight all the features? In particular, versioning/tagging. #GoodFirstIssue

Search-ability of Quarks

Many quarks are black boxes… Are the current metadata fields enough to learn about the quark at-a-glance?

Should we add more metadata fields?
Should they be displayed differently in the list view?
Many Quark authors haven’t made use of the existing metadata features, most importantly the description! Should PUNISH them??? Well ok, no… but we can
- do a public service campaign to encourage them to put at least a description
- sort the Quark list in the GUI so that those with descriptions are listed first

Pitch class

There’s been a spirited discussion around inclusion of a Pitch class to SC.

There are lots of conventions to consider, with variations in, e.g., scales and nomenclature varying across culture.
- We won’t capture all the possibilities… but that shouldn’t stop us from having some solid foundations for people to get up and running without having to build their own.
- And we can keep adding in the future of course with community feedback!
- Better yet, if the class is easily extendable so composers can easily build their own wild tonalities.
By one view, this is a perfect candidate for a Quark. On the other hand, the functionality is close enough to the heart of SC that a case can be made for it to be in the Core.
As an example of a class that is well underway to this end: CTK’s PitchClass https://github.com/joshpar/Ctk/blob/master/Ctk%20classes/PitchClass.sc
- This is NOT a good example of how to (not) document a class (Josh!!! X-P)

Threading in sclang

Could there be ways to handle threading in the language more gracefully?
Examples discussed would, in some cases, alleviate the need to call the mysterious s.sync.

Meta-resource: sc-dev-Meeting-Procedure-&-Templates

2023-04-30

James S, Marcin P, Josh P

https://github.com/supercollider/supercollider/pull/6003 pulled in, but need to check behavior in Windows terminal

Discussion on testing procedures Improvements suggested by James S - to be continued in a formalized proposal at a later date

2023-04-02

Nathan H, Luka P, Marcin P, Josh P, James S, Thales R

Discussion on Qt5 vs Qt6: In the discussion it seemed that we were leaning towards revisiting Qt6 support in 2024 and move to Qt6 dropping support for Qt5. Dropping Qt5 will mean dropping support for some platforms (Ubuntu 20.04, macOS <10.14 (the legacy build), Windows 32-bit).
For future reference: here is the branch that supports both Qt5 and Qt6 but the work is incomplete. This should provide a good reference for necessary C++ changes for when we actually move to Qt6.

PRs discussed: 6001, 5750

Comments about Windows support - IPC issues etc; in general SC could work better on Windows...

2023-03-12

JoshP, JamesS, MarcinP

Discussion on recent PRs and issues: https://github.com/supercollider/supercollider/pull/5990, https://github.com/supercollider/supercollider/pull/5991, https://github.com/supercollider/supercollider/issues/5948, https://github.com/supercollider/supercollider/issues/5978, https://github.com/supercollider/supercollider/issues/5939, https://github.com/supercollider/supercollider/issues/5973

Discussion on migration to Qt6: trying to decide between maintaining a mixed Qt5/Qt6 support and moving straight to Qt6. Raised points about platform support for Qt6, which would delay the move to Qt6-only approach. Considered maintaining Qt5 compatibility in a separate branch/fork, or gradually migrating to Qt6-only support in a separate branch. The decision on the approach to be discussed with the wider dev community.

2022-11-13

JoshP, MarcinP, JamesS, NathanH

We’ve worked on the 3.13.0-rc1 release.

2022-10-16

LukeN, MarcinP, NathanH

Discussion on Hadron SuperCollider and method return issue: https://luke.nihlen.us/posts/2022-10-05-sclang-method-return/

Discussion on language server protocol and possible plugins for other editors

2022-09-11

NathanH, MarcinP, JamesS

Discussed PRs:

Tilde expansion on windows 5431
WebAssembly 5571 - close with comment - issue of maintainability
Themes for docs 5487 - lots of tech debt; e.g. generating css in sclang would be better
UDP socket #5747
Clang-format in docker: Discussion on upgrading clang-format-8 to a newer version
create duplicated window only on forceCreate 5549

Discussion on automated updates to the changelog

Look at other projects
reference: https://keepachangelog.com/en/1.0.0/
Important information needs to go on top
Consideration against changing PR titles for use in the changelog - will be inconsistent with commit messages
Maybe the person merging the PR is to be responsible of updating the changelog on the wiki

2022-08-14

(missing minutes)

2022-05-22

Present: James S, Josh P, Marcin P

Discussion on repository permission

There are many users who are not active but have admin access… Decided to table this until a later time.

Discussion on PRs that we would like for 3.13:

https://github.com/supercollider/supercollider/pull/5610

Discussion on plugin API changes
Proposal to make a test that checks for API breakages and runs in the CI

Discussion on the libsndfile PR
https://github.com/supercollider/supercollider/pull/5776

2022-04-17

Cameron, Marcin, Josh

Discussion and merging some not-so-recent PRs

Discussion on https://github.com/supercollider/supercollider/issues/5756

Discussion on fixing submodule URLs https://github.com/supercollider/supercollider/issues/5695 Agreed on cherry-picking the update

2022-01-09

Marcin, Josh, Christof, James S, Nathan, Keithton

3.12.2 - released!

initial topics to discuss:

3.13
Qt 6
Rework cmake

Marcin - supports trying to support Qt 5 and 6 for some time

James S - Qt 6 project board: https://github.com/jrsurge/supercollider/projects/2

move to 5.15.2 first
turn 5.15 errors (from deprecations)
then moving to 6

How best to support the older systems (back to 5.13, maybe back to 5.9?)

Maybe make a request for others to help? Scott C?

Alternative to Qt: NGui? https://www.tasharen.com/?page_id=140 Nanogui https://github.com/mitsuba-renderer/nanogui imgui https://github.com/ocornut/imgui sciter https://sciter.com/ QML and QtQuick ?

Other languages as front ends?

timing and garbage collection

Synthdef optimization on the server! (Nathan)

C API for whatever is made later - lack of ability to extend the language with plugins is a pain point

Reviews for supernova

Review of modular class library proposal - https://hadron-sclang.org/articles/2021-12-21-Modular-Class-Library-Proposal/

2021-12-04

James S, Nathan H, Josh P, Marcin P

Josh has a bash script for signing macOS builds, will test more more and make a PR (fix https://github.com/supercollider/supercollider/issues/5603)

Other M1 issues: https://github.com/supercollider/supercollider/issues/5598

Qt6 discussion: many things to consider
James's progress board: https://github.com/jrsurge/supercollider/projects/2

For next dev meeting: discuss moving to Qt6

Discussion on Windows builds for newer hardware (SSE4-capable), also on 32-bit shift

Discussion on name suffix on dev branch (https://github.com/supercollider/supercollider/pull/5566) - we decided to do it and use -dev suffix
Nathan made an experiment and the merge conflict this PR would introduce would only be needed to resolve once on the first merge from a new release branch.

Discussion on MainMenu memory leak discussed on the forum - this was solved some time ago (3.10.2 ?)

sc3-plugins PRs:
https://github.com/supercollider/sc3-plugins/pull/326
https://github.com/supercollider/sc3-plugins/pull/325
https://github.com/supercollider/sc3-plugins/pull/327 (decided to keep using Xcode generator and not use ccache on macOS)

2021-10-31

James S, Marcin P

Discussion on PR approval process

Merged https://github.com/supercollider/supercollider/pull/5595

Legacy macOS build fails; Marcin plans to look whether the problem with installing Qt 5.9.9 occurs in plain aqtinstall

Discussion on open PRs

Discussion on Qt6 progress

2021-10-17

Luke N, Nathan H, James S, Josh P, Marcin P

Topics discussed:

Qt 6 update
sc3-plugins status
considering scheduled releases of SC
c++ complexity report (James S)

Qt discussion

Qt 6.2 includes webengine
Discussing on compatibility with qt 5 and when to update to qt 6
Discussion on universal builds
Updating to qt 6 guide: https://doc.qt.io/qt-6/portingguide.html
Adjacent topic: migration to m1 on macOS
Qt migration progress: https://github.com/supercollider/supercollider/issues/5169
~~(Marcin will update the issue to reflect current status)~~ EDIT: done
Apple M1 migration
~~Make an issue for this (Marcin)~~ EDIT: done

James S will look into tackling Qt 6 update
Marcin will help with CI

sc3-plugins

Marcin suggests splitting the repository and handing over maintenance, but keeping the sc3-plugins as an aggregate of the plugins for distribution/release purposes
Side discussion on libgit as an alternative to using system git - supposedly libgit is not well documented; our git interface could be better; OTOH having more primitives might not be good
Alternative package manager: Conan - but it needs python (Marcin will look into it)
MuseScore has some package manager (Marcin will look into it)

Scheduled releases

We are stretched pretty thin, so probably not a good idea right now
Side note for the release process: look into xcontary for signing (suggested by James S).

Complexity report

Python tool: lizard
report based on cyclomatic complexity
Useful for pinpointing problematic functions etc
Luke talks about lack of documentation of SC’s garbage collector - no tests etc
Discussing the need for tests
James S wants to use Catch2 for tests - others welcome that idea
Integration tests are also needed Luke refers to classic papers on real-time garbage collection:

"List processing in real time on a serial computer" https://dl.acm.org/doi/10.1145/359460.359470
"The treadmill: real-time garbage collection without motion sickness" https://dl.acm.org/doi/abs/10.1145/130854.130862

Nathan: maybe it’s possible/feasible to add sclang parser to lizard, to analyze complexity of the class library?
Luke suggests to attach minimizing technical dept to writing new code; but avoid scope creep -> create new PRs when refactoring code
There seem to be a consensus that we should revise our contribution/style guide to encourage refactoring of old code

2021-07-25

Josh, John Andrews (new) Marcin, Nathan

libsndfile will build for older builds, (legacy)
make a new RC
need to fix CI
automate signing? This sucks …
John’s sc-el PR -
- Mac OS - no pre-package sc-el library (unlike Linux)
- doesn’t work for any other platform unless you modify the source code - not ideal
- cmake translates install path as a constant defined in one of the files
- cmake generated variables - make files expect SC as a dependency
- PR tries to make this more configurable
- update the PR to make these changes optional with a flag - the old install path will have a kind of ‘manual deprecation’

2021-06-13

JamesS, Olga, Daniel, Marcin, Josh, Iannis

Introductions We discuss 3.12 release - RC week of June 14

**Remaining PRs: ** Inclusive language #5470 Discussion on #5470 Choosing alternative “new” method name to re-route non-deprecated but classes that we suggest you avoid.

Possibly: supernova bind interface #5474 Discussion on #5474 Looks good, Josh will check

Iannis starts discussion on modularizing sc code

James mentions his work on CMake

Iannis inquires on possibility of interfacing SC / running SC on GPU in the context of AI https://www.rncm.ac.uk/research/research-centres-rncm/prism/prism-events/future-music-3-16-17-june-2021/unsupervised/

Olga shares ideas about shared memory interface improvements

2021-05-16

Dev meeting notes

JamesS, NathanH, MarcinP, JoshP, PatrickD

James talks about possibly moving to a single branch linear workflow

Less bugix releases, more minor releases

Semi-linear workflow vs 2 branches

With linear workflow and getting rid of main branch we’d just tag releases; but we need to check with community particularly linux packagers

Josh: proposing more frequent minor releases, regardless of whether/which option we go for

We should ask for opinions on the changes

scsynth/email list/ slack - ask for feedback: James and Josh will look into it

Discussion on milestone PRs

Patrick will look into UnitTest

Josh will look into midi out PR

Marcin and Josh will meet to work on supernova clipping values

James will look into ableist language issue (see https://alexjs.com/)

Proposed short release meeting next Sunday (May 23) (edited)

2021-05-02

Present - Patrick, Marcin, James S, Josh P, Stewart

Introductions - welcome Stewart!

3.12 milestone review

CondVar

Needs reviewing and merging. Patrick - investigating using CondVar in the UnitTest framework. Discussion on usage of CondVar in tests - Patrick trying to find a way to use it in UnitTest::wait Patrick - will investigate refactoring currently failing tests, possibly not using CondVar or any other condition mechanism if it's not required.

Automation of cherry picking

Still investigating, decided out of scope for this milestone, moving to 3.13

Simpler release process

Scope is quite large, going to move this task to 3.13. Aim to break it down into smaller actionable items in one of the next dev meetings.

Use priority labels

Moving to 3.13.

Modernise CLI option parsing

Some of this work might be required for Bela support in 3.12. Marcin going to ask Bela developers for input.

MIDI Out logical time

Waiting for input

Clip output values on macOS

Waiting for input

Removing ableist language

This is ongoing JS to take on initial work.

Open floor

Class highlighting issue

JS to investigate issue #5434 Potentially introduced on develop, about to go into 3.12, if so should be fixed for the release. Can be listed as a known issue in RC to avoid blocking release schedule while it's addressed.

Expanding tilde on Windows

JS to investigate PR #5431

CMake

JS raised the question of supported CMake versions

2021-03-14

Members present - Marcin, Iannis, Patrick, Josh

Marcin recent work:

cmake and verifyApp
verify app turned of for Qt 5.9 for legacy build

3.12:

ImageLoader::link in server start failure - what is this doing??? - Josh and Brian to check on this for the scsynth failure to start on older MacOS

Josh to look at MIDI PR - https://github.com/supercollider/supercollider/pull/4725

Iannis - looked at sclang - simpler Condition - - what methods are essential and what do they do? - Brian? Can there be a time to sync with Iannis?

Something similar to DispatchGroup in Swift for Condition?

Patrick - - Rust: Sorcerer crate - Deferred on scsynth may be good for Condition refactoring - Does it pertain to: https://github.com/supercollider/supercollider/pull/5363 ?

Discussion of how UnitTest::wait should work, and reverting / avoiding changes for Condition / UnitTest, etc., after 3.12

Patrick and Marcin discuss reopening https://github.com/supercollider/supercollider/pull/5363

Patrick explains the change introduced in https://github.com/supercollider/supercollider/commit/2aa3374e1e52b7db3f7708498810dc6032a1d082 that broke tests; Patrick’s PR reverts this back to using a function as the “condition” argument for UnitTest -wait

There’s an ongoing work on making UnitTest use a Condition instead, but this will likely result in larger rewrite: https://github.com/supercollider/supercollider/pull/5368

Marcin supports reopening 5363 to get the current functionality back (and tests passing) in the interim

Current plan: discuss this further at the next meeting, particularly getting input from Brian

Marcin talks about proposed SC_VERSION improvements. Will create an RFC.

Ianni asks about an issue with Quarks installation and permission issues writing to the yaml file (Arch Linux) - will post question to the forum.

2021-02-07

Members present: Brian, James S, Marcin

Update from James:

looked into Unity builds to decrease build times; we might be already doing it partially; CMake needs work
- Brian: if we are doing unity builds, we are doing that for yaml.cpp only (?)
- supposedly it used to work, but it stopped and was disabled

Moved to discussion on the need to fix/largely rewrite CMake

Back to Unity builds:

Brian: probably not much improvement for Linux and macOS since we already use Ccache
James: could improve time for Qt components
discussion on one definition rule; Brian thinks it might not be a problem

Back to discussion on CMake improvements

Marcin suggests to create a wiki page documenting current CMake architecture

Problems:

"dependency inversion"
Install stuff

Brian suggest the following order of fixing things:

solve Mac installation - "dependency inversion"
minor cleanup to make sure we don’t find libraries multiple times
redoing installation code
possibly add CPack packaging

Discussion on rewrite CMake - probably wait until 3.12 release

Marcin mentions issues with microphone permissions on Mac which might need to be addressed before 3.12, to be tested

Brian’s update

wants to focus on particular aspects of the project, e.g. scripting for releases
if there’s interest, let’s restart group PR review meetings

Discussion on old PRs and stalled PRs; Finding out who has open PRs and which PRs wait for who

We need to stress that PRs need to be easier to review - e.g. have clear examples.

Plans for the release, see https://github.com/supercollider/supercollider/milestone/23

Brian is working on Bela support PR, should be merge-able soon/this week
(Adding boost program options to the milestones)
Then Brian plans to work on the release script Tentative date for the release: May 1st, 2021, with hope that it could happen earlier

Marcin mentions issues with Big Sur and proposes to create an interim build for Big Sur once all the problems are solved

Marcin's updates on GitHub Actions (GHA)

testsuite: open PR, issues with qpm,
S3 upload: waiting for credentials - Brian said we can use theirs
Windows builds - for later
GHA for sc3-plugins - Brian tentatively wants to tackle that

For next meeting:

discuss “use priority labels” https://github.com/supercollider/supercollider/issues/5248
possibly improve versioning

Possible features for 3.13:

web assembly
CMake rewrite
cleanup compiler warnings (James has a WIP branch)

2021-01-24

Members present: James S, Marcin

Free-form discussion. Topics:

Update on running tests on GH Actions
- Marcin made some progress, but it still doesn't work
Marcin built SC natively on an M1 MBP
- homebrew provides Qt 5.15.2, but without qtwebengine
- there were issues with (self)-signing - the build did not start, everyneed needed to be re-signed
- performance seems quite good (non-scientifically measured)
- James and Marcin wondered whether we use all ARM optimizaions; nova-simd library seems to include NEON instructions
discussion on QtWebEngine
- still not available in Qt6
- ideas for having help system without web engine, e.g. by using rich text in Qt text view
ideas about version numbers for non-tagged builds
- proposition: name current pre-release 3.12.0-pre (or similar)
- proposition: name future pre-release 3.13.0-pre (from develop branch, with the caveat that 3.13 release might not include all changes)
- discussion on version numbers vs short sha (e.g. 3.12.0-pre-1454 vs 3.12.0-pro-1c002dd)
James proposes using Unity Builds to speed up build process

2021-01-10

(not sure if we took notes)

2020-12-12

Members present: Brian, Marcin, Gianluca, Tejaswi

3.12

making good progress toward release
Brian planning to work on moving C++11 to 17
Gianluca planning to work on Bela support
Marcin moved us to GitHub Actions
Gianluca working on macOS clipping in supernova - Brian will create ticket

Marcin gave a status update on GHA (GitHub Actions)

building works
not yet running test suite
not yet pushing to S3

discussed dropping boost sync

Brian thinks this might be better long term since sync seems to be causing trouble during the last few releases
decided to open ticket to discuss further

discussed https://github.com/supercollider/supercollider/issues/5282

discussed compatibility and quarks

decided to postpone 3.12 release indefinitely since Josh and Brian don't have much time for SC in the next while

2020-11-15

Present: Gianluca E, Marcin P, Brian H

3.11.2 release

in progress, will finish up today or tomorrow
need to finish making sc3-plugins release too

Gianluca reported that the Bela fork maintainers are getting close to making a PR to SC. Discussed how to handle new flags in scsynth.

3.12 release

discussed #5110 macOS clipping feature; possible API/ABI change; desired for 3.12
after 3.11.2, Brian wants to do more to improve the release process
discussed ideas for prioritizing issues and PRs that don't have an associated issue

2020-11-01

Present: Gianluca E, Brian H, Marcin P, Hanns H

3.11.2 release

on schedule for release
one small build system issue and one crash reported on macOS 10.12 (#5229), found fixes for both
will do a release if that one issue is fixed

3.12 release

decided we want to include #5110 (clip hardware output on macOS)
may move to C++17 for this release to prepare for porting to Qt 6

Webassembly

Hanns discussed recent talk about porting SC, at least scsynth, to the webassembly toolchain
Discussed possible porting issues -- threading, exceptions, etc.
At this point, doesn't look like anyone else can help out, but we also aren't in a rush to implement this

Discussed using labels and milestones to help organize issues

Brian proposed using a couple labels for priority level to organize open issues
Discussed how to agree on priority levels and how to go about adopting labeling as a team
- Would want multiple people to label, and discuss to agree on how to assign priority beforehand

Discussed informal group code review sessions

Brian H, James S, Gianluca E, Marcin P have met twice to review PRs as a group, to get experience reviewing and learn from each other
Want to ask more people to join - will announce more widely for the next time

2020-10-18

Present: Patrick D, Brian H, Marcin P, Gianluca E

What are people up to lately?
- Brian: helping Marcin with jack2/jackOSX
- Gianluca: Bela bug fix
- Marcin: investigating Jack backend on macOS
- Patrick: not much SC work lately
Discussed new jack2 release for macOS (replacing JackOSX)
3.11.2 release
- overall on track
- need to fix portaudio/cmake issue (#5176)
- need to make cherry pick PRs
- discussed #5188 - does not need to be fixed for 3.11.2
- discussed #4883 - Brian will review soon
- still planning for release date in October or November
- discussed #5110 - agreed better for 3.12
3.12.0 release
- planning to release before the end of the year
- already have enough to do a release
- #5081 is a nice-to-have
- maybe Bela support if it starts moving forward soon
pair/group code review sessions
- informal group call to review PRs together
- did first one last week with Brian, Gianluca, James S
- should have someone else besides Brian "driving" next time (next weekend probably)
- send out an announce/invite to more channels if the next one goes well
big list/board/prioritization
- want to have some way to organize top-level issues/projects/concerns
- where to put it?
  - Discourse vs Github projects vs Github wikis vs other places?
- milestones? make it easier to see what goes into what release
- hard to use tools GitHub gives us to manage project easily
- look into bots for automation? / external integration
- maybe even a new GitHub repo for "meta-issues" / organization?
- agreed to dump into a wiki page for now and see how that works out
Bela
- discussed merge of Bela into SC and the difficulties involved -- everyone wants it, just takes some time
- Gianluca and Patrick offered to help with the merge & testing
- CI job is probably possible since it can be cross-compiled
help browser
- Marcin suggested it might be possible to avoid using QtWebEngine for the help browser by using a text view instead
- discussed some possible implementation issues

2020-10-04

Present: Marcin, Brian, James S, Gianluca

General greenfield question: what might a version 4 look like?
- We release breaking changes every minor release - it doesn't follow semantic verisoning, should we already be on version 4 etc.?
- When we're next able to discuss big things, this would be on the list.
Backwards compat and deprecations
- A very positive feature
- However, potentially leads to stagnation and unclear/confusing features
- Concerns about removing deprecations: in particular asInt.
Xcode 11 build issues
- Marcin + Brian tried to diagnose a segfault with a non-legacy xcode11 build, still investigating
3.11.2
- Lots of CI work to figure out first, including the Xcode 11 things
Discussion on reviewing existing PRs However people are able to contribute to the project, in whatever capacity they are able to, is massively appreciated. We're all very grateful for any work people are doing towards the project, particularly during these times.
Can we do pair-programming and/or group programming sessions? Paired reviews? With the goal of tackling larger/more complex things and sharing workload as well as knowledge and experiences about various sections/aspects of the project.
Discussion around signing and notarisation
- Questions about how CMake handles signing

Actions

Marcin and Brian will continue to work together on the Xcode 11 issues
Try to plan paired/group reviews for next week

2020-09-20

Members present: James S, Joshua Parmenter, patrick, brian, Marcin, elgiano

macOS11 problems (Joshua Parmenter):

example:

SynthDef(\test, { Out.ar(0, SinOsc.ar(440, 0, 0.2)); }).add // works 
s.sendBundle(nil, [\s_new, \test, 1000, 0, 1] ) // doesn't ever schedule 
s.sendBundle(0, [\s_new, \test, 1001, 0, 1] )

most probably a problem with endiannes with ntohl.JP is working on it

Qt problems. Waiting for next Qt release for macOS (Qt currently needs to be built from source to target macOS 11).
Binary download don’t work on macOS 11. Compiling from source works. Need to announce this. JP is announcing on sc-users.
We need both x86 + arm releases (two separate builds) when we start to support macOS 11.

macOS CI error (Marcin)

errors during testing. Seems related to no graphics env available → web engine failing.
CI is blocked for macOS until this is fixed. Marcin is on it.
Possible temporary workaround: disable tests.

3.11.2 / 3.12.0

discussed in Issue #5146:
Planning 3.11.2 for October. 3.12 right after:
macOS 11 support if possible by then, but not if it would delay the release.
macOS server-side volume clipping ?

Would there be a possibility than upgrading Qt could drop an older system we currently support?

If it happens we could include a pre-processor switch in a patch release. (add a new build job to do that)

Talking and reading about the future of Qt.

James S: Qt 6 is not advertising breaking changes, but won’t work without C++17.

Setup a Qt 6 working group, or issue, to keep track of it.
Require C++17 (open ticket for C++17 in sc as well)
Setup a C++17 working group, or issue.

Does C++17 allow new features for sclang?

Not out of the box
drop a lot of boost support?
lock/mutexes in supernova

Maybe a C++17 ticket on github is enough? Let’s start with that.

Websockets (patrick)

(see RFC #9 for previous discussion points)

with or without Qt?

without Qt would be better for headless builds
better to avoid another dependency

Qt’s websockets are split from webengine and GUIs. So Qt could be viable for headless.

Commit notation (James S)

Conventional commits: standardized way of writing commit messages

machine and human readable
based on semantic versioning
tooling to automatic generate a changelog
might be asking too much to a community project
but it could be done by maintainers when PRs are merged
even if not 100% strict, would alleviate changelog-writing pain

IT IS PATRICK’S BIRTHDAY TODAY

2020-08-23

Not much business was discussed, as only Brian H and Gianluca E were present.

We discussed the 3.11.1 and 3.11.2 releases and brainstormed ideas for future work.

Gianluca agreed to do the announcement for the next meeting.

2020-08-02

Members present: Brian H, Cliff D, Patrick D, James S, Josh P, Clare M, Marcin P, Luke N

Discussed 3.11.1 release

Discussed PR #5113, agreed that we can move forward with release now
Brian said they would move forward with the release process after the meeting
Luke wrote a script to notarize and codesign macOS binary on Travis
Discussed design of script and how we could adapt it (especially regard build time limit on Travis)
Discussed whether SuperCollider as an org could purchase an org certificate from Apple, probably has legal issues

Discussed issue of many GitHub accounts having admin access to the organization (some without 2FA)

Discussed whether to change master->main before or after the release

Agreed to do it after release since release is high priority and we don't want any issues potentially arising from changing default branches during the release process
Discussed GitHub and git changing their behavior around this as well

sc3-plugins and codesigning:

Josh said we weren't able to get a release out for 3.11 because of sign/unsigned binaries
Possibility of creating a single binary plugin that someone could use to load all of the plugins once
Josh hasn't had a successful way to download & load plugins in the signed binary
Brian and Josh said they would work together to try to debug this this week

Clare and Brian discussed release automation & pair programming within the next few weeks

Patrick brought up a Ctk quark pull request

Discussed Quarks best practices and creating a "best practices" document, and/or an example repo

Discussed GUI/headless builds and conditional compilation

Discussed JetBrains product licenses expiring

Discussed macOS 11 (Big Sur) and SC compatibility

Discussed post-release ideas:

Making shared project priorities more visible for new & current contributors
Patrick wants to discuss after the 3.11.1 release when/how we should do the next release
When to do 3.12? - supernova on Windows is probably 'the big feature'
Doing more regular/cadenced releases?

2020-07-12

Members present: Patrick D, Brian H, james S, Marcin P, Gianluca E, Luis L, Clifford (Cliff) D, Tejaswi P

Intros for new joiners (Cliff, Luis)

Luis discussed his Pulsaudio RFC:

adding PulseAudio as a build time option
Jack will stay as the default
new option for systems where getting Jack may be difficult
PR is open against SC
goal to help less technically savvy users, incl. with platforms like SonicPi that use SC internally

Discussed use of RtAudio library in PR Discussed possibility of using RtAudio for other backends Discussed possibility of using another library besides RtAudio Discussed device selection

Brian gave an update on the 3.11.1 release:

Ready to go, currently waiting on Josh

Brian suggested using Jitsi (meet.jit.si) for future calls

Most people agreed it would be desirable
James said we should check to make sure it's not blocked anywhere contributors may live
Agreed to try the next meeting on meet.jit.si, further details TBD

Discussed what (if anything) currently keeps people from contributing:

several people said they have a hard time keeping track of what's going on in active development
several people indicated they would like more shared priorities as a project, or to be assigned issues/PRs
navigating the Wiki to access new contributor info is hard
PRs are hard to review because they don't stay contained/branch into other topics

Patrick brought up some PRs:

https://github.com/supercollider/supercollider/pull/5078 - merged, will cherry-pick
https://github.com/supercollider/supercollider/pull/4939 - needs new review
https://github.com/supercollider/supercollider/pull/4990 - needs review, Brian assigned self

James brought up PR 5015, asked if it might solve the same issue as his PR 4646 and therefore could try reverting 4646.

Brian said it might, give it a try

Gianluca brought up a thread on scsynth.org about audio clipping on macOS, agreed we should try to tackle this for 3.12.

Marcin asked for attention on https://github.com/supercollider/supercollider/pull/4852.

2020-05-24

Members present: Brian H, Marcin P, Luke N, James S, Patrick D, Gianluca E, Tejaswi P, Josh P, Geoffrey M, Julian R

Release status

Josh P has had some reports of unsigned sc3-plugins not working with 3.11 on macOS 10.15
- hasn't been able to reproduce. thinks that everything is in order, but not sure.
- Marcin offered to test

Release process scripting

Brian brought up the idea of automating / scripting the release process
- James S, Josh P, Brian H, Marcin P decided to form a working group for this

vcpkg - https://github.com/supercollider/supercollider/issues/4928

James S has used it before and offered some advice
- one issue is that packages need to be built from source, not a good way to provide Qt
- generally positive impression
Marcin P tried it, ran into an issue with powershell
- for portaudio, issue with asio sdk
James S mentioned asio sdk is in vcpkg, and seems like it provides CMake integration
Brian noted ExternalProject in CMake is also an option for managing external dependencies
Luke N and Marcin P said vcpkg support for CI first might be a good way to test it out, and then recommend it if it works
- James S said he would look into that

portaudio vendoring - https://github.com/supercollider/supercollider/issues/4928

Marcin P did work to shift over to fresh, non-sc-org portaudio
Brian suggested using ExternalProject in CMake to get around
Discussed tradeoffs of vcpkg vs ExternalProject
Decided to do more research and revisit

issue management - https://github.com/supercollider/supercollider/issues/4940

Josh P wants to reset everything and start from scratch
Luke N also likes this idea, but said we need to have a policy to avoid it happening again
Josh P said most projects don't actually run as long as SC. issue trackers work good for shorter term projects, but maybe not for this duration
- fresh start could give some focus
James S explained his ideas regarding stale issues and automation
Julian R said a bot would add a kind of neutrality/fairness to it, but is concerned that closing issues will hide valuable information
James S suggested updating issue template or other obvious place to note that you may want to search closed issues
Everyone agreed messaging around closing issues is important
Discussed a gradual approach to transitioning between current process and more controlled approach
There was a proposition to have a two-step approach where a bot would comment every issue that’s been stalled for more than X months, which would explain the triage process. Then, after some other time to be determined, the issue would be closed
Someone proposed to start with proposition some texts for these messages.

2020-05-10

People present: Brian H, Marcin P, Luke N, James S, Nathan H, Patrick D, Gianluca E, Tejaswi P

Luke N talked a bit about Scintillator (https://github.com/ScintillatorSynth/Scintillator)

Brian gave a short overview of what things have been merged in recently

Gianluca discussed his help browser PR (#4883) and associated RFC (#9)

Discussed issues around SuperCollider versioning and standalones

Some points of discussion:

ease of learning - interactive learning environment
interoperability with other technologies (web, etc, LSP?)
standalones - for performers
multiple versions of supercollider
- dev work
- possible, but very difficult currently
- backward compatibility
- run 'from a USB stick'
app bundle design
server/IDE/language search paths

2020-04-12

People present: Nathan H, Brian H, Patrick D, Geoffrey M, James S, Gianluca E, Josh P

Welcoming Gianluca!

What people are up to

Geoffrey: looking at autoindent in IDE, waiting for review on #4797
James: reviews, working on implementing spelling correction suggestions in sclang parser
Nathan: working on other projects
Patrick: refactoring TestBuffer to break out server-requiring tests
Josh: managing releases
Brian: reviewing, beginning to implement RFC #1

3.11.1

discussed Brian's cherry-pick PR
need to merge in scel update for support on ubuntu
decided to postpone outstanding issues (#4544, #4826)
decided to release ASAP

sc3-plugins

discussed merging Scott C's PR and doing a release
Josh P said he thinks we should merge it and include in 3.11, general agreement

Other PRs and issues

Patrick asked about best practice quitting servers in unit testing

2020-03-29

Members present: Brian H, James S, Nathan H, Marcin P, Patrick D, Clare M, Tejaswi P

3.11.0 release:

Josh P will make new sc3-plugins release and source tarball for sc 3.11.0 as soon as possible

3.11.1 release:

#4703 close to merge
#4583 waiting on Brian's review
discussed Wayland issue
discussed cherry-picking
- Nathan suggested documenting git process w/branches in readme
#4826 - no progress yet, will revisit

Patrick brought up #4136 GPU issue on macOS

3.12.0:

Nathan suggested we should make sure we decide on / have at least one new big feature before making a minor release
RFC process needs a bit of a kick-start
Patrick wanted to have a release in <1 year
Clare talked about her experience with release schedules
- what worked: commit to a regular release schedule (quarterly at her work)
- just release whatever is available (could be patch or minor)
discussion about release schedules & universities
- more frequent releases => departments install more recent versions

other:

Nathan would like to release some new (personal) UGens soon
Clare would like to start contributing again in the next few months
Patrick wants to help with the sc3-plugins release
discussed anxiousness about reviewing
discussed review behaviors and commit messages

2020-03-15

Members present: Brian H, Josh P, James S, Tejaswi P, Nathan H, Marcin P, Julian R

3.11.1: discussed PRs and release date

Make an RC by April 15, release by April 30
#4544 is priority for 3.11.1 or 3.11.2
#4826 also recommended
Marcin recommended #4599, we agreed it should be included
Julian recommended #4779, we agreed it should be included
Brian recommended all "Cherry-pick to 3.11" PRs

3.12.0: discussed release date

Josh suggested 6 months from 3.11.0 release. Discussed impact of COVID-19 outbreak and associated instability on development
Nathan recommended focusing on a single project for next release

Julian brought up his concept for an "AbstractObject"/"Neutral" RFC

discussed design and possible implementation

Discussed open and future RFCs

Discussed deprecation policy

2020-03-01

Members present: Brian H, Josh P, James S, Tejaswi P, Patrick D, Marcin P, Geoffrey M

3.11 beta out - what issues before release candidate?

https://github.com/supercollider/supercollider/pull/4784 https://github.com/supercollider/supercollider/pull/4783

Downloads - 25 Mac OS , 20 times for Windows

Tag needs prefix of ‘Version-3.11.0-beta1’

RC in a week -

Merge 3.11 to develop soon

Verify Supernova on Mac is included.

3.12 ? - review RFCs - final comment period after Josh checks with authors

Debugger for 3.12

Created a 3.11.1 board - check the issues that were added

Open Topics:

Patrick: https://github.com/supercollider/supercollider/pull/4786

Brian: For releases, we should create an issue for discussing the release. 3.11.1 created

3-14 for next meeting

2020-02-09

Members present: Brian H, Josh P, James S, Tejaswi P, Patrick D

SC symposium - discussed who is going and informal travel plans

GSOC - weren't able to find a second mentor, won't be doing it this year

General progress update

Brian - busy in other projects lately, planning to get back to reviews this week
Josh - busy in other projects lately, suggested releasing 3.11 beta soon
Patrick - worked on updating pull requests -- wants to merge #3814, #4761
James - busy with other projects lately, planning to review some PRs
Tejaswi - just changed build environments, interested in reviewing PRs, added to Reviewers GitHub team

3.11 beta release - planned for Feb 16 - Josh will handle

Brian suggested doing calls every other weekend

Josh, Patrick agreed that would be good
James and Josh suggested doing check-ins via another medium instead of the meetings when we don't have them

Discussed moderation of the scsynth.org forum - James S said he would be interested in helping moderate

Discussed #4713 and refactoring scdoc

2020-01-26

Unfortunately no minutes are available for this meeting

2020-01-19

Members Present: Brian H, James P, Marcin, Tejaswi, Patrick D, Nathan H

Discussed procedure around releases and timeline for 3.11 release. No decisions made as Nathan wasn't present yet.

Discussed some open PRs (#4599, #4704) and review process

Patrick brough up QPM PR #10 for attention

Patrick reported that he's making progress running tests in CI, ready to make a PR that runs tests in CI on Linux

Marcin asked for help with PR #4583, Brian said he would assist

2020-01-12

Members Present: Josh Parmenter, Brian Heim, Nathan Ho, Patrick Dupuis

Josh, Brain, Nathan, Patrick

Brain is watching cool movies

And building laptops

Nathan is giving out Linux audio advice

TODO: announce RC2 3.10.4 should be about ready to go

3.11 release! Check status on the mail list with James H - can we do 3.11 soonish? OR - should we be thinking about a 3.10.5 release. Ask about 3.11 / Ableton readiness on mail list If not - 3.10.5 may be a better route (Patrick)

Discussion of release management and documentation. Nathan to fill in some gaps and help start a document for responsibilities.

Had a question about package.sh in distribution

Document minimum required version of OS X - 10.12? (Because of Qt 5.13) - should be noted in the release.

Discussion of QPM debugging with Patrick

Discussion of shell scripting problems with QPM and environment variables

2020 - year of SC website?

2019-12-08

Members Present: Brian Heim, Carlo Capocasa, Chad Cassady, James Surgenor, Josh Parmenter, Josiah Oberholtzer, Marcin Paczkowski, Nathan Ho, Patrick Dupuis, Tejaswi Prakash

Release status:

3.10.4: Beta release immediately.
3.10.5: Address three issues below.
3.11.0:
- Nathan is open to resuming release manager.
- Quality assurance for LinkClock.
- Scott Carver's SynthDef spec PR #3814.

Release board issues (now postponed to 3.10.5):

Issue #4214 (IDE stuck at "Sending Request"): James believes this is resolved, but needs more testing.
- Nathan will test and look at it
- James will write up an explanation of why this is happening and why this fixes it
Issue #4368 (Windows Defender delays scsynth boot): not much new information
Issue #3132 (CommonTests quark -> local UnitTests): considered ongoing, not important for 3.10.4

2019-11-24

Thanks to everyone who attended the sc-dev meeting! Minutes of the meeting are below. You can find archived minutes from all our meetings on our GitHub wiki page: https://github.com/supercollider/supercollider/wiki/Dev-Team-Meeting-Minutes

The next meeting is planned for the weekend of Nov 30 / Dec 1. A meeting time poll will be sent out early in the week. If you'd like to attend but our usual meeting times aren't good for you, respond to this thread or email me privately and we'll try to work something out! We are always interested in getting new people involved in the development community.

Regards,

UR_NAME

3.10.3 Release board: https://github.com/supercollider/supercollider/projects/17

Future Release Board: https://github.com/supercollider/supercollider/projects/15

sc-dev Meeting DATE Minutes:

⚠ If you have any comments on topics in these meeting minutes, please start a new thread rather than replying to this one. ⚠

sc-dev meeting 11-24

James S, Josh, Nathan, Patrick, Brian, Marcin, Tejaswi

Brian built an IKEA shelf

4214 - James S - after a lot of digging it looks like something with Boost ASIO dropping requests. IPC wasn’t getting established. PR 4646 - a modification made for a synchronous read step happen for setting the group policy for auditing removable devices it fixed the issue every time. BUT - if it is something else ??? - lots of concern about why the initial reads are lost - but, maybe it doesn’t matter.

Document it?

4368 - James has some new info. Sound card / Port Audio?

3.10.4 diversion - out before end of year / holidays

3132 - CI says latest PR passes, but Patrick says it does NOT. Top level YAML file is ok - but we need to send an error back to the calling script. Probably an issue in qpm On linux - server boots and runs the tests. But some tests don’t get run - hangs on TestNoOps. And ditches the rest. Test on local machine first to see if it works, then see if it can be fixed on Travis. Maybe only run server tests on linux? Shouldn’t hold up release.

4645 - ready to go, but solves the most serious issue. Josh and Brian will look tonight.

3.11 - Link is the big feature. Nathan would like some manual QA Look at API design

3.11 alpha at the same time as 3.10.4 and ask people to start testing it more? Linux jack timing

https://github.com/supercollider/supercollider/pull/4599 for 3.10.4? Voted down - on to 3.11!

Manage 3.11 board for 4484 and Link

James S - Soundfile view issue - possible threading issue. The way it talks back to the Qt widget seems to lock the whole GUI. As loading the sound file, something can hang the GUI thread. Will try to create reproducer.

Brian - all - try to tackle some SC only PRs if we have the time!

⚠ If you have any comments on topics in these meeting minutes, please start a new thread rather than replying to this one. ⚠

2019-11-17

Thanks to everyone who attended the sc-dev meeting! Minutes of the meeting are below. You can find archived minutes from all our meetings on our GitHub wiki page: https://github.com/supercollider/supercollider/wiki/Dev-Team-Meeting-Minutes

The next meeting is planned for the weekend of Nov 23-24. A meeting time poll will be sent out early in the week. If you'd like to attend but our usual meeting times aren't good for you, respond to this thread or email me privately and we'll try to work something out! We are always interested in getting new people involved in the development community.

Regards,

Josh

3.10.3 Release board: https://github.com/supercollider/supercollider/projects/17

Future Release Board: https://github.com/supercollider/supercollider/projects/15

sc-dev Meeting DATE Minutes:

⚠ If you have any comments on topics in these meeting minutes, please start a new thread rather than replying to this one. ⚠

SC-Dev meeting 11-17

Nathan, Iannis, James S, Tejsaw, Brian, Patrick, Josh

4368 - decide next week if it stays in 3.10.4

Consider what for 3.10.4, think for 3.11 while considering 3.10.5

Nathan - update change log today

4124 - James S - maybe not an IPC issue? From the IDEs point of view it is writing to standard input - no errors reported. But the language process is NOT seeing anything on STDIN. So, the IPC never gets kicked off. Really hard to follow up - Nathan has shown that his python script probably shows it is IDE related (since sclang talks listens from python ok).

Probably something wrong with QProcess

Maybe don't subclass QProcess?

Another possible move to 3.10.5

3132 - Patrick

Some good progress, but feeling like he isn't moving forward. Server tests on Travis still don't work. Might leave server tests for another day.

Removed common tests. Have included the test suite in the repo. QPM now runs the tests in the repo.

Might do server tests (at least on one platform) for next release.

4363 - consensus on how to fix the crash - Nathan will do a pull request.

Josh - lots of code-signing progress, still trying to get to unsigned binary plugins.

3.11 - Abelton Link should be main new item.

Brian - talked with Andrew Beltz - works for VCV Rack (creator?). Prototyping thing that lets people write code with various scripting languages. Looking for someone to help with sc backend for prototype repo. Any interest?

Also - Brian wants his PRs merged. 4585 is merged, 4612 will be rebased to 3.10

Patrick would like someone to review: PR 4643 Server related fixes for some UnitTests PR 7 in supercollider-quarks repo PR 4598 Classlib: Buffer:write should use Buffer:writeMsg

Discussed possible future improvements to UnitTest: fixtures, mocks, etc.

Talked about GitHub Actions:

general feeling - no compelling reason to use it now, but could research it more

For next meeting:

plan to put together a list of issues and PRs for 3.11

⚠ If you have any comments on topics in these meeting minutes, please start a new thread rather than replying to this one. ⚠

2019-11-03

Nov 3rd 2019

SUBJECT: sc-dev Meeting Minutes Hey all,

Thanks to everyone who attended the sc-dev meeting! Minutes of the meeting are below. You can find archived minutes from all our meetings on our GitHub wiki page: https://github.com/supercollider/supercollider/wiki/Dev-Team-Meeting-Minutes

The next meeting is planned for the weekend of Nov. 9th, 2019. A meeting time poll will be sent out early in the week. If you'd like to attend but our usual meeting times aren't good for you, respond to this thread or email me privately and we'll try to work something out! We are always interested in getting new people involved in the development community.

Regards,

Josh

3.10.4 Release board: https://github.com/supercollider/supercollider/projects/17

sc-dev Meeting DATE Minutes:

⚠ If you have any comments on topics in these meeting minutes, please start a new thread rather than replying to this one. ⚠

Present: Patrick, Brian, Clare, James S, Nathan Ho, Marcin, Iannis

Intros - welcome Clare!

Check out includecpp.org

3.10.4 board 3132: Patrick will be pushing a branch for 3132. Can server tests run on Travis? It may work on Linux.

may have a linux way to test
maybe OS X?
Is there a ‘user’ logged in with the images on Travis?

Brian will bring QPM into the org

4214: James - ‘This is a bit of a monster’. Has had some time to look into it. Nathan has insight into IPC between lang and sc-ide Not a good idea to subclass QProcess … which we’ve done. It owns a NULL pointer to the IPC client in sclang. When sclang boots it fires a connect cmd. Then the IPC gets initialized and the client connects to the server on the QProcess. Signal and slot set up that registers and sets up the two way communication. When the variable gets set that triggers the issue, there is no IPC client attached. It doesn’t see that sclang has tried to connect to it. Find a way to start VS when lang starts? Really hard to debug. Attach to process by name in VS? Keep in the 3.10.4 board.

4368: Maybe language related? Or - can we discount it for now?

4533: Add to Brian’s to-do

4363: Number 1 on Brian’s to-do. Hopefully next week.

Brian update: Preparing for and taking a vacation. Now he’s back. Maintainer tasks, mostly.

4631 - approved, Brian will merge / push

RFC 1 - support for OS’s / systems and setting up CI to show support it.

Qt tends to be a limiting factor. Other / home-brew limitations may be an issue.

Josh to comment about past support. Nathan as well will soon

RFCs to review https://github.com/supercollider/rfcs/pull/1 https://github.com/supercollider/rfcs/pull/4

Anyone not in the meeting who can review, please do!

Qt - ask on hash include discord about Qt mic input

Clare - initial testing progress:

PR in progress that needs some rebasing.

builds sc-ide as a static lib
- this lets us set up a minimal test framework so anyone who wants to add tests can do so.
branch sc-ide-test-experiments in test suite/editors/sc-ide … (will be pushed later)
Showed her initial setups.
Brian thinks these can be ported into a different test framework. Perhaps commit 'catch.h' into the external part of the repo. James has used it in his personal projects, and says it is amazing.
some licenses questions?

Josh to post notes about Mac OS notarization.

⚠ If you have any comments on topics in these meeting minutes, please start a new thread rather than replying to this one. ⚠

2019-10-27

3.10.4 Release board: https://github.com/supercollider/supercollider/projects/17

Attending - Patrick, Josh, Marcin, James S, Iannis

3.10.4 - 3132 - Patrick - quarks package manager to run tests - JSON in root or repo to run tests by QPM, right now those scripts pull those quarks into the tests. JSON lets you skip tests 1st step - not install common test quark, and just make JSON to include all tests that currently are installed. All server boot needed tests can be skipped. Make a lists of tests that we want to run in Travis - might be a good first step for now. Figure out how to run tests that do boot the server for the future. Maybe in Docker? Branch and have Travis build the branch

4214 - new comment, but there are a couple separate things for that. James has been busy with his Ph.D. (submitted on the 18th!). Hasn’t had time otherwise. Will look this week. Group policy settings may have an effect, but there is a specific one that seems to be a good test. Command line is a known issue - readline prevents proper usage.

4368 - Geoffrey - windows tickets not working. Maybe related to 4214? James has gut feeling that they may be.

4278 - Josh needs to test and we can pull this in.

4533 - Need Brian to sign off on linting change. If Brian can’t., Josh will nudge it.

4363 - Follow up with Brian and Nathan.

Signed SC maybe? Notarization may not work with sc3-plugins. Windows may have an issue with this as well? James S - maybe Steinberg can help - they’ve had similar issues. Is it viable for external plugins to have them by default?

Iannis and Josh to talk more about Server and Multi-Server classes

Josh to write up multi-server approach

Jack and Linux issues

Add https://github.com/supercollider/supercollider/pull/4599 to 3.10.4? Josh and Brian (Josh volunteered Brian) to also look at this.

⚠ If you have any comments on topics in these meeting minutes, please start a new thread rather than replying to this one. ⚠

2019-09-22

Members Present: James Surgenor, Nathan Ho, Brian H, Patrick D, Josh P, Marcin P, Tejaswi Prakash

These notes were not taken at the meeting - apologies - but I believe this is a good summary (Josh P)

RFC proposal will be finalized for next week's meeting (as a goal)
Reviewed 3.10.4 release board
Discussed possible release dates. We want to hear back from a couple people assigned to tasks at the next dev meeting then decide. But we're targeting 10-15 for a beta.
Items on board are the ones we want to attempt to get in (we see this as our goal for a release). Other PRs / issues can be included as we see fit.
Discussion about possibly pulling plugins out of sc3-plugins for self-hosted solutions. Brian will do some cleanup on cookie-cutter, and a couple people will look into pulling their plugins out to encourage others to do so (Josh and ???)

*** NOTES were written very much after the fact … others mostly agreed with this summary. If anyone else was on the call and has additions or suggestions, please let us know ***

2019-08-25

Members Present: Iannis Zannos, James Surgenor, Nathan Ho, Tejaswi Prakash

Slow week, no real updates on the release. Only change is that Nathan put the wrong pull request on the board: meant to put https://github.com/supercollider/supercollider/pull/4510 (Plotter horizontal resize bug) rather than https://github.com/supercollider/supercollider/pull/4511 (Plotter default colors). He has rectified this error.

Iannis is interested in reworking the server boot logic (https://github.com/supercollider/supercollider/issues/3286) and clarifying some of the finer points of the server initialization process (e.g. creation of default group, loading synthdefs, etc).

2019-08-18

Members present: Brian H, Nathan H, Marcin P, Patrick D, James S

SC 3.10.3-rc1 is out!

Todo issues for 3.10.3-rc2:

https://github.com/supercollider/supercollider/pull/4511 ("Plotter: update default colors to valid colors."), which fixes a regression introduced in an earlier 3.10 release.
Code signing - still in progress
- Josh P has successfully codesigned the 3.10.3-rc1 app package, but an issue with codesigning server plugins also needs discussion and investigation

Nathan suggested we should continue with the 3.10 release series in 3.10.4: "I want there to be a stable version of 3.10 that people can use for a long time"

Nathan suggested that since we were able to solve all 6 items on the release board relatively quickly for 3.10.3, we should shoot for 6 for the 3.10.4 release.

We spent some time discussing which items should be in the 3.10.4, 3.11, and Future Release boards.

Marcin will review and rework his PRs in a few weeks when he is done traveling.

Brian brought up the PRs opened by Christof R for his VSTPlugin UGen (#4499, #4379) and wants to prioritize them. Some concerns were raised about #4499, mainly about maintainability. Patrick was concerned that we should not be too quick to introduce a feature that may become broken due to project decay in the future. We agreed to continue discussing it, but not unduly delay the PR since it is a project we want to support.

Nathan suggested that after the 3.10.3 release we could propose an RfC process. His initial concern is that many RfCs will be submitted at once and it will be overwhelming to prioritize and discuss them. We discussed some ideas: "first come first served", cap on active number of RfCs, use "active" and "final review" states to indicate which RfCs are currently prioritized. We agreed post-3.10.3-release would be a good time for Nathan to propose it.

James S talked a little bit about his SuperDiffuse project.

2019-08-10

Members present: Brian Heim, Iannis Zannos, James Surgenor, Marcin Pączkowski, Nathan Ho, Tejaswi Prakash

Release updates:

Josh's macOS codesigning efforts are not required for 3.10.3 and are therefore deferred due to the use of manual release
Marcin's pull request is basically done! Awaiting James Harkins' OK on some minor changes

New item added to future release:

macOS interpreter crash on cmd+q https://github.com/supercollider/supercollider/issues/3824

Although there are some high-priority tasks remaining, we decided against adding ANY new things to 3.10.3 largely for psychological reasons -- this release has been seriously delayed and it is unnecessarily stressful to drag it out further.

Nathan organized the slew of issues in the past few years concerning the help browser and organized them into a board. He closed all issues related to the Linux JavaScript error because, to our knowledge, this is a downstream issue with the Ubuntu packaging.

There were some recent merges which violated the process that Brian had laid out for reviewing. (This was Nathan's doing and he really needs to read the damn reviewer guide haha)

For some reason all reviewers also have write access to the SuperCollider repository, which seems wrong...

Brian believes that in a 3.10.x release, there was a change in CI that downgraded Qt 5.11 to Qt 5.9 and the consequences of it were not properly thought through.

Iannis discussed some of the design issues with NotificationCenter and has a new class, Notification, that he'd like to introduce to the core class library. He will send an email to sc-dev to propose this new change.

Nathan brought up the recent resurfacing of pre-sample initialization and sample-accuracy in SC's core UGens. Unfortunately this is a really, really difficult problem for several reasons: it will take considerable effort and will likely break backward compatibility -- in minor ways for users that don't care about it, and in potentially major ways for users who have used workarounds in their SynthDefs.

Soon, we should discuss a Request for Comment process and a reshuffling of permissions issues in the SC organization.

The roadmap for 3.11 and 3.10.4 will be discussed in a future meeting.

2019-08-04

Members Present: Brian Heim, Geoffroy Montel, Iannis Zannos, James Surgenor, Luke Nihlen, Marcin Pączkowski, Nathan Ho, Patrick Dupuis, Tejaswi Prakash

The Backlog Board is hereby renamed to the Future Release Board (but still usually referred to as the backlog).

Some discussions on the structure and process:

We discussed including the backlog in the Release Board, but decided against since the purpose is to create focus and avoid distraction.
The decision process for adding, removing, and prioritizing items (especially across different communication channels) is not very clear due to the SC community's lack of a clearly defined leadership model.
By a quick straw poll, we decided that it's easier if the Release Board has issues in "To Do" but are replaced with PRs as soon as a PR exists.
The release manager has to leave the process open and democratic but is responsible for watching the process and making the tougher decisions that nobody else wants to make.

3.10.3 Release Board updates:

macOS code signing: Josh (not present) made good progress in the past few days, not far off.
WebSocket port selection: Nathan handed it off to Brian yesterday. Essentially done, just needs a final review and merge.
windows audio devices: Very close, some testing from Windows users is wanted.
network sockets: Luke gave some feedback, awaiting Nathan.
Cmd+Q: Luke reviewed. Tested on macOS and Windows, but not Linux.
Optional QtWebEngine: DONE!

Out-of-board updates:

Iannis received reviews on NotificationCenter help file updates and will be responding to them.
James looked into finding the best way to properly detect and set the SSE instruction set in compiling.
Marcin brought up matching partial device names in Windows.

New items added to backlog:

LinkClock quantum handling and sync https://github.com/supercollider/supercollider/pull/4484
supernova lockup on dsp helper thread https://github.com/supercollider/supercollider/issues/3461
supernova sound input failure https://github.com/supercollider/supercollider/issues/4029
UnitTests do not run on CI https://github.com/supercollider/supercollider/issues/3132

2019-07-28

Members Present: Geoffroy Montel, Iannis Zannos, Josh Parmenter, James Surgenor, Marcin Paczkowski, Nathan Ho, Patrick Dupuis, Tejaswi Prakash

Updates:

Iannis submitted a pull request on NotificationCenter. Iannis is also interested in investigating an issue he's having with remote server.
Patrick responded to James' code review on HelpBrowser.instance.
James did some code review work and started looking at Marcin's Windows I/O device pull requests and added a denormal. He noticed a bunch of deprecation warnings with new Qt.
Marcin responded to Brian's feedback for Windows I/O devices, dependency/dependancy documentation question.
Geoffroy fixed cmd+Q issue on macOS.
Josh dug into the macOS signing issue and has been sketching out ideas for multicore scsynth.
Nathan reorganized the project docs and investigated a dangerous security configuration in scsynth.

We discussed the network security issue in scsynth and supernova (https://github.com/supercollider/supercollider/issues/4496). Despite the fact that fixing it properly involves the addition of a new feature and a minor breaking change, it is important enough that it should go in 3.10.3.

Josh discussed multicore scsynth.

We discussed the newly proposed backlog and release boards and how to keep the process of maintaining these boards efficient (using dev meetings) and inclusive (allowing people who aren't on dev meetings or slack).

Nathan demoed a fun delay UGen.

We discussed the QtWebEngine PR. James brought up QTextBrowser https://doc.qt.io/qt-5/qtextbrowser.html as an interesting alternative to QtWebEngine.

2019-07-21

Members Present: Geoffroy Montel, James Surgenor, Marcin Paczkowski, Nathan Ho, Patrick Dupuis, Tejaswi Prakash

Updates:

Geoffroy is still working on the Cmd+Q bug on macOS.
Patrick tested out the WebEngine PR on both his laptop and RPi, made a pull request #4488 (fixing an error in HelpBrowser.instance in sclang), and updated #4473 (Linux README).
Marcin is working on the feedback that Brian gave him on the PortAudio device selection PR.
James hasn't done anything but hopes to help with Marcin's work this week.
Nathan worked on moving the project docs to the wiki.

We discussed the maintenance status of sc3-plugins.

Nathan suggested the idea of a "backlog board" containing a list of issues of interest, ordered by priority, which is regularly cleaned up.

2019-07-14

Members Present: Patrick Dupuis, Nathan Ho, Geoffroy Montel, Marcin Pączkowski, James Surgenor

Geoffroy worked on fixing the Cmd+Q problem on macOS but has not yet been successful in debugging it (#4300).

Following last week's discussion, Marcin split his huge PR into a bunch of smaller PRs and will be responding to the code review Brian gave in #4475.

Patrick tested #4267 (SCIDE crash when opening up a second simultaneous instance, JavaScript errors when running HelpBrowser outside the IDE). He's been investigating HelpBrowser in command line sclang, but #4267 doesn't fix it. He also went through the guide on the wiki for building SC on Fedora and updated it.

James has been working on fuzzy array comparisons pull request.

3.10.3 drags on. The set of changes in the changelog is not particularly substantial, but code signing issues on macOS are potentially urgent enough for 3.10.3. We also discussed similar permissions-related issues on Windows, which Geoffroy has been looking into (https://github.com/supercollider/supercollider/issues/4368).

Nathan is halting the RFC proposal until 3.10.3 is out.

2019-07-07

Members Present: Patrick Dupuis, Brian Heim, Nathan Ho, Marcin Pączkowski, Iannis Zannos

Brian hasn't done much
Nathan fixed bugs in the QtWebEngine PR and did some standard custodial work
Marcin has been working on the Windows audio driver PR and has been dealing with a long string of issues.
Patrick did some cherrypicks, redid a stalled PR, and tried out the WebSockets one

Marcin has been working with fixing Windows audio drivers on scsynth and supernova (https://github.com/supercollider/supercollider/pull/4009). Some concern was expressed about the overwhelmingly long comment thread, and scope creep happening in the pull request itself, and we agreed to break it down to separate pull requests to make things easier for reviewers and deferring some of the trickier changes to 3.11 rather than 3.10.3.

Iannis is interested in getting started with SuperCollider development and will be looking at the "good first issues" tag to file his first pull request. Iannis also noted some frustrations with remote servers and poor design of Synth class and Event.

Nathan expects to get a working version of the redesigned website in the next week.

Brian is interested in nailing down the project docs (at Mike McCrea's suggestion). We discussed moving them all to the SuperCollider wiki for better unification.

2019-06-30

Members Present: Josh Parmenter, James Surgenor, Luke Nihlen, Nathan Ho, Patrick Dupuis, Marcin Paczkowski, Brian Heim, Tejaswi Prakash

We discussed a potential new RfC (request for comments) process [https://github.com/snappizz/rfcs]: when to introduce, how to introduce, requirements for RfC submitters, and how RfCs should be announced.

We discussed some future organizational concerns: project permissions levels and fragmented discussion venues. There are many places we can discuss SC (sc-users, sc-dev, Discourse, Slack, Skype, GitHub, Facebook), and sometimes knowing where to discuss what is not easy.

Some felt a problem with the forum is that very few developers are using it. In that way, it made the fragmentation worse. We had general agreement that lack of searchability for the mailing lists has reduced their usefulness. General agreement that GitHub, sc-dev, and Slack combined seem to make a good combination of tools for developer collaboration.

Discussion then focused on how we use sc-dev vs. GitHub. General agreement that "goal-oriented" discussion should happen on GitHub. Some felt sc-dev should be seen as a forum for asking and answering development-related questions, reaching out to third-party clients, and announcing important activity. We discussed how to do that when the topics are more "meta" level. A few people remarked using the Core Team discussion area did not seem very inclusive; Luke suggested using GitHub issues, general agreement this was a good option.

After that, we discussed good places for user support discussions. General agreement that if something rises to the level of a bug report or feature request, it should be on GitHub.

Some expressed a desire to focus less on organizational discussions and more on development work for a while, until 3.10.3 is released.

2019-06-15

Members present: Brian Heim, Calvin Yung, James Surgenor, Josh Parmenter, Luke Nihlen, Marcin Pączkowski, Tejaswi Prakash, Nathan Ho, Patrick Dupuis

Most number of people we've ever had on a call! Wow!

Top priority pull requests for 3.10.3:

Separating input and output devices on Windows https://github.com/supercollider/supercollider/pull/4009
Fixing WebChannel related errors https://github.com/supercollider/supercollider/pull/4267
Making QtWebEngine optional https://github.com/supercollider/supercollider/pull/4328

On the topic of making QtWebEngine optional, we discussed how the ability to run code from the help browser is just a nicety, and has the development overhead of requiring two editors.

We discussed a few fun hypothetical UI/UX improvements to scide. These include:

colors + text formatting in the post window
Programmatic access to all UI elements in scide from the language.
Toolbar buttons for running code and entire file.

Josh brought up multicore support for scsynth. The first step is to the waters by evaluating the feasibility of such support and running performance benchmarks on each server. We need to be careful that the reverence for supernova is based on hard data, and not a halo effect where we assume that supernova is good because multicore = faster.

Luke noted that a review of the academic literature on supernova demonstrates somewhat different goals from scsynth. scsynth is designed to minimize latency, supernova for thoroughput. In particular, memory locking is a nondeterministic process, which directly violates scsynth's design philosophy. The impact (to my understanding) is that supernova is really performant on a good laptop or desktop machine, but sacrifices reliability in environments such as RPi.

Optimization isn't just making something faster -- it's the progressive refinement of requirements.

Josh noted that multiple instances of scsynth running allows for a more stable approach to parallelism, which may be more in line with scsynth's design goals, so a possible area of focus would be providing good built-in support for that.

Brian noted that the project would also give us a good chance to clean up the scsynth code base and address some bugs. Ultimately the two servers can absorb each other's strengths.

The long term health of the project will benefit greatly by reducing the number of servers we're maintaining from two to one, and we'll start by assessing the best way to do that.

We discussed better timeboxing of the dev calls. Several of us are more than happy to talk for 2 hours or more, but we're going to keep it to 90 minutes from now on.

Brian has written up some documentation on PR review process so that newer contributors can participate. There are several procedures that Brian, Nathan, and Patrick have informally agreed on but were never written down, and this causes major problems when bringing new reviewers on board.

He brought up some concerns about how our project does not have any formal procedure for the delegation of write permissions.

Our idea is to stratify permissions as follows: 1. reviewers (can hit approve and request changes), 2. committers (can merge PRs). Historically we've been too eager to hand out committer privileges. This is problem not because we want to gatekeep, but because inexperienced Git users have a chance of making mistakes. Some on the call said that they would be more comfortable not having write access for fear of screwing up. Reviewer rights, however, should be handed out to many people.

Action items:

Give write access to Marcin, who has been around for years.
Write documentation for reviewers.
Create two tiers of contributors: reviewers (handed out early and often), and committers (handed out after a period of months).

2019-06-02

Members present: Brian, James S, Luke, Nathan, Patrick

The reformat is done! We're back in action!

Current task is to review our PR backlog and help people with the clang-format process. Rebasing is a bit tricky especially for git beginners, plus it has some minor bugs that we will need to help people work around. However, the number of PRs affected is finite.

This puts us on the road to 3.10.3. The most important PRs for this release are:

Making qtwebengine optional: https://github.com/supercollider/supercollider/pull/4328
WebChannel - fix crash opening a second IDE, fix JavaScript errors running without IDE: https://github.com/supercollider/supercollider/pull/4267
HelpBrowser executes code twice: https://github.com/supercollider/supercollider/pull/4390

Patrick brought up the problem of inaccurate documentation in supercollider-quarks master repository, specifically the use of @ tags.

Luke investigated poor design of .asFloat and .asInteger: https://github.com/supercollider/supercollider/issues/4418 Their behavior is surprising and arbitrary: they return 0 when given incorrect syntax, they ignore characters at the end of the string ("0fdsa".asFloat == 0.0), and they don't support sclang literal features ("0xfa".asInteger == 0). However, unintended consequences of breaking backward compatibility is a real concern in the wake of Float:asString. Changing the failure behavior is particularly dangerous. Discussion on how to move forward remains inconclusive.

We did some early stage brainstorming of how the SC community can adopt an informal RFC process to finalize proposals in major project direction. In particular, we looked at the Rust RFC process: https://github.com/rust-lang/rfcs.

SC development is going to be a bit frenzied in the next two weeks while we catch up with the PR backlog and get in gear for 3.10.3. Once things are relatively stable, the timing is good to open a discussion about RFCs on sc-dev.

The process of proposing and adopting an RFC protocol is a bit chicken-and-egg, but it won't be an issue if the discussion is done in a way inclusive of all SC contributors whether or not they're on Slack or the dev meetings. We make a point of not finalizing any important/controversial decisions on these two platforms, since not everyone is comfortable using those and people are in different time zones. However, contributors who want a say in project decisions are expected to follow at least sc-dev and GitHub.

We had some discussion about upholding civility and ensuring psychological/emotional safety in the SC community.

2019-05-26

Members present: Christof Ressi, Josh, James Surgenor, Luke, Nathan, Patrick

James Surgenor has a PR that fixes highlighted code execution in SCDoc #4390, later a Windows issue with the recordings directory #4420, and is struggling with a mysterious SCIDE issue #4413.

Christof Ressi has a pull request for the supernova architecture (#4379), we discussed some uncertainties with the future of supernova/scsynth. A good first step that would help that decision is implementing ParGroup support for scsynth.

The code reformatting is very close to done -- most of the remaining work is on tooling and documentation. Realistically it can be completed this week. We discussed the possibility of unfreezing the repository but the work on reformatting is so close to done that we agreed this is unnecessary.

Two related but separate issues should be discussed in the wake of what transpired in March: 1. the lack of a governance and leadership model in SC development, and 2. problems of tone/atmosphere in the SC community.

On the topic of governance, how do we establish important decisions that affect long-term health of the project? One approach that was discussed is a semi-formal RfC system. Nathan is interested in reviving his backburnered proposal to clip the audio output on macOS, using it as a guinea pig for a new RfC protocol.

Luke suggested using Code of Conduct enforcement as a way of dealing with tone in both the user and dev communities. SC's community is better than most other open source projects in this regard, but unfortunately the reality is that the user and dev lists still actively scare some people off. James noted the Csound community's approach to this -- a monthly "Administrivia" reminder sent by the list administrator.

Neither Luke or James had heard of the scsynth.org forums, so Nathan sent out a reminder of their existence. The forums and the Slack are linked in the SC README, but the website is still a mess and could do a better job of alerting the community to them.

2019-03-03

Members present: Patrick, Brian, Nathan, Geoffrey M

Codebase reformatting:

Brian wants to do this tonight/tomorrow
Plan: merge Ableton Link PR before doing this (needs quick re-test of Brian's branch)

Date improvements PR (3259):

discussed potential impact of changes
decided to discuss on dev list

Patrick opened several PRs to improve sclang unit tests (4342-4346)

Float->String behavior:

NaN gets printed as "nan" or "-nan" right now, this makes it hard to get a compile-string from it.
discussed a few ways of fixing this ("Float.nan", "(0/0)")

Discussed post-survey thoughts and thoughts for next survey

Discussed Nathan's proposal about sc3-plugins

Nathan plans to contribute more effort to project tutorials/documentation

Patrick plans to contribute small bug fixes and updates to unit tests

2019-02-23

Members present: Patrick, Brian, James H, Mark L, Nathan Ho

Ableton Link:

James will make a PR (squashed) against develop of his new branch
Additional testing? -> No, too much work
Latency issues have been addressed
Brian will try to review & merge before next weekend

Mark L:

Looking into timing in ALSA MIDI implementation -- may be submitting fix sometime (next couple weeks)

PRs:

4324: let's document this way of keeping old things around

MIDI 2.0 & MPE:

Could SC project ask for a copy of the spec?
MPE might take some time to implement, no obvious way to do it

Survey:

where to post results?
- website
- possibly a series of longer 'thoughts' post afterward

JITLib tests:

Patrick is working on some basic tests for NodeProxy to add robustness in future changes

Testing:

writing tests that wait is difficult
Mark: think hard about how to make easy-to-use patterns in test framework
marking requirements on tests

3.10.3:

Nathan wants 2 PRs in before:
- QtWebEngine PR
- QtWebSocket

3.11:

Could release as soon as Ableton Link PR merged

Documentation:

Brainstormed ideas for how to tackle documentation/tutorials

2019-02-03

Members Present:

Nathan, Brian, Patrick

Discussion Topics:

3.10.2
- almost ready to release, just need to merge Brian's PR
- plan: do rc ASAP, release 3.10.2 on Friday if no major issues
  - in the past, rcs have been useful, for example for 3.10.1 we got 3 issues in the first few days
3.10.3 release date set for 2 weeks after 3.10.2
talked about organizing project documentation
- how to balance things between wiki & CONTRIBUTING.md/DEVELOPING.md?
Nathan: seems like SC doesn't use heavy vectorization for UGens with MSVC
- because nova-simd doesn't make the correct check under MSVC
survey: send out another reminder today, close survey in a week
- publish a report & aggregated results at the same time (ideally, at most a week after close)
git workflow: how to manage PRs where original author doesn't have much time to make changes
- everyone is more or less in favor of helping each other out
25th-anniversary edition of SuperCollider should be released as a limited edition CD box set

2019-01-27

Members present: Brian, Geoffroy, Patrick, Nathan

Send out reminder for survey in one week, close in two weeks. Sent out a reminder email only to sc-dev, inviting SC educators to pass it on to students.
Possible doc-a-thon for fleshing out Learn SC
With the Menu memory leak in sclang, 3.10.2 needs to get out ASAP. Once MainMenu is fixed, release 3.10.2-rc1 TODAY, and 3.10.2 in a few days.
Also sc3-plugins 3.10.1...
Nathan has been working on automated tarball uploads
Patrick brought up really bad CPU usage of PartConv even on moderate audio files (5 seconds), + poorly written API and missed opportunity for zero-latency partitioned convolution
No current plans to merge VST plugin support into core -- current state as a 3rd party plugin seems pretty OK
Ableton Link support is stalled and deprioritized for 3.11

2019-01-20

Members present: Brian, Patrick, Nathan

Nathan fixed the old editor themes issue
Nathan has been tackling the WebSocket problems in SCIDE
Brian has been working on whitespace formatting
Brian documented how to use git rebase in CONTRIBUTING.md to help contributors' difficulties with it
Brian fixed string/symbol lexing errors
Nathan has been working on automated tarball uploads, optimized a new WIP compressor
Patrick investigated Platform:helpDir
Patrick fixed a bug in ServerOptions
We released the user survey and spent like an hour watching the first 20 results roll in like we're watching ESPN

2019-01-13

Members Present:

Nathan, Brian, Hanns, Geoffroy

Discussion Topics:

Recent work on VST host support by Christof Ressi
Limitations resampling quality in VDiskIn, PlayBuf
Divergence between AudioClock and SystemClock: OSC bundles are not sample-accurate
NRT mode with OSC socket
SC on WebAssembly+WebAudio: the upcoming version of the WebAudio API will be much more stable in performance than the current one, so reliable real-time audio may be in reach
Ability to query for the existence of a certain UGen via OSC messages
Website redesign

2019-01-06

Members Present:

Nathan, Brian, Patrick, Josh

Discussion Topics:

3.10.1:
- decided to release after 4110, 4180, 4198, 4222, 4230
- will do a release candidate so changes in 4180, 4191 (serial port related) can be tested on Linux & MacOS
- will do a 3.10.1 release of sc3-plugins
- planned release: Jan 13 (possibly earlier)
recent PRs:
- sc3plugins: new plugin PR (BFold)
3.10.2:
- planned release: a month from 3.10.1 release
3.11:
- no strong ideas yet, will talk after survey results come in
user survey:
- run it by the dev list for comments, then post it shortly afterward
formatting:
- Brian has been working on a formatting/linting branch, planning to run by the dev list for discussion

2018-12-01

Members present: Brian, Edmond, Josh, Nathan, Patrick

At the current rate of development, 3.10.1 should be ready to go in a week or two.

Issues in SerialPort.devices and SerialPort.open, and QtWebEngine

nan printing issues: https://github.com/supercollider/supercollider/issues/4139. Possible solution is to introduce Float.nan or Float.quietNan.

Edmond has been maintaining the SuperCollider PlanetCCRMA release.

2018-11-18

Members present: Brian, Bruno, Geoffroy, Nathan, Patrick

Geoffroy and Bruno introduced themselves.

3.10 is all set for release on Saturday (Nov 24). 3.10.1 should be released 1-2 weeks after. #4010 (QtWebEngine) is the priority but not blocking. Nathan has offered to work on it.

#4139 (floating point compile string) can be fixed this week.

#4132 (starting sclang as a systemd service) is more of an issue with systemd.

Confirmed legitimacy of #4133 (split window can crash IDE).

Geoffroy offered to work on redesigning the website. We agreed that it's much easier to just start from scratch.

Bruno is interested in doing GSoC work for SuperCollider. We will wait for the survey to make a decision on how he can best help the project.

New tutorials are chugging along, slowly...

Patrick brought up ways we could improve performance for embedded Linux -- particularly denormal issues on ARM processors.

Nathan discussed how the BEQSuite could be replaced with a faster and more numerically stable set of EQ ugens using state variable filters.

We discussed the future of sc3-plugins. Should we get rid of the trash and slim it down to an "incubator" for core ugens? Should we introduce the incubator as a new repository? Or should we let things be?

2018-11-13

Members present: Brian, Nathan, Patrick

We're back !!!!!!!!

Merged #4105, an important issue for 3.10.

3.10.0-rc1 is ready. Between 3.10-rc1 and 3.10, only help fixes should be done.

We should take a look at #4137 soon.

Thanks to Scott C, UnitTesting class library issue is mostly resolved.

Nathan wrote a new compressor UGen that is almost ready for 3.10.1.

This weekend we'll comb over the 40 open pull requests and look at reviving GitHub project boards.

2018-09-24

Members present: Nathan, Patrick

Nathan hasn't done much
Patrick looked for a solution for the UnitTesting conflict bug and found that quarks has a "compatibility" feature which we could use
We discussed a new issue with scel helpbrowser loading failure
We delisted #3869 from 3.10 since its urgency is not clear
Three issues remain before 3.10.0-rc1 is to be released:
- Ndef fadein
- Syntax colors affect IDE colors
- keyDownAction message

2018-09-15

Members present: Brian, Nathan, Patrick

Critical issues in the wake of 3.10 beta 2:
- Ndef fadeTime bug: Julian has fixed, test needs a touch up
- Syntax theme changing the UI colors (better IDE customization)
- Daniel reported that HelpBrowser doesn't load
- Float printing side effects via adclib: if you override Float:asCompileString it's kinda your problem buddy
- Issues running on older Macs
- QtWebEngine only runs on macOS 10.9 or later and macOS 10.10 SDK
Next beta: Brian will write up a quick blurb on how to properly report issues.
On release, point people to a guide on how to report issues
Brian reformatted the repository's whitespace in a branch
Nathan has been working on making QtWebEngine optional
Patrick:
- https://github.com/supercollider/supercollider/pull/3968 - closed
- https://github.com/supercollider/supercollider/pull/3728 - critical (pressure from Norns devs)
- https://github.com/supercollider/supercollider/pull/3870 - not critical, change milestone to 3.10.x
- https://github.com/supercollider/supercollider/pull/3221 - not critical, but should be reviewed
Cookiecutter ugens
UnitTesting quarks duplicate class error: we need to open an issue for this...
Bela denormal test

2018-09-13

Members present: Brian, Nathan

Brian has been working on a template for generating UGen projects
Nathan has been working on tutorials

Topics discussed:

Ways we could simplify and improve sclang path searching
macOS bundling problem is fixed!
Ways we can improve our CMake code
Debian packaging
Brian has been working on automatically reformatting whitespace. After 3.10 release is the perfect time to do that.
Release 3.10-beta2 as soon as mac thing is fixed

2018-08-19

Members present: Alex Goldsmith, Brian, Nathan, Patrick, Scott, Thomas

3.10.0-beta1 is out!!!!!!!!!!!!!!! (not announcing yet until sc3-plugins beta is ready)

Member updates:

Alex uses gen~ a lot and would like to see single-sample feedback for more fine-grained DSP goodies such as TPT filters & ladder filters with customizable nonlinearities, and discrete summation formulas. He had some trouble with HID, which was last touched 4-5 years ago
Brian hasn't done much
Scott hasn't done much
Patrick has a bandage for his HelpBrowser issues, developed a new quark called SATI
Nathan is working on improving the look of the IDE

Topics:

We'll be (privately) putting together a survey after 3.10 release to get a good idea of the direction for 3.11, which we hope will be released very quickly
New forum is going well: questions are getting answered, lots of little mini-articles
We have tried to get sclang into some major syntax highlighting packages like Highlight.js but most of them have gone without response
A priority for 3.10 is packaging supernova in the official release for Mac
Brian's big projects moving forward are improving the test suite and standardizing C++ formatting across the codebase
Pinning test for ugens
Rendering SCDoc and uploading CI
Remaining "big annoying projects:" SCIDE startup sequence unreliability, debian packaging, supernova on windows, command line on windows
Brian suggested that Alex work on compiler warnings
Possible new official tutorial development with e.g. gitbook, outside SC help system
"Clear post window" menu item
Aaaaaaaaableton Liiiiiiiiiink: going slow, going steady

2018-08-12

Members present: Brian, Nathan, Patrick, Thomas Capogreco

Signal:== random true/false PR
Patrick is still having help browser issues and will file a ticket
Luke's UI colors PR
Thomas's work involves connecting SC to modular synths, which requires clock synchronization

2018-08-05

Members present: Brian, James Harkins, Josh, Nathan, Patrick, Scott Carver

Status of the 3.10 release:
- Linux help browser shortcuts fixed
- Help browser shortcut almost fixed
- SerialPort almost done
- FileDialog hangup and SCIDE look and feel still not started
Josh have been working on package manager for plugins
James is working on Score/NRT helpfile improvements
Brian suggested that we release beta this week, documenting the 2 remaining issues
Issue + PR templates: good idea, a bit too long right now
File object, File APIs
Time for a new logo?
Resurrecting the UI refresh branch
Design documents as a method for preventing pull requests that attract huge amounts of nitpicky comments
Nathan brought up a safe output clipping proposal
Patrick is having a bizarre issue with the help browser

This week:

Merge SerialPort and the Cmd+Enter help browser
Release beta with "known issues list"
Josh will take initiative on logo redesign
Nathan will work on SCIDE
Scott will work on FileDialog
Put out a user survey

2018-07-28

Members present: Josh, Julian, Nathan, Patrick

State of 3.10 and "project docs task force"
getToFloatArray PR
HOAUGens sc3-plugins PR
Divide between new forum and lists
Examples were historically a huge part of SC
Ideas for improving official tutorials, e.g. a "choose your own adventure" format allowing choices between JITlib, architectural info, and tours of UGens

2018-07-20

Members Present: Josiah Oberholtzer, Nathan, Patrick, Scott C.

New Discourse site, legal concerns and Code of Conduct, longevity of the forum, diversity and community health
Suppressing dock icon when sclang is built with Qt
Josiah is working on real-time server without audio driver ("null driver"), building headless SC on travis
Being decisive about replacing bespoke components (e.g. SCDoc) with established software
State of unit testing in SC
Merged Windows Qt issue
Rebasing server menu issue
SerialPort and Windows PR is basically ready to go, but tests should be skipped if the user doesn't have socat/com0com installed
Various shortcut issues evaluating code in SCIDE
Embedding a code font on SCIDE: the defaults are really blinding, and a consistent visual style is nice
Idea: merge Yvan's ServerOptionsGui quark into core for 3.11? (with some improvements to deal with cross-platform differences)
Scott has a lead on the KDE FileDialog issue -- the real mystery is that it's not happening on other platforms
Patrick's help browser issues
Scott's SynthDef specs PR: 3.10 or not?

2018-07-12

Members Present: Brian, Luke, Nathan, Patrick, Scott C

We reviewed the remaining to-do tasks for 3.10:

Linux SCIDE theme -- Luke has decided to look into it
KDE FileDialog issue
Scrollbar issue delisted for 3.10
SerialPort is 99% ready, but RPi and Windows tests are a good idea.
Help browser code evaluation bugs (#3777, #3829)
Scrolling userview with non-integer device pixel ratios
Ableton Link PR has stalled despite attempts in the past month to revive it. There are current disagreements about latency issues.
- Arguments for inclusion in 3.10: we promised it, and it's okay to merge an imperfect feature and fix it later
- Arguments for exclusion in 3.10: we've already done a lot for 3.10 and it's not a mortal sin to wait another release

Overall, we've been doing well! We hit 2000 stars on github and we're closing a dozen pull requests each week. We could be improving ways to help new contributors find the best way to have a good impact on the project. The "good first issue" label helps. We could also be making good use of the Projects feature to map out the next 2 or 3 releases and give a good idea of what to work on.

How do we chip away at 600 open issues (only 200 of which are tagged as bugs)?

An extreme solution would be "bug bankruptcy:" closing ALL bugs except things currently being worked on. If a bug really is important, users will ask the issue to be reopened. Too radical right here and right now.
Establish limits on the number of open issues?

Experienced developers working on and discussing small issues isn't necessarily optimal. If someone files an issue, someone more experienced can point them to a fix.

We haven't really worked out a process for giving push access to new contributors.

We've reached a point where we have some PRs we don't want in 3.10, so it's time to make a 3.10 branch.

Scott got some emails back from 3rd-party devs of SC-adjacent software, and for a dev meeting in the near future, we will be inviting some of them.

In addition, we should also get talking with the user base a bit more about the long-term direction of the project, perhaps with a new survey, to help close the gap between what many users want and what developers are working on.

We discussed some fantastical ideas about GPU SuperCollider and VST integration.

2018-06-10

Members present: Luke Nihlen, Nathan, Patrick

Recent work:

Nathan worked on the Linux README and investigated the no-Qt CPU hog issue
Patrick has been working on the long-stalled HOAUGens pull request in sc3-plugins, and has several class library PRs going
Luke made his first PR, which fixes a crash in the Array:lace primitive

Discussion topics:

Various growing pains in UnitTest that have been causing delays in language and class library pull requests
UnitTest clogging up the quark pipes is a pretty serious issue but it's not receiving any discussion right now
The remaining 3.10 features are Windows SerialPort and Ableton Link
State of SuperCollider tutorials

2018-05-25

Members present: Brian, Nathan, Patrick, Scott Carver

Recent work:

Nathan wrote NHHall UGen -> sc3-plugins, wrote a spec for antialiasing UGens
Scott has been working with pattern library and thinking about improving consistency w/ multichannel expansion
Patrick has submitted some small and helpful PRs
Brian has reviewed some PRs and has ported SerialPort to Windows

Topics:

Denormals - we want them to be always flushed, but it sounds like on ARM (and sometimes on x86) they aren't (reported by Nathan)
HOAUGens - Patrick will help move this PR through
- need to remove the units that don't build on other platforms
Scott has been working with ATK members on their HOA generators - may be a better HOA implementation for SC project

3.10:

Target goals: Qt update, Qt Menu support, SerialPort port, UnitTest/Quarks issue, LinkClock
Release mode when?: will revisit soon

3.9.4:

discussed possibility. Nathan is unconvinced of the need for this, will possibly revisit.

Norns/Embedded:

recent popularity bump. Should work on improving tutorials
interest in SC on embedded devices may be ramping up
consider focusing on improving RPi-SC experience for 3.11 (in the same way 3.9/3.10 were about improving Windows experience)

Documentation:

Brian has an "edit this doc on GitHub" button

Bela: Bela has a remedy (not a complete fix) for this nasty issue when building without Qt: https://github.com/supercollider/supercollider/issues/2144. This is a pretty bad issue especially as SC finds use in embedded systems like the Norns. Maybe the Bela team's patch should be merged in?

Another important performance issue for embedded SC: https://github.com/supercollider/supercollider/issues/3524

Scott offered to reach out to the Monome, TidalCycles, and Sonic Pi teams via email and improve communication with big commercial and open-source projects.

Pushed 3.10 milestone due date to June 30th

2018-03-31

Members Present: Brian, Nathan

Discussion Topics:

3.9.3 release:
- (Kind of) necessary to patch regression in Score (fixed in https://github.com/supercollider/supercollider/pull/3608)
- Could also backport https://github.com/supercollider/supercollider/pull/3558
- Updated release date to April 7
3.10 goals:
- Still agree that Qt 5.9 branch and Ableton Link support are among the top goals

2018-03-03

Members Present: Brian, Nathan, Patrick

Recent work:

Brian: reviewing & merging PRs
Patrick: website PRs
Nathan: reverb development

Discussion Topics:

3.9.2 release - what to merge before releasing
- 3486 (Alberto - fix re-login behavior)
- 3521 (James - isRest backport)
- 3544 (Julian - asScore)
Issues for 3.9.2:
- 3396 (Go back/Go forward) - maybe close as wontfix
- 3454 (GC bug) - move to 3.9.x
- Remaining moved to 3.9.3
Move back 3.9.2 release date to March 10 to allow for last PRs to merge
Agreed to focus on 3.10 after 3.9.2, but still allow work on 3.9 branch
Patrick mentioned he knows someone who has an issue with HiDPI & performance stuff on macOS
Goals for 3.10:
- Ableton Link integration
- Upgrade to newer Qt versions
- Make SerialPort available on Windows
- Fix startup IPC among components
SCDoc replacement?
- Nathan vouched for Sphinx
Nathan discussed his anti-aliased UGens (SawPoly1, reverb)

2018-02-24

Members Present:

Brian, Julian, Patrick, Scott C.

Recent work:

Brian: primitive-defining macro for cleaning up sclang
Julian: neurological SC, project with Dutch CS/math prof; ideas about having extra sclang processes in background; small PRs
Patrick: testing HOAUGens PR, Issue 3396 (Help browser navigation)
Scott: cleanup on Qt WebEngine PR, Atk-related HOA, generic primitive wrapper (to bind to Boost.Math headers), calling native C functions from sclang using dyncall (proof-of-concept)

Discussion Topics:

Issue 3396
- Scott thinks this is a Qt problem and may not be under our control
Julian: could we unify the code editor and help browser?
- Scott: would take a lot of rebuilding; possible as a big project; could make a rich-text webview using existing open-source editors
Scott C's PR to update the help browser to QtWebEngine
- Allows us to move to newer versions of Qt
- Also fixes HiDPI-related issues
- Qt Menu addition would ideally be merged not long after
Qt Menu idea - could make it easier to add system menu items for the IDE from sclang
Julian: would like to add more examples to Help system
- Scott: been doing overview-type work, have examples for WebView
Making it easier to submit bugs/changes from the Help Browser
CMake: update to 3.x because of Ableton Link PR
- Scott: use CMake 3.9.4 (what we have on Travis)
- Make sure smiarx gets credit
- Patrick: maybe 3.5 (Ubuntu) or 3.7 (Debian)
- Scott: be transparent about what we use on Travis
Scott: create a "template" for repos to easily make your own repo w/ auto-released binaries
- Make easy alternatives if we're going to say no
Do a better job of announcing/promoting 3.10 and its improvements
- Get links to Eli Fieldsteel's tutorials
- Get links to the DX7 project
- Show how to link to other DAWs

2018-02-17

Members Present:

Patrick, Nathan

Recent work:

Patrick has been removing some old crap on the website
Nathan has been refactoring the new reverb for efficiency

Topics:

3.9.1 announcement delay
Recent advances in Debian packaging
Timing of introduction of scel and Ableton Link submodules
3.9.2 release date moved to March 3rd
Two Rest-related issues for 3.9.2
Some issues tagged as 3.9.2 have been moved back to 3.9.x since nobody is actively working on them
Refactoring scsynth to improve the API, advantages and disadvantages of moving to modern C++ practices
Timing of the creation of 3.10 branch (in my opinion, creation of the 3.10 branch indicates that it is closed for new features)

2018-02-03

Members Present:

Nathan, Brian, Patrick

Discussion Topics:

3.9.1 is ready to release
VBAP panning bug in sc3-plugins was fixed by Nathan
Brian is working on a unit testing guide
Nathan is working on unit tests for scsynth and for unit generators
HOAUgens are nearly ready to be merged to sc3-plugins
people have learned a bit more about CMake recently
considering moving to CMake 3(.1?) - seems well-supported at this point

2018-01-27

Members Present:

Brian, Patrick, Nathan

Discussion Topics:

Recent work:

Patrick: lots of small website fixes, sc3-plugins PRs
Nathan: custodial stuff, UGen testing, planning to work on UGens for school project
Brian: couple of minor fixes, Boost update PR, custodial stuff, looked at Qt update PR

sc3-plugins

PR #146 has some issues
It's still an open question of how to best add Faust-to-SC plugins to sc3-plugins
Would be nice to have a minimal checklist for things that go in

3.9.1:

Ready to start the release process
Merge #3469 as last item for 3.9.1 (?)
Nathan has created a 3.9.2 milestone

Unit-testing:

Guidelines are badly needed
A future goal is to move most (if not all) of UGen testing code to C++ for speed and dependability

2018-01-20

Members present: Nathan, Brian, and Patrick

3.9 release went well -- downloaded over 1000 times.
3.9.1 has 14 closed pull requests, which is plenty enough for a patch release. Although we are not in any rush, we could easily release well ahead of the scheduled date of January 31st.
Brian has been working on AppVeyor integration, monitoring LiveCode Slack for new issues.
Unit tests are not written consistently due to lack of documentation.
Unit & integration tests for UGens can be written in C++ using Boost.
Various ways the appearance and usability of the IDE could be improved:
- For 3.9.1, let's just make auto-indent optional instead of fixing it entirely. Unfortunately, there is no reliable way to test changes to auto-indent.
- Embedding volume meter and other basic controls.
- Difficulties making SCIDE look attractive on arbitrary native themes, and the possibility of
- Replacing the default light theme entirely.
- Making the Documents docklet match the theme for visual consistency.
- Making the Documents docklet match the theme for visual consistency (much more difficult!).
- Licensing of themes.
SCDoc regressions
FreqScope improvements -- afterimage, antialiasing
SuperCollider installation on Raspberry Pi is absurd, involving manually moving files
Debian packaging has mostly hit a wall :(
Adam's Guard configuration PR can go into 3.9
Release signing
Travis is back in order

2018-01-13

Members Present:

Brian, Julian, Patrick, Nathan

Work remaining for the 3.9 release (laments about Travis issues)
Licensing concerns for new editor themes
"Known issues" section in changelog

2018-01-06

Members Present:

Brian, Patrick, Gerard (g-roma)

We just discussed the SuperColliderAU PR/project and where it belongs in the SC org repository constellation.

2017-12-30

Members Present:

Nathan, Patrick

Discussion Topics:

3.9.0-rc1 needs to be announced to Facebook...
Currently waiting for users to test 3.9.0-rc1. If all goes well, we will make a decision on January 6th
Merged last remaining PR for 3.8.1.
Fragmentation of SC community across different platforms.
Would be a good idea to revive sc-dev and have more in-depth discussions on the list instead of on GitHub.
We should announce major PRs to the list and regular updates about what we're working on.
Decided against creating a 3.9.1 branch for simplicity. 3.9.1 patches can wait until the 3.9.0 release.
Speed of release schedule can be improved by being less choosy about what needs to go into each release. If something holds back the release instead of pushing it forward, it needs to be delayed.
Patrick redesigned the download page for the website to be up to date for Linux users.
Nathan has been working on Debian packaging but has mostly been hitting dead ends.
Bela port of SuperCollider has diverged considerably from core, we need to consider what to merge in.
Future website redesign could probably be done as a quick weekend project.

2017-12-23

Members Present:

Brian, Nathan, Patrick

Discussion Topics:

3.8.1:

Merged #3348, will update changelog and release 3.8.1 soon.
Because of #3348, will also have to add binaries to release.
Nathan has created a draft release.
Will have to be tagged on 3.8 branch since master already has 3.9 stuff in it.

3.9.0:

Nathan will review and merge 3275
And after that, release next instance because it closes all open 3.9 milestones
#3266 - no longer milestoned as 3.9. Marked as "waiting for information" since cause is unclear
Decided to call it a "release candidate" since all bugs from 3.9.0 beta are eliminated and signals that we are very close to release
3.9.0 release set for 1/1 unless major issues arise

3.9.1:

Nathan wants to release 3.9.1 a month after 3.9.0. Ambitious but we are setting the bar low for the number of changes going in.

Wanted for 3.10:

Nathan: new UGens (will work on as an independent project for school)
Ableton Link synch (#3351)
Brian: Update Boost, update Qt version
Brian: Fix SerialPort on Windows

SuperColliderAU PR (#3350)

SuperColliderAU reboot that runs from current develop.
Agreed it would be better to move some of the project to a submodule

scsynth allocator PR (#3318)

milestoned 3.10 at Brian's request

Patrick: safeguard for syntax errors in startup files.

Right now it causes a mysterious error with no indication that it came from the startup file.
Could easily be fixed for quality of life improvement

Thanks to all who attended! The next meeting has been set for December 30, 2017 at https://appear.in/sc-dev-meeting.

2017-12-16

Members Present:

Brian, Patrick

Discussion Topics:

3.8.1:

waiting on Nathan to release this small update
purely meant for Arch Linux packaging
just source code, no binaries

3.9.0:

Alberto merged Brian's PR into the 3275 PR
Patrick's PR cleaning up TestServer is ready to be merged
Plan (tentative): merge 3275 within a week and release a second beta by Dec 23

Thanks to all who attended! The next meeting has been set for December 23, 2017 at https://appear.in/sc-dev-meeting.

2017-12-09

Members Present:

Brian, Patrick, Nathan, David (Runge)

Discussion Topics:

3.8.0:

possibly releasing 3.8.1 with a header include fix so that it builds with latest gcc toolchain
see discussion in #3015/3029, would help with Arch Linux

Debian packaging: ongoing woes. Might contact umlaeute (Debian packager for pd)

PRs for 3.9:

3275 (lockClientIDWhileRunning):
- Patrick has no issues with branch, has been using for awhile
- Brian is ready to review
- Julian should also review
3332:
- Fixes an issue with the default server Volume synth

3.10:

Brian wondered about starting to update libraries (like Boost) on develop branch in advance of 3.10
- is OK, but should still focus efforts on 3.9.0/3.9.x

Thanks to all who attended! The next meeting has been set for December 16, 2017 at https://appear.in/sc-dev-meeting.

2017-12-02

Members Present:

Brian, Patrick, Nathan, Josh P., Julian

Discussion Topics:

PRs for 3.9:

3317: merged, closing 3196
3318: maybe a bit of testing before merge
3275: still needs some work
3267: merged

Issues remaining for 3.9:

3266: still an open question
3176: Nathan can fix but is busy, might not go into second beta

3.9.1 issues and PRs:

3 good-to-go PRs already queued up
1390: "Error: ScIDE not connected": possibly not able to tackle in 3.9.1
3310: milestoned as 3.10

Nathan wants to work on new UGens for 3.10

Josh: plan out things to unit test in 3.9.1, .2, .x based on issues we're running into now – e.g.: server booting process; synthdef loading

Future of Supernova and Scsynth – could one be merged into the other?

Library maintenance for 3.10: boost upgrade, Qt upgrade

Thanks to all who attended! The next meeting has been set for December 9, 2017, 21:00 UTC, at https://appear.in/sc-dev-meeting.

2017-11-18

Members Present:

Brian, Patrick, Ben, James (McCartney)

Discussion Topics:

Brian:

planning to debug beta-related issues (#3196)

Patrick:

wants to test Alberto’s PRs (#3275, #3286)

Ben:

has been working on building SC on Windows to get familiar with the build process
will start working on Supernova n_order issue (#3100)

James:

just came to lurk

Issues before next beta release: with everyone's planned combined efforts, it sounds like we should be able to address most of the relevant issues in the next few weeks!

Symposium 2019 discussion on mailing list: yay

Thanks to all who attended! The next meeting has been set for November 25, 2017 at https://appear.in/sc-dev-meeting. We will try to keep the same time: 4 PM EST.

2017-11-04

Members Present:

Brian, Nathan, Josh, Patrick

Discussion Topics:

Issues arising from AudioControl changes (#3266, #3196) History cleanup PR – can be merged once done (#3267) SCDoc UI - Nathan wants to make TOC popout only to smooth over bad behavior of dropdown TOC Lock client ID while Running PR (#3275)

Priority: fix audio control issues for 3.9.0, possibly releasing a second beta

Dan Stowell’s blog post about Linux packaging Should remove outdated PPA mention from website Use Docker for testing Pulseaudio/Jack woes Would like to add documentation on buffer allocators

3.9.1: Will be mainly our testing ground for shorter release cycle. Nathan wants to fix two issues (auto-indent in IDE, default font on macOS)

Thanks to all who attended! The next meeting has been set for November 11, 2017, time TBD.

2017-10-28

Members present: Brian, Julian, Nathan, and Patrick

We are moving the next meeting to 6pm eastern.

We are just about to announce the 3.9 beta, and we're currently waiting to test the windows builds.

Development cycle for 3.9.x releases will tighten considerably -- maybe about two months between each one, or about 20 pull requests. We are also aiming for a fairly short 3.10, something around six months.

To help motivate development progress, each patch release has one required major bugfix. For 3.9.1, we should fix two longstanding IDE problems: auto-indent and the default font on macOS.

Some other good issues that we should turn our attention to, but arent required for 3.9.1: Integer:forBy bug and CPU hog with Qt-less sclang. "Edit on github" feature is almost done. Brian is also interested in fixing a lot of our development infrastructure such as the tests system.

Release of stable version is done by merging 3.9 branch into develop, and then 3.9 into master.

We are changing our approach to milestones. 3.9, 3.9.1, and 3.10 milestones are all strict -- if an issue or PR is categorized under them, those issues MUST be resolved before release. 3.9.x milestone means issues that aren't required, but it would be nice if we could fix them in a patch release soon. Issues can be moved from 3.9.x to 3.9.1 if it is decided that it's practical to complete them in time for release.

2017-09-30

Members Present:

Brian:
Nathan
Patrick

Discussion Topics:

Patrick’s PRs to the supercollider.github.io site and his plans for future work on the site
The last few things that are ready to be done before 3.9 release (getting very close)
Issue https://github.com/supercollider/supercollider/issues/3211
git flow maintenance of the release and develop branches

2017-09-23

Present: Brian, Nathan, Lucas, Edmond, Patrick

Brian: GitHub edit link with Cian, distance-based amplitude panning (DBAP) UGen
Nathan: Linux packaging, Debian packaging
Patrick: working on help system soon
Lucas: introduced himself, interested in contributing when possible
Edmond: introduced himself, interested in contributing C++

Discussion Topics

Multi-client ID PR:

still failing on Travis because of test integration issues
either fix test integration or disable tests temporarily

New UGens:

Nathan wants to work on more UGens after 3.9 release

Cleanup:

Brian wants to work on documentation for new contributors and cleanup/organizational work for the codebase

main SC site:

Needs love
Feature more projects
Update text

Moving out Emacs submodule:

Open issue (https://github.com/supercollider/supercollider/issues/3066)
Will wait until post-3.9 and ask on dev list

Thanks to all who attended! The next meeting has been set for September 30, 2017, at 16:00 UTC (12p EST) at https://appear.in/sc-dev-meeting .

2017-09-16

4 members were present: Brian, Alberto, Cian, and Nathan

Recent work:

Brian: documentation, especially unit testing documentation
Alberto: multi-client ID PRs
Cian: Ableton Link work, forBy interpreter bug
Nathan: pitch shift window size PR

Discussion topics:

issues with ReadableNodeIDAlloc PR
unit testing documentation
creating a template/generator for unit test code
documenting C++ source code
adding a link to help files to go to editing the help file on GitHub
removed email notifications from GitHub to sc-dev
getting the help browser to open a GitHub edit link in default OS browser

Thanks to all who attended! The next meeting has been set for September 23, 2017, at 16:00 UTC (12p EST) at https://appear.in/sc-dev-meeting .

2017-09-09

Five members were present: Cian (@cianoc), Nathan (@snappizz), Brian (@brianlheim), Alberto (@adcxyz), and Jack (@jarmitage)

Recent work:

Brian: travisCI, unit testing, organizational documentation
Nathan: Debian packaging
James: interested in helping out (currently mainly a user)
Alberto: multi-client ID PR
Cian: fixing help files, potential Ableton Link support in 2-3 upcoming PRs

Topics of discussion: multi-client ID PR:

Alberto has raised new issues on GitHub to target specific design problems that arose in the PR
He plans to rework #3106 (the current PR) into a few smaller PRs to avoid stagnation
We talked about whether to put it in 3.9 or 3.10, and agreed that some of it should definitely go in 3.9 (see discussion below)

Suggestions from Cian:

improve documentation for new supercollider users (coming from i.e. Ableton)
add a UGen overview
add a Quark overview

3.9 critical todos:

block allocators portion of multi-client ID fix
sendNotifyRequest extension of multi-client ID fix
after that, release! OK to push a beta without full Linux packaging
continue to work on Linux packaging, hoping to have a good release

Adding UnitTest and test suite in common:

Nathan pointed out there are issues with the UnitTest class that should be worked on
We discussed (and tentatively agreed on) putting the test suite in the main class library
This would be aided by adding a helpfile for unit tests documenting how to disable unit tests if desired

Thanks to all who attended! The next meeting has been set for September 16, 2017, at 16:00 UTC (12p EST).

2017-06-10

Three members were present: Brian (@brianlheim), Nathan (@snappizz), and Julian (@telephon).

Topics of discussion were:

Till's recent email to the dev list, sc3-plugins and maintenance of SC's "satellite" projects
some close-to-being-merged PRs: we talked about what was needed to merge
method table: Brian agreed to test the performance of the language (both memory and speed) with a high number of methods defined, to either put to rest or confirm old rumors
PR backlog: Julian agreed to move a number of his inactive PRs to the PR backlog (https://github.com/supercollider/supercollider/projects/7).

Thanks to all who attended!

2017-06-03

Brian finished the breadcrumbs link issues and filesystem UTF-8 support.
Nathan didn't do much aside from participating in discussions

topics:

we merged 10 pull requests and closed 16 issues this week! holy hell!
Rest refactor is pretty much ready. Nathan should review it, merge within the next week, and we can then do a post-mortem
current open discussions regarding style guides, and issues with design by committee in free software communities
should we really dedicate time to sc3-plugins?

2017-05-27

5 people were present: Brian, Alberto, Nathan, Julian, and Patrick.

Brian Heim has been working on his big UTF-8 pull request which fixes the Windows help file issue.
Alberto de Campo has a topic branch for multiclients to improve node and buffer allocation, and has a PR for OSX standalones.
Nathan Ho has been working on UGen regression tests, and small help files and class library issues.
Julian Rohrhuber worked on File.read* methods, Rest/Operand reform, and a quark for a Neutral object that records every message sent to it.
Patrick Dupuis has been investigating the Ubuntu keyboard shortcut issue and has been working on help file, class library, and Linux-related issues.

Topics:

Old standalone instructions are gone.
A PR can be merged when it presents an improvement and doesn't introduce new bugs.
3.9.x releases and eventual adoption of git-flow
SCDoc, barriers for new helpfile contributors, features we can add to the help files to make it easier to contribute
Number of PRs open, speed of merge, filing PRs with incomplete work

2017-04-22

Nathan did nothing
Brian worked on the Windows help file issue and include/exclude paths for scsynth

Topics:

Merged/closed some small PRs
CONTRIBUTING.md, and issue and PR templates

2017-04-01

Nathan did nothing
Brian updated yaml-cpp, filed a PR to fix the .putPascalString crash, and has done some work on the Windows help file bug

Topics:

Release mode for 3.9 in about two weeks?
sclang header refactoring
WebView:onLinkActivated
LPC regression tests

2017-03-11

Brian Heim and Nathan Ho worked on sclang LPC tests
Nathan Ho also made (marginal) progress on UGen regression tests
Patrick Dupuis investigated openbuildservice.org and HID on Fedora

Topics:

Plan for merging LPC test suite: get it to run, see if it catches changes to sclang, quick review, merge
openbuildservice.org, while good, is not a useful service for the SC dev team since it creates a PPA/third party repository.
Performance on MacBook Pro 2016
Brian is pushing the Boost updates because it works towards fixing the Windows helpfile problem
Find people and get support for the SC_SCLANG flag: https://github.com/supercollider/supercollider/pull/1939
Mixed feelings on single quotes in variable names: https://github.com/supercollider/supercollider/issues/2773
Backing up SC: https://github.com/supercollider/supercollider/issues/2776
Rational numbers implementation: put off until 3.10?
Push release date back to May 1
sclang verbosity proposal is not a requirement for 3.9, but it's important
Brian and I share an opinion on the state of SC development right now: we're overloaded with work, and the lists of issues and PRs often feel like a huge wall of noise. We've been cutting down on multitasking and trying to focus on what's important, and have felt increasingly nonchalant about proposals for new features.

2017-03-04

What we did:

Tom Murphy did nothing.
Brian Heim has been working on regression tests for sclang, which should be ready to merge within a few days. He has a working proof of concept using the recent nested multiline comment fix.
Rainer Schütz is working on making SC buildable on VS 2015. The difficult parts are QtWebKit and supernova.
Nathan Ho worked on a bunch of small things as usual, FINALLY fixed the Linux tooltip issue with Rainer, and has made some progress on UGen regression tests.
Patrick Dupuis is looking into HID issues on Fedora Linux (the help file contains an Ubuntu-specific udev rule).

Topics:

appear.in supports stickers, as we discovered this meeting
Cross-platform compatibility of the older Python sclang tests.
April 1 was a bit optimistic for 3.9 (we only have 2 out of 8 major issues outlined in January), but we can still try to push to finish some important issues.
Issues with packaging. Looked at openbuildservice.org and discussed Travis CI, AWS, and Linux PPAs. We don't really have a documented release process right now.
Our thoughts on the recent mailing list discussion:
- It's okay if we use a mailing list even if they're out of vogue
- It's not okay that people are sending messages to the list through Nabble and we can't do anything about their messages ending up in limbo
- We should replace Nabble, not the list
Concerns over scvim development rate
Unanimous support for deprecating OSC(path/r)esponder[Node]
Missing sclang features: .asStringPrec with trailing zeros (see http://new-supercollider-mailing-lists-forums-use-these.2681727.n2.nabble.com/asStringPrec-td5826156.html), converting a hex string to an integer, binomial coefficient
SC decision-making processes, then and now. Conference calls vs GitHub vs sc-users vs sc-dev for discussions.
Extension of this discussion: http://new-supercollider-mailing-lists-forums-use-these.2681727.n2.nabble.com/Github-in-web-editing-disable-td7630916.html

2017-02-25

Brian Heim has been working on regression tests for lexer/parser/compiler, which will ensure that changes such as #2673 and #52 can be safely fixed. Also started work on refactoring Document.
Nathan Ho didn't do much, aside from starting to replace OSCpathResponder, etc. with OSCFunc.
Luca Danieli has been working with Scott Wilson on making it easier to extend the IDE.

Topics:

Migrating Contributing page from website to the repository itself
Introducing a new issue template
The changelog has gotten too long, time to clean out entries before 3.6.6

2017-02-18

Tom (@vivid-synth), Brian (@brianlheim), Rainer (@bagong) were present.

Recent work:

Tom has been investigating UGen stability, and reports that Select is a prime example of a highly stable UGen
Brian has been working on a refactor of the Document class
Rainer has been working on the SC_SCLANG/MACOS_FHS build options

Topics:

Full Windows support: obstacles are readline+Visual Studio (and the suggested alternative linenoise-ng), and the ongoing filesystem bug
A possible structure for the new Document (and possibly IDE) classes - no decision reached
Meeting frequency and format - we agreed that it might be a good idea to try to have once-a-month meetings as a larger group, and that the other weekly meetings could be smaller status updates. We'd also like to choose meeting topics ahead of time so that people with relevant experience will be more likely to participate.

2017-02-11

What we did:

Brian Heim has been trying to build SC on Fedora. Investigating MacBook Pro 2016 performance issues with Sam Pluta. Details are very unclear right now due to lack of data, could be a mix of a hardware issue and a bug in SuperCollider. Drafted proposals for sclang regression testing and verbosity.
Nathan Ho made a small amount of progress on UGen regression testing with an NRT mode version of loadToFloatArray.
Tom Murphy has been reading the server code.

Topics:

Boost submodules again
Method table issue: https://github.com/supercollider/supercollider/issues/1450

2017-01-28

What we worked on:

Tom Murphy worked on a minor control bus issue (issue 1280) and has been assigning trustworthiness labels to UGens.
Alberto de Campo has three ongoing projects: multiclient server, improving node ID allocation, and improving the Quarks system so one can trace the quark associated to a given class.
Nathan Ho did nothing aside from some small help fixes.
Brian Heim sketched out verbosity levels in sclang.

Topics:

Potential compatibility issues with the node ID allocation refactor
Definition of sample-rate independence for UGens
Automated testing pool for UGens
Regression tests for the parser and lexer
SourceForge must die
Post-3.9, consider expanding our set of filters and reverbs
Assigning a theme to each release and/or a funny name
Making Boost a submodule, such as using the boost library instead of fopen
Brian's ongoing PyrLexer rewrite

2017-01-21

What we worked on:

Brian Heim managed to get SC built on Windows and has dug a bit into the Windows helpfile issue, and has been working on a huge refactor of PyrLexer.cpp (largely untouched since the initial commit!).
Nathan Ho slacked off with some miscellaneous changes such as a Ctor bug in FOS, and investigated OSC v1.1 "compliance."

Brian proposed that 3.9 be delayed until every important issue regarding compatibility (in particular Qt 5.7, command line REPL, Windows help files) is fixed, making it arguably the first fully cross-platform release of SC. After that, 3.10 could concentrate on improving user-friendliness by improving SCIDE and Qt GUI.

2017-01-14

What we worked on:

Tom Murphy worked on benchmarking TCP/UDP, and on the new PlayBuf proposal.
Brian Heim read PyrObject and PyrLexer classes and filed a number of sclang PRs.
Nathan Ho mostly worked on help files.
I couldn't hear Julian Rohrhuber very well, but I know he worked on various (mostly classlib) tasks.

Topics:

Brian discussed parser changes, e.g. "var" statements after other statements.
Julian discussed how difficult it is to trust the "_" notation.
Julian's server refactor isn't quite complete -- server crashes aren't completely graceful, but still better than before.
Problems with class library standardization. Example would be the various problems with the Rest system.
Brian is concerned that the huge backlog of issues and PRs is overwhelming. We could be more aggressive closing old issues and PRs, and also be less shy asking people to finish things up.
Fredrik Olafsson suggested using larger SynthDefs containing collections of UGens in addition to pinning tests that target single UGens.
Julian talked about using mocking/stubbing in class library tests.
Tom brought up issue #1209, a small mistake in the class library that blocks headless systems.
We should go through all the UGens and assign a confidence rating to each one.
Nathan started a draft of a comprehensive guide on how to record in SC.
Ways to improve our git workflow:
- Consider a stable master with develop branch
- Codify rules about when to merge things.
- Only approve a PR if you've read the code and tested it, and say what you did in the approval message.
- If you don't understand a PR, don't be shy about prodding for an explanation.
The dev team should specialize formally -- put up a list of major components of SuperCollider and who is assigned to what.
Created two GitHub projects, respectively compiling the most important issues for 3.9 and listing the long-term projects in SC: https://github.com/supercollider/supercollider/projects/1, https://github.com/supercollider/supercollider/projects/2

2017-01-07

Development progress:

Tom Murphy: started PlayBuf 2017 proposal, currently reading through scsynth and supernova code.
Brian Heim: generally exploring the code base, especially sclang; submitted miscellaneous help file fixes; found a mysterious bug possibly related to GC.
Nathan Ho: lots of class lib and help miscellany.
Scott Carver: connection quark, finishing up Qt menus, discussions with the ATK devs about splitting from sc3-plugins.

Everything else we discussed, in roughly chronological order:

Probably release beta for 3.9 in April.
Scott discussed progress on the QtWebKit -> QtWebEngine port, which faces difficulties due to the asynchronous nature of QtWebEngine.
Code review and better docs for core features that need to work, like GC and SynthDef optimization.
Mounting complaints that SC is getting slower.
Nathan should break the ice on unit tests by writing "pinning" tests for UGens to guard against accidental behavior changes.
Getting more people involved in Windows development, esp. fixing that blasted help file bug.
Ron Kuivila had some general comments:
- Confusing abstractions in the Patterns system, such as the opaqueness of EventStreamPlayers.
- Making SCIDE more user-friendly. A larger pool of built-in SynthDefs and/or integration with sccode.org.
- Embedding sclang in Max, better connectivity to openFrameworks.
TCP vs. UDP: create a new quark for automated benchmarking to allow easy testing across different systems.
Website improvements. Redesign can probably wait until later, but we definitely need better resources for users interested in development.
Brian volunteered to lead a "documentation drive" to help drum up more user participation. Establish guidelines on how to write good help files. Don't request minor changes like typo fixes on help PRs, just merge and fix later.

Wiki Home

Wiki directories

Contributing
Contributing to the project, filing bugs, creating pull requests, style guidelines.

Development resources
Project documentation, structure, reviewing, releasing, and other processes.

User resources
FAQ, resources for learning, tutorial lists.

Community
Forums and communication, community projects, artworks and initiatives, info about the SuperCollider project.