support reviews, comments, user submitted audio clips, etc. for top-level schema types

[RustoMCSpit]

"I think the Registry specification could be extended to support reviews, but would need some thought to it."

will the reviews, comments, user submitted audio clips, etc. be collected on each app / cli / website in different repos or will they all be aggregated and sent upstream and downstream.

also, will reviews be broken up into multiple categories (e.g. gui, dsp, etc.) and each gets a 1-10 rating and then thats averaged out into an overall 1-10 or is it just an overall 1-10, and will reviews be able to submit markdown text, gif, image, audio, midi data, etc. and finally can people respond to reviews (especially the developer)

https://www.thomann.de/ie/harley_benton_hbma_50_mandoline_vs.htm

[kmturley]

The Registry has top-level schema types such as:

• plugins
• presets
• packages

Potentially it could be extended to add:

• comments
• reviews

comments/reviews could have various properties such as:

• author
• date
• description
• files

Based on the current architecture comments/reviews would need to be submitted as yaml files, which is not ideal. Likely there would need to be an API and database to allow login and saving of comments/reviews.

Definitely interesting feature idea, but would say this is a long-term feature request, after everything else is done.

[RustoMCSpit]

comments/reviews could have various properties such as: author, date, description, files

links to project files? so just markdown i guess

also if a plugin is ever detected it should have a "projects used in" section

https://github.com/open-audio-stack/open-audio-stack-registry/issues/23

[RustoMCSpit]

The Registry has top-level schema types such as: plugins, presets, packages

this should apply to projects too, people should be able to review them. soundcloud lets people add comments (which should be able to include markdown text, gif, image, audio, midi data, etc.) on a wav file animation, that could be done specifically for this. you could also have each track as its own wav and have a dropdown to see the master wav or the individual wavs / midi (so detecting track groups would be important too)

[RustoMCSpit]

author

https://github.com/open-audio-stack/open-audio-stack-registry/issues/24

this would be going into user login territory and that means user pages and passcodes