I wouldn't say this is a detractor, based on the comment below what you quoted:

> 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.

In my opinion, the fact that it is feature complete and no big changes are expected is a strong point. It means if I put the time to learn this tool, it will not change on next update and get on my way.

You could technically use an IMAP server and client as a Kanban board. Make a folder per swim-lane, make a backlog, move e-mails from one folder to another as you get each item done, share the mailbox with your team. IMAP already supports searching, filters, flags, attachments. You can treat a thread of replies as comments on the original item and move them all as a group. Create a custom client to hide the fact that the backend store is basically an immutable log journal of MIME entries.

Planka https://github.com/plankanban/planka changed license from MIT to AGPLv3.

There is MIT license based fork at:

https://github.com/RARgames/4gaBoards

I don't think a kanban board really needs constant new features.

At some point, it wouldn't be a "kanban" board any more.

Installing in this case means copying files to your web server.

> Installing in this case means copying files to your web server.

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.

In Php Land I would say <?php $no $thanks ?>

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... "

Php is a fine language nowadays.

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 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 don't understand what your criticism is

My criticism is that php was designed to be a violation to mvc. The <?php> file header already a commitment to mixing front- and backend code (HTML + php in one file) inevitably leading to spaghetti code. The $annotation an inheritance from perl imo also a major distraction. also Laravel, other frameworks and newer php versions might try to tackle some of the historical tech debt embedded into the language but I personally don't see a point in revival of php altogether. I guess my point is to some degree subjectal and shaped by some major crimes I have stumbled upon when debugging. Even though the code in this repo looks fine, the mere use of php is reason enough for me to stay away from it altogether

I mean, you can do MVC in PHP if you want. I used perl long before I used PHP so the $annotation never bothered me.

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.

PHP is a nature stable language and running a PHP program is very simple and cheap

Please stop waving the flag!

Docker containers solved this for me. I can’t remember the last time I installed a web app.

Yes, if I really want the software I will build a Docker image, but still I would prefer not to deal how to config/run Parcel/Webpack/Babel/Esbuild/Grunt/Whatever.