Notices by Kat Marchán 🐈 (zkat@toot.cat)

Thinking about @LicenseZero's cross-license collaboratives/collectives: https://xlcollaborative.com/

tl;dr: a manageable way to license software across contributors while doing stuff you usually use companies or foundations for, like long-term project survival, relicensing, etc

It's time we stop fussing about source code.

It's time to start fussing about the incredible range of humans that have always made it possible.

Shout out to every woman who's had to make a post about "you guys" language. Every ESL speaker who has had to launch their own localization effort. Every disabled person who's had to remind maintainers about a11y. Every Black person who's had to deal with "master/slave" language

Shout out to every meetup and conference organizer. Every collaborator who jumps into issue trackers and constantly answers questions. Every docs writer. Every person crafting and scaling project processes. Every person who QAs (pre-!)releases as they go out.

A friend suggested today that it's time for a manifesto and I agree. Another friend in another conversation mentioned that "free software" and "open source" are not relevant terms for what we need. I also agree.

It's time for something new. A new, community-centered ecosystem.

I'm increasingly of the opinion that the way forward for us is to build a dual-purpose Commons: one where our communities can freely partake and share and collaborate and learn and build each other up, while those who seek to profit on their own terms put cold hard cash down.

Dear FOSS maintainers who have experienced issues with sustainability for your projects: What would help you more when it comes to successfully executing your projects?

Thinking a lot lately about how the whole "quit and you'll get more money" thing in the Bay Area tech industry just perpetuates all the abuse that unions could protect us from.

It me-ish!

Founders jumping ship is a great sign and definitely means a startup is succeeding, right? https://www.businessinsider.com/npm-cofounder-laurie-voss-resigns-2019-6

Are you interested in distributed/federated systems? @isntitvacant@twitter.com just posted his idea for the algorithm to sync between different #entropic instances. Join the conversation! https://discourse.entropic.dev/t/entropic-entropic-syncing/244

My newest @github@twitter.com sponsors update just went out, with juicy details about my new job, my plans for open source work, and other details! Missed it? Sign up now to get them in the future or get access to the exclusive archive + discussion repo! https://github.com/users/zkat/sponsorship

So.... you can sponsor me on GitHub now. Check out my sponsorship page! https://github.com/users/zkat/sponsorship

Looking for something that you wish were there in the tiers list, but can't find it? Let's talk! I'm still working those tiers out and I haven't done something like this before!

I desperately want/need a port of http://npm.im/standard-version for Cargo. After all the work I put into my Node-land release stuff, doing a manual `cargo publish` is such a pain. And I know about the `cargo-release` crate. It doesn't do what I want it to do. Most notably, changelogs.

Stuff the @npmjs@twitter.com CLI team is working on this week:
* A shiny new `npm link` command (and other goodies)
* Overrides support

Stuff we're working on once that's done:
* Workspaces (!!!)
* Other goodies for the npm@7 release.

This had its own effect on the lesbian communities, too -- they're the ones that survived; the ones who took care of the dying and watched them go.

They're the ones who tell us the men's stories.

The solidarity and love I've seen them express is incredible and humbling.
---
This information shook me to my core. We are missing an entire generation in the gay community.
https://twitter.com/anthonygonnn/status/1044620714794352641