this post was submitted on 20 Mar 2025
29 points (100.0% liked)

Opensource

2230 readers
117 users here now

A community for discussion about open source software! Ask questions, share knowledge, share news, or post interesting stuff related to it!

CreditsIcon base by Lorc under CC BY 3.0 with modifications to add a gradient



founded 2 years ago
MODERATORS
29
Open source maintenance fee (opensourcemaintenancefee.org)
submitted 1 day ago* (last edited 1 day ago) by fxomt@lemmy.dbzer0.com to c/opensource@programming.dev
 

Note: This uses github sponsors, which is a microsoft owned middleman as @poVoq@slrpnk.net mentioned. I heavily recommend https://liberapay.com/ as an alternative. The idea of the project is solid, though

cross-posted from: https://lemmy.world/post/27040265

I personally think this is a good idea. FOSS is amazing but it needs some funding in reality. What are your thoughts?

top 13 comments
sorted by: hot top controversial new old
[–] FizzyOrange@programming.dev 2 points 15 hours ago (1 children)

Pretty unclear if this has any actual teeth - if you don't pay it says "don't create issues" etc. but is anyone going to stop you?

But let's assume that it did stop you. I'm going to give a dissenting opinion - I don't think it's a necessarily bad idea. Phabricator had that business model for years; without paying you got zero support. No ability to open issues, etc.

My company ended up paying for support... so that we could get support. There's absolutely no way they would have paid if it was a standard license and you could just open a GitHub issue, even if the issues were ignored.

Annoying for non-corporate users though I guess.

[–] Umbrias@beehaw.org 1 points 14 hours ago (1 children)

many for profit companies have done this before, however:

Think about the incentive structure here, it incentivises not learning about bugs in the software. it incentivises as this always does, that those with money to swing around get additional explicit systemic power to dictate the features and bugs that get fixed. this is a bounty system with extra steps and not learning about bugs. and to boot, if a company really wants to pay, they can probably pay a dev of their own to work on many of these issues. it doesnt seem like this really solves any issues and just imposes a pay-to-speak system. ick.

[–] FizzyOrange@programming.dev 1 points 14 hours ago

Yeah true. It definitely has downsides. But so does begging corporations for money...

[–] cypherpunks@lemmy.ml 5 points 23 hours ago* (last edited 23 hours ago) (1 children)

cross-post of my comment elsewhere:

I immediately knew this was going to be from Microsoft users, and yeah... of course, it is.

Binaries distributed under this EULA do not meet the free software definition or open source definition.

However, unlike most attempts to dilute the concept of open source, since the EULA is explicitly scoped to binaries and says it is meant to be applied to projects with source code that is released under an OSI-approved license, I think the source code of projects using this do still meet the open source definition (as long as the code is actually under such a license). Anyone/everyone should still be free to fork any project using this, and to distribute free binaries which are not under this EULA.

This EULA obviously cannot be applied to projects using a copyleft license, unless all contributors to it have dual-licensed their contributions to allow (at least) the entity that is distributing non-free binaries under this EULA to do so.

I think it is extremely short-sighted to tell non-paying "consumers" of an open source project that their bug reports are not welcome. People who pay for support obviously get to heavily influence which bugs get priority, but to tell non-paying users that they shouldn't even report bugs is implicitly communicating that 2nd and 3rd party collaboration on fixing bugs is not expected or desired.

A lot of Microsoft-oriented developers still don't understand the free software movement, and have been trying to twist it into something they can comprehend since it started four decades ago. This is the latest iteration of that; at least this time they aren't suggesting that people license their source code under non-free licenses.

[–] fxomt@lemmy.dbzer0.com 2 points 18 hours ago

Yeah, the fact they use github sponsors drill your point further. Great comment by the way.

[–] Kelly@programming.dev 10 points 1 day ago* (last edited 1 day ago) (2 children)

Q: What if I don’t want to pay the Maintenance Fee?

That’s fine. You can download the project’s source code and follow the Open Source license for the software.

Do not open issues. Do not ask questions. Do not download releases. Do not reference packages via a package manager. Do not use anything other than the source code released under the Open Source license.

Also, if you choose to not pay the Maintenance Fee, but find yourself returning to check on the status of issues or review answers to questions others ask, you are still using the project and need to pay the Maintenance Fee.

I disagree vehemently! The community adds value and is a form of contribution.

[–] fxomt@lemmy.dbzer0.com 1 points 16 hours ago

Yeah, that last point is the most BS honestly. So even if you aren't using the project, checking up on it gets you to have to pay? Wtf.

[–] Brewchin@lemmy.world 3 points 1 day ago

Agree with you. That last paragraph reeks of Reddit-like monetisation of community goodwill.

[–] poVoq@slrpnk.net 11 points 1 day ago (1 children)

Seems like a Github sponsors promotion website. Why waste money by using a Microsoft owned middle man, when better projects like LiberaPay exist?

[–] fxomt@lemmy.dbzer0.com 5 points 1 day ago* (last edited 1 day ago)

Ah yeah i agree, i forgot to mention that. I think the general idea of it is good though. I'll write a note recommending liberapay.

Edit: fixed!

[–] ertai@programming.dev 1 points 21 hours ago* (last edited 21 hours ago) (1 children)

This is so stupid. you don't pay so you're not allowed to make the project better by contributing?? I think this person has a very poor understanding of what open source and libre software are. also, open source has not been refered to as a cancer, the GPL has, because of it's copyleft. I have the impression this person does not really know what they are talking about.

[–] fxomt@lemmy.dbzer0.com 1 points 16 hours ago

yeah... I posted this with a general idea of what this looked like, but after reading into it more and reading some of the comments here i agree with you. Seems like BS now.

How does a project enforce the license? I'm not familiar with a mechanism for public projects to limit who can open issues, etc.