ContribKanban is a project I started in January of 2015 to provide Kanban boards for Drupal.org project issue queues. It started out as a MEAN - Mongo (Parse.com), Express, Angular, and Node application and then morphed into a progressively decoupled Drupal 8 application. The source code can be found on Github: https://github.com/mglaman/contribkanban.com
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.
Following up on my post announcing updates for ContribKanban, I wanted to take the time to write about an initiative taken by AmyJune Hineline
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.
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.