Shared resources installation

Another brain feeding idea for upcoming LGM :)

Recently I compiled SVN build of Hydrogen — a cross platform open source drum machine. Hydrogen uses drumkits — libraries of drum samples that are usually stored in a local directory. SVN version features a network drumkits installator. It fetches updated list of available drumkits and lets users download new ones or remove existing ones.

What do you think about creating a similar online repository for shared resources and either internal or external clients to it? Internal client for each application means tighter integration, but also more work in common. External standalone-client means less work, but also less integration.

The most serious cons, I guess, is that this would clearly be installation into ~/.create and thus not efficient for multiuser desktops.

Subjects to further consideration:

  • introducing modularization of shared resources (and thus having separate branches in repo for each kind of shared resource);
  • introducing basic metadata for resources (name, description);
  • organization of repository;
  • administration of repository.