I have developped several HLAs in the past weeks (Python API is pretty straightforward to use!) and I would like to publish them so others can enjoy them.
According to the extension pages, GitHub is the only supported method to host and publish extensions.
Unfortunately, the platform has gone AI-first with massive scraping over hosted repositories in the last months / years, so I try to stay away from the platform as much as possible.
Would it be possible to host source code of LLA or HLA on other git platforms like GitLab or Codeberg, and publish the extension to Logic marketplace ? I guess such platforms would need to support releases like GitHub, but major competitors do have that feature.
Thanks for asking. We’ll need to think about this. The reason we use github as the source of truth for published extensions was because it helped us keep our infrastructure as simple as possible. We don’t host anyone’s extension, which is really nice. We also only have to have one registration and publishing flow. We would need to weigh supporting multiple platforms vs. alternative solutions like just hosting the published extensions ourselves.
Back in the day, we did consider adding support for custom extension marketplace servers, so say closed source extensions could be easily shared inside of an organization. Not quite the same thing here though.
I’m a little surprised it’s taken this long for someone to request support for other platforms. In the meantime, if anyone comes across this post looking for support for non-github extension hosting, please comment to let us know!
I totally understand the simplicity of supporting a unique infrastructure instead of multiple ones, especially since it’s the one you use for your own internal development.
When looking at the publication workflow and how users installs and consumes the extension, do you use GitHub-specific features appart from the release (which is basically an archive of the source code usually attached to a git tag) ? It doesn’t seem to be far from the basic git repository that can be hosted anywhere.
Perhaps it could possible to have something similar to winget packages (Windows’ package manager) ? They have a central repo that only stores the list of packages and their metadata, and the actual source code / install scripts of the packages are hosted somewhere else, on each package supplier repo.
But it’s certainly easier to drop a proposition here than to actually implement a solution that covers all the use cases you want to address while remaining easy on maintenance.