Great news: Contrib Kanban is back thanks to Matt Glaman.

As a result you can get an overview of every issue with a given tag again. For example, everything that is tagged with "rosetta" from the DrupalCon Rotterdam DriesNote.

I liked the idea, but the project could use some visual polish and a dash of fun!

So here it is: an improved UI and an issue roulette.

Spin it, take the issue that stops under the marker, and get to work. You get three re-rolls.

What do you think and what needs to be improved?

---

Some stuff is still in a Github PR but here are the links.

Website: https://contribkanban.com/
Github repo: https://github.com/mglaman/contribkanban.com

For years my workflow to solve a problem in Drupal was as follows.

First I try to find someone else who had the same problem and if there is a patch available. If there is a patch I use it. If the patch doesn’t apply, I fix it for the module version I’m using and publish the updated version. If I’m the first with that problem I report it and try to find a solution. If the solution is generic enough, I share it with the community so more people can build on top of it.

These days things have changed. We use Claude Code to fix the issues now and sometimes it ends up patching stuff in core or in contrib modules. When I suggest my coworkers share the result with the community they refuse. They can ask Claude to fix future issues so there is no need to share. But I also think they don’t understand the code and that is why they don’t want to share it.

So I wonder. If everyone starts doing the same, who is going to contribute to Drupal? Do you know if the contributions have decreased this year due to AI?