The biggest issue in open source right now is the devaluing of the PR.
Everyone OSS project of note is drowning in AI committed PRs. A few add heavy processes; most ignore them.
The only way to get a PR merged is to know a maintainer. At recent conferences, when talking with maintainers, we're frequently interrupted by people asking them to look at their PR. That's what OSS contribution looks like today: finding people in person.
But people do it because landing a PR means something. It's how people enter the community. It's how people become maintainers. It's how people GET JOBS. (That's why we're drowning in automated PRs. Any public route to value will be deluged by agents.)
PRs were our engine. It's how people got cred. It's how the community distilled knowledge and discussion into artifacts. PRs were the engine for OSS.
So how do new programmers get a foothold, now that the PR is gone? How do we incentivize people to participate and build knowledge with us?
@dotpem@nateberkopec I have tried it with 6 concurrent ds41-flash ablated, and let me tell you, they are persistent. Used a VM with pi-durable with a tiny coordinator around it.