i actually used kanboard once in my life, and immediately was like, this is great and exactly what i need, but i need it to do “These” things, which I felt at the time would be what anyone else would say, so I capitalized off that need.
1.) Send me an email a due date is coming up, like why doesn’t it do this.
2.) I can’t assign this task to a group of people? WTF?
3.) My boss saying, can you print these tasks out? This is important for people who exist in the physical realm and need a job bag to connect to a task. These people exist, trust me.
4.) I wish we could have a custom field, to track such and such.
So those were the first ones I tackled. and I pretty much did all 4 of those around the same time. I would even say Group_assign was probably my first, but I didn’t understand a plugin at the time, so I had code that I just wrote over the core, but by learning the others, I was able to get Group_assign into a working plugin. Which is confusing, tbh, because there was quite the demand for that one, many github topics on “OMG we need group assignments” and many conversations and I think even PR’s people tried but Fred was not having it. So I was like, boom, here is the solution for it, here is the plugin, and all those conversations died, and now it is just a thing. But putting that, into a plugin, and making that shit work, man, that was a challenge, especially from someone like me who had no idea wtf i was doing, and its about as fully intergrated as you can make it, seamless with API now, notifications, actions, calendar, like a monster. Never really thought it got the credit it was due, like Customizer, meh, thats nothing in comparison to Group_assign. And there was NO community at that time, no one to ask questions. Fred never responded to any question I asked on Github. and there were no forums. aand there weren’t many plugins around that time either, or at least nothing complicated by any means to use as reference.
