(:e hash) @ehashman@toot.cat

cinnamon hearts are the best candy 💕​

damn, it is crocus season my dudes

*boosts harder*

Anyways this is a long-winded way of saying that I really wish I could spend more *time* on Python packaging, and the complexity and scope of the problems make it extremely challenging to make meaningful contributions nights and weekends. >_<

So not only do we get a tragedy of the commons in the wider ecosystem, we also get this happening at a micro-scale *within* companies that depend on the very same technologies. It seems to me it might be easier to meaningfully tackle the latter?

More than anything, I wish my employers, whose businesses depend on the FOSS tools I build in my spare time, would carve out 10 or 20% time so I can build this shit on the clock.

But "businesses are inefficient" and no one wants to own that in their org budget.

And so as a result, at least 40 hours of my week are dedicated to my dayjob, which relegates my FOSS contributions to the margins: evenings, weekends, vacation days, "own equipment, own time." Assuming I get IP signoff to work on it at all.

It's true that I do my dayjob for money! But I also do it so I have legal status to be resident in the US, and so I can have access to healthcare here. You can't buy either of those things with dollars alone.

"Money" and "time" are treated as sort of interchangeable when we talk about FOSS development, but that's only true at scale. At an individual level, my contributions are blocked on time, not money, because I have to have a dayjob.

Read https://motherboard.vice.com/en_us/article/43zak3/the-internet-was-built-on-the-free-labor-of-open-source-developers-is-that-sustainable which touches on some of my burnout, but I'm not really feeling it. Tired of this history of FOSS in which women are erased (I saw two quoted in this article, both non-devs).