Drupal projects are moving their issues from Drupal.org to GitLab work items, and ContribKanban couldn't see them. I rebuilt it so that one board tracks both.

For the past three months, Richard Sheppard has been a financial contributor to ContribKanban on OpenCollective. I'm extremely grateful for his decision to put his money towards my project every month. $5 a month may not seem like much, but the impact is greater than its monetary value.

I wanted to take the time to write about an initiative taken by AmyJune Hineline. AmyJune is the Open Source Community Ambassador for Kanopi Studios. She has taken upon herself to work with Drupal camps and make sure they have a Contribution Day sponsor tiers and that a portion of that sponsorship goes to community tools. Through her work, SimplyTest.me and ContribKanban have received funding to ensure they have maintenance and feature development.

Every year I dedicate a block of time to provide new features and improve ContribKanban, beyond regular maintenance to keep dependencies up to date. This year brings some significant changes, which I am excited about!

It seems that I do a roughly annual update for ContribKanban and what I plan on doing with it. This year I evaluated its future and roadmap and how it can be more useful for the community at large.

At the end of October 2017, I wrote about the new and upcoming changes to ContribKanban.com. I decided to migrate off of a MEAN stack and go to a more familiar (aka manageable) stack. I decided upon Drupal 8 to manage my backend. Drupal is what I do, and Drupal is amazing at modeling data. People can moan and whine - it handles data models like a boss. I decided to treat it as a "progressively" decoupled web application.

Back in 2015, I created ContribKanban.com as a tool to experiment with AngularJS and also have a better tool to identify issues to sprint on at my previous employer before Commerce Guys. At the Global Sprint Weekend in Chicago, I received a lot of feedback from YesCT and also ended up open sourcing the project.

A recent project of mine has been ContribKanban.com for the Drupal community. The name speaks for itself - it provides a way for contributors to work on Drupal.org project issues queues through a kanban board. This app has two purposes: visualize the Drupal.org project issue queues in a useful fashion, and provide an experiment that tries to fully utilize Drupal.org APIs.