Many #openweb projects have failed over the years, and there are reasons, first is the challenge of sustaining a project that is built on open-source principles and relies on community involvement and collaboration. In capitalism, without a clear and consistent funding model, it can be difficult to keep projects going over the long term.
Another factor is the competition from proprietary technology that is always better funded and more easily accessible to the public. This can create a challenging environment for open-source projects that struggle to keep up with the pushing of “innovation” in the tech industry.
There are also ideological differences between different groups within the open-source community that leads to conflicts and disagreements over the direction of projects. This can result in splintering and fragmentation of the community, making it difficult to achieve a shared goal.
Non “standard” #UX is a big issue as well, nice to make something you like, but better to do something the user community likes.
From @bob@epicyon.libreserver.org Irreconcilable musical differences, someone in charge of donations taking it to Vegas, becoming a parent or getting a new job, burnout, unrealistic expectations based on hegemonic BigTech systems, illness, an excess of technical debt and trolling can all result in failures of open source projects.
Most projects are one or two people with occasional driveby patches. Projects with more volunteers than that are rare exceptions. Most maintainers are not people on six-figure salaries going on slides at Google. Usually they are barely making rent.
Another factor is that often accessibility is not as good as it could be. The big companies can dedicate a department to just ensuring accessibility meets a minimum standard, but open source projects often don’t have the knowledge and are regularly criticized for accessibility problems.
From the #openweb
(https://elplatt.com/) happy to remove this link if asked
The main challenges I’ve experienced in projects I’ve been a part of:
* Tendency for potential contributors to start new projects from scratch
* Lack of communication within the user community and between users and maintainers
* Contributions driven by prestige or excitement, prioritizing new features over maintenance
* Lack of funding
It’s a good list, maybe we need a post writing up covering them all.
(This is why I work #KISS whaw that is bad behaver, lie about someone then blocked their instance. #GreatjusticeNet has blocked campaign.openworlds.info for plagiarizing fediverse content. In this post, it says “From the #openweb” in BOLD, so clearly it’s not plagiarism. But happy to remove stuff if people don’t won’t it archived)
Over the years, many #openweb projects have failed due to various reasons. The first challenge is to sustain a project that is built on open-source principles and relies on community involvement and collaboration. In a capitalist society, without a clear and consistent funding model, it becomes difficult to keep the project going over the long term.
Another factor is the competition from proprietary technology that is better funded and more easily accessible to the public. This creates a challenging environment for open-source projects that struggle to keep up with the “innovation” pushed by the tech industry.
Ideological differences within the open-source community leads to conflicts and disagreements over project direction, resulting in splintering and fragmentation of the community, making it challenging to achieve shared goals.
Non-standard #UX is also a significant issue, as it’s better to create something the user community likes than something just the developer likes.
Some ideas on this from the #openweb, irreconcilable musical differences, individuals in charge of donations taking it to Vegas, becoming a parent, getting a new job, burnout, unrealistic expectations based on hegemonic BigTech systems, illness, an excess of technical debt, and trolling can all result in open-source project failures.
Most projects have only one or two people, with occasional drive-by patches. Projects with more volunteers are rare exceptions, and maintainers are typically not people on six-figure salaries going on slides at Google. Usually, they barely make rent.
To sum up, the main challenges experienced in the projects that the author has been a part of include the tendency for potential contributors to start new projects from scratch, lack of communication within the user community and between users and maintainers, contributions driven by prestige or excitement, prioritizing new features over maintenance, and lack of funding.
Additionally, accessibility is often not as good as it could be, as big companies can dedicate a department to ensure accessibility meets a minimum standard, but open-source projects often lack the knowledge and are regularly criticized for accessibility problems.
In conclusion, a post covering all these challenges would be useful.
