this post was submitted on 11 Jan 2025
-31 points (29.3% liked)

Open Source

31972 readers
101 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS
 

Why are open source projects too rigid and stuck in dogmatic position ?

take for example mastodon, its CEO recently posted a toot asking who has already considered deleting facebook / threads after the recent controversies, but on the other hand ignores that his stubbornness about certain points like not adding quotes just doesn't make the project appealing for ordinary people, this feature has been the most request since twitter exodus two years ago. and at every surge of new users mastodon struggles to keep them using the platform, why do these projects struggle to acknowledge what people want the most and deliver on it.

another example is LibreOffice, I was trying to get acclimated to this new office suite and was happy to find that I can theme it to my liking to ease up my transition. but it wasn't long before I found out how tiny dogmatic decision really pushes to give up on it. I found that LO doesn't auto-capitalise first letter after line breaks but only after end of sentences, something Word has been doing as long as I can remember, LO argument is that only a . and ! characters mark the end of a sentence in "proper English". line breaks don't qualify as a proper end of a sentence for them.

For people coming from proprietary software that among many short comings still strive to offer the best features and smoothest user experience, it is hard to try and stick to open source projects and even contribute back.

Should big OSS project shift to more democratic structures, where decisions are made based on consensus? or do you think the actual models are fine, and I am an entitled user ??

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 2 points 3 days ago (1 children)

If an OSS project wants to thrive, it would behoove them to implement things that people want. I don't think there's a one-size-fits-all solution there, but they shouldn't be surprised if nobody wants to use their software because it doesn't do what they want.

[โ€“] [email protected] 2 points 3 days ago

The goal for OSS projects is always different. Many projects solve a problem for the developer(s) and them alone. They don't care about it 'thriving' or adding features that don't align with that problem.

I find it confusing when people complain that other people won't spend time implementing things that they want. If you want feature A, fork the project and add it. I appreciate that's easier said than done, but if you can't or won't do that, stop complaining about what other people do with their time.

Not all software is the same. Get used to them being different.