@jayrope I might call myself a ChucK investigator. After defeating my dislikes of the terminology (chucking, sporking, screduling) I’m convinced of ChucK‘s potential for any kind of concurrent process control.
Obviously #chuck is not a good hashtag for finding it. Same with the guppe group chuck you’re proposing. What about spork or scredule? chorkule? Too far off?
Or perhaps the collaboration medium could be something completely different, like a #mumble room. Or the good old chat rooms.
My best experience was with their book „programming for musicians…“, Kapur et al. And the Ge’s PhD explains the details. See https://chuck.cs.princeton.edu/ for reference. But this tends to make ChucK a bookware which runs against http://gnu.org/philosophy/free-doc.html
Just working on a publication which involves R packages like #tuneR and #seewave, ChucK, and #lilypond. It’s wrapped around the first chapter of the Kapur et al book. Right now I’m focusing on the event mechanism for loop sequencing, with an eye on Atari #Notator like event and score handling