New upload process draft spec

Sporiff

Hi everyone o/

We're kicking off development of some new features and are starting to spec things out. I've started work on speccing out the new upload process we'd like to implement. At the moment, the spec is mostly just a collection of thoughts and process descriptions, but I'd like to get your feedback nonetheless so we can make sure we address all issues!

You can find the spec draft here.

Sporiff

Since we've not had any feedback on this, we'll go ahead with the specification as-is. The specification can always be updated at a later date if we find the implementation has any shortcomings!

Spec link

gcrk

Sporiff This specification does not yet mention any enforcement of rules that might be set by an admin.

There is the discussion about enforcing only tracks with mbids, from managing open.audio we have the need to enforce that a license is set. If we do this in the background by the service worker, how can the user take action here? The track upload and publication would fail, is there any way to update the metadata and ask for the publication again?

Maybe something to discuss in our next session 🙂

Sporiff

gcrk Yeah let's discuss this. Whatever we do, we need to make sure it's easy for a user to rectify the problem in the app if possible, otherwise we're just going to frustrate them.

petitminion

Sporiff @gcrk Afaik the main issues are metadata update or audio conversion. And do this in the app seems difficult to implement. But a message explaining how to resolve the problem would be great o/ (which software to use for example, what tags to set)