3 ms·
You're welcome to compile, sign and release your own Mac binaries, and even charge a fee for them if you want in order to cover the costs. It's OSS after all. O
by askvictor 10y ago
You're welcome to compile, sign and release your own Mac binaries, and even charge a fee for them if you want in order to cover the costs. It's OSS after all. Or even make a polite request or ticket on the problem. But don't tell OSS devs what to do in a snarky voice.
- pyre 10y agoAt the same time, when your project takes off past a certain point, don't you gain some amount of responsibility if you know that you have become an attack vector? If you don't want to take on that responsibility, then you could just quit hosting binary builds, and focus on the source. Then it becomes "someone else's problem" to deal with hosting binaries, and providing security.
- askvictor 10y agoGood point; though approaching the problem in an indignant and righteous fashion doesn't achieve anything; offering to help with a solution is more in line with the (ideal) OSS ethos.