You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The chronic problem with Kanboard is that while it supports a variety of features in the form of plugins, as the main Kanboard complies with the latest HTML and JavaScript standards, plugin developers are departing, and the plugins dependent on those abandoned also get discarded routinely. I believe plugins should operate as a testing ground for users, and all functionalities of the plugins should be merged into the main code. Everyone in the community points out this issue, but no one has been able to provide a solution. Since we follow the MIT license, even if the main branch does not accept it, we will continuously make pull requests with an integrated branch of useful plugins. If this proposal is not accepted, we will fork Kanboard and create a new project in the direction we envision. I am seeking the opinions of the main developers.
The text was updated successfully, but these errors were encountered:
Due to the discontinuation of Trello, we have adopted Kanboard as our internal management tool. To avoid the common situation where suggestions are made but not shared, we plan to release our modified version of Kanboard in a new repository. This is scheduled for November. We have already made extensive customizations and believe it is sufficiently usable in its current state.
As a development company, this decision might raise ethical concerns, but it is disheartening to see plugins that have been abandoned for nearly a decade or are functionally inadequate still in use. We feel that the original creators are gradually being forgotten, which is not respectful to them. Therefore, we seek the opinions of fellow developers on this matter.
If the feedback is negative, we will use this project exclusively for our internal purposes. This decision stems from our deep respect for those who have led this significant project so far.
Currently, no one is actively stepping up to improve Kanboard. We aim to remove the plugin concept entirely and create a standalone version of Kanboard.
We hope you understand that this is an unavoidable choice.
The basic features of Kanboard are very robust, and with just a few more tweaks, it has the potential to become a killer open-source tool that could completely surpass Trello.
The chronic problem with Kanboard is that while it supports a variety of features in the form of plugins, as the main Kanboard complies with the latest HTML and JavaScript standards, plugin developers are departing, and the plugins dependent on those abandoned also get discarded routinely. I believe plugins should operate as a testing ground for users, and all functionalities of the plugins should be merged into the main code. Everyone in the community points out this issue, but no one has been able to provide a solution. Since we follow the MIT license, even if the main branch does not accept it, we will continuously make pull requests with an integrated branch of useful plugins. If this proposal is not accepted, we will fork Kanboard and create a new project in the direction we envision. I am seeking the opinions of the main developers.
The text was updated successfully, but these errors were encountered: