Sorry for the dramatic headline this morning, but I am slightly emotional yet at peace…
After 66 months of intense work (research, development, musicking, teaching, scheming, devising, revising, etc) with some of the most talented and generous people in our field, the funding is now finished, and we officially go on to other occupations within various institutions… the list of people to thank is immense, but let’s focus on the core: the immediate team of @weefuzzy @groma @jacob.hart @tedmoore @jamesbradbury - then @a.harker who was part of that lot and part of the second lot, the artist consultants who contributed, musicking and commenting on our interface research, struggling against early iterations of it all… @rodrigo.constanzo @pasquetje @saguaro @leafcutterjohn @alicee @Chriskiefer @tutschku @rdevine1 @spluta - and then the keynotes and other collaborator and some of you on this forum when we went public… now if I start to name everyone this will be wayyyyy too long so I’ll stop here about the past. I think every FluidCorpusManipulationToolbox user owes them a lot!
That lot: obviously the toolset, but as importantly for our field, music and code and reflection on it, learning and teaching material to get on with it, articles to poke at the research and an open source codebase
This is where the long live part of the subject comes into play: it is now up to all of us as a community to maintain and develop this resource. Everyone can contribute:
- from finding bugs by using the cutting edge in your practice,
- to sharing (Max/Pd/SuperCollider) code,
- via maybe helping with the release process;
- to sharing (Max/Pd/SuperCollider) code,
- from asking to answering questions here;
- from providing better explanations on the learn.flucoma.org platform tested within your community,
- to (obviously) making Fluid Corpus Manipulation · GitHub reports on bugs and ways forward.
I, for one, will continue ploughing slowly at all of this, but help is always welcome.
Thank you everyone for what was a hell of a ride!
p.a.