Listen

Listened to What's New in CHAOSS: Podcast Reboot Episode by CHAOSS Project 
Post details
In this episode, the CHAOSScast team is back! Georg Link, Dawn Foster, Sean Goggins, Matt Germonprez, and Elizabeth Barron discuss the relaunch of the podcast after taking a short break. They delve into the fascinating world of open source community health, focusing on metrics, metric models, and the CHAOSS Project’s role in measuring the health of open source communities. They share insights on how they’re working to make metrics more accessible and how they interpret these metrics within the context of specific projects. Additionally, they highlight the Data Science Initiative, the growth of CHAOSS community chapters worldwide, and their initiative to improve newcomer experience and promote diversity and inclusion in open source. Download this episode now to find out much more!

by Jamie Tanna's profile image Jamie Tanna .

 Repost

Reposted Liana :v_trans: :v_kirb: (@bubbline@tech.lgbt)
Post details
The whole bad space thing and blocking tech.lgbt from other instances is absolutely insane. Some of the instances involved haven't blocked mastodon.social (which is full of basically anything and tons of random abuse because it's so big), but are blocking tech.lgbt. As usual, queer people are hyper-scrutinised, and all it takes is one terminally online with an unhealthy obsession to find a way to frame an entire community as fundamentally evil based on some questionable disagreements. Don't use block lists. You really don't want your blocking decisions to be based on people who add things to a list on a whim with no accountability and oversight. But even outside of block lists... god when are progressive communities going to get over this obsession with performative punishment and branding people as bad? I've never seen this instance allow bad people to stay, moderators always take care of things, and they're usually pretty responsive. It's beyond absurd to block tech.lgbt

by Jamie Tanna's profile image Jamie Tanna .

 Repost

Reposted Matthias Ott (@matthiasott@mastodon.social)
Post details
Attached: 1 image I’m starting something new! 🤗🎉 Own Your Web is a newsletter for anyone who wants to design, build, create, and publish on the Web. Whether you want to get started with your own personal website or level up as a designer, developer, or independent creator working with the ever-changing material of the Web, this little email is for you. 💚✊ Sign up here: 👉 https://matthiasott.com/newsletter #OwnYourWeb #newsletter #web RT=❤️

by Jamie Tanna's profile image Jamie Tanna .

 Repost

Reposted Tim Perry (@pimterry@toot.cafe)
Post details
The Cypress.io situation is wild! https://currents.dev/posts/v13-blocking In short: when installing the Cypress npm package, on postinstall it checks what other packages you installed, and you're using any packages they don't like (e.g. tools for self-hosting that compete with their cloud service) then it refuses to run. More detailed summary from @jess@webtoo.ls here: https://twitter.com/_jessicasachs/status/1712043659330310488 Very hard to argue your product is good if you have to actively block your customers from even testing alternatives! Yikes.

by Jamie Tanna's profile image Jamie Tanna .

 Repost

Reposted linear cannon (@linear)
Post details
i have outright deleted a major patchset i wrote for a project under freedesktop.org stewardship, which someone else is probably going to write again in a year or two, because i realized the project had a real-name policy, and decided it wasn't worth it. i then lost motivation for the cool thing i was working on that needed me to write that patch this is not the intended effect of a "real-name" policy, but it is the actual effect. and, as the cool kids say, "the system is what it does". there is no such thing as a "real name". the concept of a "legal name" is fraught, and most certainly is not what you think it is, or what you are looking for, if you are a software developer. many assumptions you have about what a "legal name" is probably are not true. consider this: the name on my birth certificate is different than the name on my drivers license, and that is different from the names i am called by my friends. those names are all different from what is likely to be on my passport when i get it, and all of those are different than the name i publish my open source projects under. all of these, in different jurisdictions, might or might not be something you could consider a "legal name". which one do you want me to use when i submit a major feature to your library? are you going to turn me away if i try to submit it as "linear cannon"? why? if i have a website and contact information under that name, why does this matter? how is it substantially different than an author of fiction novels publishing under a pen name? does it change if i produce a piece of government-issued documentation with that name on it? why, or why not? if your real name policy does not answer these questions adequately, then there's a very good chance i'm just going to assume that you're going to turn me away, as has happened to me several times already RE: it would be nice if it were actually as easy to contribute to free/open source software as the developers and maintainers of such software claim it is but meritocracy is a lie, and bullshit policies and procedures (see: "real name" policy) scare away minorities who might otherwise do important work

by Jamie Tanna's profile image Jamie Tanna .