[sadfaceunread]

Very cool. A couple questions: is the song really the right vehicle to pass around? By analogy isn't that like moving the binary instead of the code? I understand the lack of DAW cross-compatibility but it seems like you might need all of the components that make up a song along the way in order to work on a subsequent task.

It looks like this is still in the experimental/conception stage. Right now it seems more like a mental model for music than actual tools. I'd be interested in seeing what analogies besides code would be applicable or might have lessons learned. For example, I know that collaboration and sharing of mechanical engineering design software is relatively less useable/mature than sharing a git repository. For artists that collaboratively work on 3D models or images I'd imagine that the workflow is passing around .psds or whatever, rather than final images because everyone is on the same platform.

I'll be paying attention as this develops.

[crablar]

Passing an entire song between phases is only one model. Within that model, the spec I prefer is: whoever is receiving the song gets to choose what format he receives it in. Lots of small files, one big wav, whatever.

I have heard good things about Splice, which allows git-like collaboration.

What I want to underscore: there are great tools for individual and small-group creativity. I'm interested in processes for a large team that allows asynchronicity and scalable development.