Is there any copyright/licence specialist here? I've come up with an idea of having a free open software library that randomly displays offensive[0] messages full screen that comes with a BSD type licence with a clause that forbids removing/disabling that message. I assume that many developers or end-users[1] at home are perfectly fine with a messagebox popping up once a month with a "f## off" message, while any corp…
> with a clause that forbids removing/disabling that message This sounds similar to the "invariant sections" clause of the GNU Free Documentation License; except you're talking about software instead of documentation. > I assume that many developers or end-users[1] at home are perfectly fine with a messagebox popping up once a month with a "f## off" message Some people are really angry about GNU Parallel's citation "…
FUSE for macOS is no longer open source
261–270 of 407 posts
Re: FUSE for macOS is no longer open source
#262I agree that any aggressive towards the maintainer is unwarranted, even if I personally disagree with his move. In particular this comment quoted in TFA amused me: >Then drop it and let someone else maintain it. I want to reply to this person: then fork the last open source version and maintain that. That's the whole point really. Besides he apparently made the change two years ago and people only start noticing now,…
I'm a startup tech founder, benefiting massively from FOSS code. I realise there is a debt here, and the plan is definitely to repay that debt once we're cash-positive. Being able to have that plan, and not having to pay for software licences up front, is awesome. But I totally understand TFA's point of view. Maintaining a FOSS library is hard work, and those benefiting from it should contribute. If he's not seeing t…
By failing to contribute, small companies cost themselves money very quickly. How can a small business afford to live in a world of un-maintainable forks, patches and tech debt?
Only large companies can afford to maintain private forks of FOSS. Small companies have to give back, or they will simply disappear.
Re: FUSE for macOS is no longer open source
#263The problem with permissive licenses is that they do nothing for the people actually developing the software, and makes it extremely likely that others will profit off their back without ever pushing even a line of code upstream.
People will try to guilt you into changing licenses so they can use it in a commercial product, but seriously - if that person is going to profit off your code, you should be profiting too.
Re: FUSE for macOS is no longer open source
#264Earlier quoted context omitted.
Yes, and I am saying that is not a great thing for FOSS.
Why isn't it a great thing for FOSS? It is what FOSS is, and FOSS is in a pretty great place right now.
Re: FUSE for macOS is no longer open source
#265Earlier quoted context omitted.
There are two possible scenarios: The developer always thought that contributing back code or financial support should be a requirement of use but failed to reflect this in the license chosen and now is correcting this. The developer over time has changed their believe of what the requirements for use should or need to be. This change of thought may have been informed by the behavior of those using the code but is st…
In my system of value (which is of course subjective and you may not share) I do consider that these open source projects suffer a sort of tragedy of the commons where some companies benefit immensely from them (think how expensive it would be to build and maintain something like osxfuse from scratch) but don't contribute anything back to it. It's like big corporations managing to pay little to no taxes in the countr…
In that world, would it matter so much if some commercial interests took a product, since they'd always have to at least show their work? The idea was that we'd eventually have FOSS replacements for everything from Photoshop to Word to video editors.
2019 and GIMP is is nowhere near the level of Photoshop, Libreoffice is pretty decent through, and DarkTable isn't too shabby.
Still, this FOSS utopia of all our software never happened. Linux as a kernel for Android has led us to an even more closed system than before. Sure if Linux was GPLv3, maybe we wouldn't see it as the basis of Android at all, but if we had gone down that route, I wonder how things would be different.
I've written at length about this before: https://battlepenguin.com/tech/the-philosophy-of-open-source...
Re: FUSE for macOS is no longer open source
#266I agree that any aggressive towards the maintainer is unwarranted, even if I personally disagree with his move. In particular this comment quoted in TFA amused me: >Then drop it and let someone else maintain it. I want to reply to this person: then fork the last open source version and maintain that. That's the whole point really. Besides he apparently made the change two years ago and people only start noticing now,…
But the current maintainer has the Apple provided signing cert, that's the whip hand in this whole deal.
I personally don't blame this fellow and in fact apluad him. To many companies exploit OSS maintainers. I think it's great to see someone turn it around for once.
Re: FUSE for macOS is no longer open source
#267Earlier quoted context omitted.
I'm not sure the argument "FOSS has done fine so far" is that convincing when you then lay out many of the places where FOSS has been failing miserably.
Not to forget the many, many places where it has and is succeeding happily. Here's my "get off my lawn" perspective: those developers who remember a world where there was little or no free software (from, say, the mid-1980's, when Sun made the C compiler a for-cost option on SunOS through until commercial Linux distributions), have a visceral understanding of free software that those who came to it later, and (perhap…
Re: FUSE for macOS is no longer open source
#268Earlier quoted context omitted.
I wasn't aware that osxfuse is distributed by Google. If that is the case then I am sorry for spreading false information and indeed, the GPL would apply.
It's still not clear whether the GPL would apply in the way commenters here think it would. GPL clauses would only affect Google code upon linking. It's often possible to use fuse style software without linking - they could use it via the command-line and mount whatever they need at startup or even dynamically. Does osxfuse have a command line tool? Most fuse style software does. If it doesn't, Google could have writ…
Re: FUSE for macOS is no longer open source
#269Earlier quoted context omitted.
I'm a startup tech founder, benefiting massively from FOSS code. I realise there is a debt here, and the plan is definitely to repay that debt once we're cash-positive. Being able to have that plan, and not having to pay for software licences up front, is awesome. But I totally understand TFA's point of view. Maintaining a FOSS library is hard work, and those benefiting from it should contribute. If he's not seeing t…
"Small companies don't have the resources"... that's some backward thinking right there. By failing to contribute, small companies cost themselves money very quickly. How can a small business afford to live in a world of un-maintainable forks, patches and tech debt? Only large companies can afford to maintain private forks of FOSS. Small companies have to give back, or they will simply disappear.
Re: FUSE for macOS is no longer open source
#270This is a very sucky situation to be in, and I've been on both sides of it. I wrote KSCrash [1] a decade ago, and it's become the de-facto standard for crash handling in the Apple ecosystem. I didn't intend for this to happen; I just wanted crash handling MY way. But it's my baby, and I need to support it (technically no, but yes I do), even though I get no financial benefit from it. For a year, I was paid by a priva…