This is indeed a problem. Somehow it became much harder to attract younger developers.

Excellent post showing unhealthy consumer/maintainer dynamics in FOSS projects. This particular example was instrumental in getting the xz backdoor in place.

Lots of good advices of course. It goes a long way to improve the quality of the project and the ease to on-board people. This is quite some initial work though.

Indeed, time to leave Redis behind in favor of Redict. It's not like one can expect new things to come out to such a project.

Good reminder that contributions are not only about code. Documentation, support, release management and so on are very important as well and too often underrated.

This study does a good job looking at the impact of community smells over the presence of code smells. This is an excellent reminder that the organization influences greatly the produced code.

Despite understandable limitations, this studies has a few interesting findings on how communities can more easily switch platforms (in this case from Twitter to Mastodon). At least one is a bit counter-intuitive.

The fact that they felt the need to write such a letter is troubling. What's going on in the Python Software Foundation really? Something needs to be fixed it seems.

Very interesting study, shows how toxic comments impact contributions. Gives a good idea of the probability for people to leave. In the case of Wikipedia this highlights reasons which contribute to the lack of diversity in the contributors. This is a complex community issue in general, this studies does a good thing by shedding some light on the dynamics in the case of Wikipedia.

Interesting exploration of the Wikipedia community dynamics. This explains quite a few things on its evolution. It highlights how it became a beacon of sanity in the insane political landscape we're collectively facing.

Some people lash out at the wrong group... they should be angry at YouTube not at the tiny team making the extension trying to help block the ads.

Good exploration on how and why async Rust was designed. As usual it's not purely for technical reasons, there's a human and community factor to it.

This is a very important point. Communities should make sure that new blood gets in. Companies should also avoid just recruiting top talent and groom juniors to contribute.

Interesting, the situation for kernel maintainers is actually harder than I thought. You'd expect more of them could do the maintainer job on work time...

I'm not necessarily convinced this is as much a silver bullet as it is presented here. Still there are benefits to such a structured approach for reviews in community projects.

Facebook getting interested in the fediverse indeed looks like XMPP or OOXML all over again. Beware of those old tactics, they are very efficient against communities.

Happy birthday the KDE Free Qt Foundation! It's really nice to see it survived the test of time. It is for sure an essential tool of the KDE ecosystem. I wish there would be more such foundations around.

Interesting and provoking thought... Indeed it's hard to build communities while also aiming for rapid and constant growth. There's no chance of having communities properly stabilize which leads to the tribalism and bad behavior we see on social media.

Interesting post, highlights why it's better when languages are designed in a more community fashion (make sure to read until the conclusion). At least in term of popularity it seems to help.

Interesting set of challenges indeed. I think Rust is a bit at a crossroad now. The next few years will be crucial, either they will lead to further adoption or it will stagnate and slowly disappear.