> “This application is in maintenance mode.”
Source: https://github.com/kanboard/kanboard
I think there are better open-source kanban-style applications out there that are also actively maintained. For example:
> The author of this application is not actively developing any new major features (only small fixes) > New releases are published regularly depending on the contributions made by the community > Pull requests for new features and bug fixes are accepted as long as the guidelines are followed
So it's more that no new features will be added by the main dev however it is still maintained. Other software like this exists (Miniflux for example) and they work well.
A Project doesn't need a constant influx of new features to be useful or even maintained.
EDIT: Turns out it's made by the miniflux dev which I respect.
There is MIT license based fork at:
At some point, it wouldn't be a "kanban" board any more.
In PHP land, once you have the web server set up with the basics, this is just such a nice easy way to deploy software. I actually run Kanboard on the same server as my WordPress blog and installed it simply by throwing the files into a directory.
The most complex thing you might need to do is add a new database somewhere but I find it so much less overhead than Docker or most other things.
It's the red waving flag of this project. I cannot understand how people are still arguing for this kind of stuff or stick with this dinosaur language at all.
I am sorry but I have such an aversion against the attitude of "we use xy because of historic reasons but hey actually it is really good because the design pattern that has proven crucial over the last 50 years imo is just overhead and you can just put some files here and there copy a bit of that and... "
I used to work at a company that was heavy on php but had very good practices, and the php runtime was quite good.
I don't understand what your criticism is
I personally like mixing frontend and backend. I get why it's anathema to some, but there are simply tons of use cases where I think the simplicity it offers - being able to capture an entire page of functionality in a single file - outweighs the disadvantages because of the simplicity it offers.
For larger scale applications it's easy to make terrible mistakes leading to spaghetti code - I feel your pain about major crimes and have witnessed a few (and been responsible for some) myself. But this is possible in many languages if you're not using a framework, and modern PHP gives you way more tools to avoid it, even before you look at frameworks, which almost completely obviate the problem.