ilfelice
But we have different interpretations of "reusing". If one has to setup and maintain a separate repo, then
that's duplicate effort to me.
You don't expect to be free to present your product on a shelf of a store who disagree to distribute your product. The only viable solution is then to either find another store accepting to distribute your product or setup your own distribution platform. With digital products, it's far more easier than with physical ones.
I'm not saying I'm agreeing or not with the Haiku-OS project rules, what I'm saying is they're entitled to set the rules on their own infrastructure, and you can't expect to be freely using their infrastructure while not respecting their rules.
It's not fully duplicate effort, as it's not only setup a second package repository, it's also getting ruling power on what can be distributed on it. This second part give you something you didn't have before.
I don't know what you are referring to "wanting to get something without effort".
We are contributing to the Haiku community with native apps that have never existed before.
Developing is one part. Distributing is another. Otherwise we won't have this very discussion, right?
Here, the issue is not developing, it's about distributing and reaching the highest audience possible.
It's not part of developing a software, but it is part of distributing a software to potential users in a way they will find it convenient to find, to install, to uninstall, and to get support if needed.
I'm not saying developing software with AI is not a contribution or needs no effort. What's I'm saying is AI doesn't help you to distribute software (yet), and therefore you rely on either conform with pre-existing distribution channel(s) rules or setup your own. Expecting not having to conform to existing distribution channel(s) rules because you don't want neither to accept their conditions nor setup your own distribution channel is what I call "wanting to get something without effort".
