Having to justify obvious changes is just wrong in the open source world.
191 open issuesā¦ even bugs are being ignored!
https://github.com/kanboard/kanboard/security/policy
This is very discouraging!
Over the years Iāve become more and more puzzled by the core kanboard developers. They are not very transparent and they donāt seem to hesitate to make large changes without communicating with the people who use kanboard. They have twitter and mastodon accounts but have only ever posted about new releases for years. And now it looks like they neglect important changes like bug fixes and do not accept āfreeā additions such as your PR. Itās hard to understand their motivations.
Now and then I poke around looking for a roadmap, but Iāve not found one.
Forking an established project like this on github is fraught with peril, but perhaps itās worth considering.
2 Likes
It annoyed me that I have to justify back and forth the inclusion of the svg icon.
- I purposely kept the filename different, in case that would be an issue of āreplacing the fileā
- How obvious is it that Inkscape has added bloated code to the svg, which is bloated code, meaning it is not needed for the SVG to render, it is only used by Inkscape if the file is edited in Inkscape again.
- More importantly, look at all the core icons includedā¦ the svg is using a basic text font, like a cowboy. My svg version was an identical copy of the png versions so there i consistency.
- You say ācore kanboard developersāā¦ there is just one!
I wish I could fork it and maintain it, the numbers show how high the demand is, meaning how useful it is to people in the (mainly) professional world. Problem is, I am not a developer so I dont know much about databases and security related code etc. Without @creecros, my first plugin would never have been published.
3 Likes
Because itās in maintenance mode. Why the heck should this have a roadmap?
The main development is closed, period.
And you have keep in mind:
There is no fancy user interface, Kanboard focuses on simplicity and minimalism. The number of features is voluntarily limited.
But we all have the chance to write plugins for any desperately missing feature. No problem.
Personally, I have tried other Kanban-Board apps, but always came back to Kanboard.
1 Like
Agree, with both.
My only wish would be, that we could get more collaboration on plugins.
Iām glad I could help anyone and everyone I could with getting plugins built, but Iām no pro at this.
3 Likes
I wouldnāt be so hard on fred either. That guy is pretty much a 1 man show, he deserves a lot of good vibes.
3 Likes
Maintenance mode is reworded nowā¦ to be honest it should never have existed as releases after that have not always been ONLY bug fixes. And if they were, then Fred needs to address, fix or close the bugs reported since 2019/2020 in the repository. To state in the readme, that all bugs and security issues will be addressed once a month in a maintenance roadmap would be good at least. A roadmap doesnt have to be just for new features. Right now, Fred just picks and chooses, then ignores if he feels it shouldnt be included.
There is no fancy user interface, Kanboard focuses on simplicity and minimalism. The number of features is voluntarily limited.
- This is just a lazy text that Fred put for his own usage but when I software project has x00000 stars and comes up across other websites and people do reviews and tutorials on it, Fred needs to wake up and take some responsibility and acknowledge that his work is appreciated and popular. I mean some businesses, offices, professionals run their working life on Kanboard.
Plugins are VERY VERY hard because of VERY VERY poor documentation.
Personally, I have tried other Kanban-Board apps, but always came back to Kanboard.
- I feel the same, I want to leave but there is no other viable option. I personally think the core developer knows that and takes sad advantage of that!
1 Like
but there are x developers screaming to offer help through issues, posts, pluginsā¦ and Fred just wants to stay silent and not accept any help.
Its not about being hard, its about recognising that if you make a tool to deal with productivity, then the tool should be fully maintained and I dont think it is.
1 Like
That guy is pretty much a 1 man show
I am the same, yet I find the time to keep in touch with the Kanboard community.
1 Like
Be happy that you can, maybe he cannot.
1 Like
I can understand that, but that is exactly why Fred can build a team of collobarators to manage the repository.
by the way, I am not so happy that I find the time lol, I code out of depression.
1 Like
Kanboard is not really in maintenance mode. New automatic events have been added and adjusted in the last few releases. Experimental support for a new database backend was added. Support for new file formats has been added. All of these are new features, above and beyond maintenance, which is usually confined to bug fixes, dependency upgrades, and maybe cosmetic changes. Thereās some kind of plan behind which features are added and which are not.
All a roadmap would do is explain this, why some features are added when they are added, and why other features are not. Itās not a heavy lift. A one page bullet list would suffice. Itās not legally binding or anything, just a document that says āhere are my thoughts about whatās coming in Kanboard.ā
I get that if itās a one-man show maybe heās just tinkering with it when he feels like it and adding what he feels like adding. That makes sense. What doesnāt make sense is not accepting changes freely offered by others, or not accepting at least some amount of feedback (e.g., several people donāt like the new documentation, but he seems to be forging ahead with it anyway). Realistically itās not a one-man tinkererās project anymore; itās a project thatās fairly widely used, and at least according to some folks, best in breed. The one-man show mentality inhibits the project.
Here you got the point. Itās his baby, and he decides. Once I was in a similar situation.
Oh my! You are welcome to use mine! 
3 Likes
Oh wow thank you! Iāve been using the Internet Archive to get to the old version of the documentation site but this is much better!
2 Likes
Maybe you know that you can replace the location of the built-in docs in your config.php:
define('DOCUMENTATION_URL_PATTERN', 'https://abu.codeberg.page/kanboard-doc/');
3 Likes
omg why have you been hiding thisā¦ this is excellent, thanks!
1 Like
Itās of minor importanceā¦
Here you got the point. Itās his baby, and he decides. Once I was in a similar situation.
Realistically itās not a one-man tinkererās project anymore; itās a project thatās fairly widely used, and at least according to some folks, best in breed. The one-man show mentality inhibits the project.
- I agreed with this