Hi, Clapper dev here. This issue was brought to me recently, so allow me to state my opinion here. The REAL problem here is that Clapper Snap package is currently completely broken and doesn’t work at all. The person who published it, knew that it does not work, but still did not hesitate to publish broken package.
i had already the recipe ready
You cannot say you had it “ready” if it did not work at all. You just published it broken, people might be already installing it, and now you just saying that “not working there are issue from my side” and you promise to make it work eventually in future.
By having package is such state on Snap store, not only this makes it look to any potential users that it is my app that is broken, but it also makes people lose trust in Snap distribution system.
I do not really care if anyone copies someone else build manifests. It is a common practice to search for examples and help when trying to make something but unsure how. The difference here is that at least @soumyaDghosh contacted upstream with seeking help to present Snap community the best possible working package when ready, while @SamAlex published something completely broken just to have it right now.
Considering such behavior and all problems for myself that will come with it, like explaining users until/if fixed, who open issues on Clapper github that my app is fine and it doesn’t work just cause you use Snap. I am in favor of of transferring ownership to a maintainer that first asks and only acts later.