Hello everyone,
I want to introduce myself - I am one of the members behind PatchStorage.com.
I would like to thank @workerparasite303 for inviting me to join this conversation.
To begin with, we do want to add Axoloti support to our site and we are ready to address all the specific needs you guys may have. In matter of fact, we have been discussing about Axoloti last week that this platform is a great example where all the music hardware is going right now, especially looking at possibilities/cost ratio and we want to be part of that!
Addressing main concerns that you have mentioned here:
@mongrol: regarding legal ownership of patches - uploaders have full ownership and during upload process they can choose under which license they are sharing their work. This is the same way SoundCloud or any other user-content-based project operate.
@thetechnobear: we started this project for the same reason to avoid hunting for patches over different places. Regarding integration with Axoloti Patcher UI - we will be making our own web API. In the first revision we will be implementing get requests for specific platform and search functionality. We could discuss this further...
@johannes: compared to Git, we do provide more user-friendly approach, especially for "non-technical" users. At the same time uploaders can still provide the version number of their project, update it and other members can suggest their own versions of the patch by uploading it in the comments section.
Also, as you have mentioned, the biggest advantage of PatchStorage is the social aspect. We have user profiles, ratings and comments. Later this week we are introducing "Follow" functionality. Such kind of features are the ones that boost the growth and the engagement of the community.
So, I really think that PatchStorage could bring more traction for Axoloti platform. All our members are there for the same reason, just the tools they use are somewhat different.
Let me know, what do you guys think.
Cheers,
Pranciskus