I'm going to rant about open source a little, I am so sorry.

So much of open source favors people that ~ have time ~ That usually means:

- They aren't caretakers (i.e. they don't have children or elder family that have care needs) or can rely on a partner to do all of that in their stead.
- They can work long hours outside of their 9-5 jobs which excludes many Disabled people or those that have chronic pain.
- They already have a high paying job, they have health insurance.

- OR you work for a company that values open source for one reason or another (there are some very cynical reasons you can think of there, obviously, the potential for unpaid labor).

But ultimately, at the root, because we live in this hellscape where people can't have healthcare and it's a race to the bottom for wages, it's incredibly exclusionary to Disabled people or any one who considers themselves a caretaker.

it just feels like we're never going to live up to the baseline that open source needs to actually thrive. I don't see the current landscape of burnt out maintainers, especially those that are unfortunate enough to have very popular libraries with no corporate backing, as succeeding? People need healthcare. People need UBI. They need childcare. They need elder care.

Not saying we should give up on OS, but sometimes I'm overwhelmed at what we're missing.

I think about this a lot when I see maintainers who shrug off accessibility requests as "Well make a pull request! It's open source!"

The very people that are experts that you need contributions from aren't included or welcomed in this community.

Then, throw in the complicated mess that is "modern" javascript or just frontend development in general. You expect people to be experts at accessibility, to have the bandwidth to contribute, AND to navigate that landscape?

The amount of incredibly detailed Github issues I've seen where someone has taken the time to do a manual accessibility audit and give suggestions, even to write the expected HTML, but because it's not wrapped up in a PR with proper Typescript and accompanying unit tests and broken down into 5 different components for "potential" reuse it gets no movement. This is why you get no contributors for these things.
So much of the core of tech leaves out Disabled people and that's ultimately why we can't have nice things. It's why everything ends up being just a little bit worse for everyone. It starts there, then it reaches out to other groups of people that aren't overrepresented in tech, then FINALLY to everyone else who all throw up their hands and say "Who could have seen this coming?"
To the people replying to this that are all "you're describing people that have time for hobbies": I'm going to give some of you the benefit of the doubt that you know nothing about open source software, but to the others that are intentionally missing the point so they can be dismissive in a conversation regarding the inclusiveness of the OS community, you can kindly go fuck yourself.
@hbuchel Ouf. Yeah, hobbies are totally different from OS work. I can knit for 5 minutes waiting at a bus stop. 5 minutes isn't much of anything for a software project.
@hbuchel I fortunately don't need accessibility tools to use my PC, but at the same time this also makes it somewhat hard to develop accordingly. For web stuff, there is https://wave.webaim.org/ which helps but with other types of applications, I don't know of any kind of linter.
WAVE Web Accessibility Evaluation Tools

@hbuchel Yup. Open Source doesn't get to ignore the awful system of incentives and privilege.

It just has a slightly different system of incentives and privilege.

I'm really glad there's an alternative at all, but it only gets to "cheat" a little, not a lot.

It still favours people with money and time, like so much of all current human endeavour.

@hbuchel I'm to the point in this realm, because I keep seeing this "choice" of big tech with spying & privacy invasions galore with a sizable amount of disability accessibility vs open source where there's less spying & privacy invasions of smaller entities as mostly I get data repeatedly lost ( instead of stolen & purposefully deleted as with big tech)& close to no accessibility, where when I can, I'm going plunge in, for redesigns, mainly of hardware because so far there's no open source operating systems for phones that are Rugged (durable enough to withstand the messes those of us with neuropathy dish out). I can't say when it'll be though, as on your track, I'm already a almost 2 years behind on my project lists.😬 #DisabilityAccessibilty
@hbuchel I wonder if there's an initiative out there for accessibility templates for different frameworks, languages, etc. If there is, it obviously needs more exposure. If there isn't, it'd be cool to see.
I remember interacting with some visually impaired people over IRC maybe 10 years ago who were very thankful for Orca in Ubuntu. (This was a long time ago so some details may be off.) OSS can do great things for accessibility, and I'm hopeful that won't end.
@shroudedscribe It'd maybe be helpful to have accessibility specific contribution guides. I see so many people say they don't have expertise in that area and they'd love to have contributions. But I think outlining the ways people can contribute and how you plan on helping guide them through contributing, would be helpful. There are a lot of folks in web accessibility for instance that don't know specific frameworks like React, but they know the DOM well enough to give maintainers a start
@hbuchel In enterprise software, it's easier to get regular expressions past code review than it is to get to rewrite a badly inaccessible component from an external library. I've written React for close to a decade professionally and don't have any problem conforming to the conventions, but it honestly feels like simply being able to write CSS and HTML prevents me from participating in front end dev. I just focus on other areas and let people who hate it do the things I love to do. It's weird.
@hbuchel good lord, flashing back hard to that time years ago when I just wanted to make a very small a11y fix to a project, hadn't touched git/github until that point...and had to persevere for weeks to basically learn how to do it etc, all just to add an extra `:focus` style to a control. "luckily" this was just around the time i was let go from my job, so i had plenty of time to devote to this...

@hbuchel as some have mentioned previously, this affects many fields, artists among them. I think a big reason many arts conferences skew young (or elderly) is that without proper financial support (paychecks) the grind is so tough that many burn out after 5 or 10 years.

Life can be tough for freelancers. I see the same thing in volunteer radio DJs and other "hobbies". It's a volunteer effort for the greater good.

@hbuchel I would like to see a large marketing effort made to pay the people who write the FOSS applications that many depend on.
I think many consumers value the type of work FOSS contributors are doing. By repeatedly nudging them to financially give to those who freely provide their time and resources, they would be paying the workers directly- and not some profit hungry exec who pays the workers just enough to get by.

I believe that sentiment would resonate with a lot of unaware consumers.

@hbuchel I agree in general, but be mindful that not all countries have a broken healthcare system like the US. In many EU countries you get almost free healthcare and a much lower cost of life. That still doesn't change the imbalance about time / energy left for open source for many people though.
@hbuchel and then we get things like xz 😞

@hbuchel Yup as a married parent who values time with my family, OSS isn’t really an option.

Even if it was, the idea that it’s virtuous to turn hobby time into effort that benefits corporations is pretty depressing.

@SamStrong @hbuchel

Isn’t it the other way around? Turning my work paid by corporations (SUSE in my case) into an opportunity to contribute to FLOSS?

@mcepl @hbuchel You get paid to write OSS?
@SamStrong @hbuchel Yes, of course. When maintaining patches for #SUSE all our patches and fixes should go upstream first. We have to participate in many upstream FLOSS projects (and I am an upstream for some, e.g., https://gitlab.com/m2crypto/m2crypto/).
m2crypto / m2crypto · GitLab

GitLab.com

GitLab
@hbuchel so much broken around OS.
@hbuchel in other words, they have the time ?

@hbuchel

The same mechanisms are used to trim entire groups out of leadership positions and other better paying gigs.

Women. POC. Immigrants. LGBTQ.

The ability to do unpaid overtime is easier for single young white men.

@hbuchel @chris yup. I contribute way less now that I do most of the childcare while my wife works evenings.
core-js/docs/2023-02-14-so-whats-next.md at master · zloirock/core-js

Standard Library. Contribute to zloirock/core-js development by creating an account on GitHub.

GitHub
@hbuchel those are very important insights, thanks for sharing.
@hbuchel none of this seems specific to open source. You're describing characteristics that allow people to have a hobby.

@hbuchel So much of hiking favours people that ~ have time ~ That usually means:

- They aren't caretakers (i.e, they don't have children or elder family that have care needs) or rely on a partner to do all of that in their stead while they're out in the mountains.
- They can hike long hours outside of their 9-5 jobs which excludes many Disabled people or those that have chronic pain.
- They already have a high paying job (can afford hiking gear), they have health insurance (if they get injured)

@nikclayton I love when people reply to a post and are intentionally obtuse.

@hbuchel nope. Your thread is predicated on the idea that an open source project maintainer owes anyone else anything.

They don't. https://www.softwaremaxims.com/blog/not-a-supplier covers this in some detail in a supply chain context, but it applies equally to e.g. PRs received.

Every time you have a PR accepted, or an issue you reported is fixed, the maintainer is going above and beyond their responsibilities to you. Too few people recognise and appreciate that.

I am not a supplier

For the past few years, we have seen a lot of discussions around the concept of the Software Supply Chain. These discussions started around the time of LeftPad and escalated with multiple incidents in the past few years. The problem of all the work in this domain is that it forgets a fundamental point.

Musings about software

@hbuchel UBI? Great idea, I'm a big fan.

But even if the maintainer of your favourite open source project receives UBI and never needs paid work again, they *still* don't owe you feedback on your PR or issue.

If they do provide that feedback they have chosen to do so, and they are free to make a different choice at any time.

Anything else and you're demanding unpaid labour from volunteers.

@hbuchel A glance through, e.g., my GH issue history will show that I generally make the choice to help and resolve issues wherever I can.

But the thing that makes that possible - and has prevented burnout for more than 30 years of open source contributions - is the sure knowledge that I am making an active choice to do this, it is not an obligation imposed by others, and a willingness to push back on entitled behaviour when I see it.

@hbuchel well yes. Of course. Only those that have surplus resources (time /energy/spoons/money) can effectively donate that time to OpenSource projects. Or grow any other structure worth growing for that matter.
@hbuchel this is an awfully good thread, thank you

@hbuchel

Same.

https://chaos.social/@onepict/112242171729685943

But I think it's good you ranted. More of us need to.

I just wish we didn't have to do it constantly.

We also can't participate in "Networking" at conferences because of cost, health etc. So many ways in which folks are excluded from any participation in FOSS.

Esther Payne 🏴󠁧󠁢󠁳󠁣󠁴󠁿 (@[email protected])

I have some thoughts about FOSS sustainability and burnout. If we want projects to be a part of the commons to encourage the commons to join in, they need to be able to afford to. TLDR: We need universal basic income. Our current systems can't cover everything. If we want to prevent maintainer burnout, we need better support structures. Which isn't going to happen with anymore Orgs set up specially. http://onepict.com/20240409-sustain.html

chaos.social

@hbuchel

they have health insuranceLaughs in European

@hbuchel Thank you for this good rant :). I think what you are articulating here is a good call for solidarity. Many of these problems extend past the disabled community as well which limits OS adoption and any potential freedom from tech monopolies.

@hbuchel @dabeaz

An alternate way to view this is as a voluntary tax paid by some of the temporarily privileged.

@hbuchel May I quote-post you? Regrettably, I have thoughts.
@kissane @hbuchel "Regrettably, I have thoughts" is a whole mood

@hbuchel although I don't disagree with you overall, I have severe chronic pain (due to fibromyalgia) and contribute a lot to open source software due to it rather than despite it

it made existence somewhat tolerable in the many years I spent without having any working treatment, and it was also basically the only thing I could do anyway, as anything more physical or requiring commuting or using public transit a lot was excluded, work or hobby

@hbuchel (my OSS work was also what allowed me to finally emigrate from a country that was falling apart, on comparatively incredibly good terms too, though this part did involve a much greater degree of luck on the whole)

@hbuchel Is this a rant about open source, or is it just a rant about economy/politics? Essentially: In your opinion, who is doing wrong here?

I don't think you can really berate either open source maintainers or contributors who are just doing as much as they can for the benefit of everybody...

@hbuchel This is one more problem that UBI would help solve, of course.
@hbuchel
- healthcare: it’s a done deal. Americans figured out a ok-ish healthcare system … but they only implemented it in Japan. It been 60 years, what are you waiting for the mainland
- (accessibility) features request: maintainers asking a well formed contribution is to limited the burden on them. I don’t think putting more pressure on maintainers will limit the burn out, in the contrary. Any code is tech debt they will need to maintain, not the contributor.