I think basically it’s a nuanced decision that’s worth making on an per app basis, there’s some valid justification for respecting upstreams wishes and some valid justification to ignore it, and either option is valid depending on perspectives. But if the answer is no, for example, if snap creates new categories of issues that innately unfixable or this might tarnish their brand or their bug tracker, I’d be inclined to hold off snapping it too. If the answer is yes, then honestly I’d say that despite the upstreams wishes, it’s still a good move overall for both users and the upstream to snap it. The question then could be viewed as, would the Snap be better than the other options available, and if so, by having more people use the Snap does it decrease the amount of issues third party packages generate overall. I think this is a strong arguement for respecting upstreams wishes, because I’ve seen it in action, it essentially adding cost to upstream unfairly, given they ask not to.īut it’s something that needs to be weighed against the current scenario, that third party packages do exist already, including in Ubuntu’s own repositories.

I think this is a valid excuse ethically, it’s understandable to ask people not to give you more work to do that they’re not responsible for.

Regardless, it’s legally viable.Īt a guess, they don’t want people making third party packages because bug reports could end up being sent back to upstream which are introduced by the third party packages. It seems conflicting to me they would make it to be GP元 whilst also basically encouraging people to revoke the rights they grant for it being GP元. I’ve had the same response in the past, but I think it’s worth mentioning just for sake of discussion that there’s some justification for going against upstreams wishes, though I’m not specifically saying do or don’t.Ĭalibre specifically is a GP元 application, and that’s a choice made by the developers themselves.

Calibre epub reader for windows