mirror of
https://github.com/plankanban/planka.git
synced 2026-02-25 11:21:03 +03:00
Roadmap and next version announcement #433
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @meltyshev on GitHub (Mar 15, 2024).
Dear community members,
During the last few months, we have seen noticeable users joining the PLANKA community. We feel honored about all this, and our dedication to making PLANKA a complete and battle-tested platform is greater than ever.
For many months, we have already been working on the next generation of PLANKA. The next version of PLANKA is getting bolder and much more powerful.
It will pack many new features, and below, we have assembled a roadmap of things that are already mostly battle-proof. Others are still being implemented and improved. And some things are left out intentionally because we have yet to decide whether they will make it into v2.
At this moment, several people are dedicating a big part of their lives to this. At the same time, we are trying to maintain and push forward the current version in the best way we can.
Here's a quick Roadmap for the upcoming version:
We want to make sure to deliver something awesome.
Without our community, this would never have been possible.
Thank you all so much for your support 🙏
@alixleger commented on GitHub (Mar 19, 2024):
Hello @meltyshev, this v2 sounds awesome !
Can you give us any indication of a possible release date? Are you planning an alpha and/or beta so that we can test and contribute too ?
Thanks for your work !
@nickbe commented on GitHub (Mar 19, 2024):
Only thing I can say is it's still some months away.
We haven't decided about things like beta stage releases yet. But right now we tend to relase a fully working release version, since the V2 dev version is already being tested on a daily basis and beyond.
Best thing we can say right now is simply.... stay tuned
@DeAlexPesh commented on GitHub (Mar 20, 2024):
Maybe create beta's branch)?
@Mattzi commented on GitHub (Mar 26, 2024):
Unfortunately the publicly accessible boards by link are a must-have for us to switch over from trello.
Any chance that dev progress on V2 will be available soon on a beta or alpha branch or anything in that direction?
We are currently struggling to find an alternative until the trello deadline that works for us
@nickbe commented on GitHub (Mar 26, 2024):
Public board are on our roadmap but not fully implemented yet.
We are planning a release as fast as we can but currently there's simply too much workload to be able to tell an exact date.
Stay tuned.
@mattboll commented on GitHub (Apr 4, 2024):
Thank you for sharing this kind of information
It would be awesome to link issues if they exist to this one, so that we can follow any progress and maybe help for some issues
@JordanPicton commented on GitHub (Apr 5, 2024):
I didn't even notice this post about a v2, sounds interesting. Though I do want to ask about how many people there are in regards to the project that are actively developing? I know this is a passion project and ultimately open source but I'm just curious. :)
@nickbe commented on GitHub (Apr 5, 2024):
In the background this is a team effort of different companies now. Once we go public with the new version it will become quite obvious that this project has gone from passion to purpose for us. Simply stay tuned and thank you so much for all the interest in Planka.
@mattboll commented on GitHub (Apr 5, 2024):
Hi! I noticed that there hasn't been much activity on the repo in the past 6 months, apart from a few translations. I'm curious about why the "v2" isn't public yet—is there something you're keeping under wraps? I want to contribute and improve the project, but if it's being worked on secretly and the same tasks are being duplicated, I'm concerned about potentially working in vain.
@JordanPicton commented on GitHub (Apr 7, 2024):
I honestly can't wait to see what has been accomplished, Plankanban is one of the many things I rely on to keep track of what I'm doing etc. Trello is nice and all but it's got a lot of bloat to it.
@ADeeeee commented on GitHub (Apr 8, 2024):
Okay, it seems like another repo is in process of v2 which is kind of unexpected. I hope the migration from v1 to v2 is smooth enough while my Trello board is going to be read only after 20th May and I need to migration to planka before the deadline.
@brzlvch commented on GitHub (Apr 9, 2024):
Hello!
I want to say thank you for the product, it is very cool!
We moved to it from Trello, but we really miss push notifications and search by boards/tasks
Are there any deadlines for implementation?
Thanks!
@Yehuda-Bergstein commented on GitHub (Apr 12, 2024):
Thanks! the best Kanban board around :-)
@filcuk commented on GitHub (Apr 19, 2024):
That made me chuckle, considering v1 already feels snappier than anything I've tried. Can't wait for v2.
One major feature preventing me from switching over (from Vikunja) is seeing tasks/cards from across multiple projects in one view.
For example, I would like to see what's assigned to me, what's due, or a specific tag regardless of where the card is.
Is that by any chance something planned or considered for v2?
@janmashat commented on GitHub (Apr 24, 2024):
Isn't this "hidden v2" causing a lot of duplicate work? Why not push it (to a separate branch) so that the community can collaborate on it?
@nickbe commented on GitHub (Apr 24, 2024):
v2 will be released when it's done. We would have no spare time to answer any questions or maintain pull request and a clean codebase and are occupied with managing the current open source version while integrating some of the current community wishes in v2 as well "on the fly" while we speak.
v2 is still some time away and will be a full fletched and already battle tested product available to the community. From there on people are welcome to migrate and join development.
@shashinma commented on GitHub (May 22, 2024):
@meltyshev, thanks a lot for developing this project and for listening to the users ❤️.
I hope we can make this project even more functional!
@dmltdev commented on GitHub (May 28, 2024):
@meltyshev Thanks a ton for developing this project, it helped our team a lot. Do you have an estimate when v2 is expected to be done?
@sev- commented on GitHub (May 29, 2024):
We switched to Planka after Trello went through enshittification.
This software is an absolute marvel, even with the current restrictions. We are using it internally for the ScummVM project.
Looking forward to the v2. And if you need alpha-testers, we can help.
@meltyshev commented on GitHub (Jun 1, 2024):
Hi! We don't have any estimated date as our resources are very limited and we don't want to promise and then constantly move the date. But we'll be sure to let everyone know as soon as we realise we're getting close. Also, we might consider adding some of the planned features after the release.
@chris-NR commented on GitHub (Jun 9, 2024):
Hi @meltyshev
I (along with many others!) are now looking for a solution following the 'pivot' of the Jetbrains space product (see here).
I am looking for a solution for Agile Software/Product development for small teams (say 1-10 people per product team). I need to be able to represent a hierarchy of product planning items such as this:
Epic -> Feature -> Task where Tasks are assigned from a backlog to Sprints for development.
I evaluated Planka a while ago and found it to be a fantastic alternative to Trello and looked at using Labels/Boards for this purpose. I have a few suggestions and wonder if these are something you might consider for v2?
@Smiley3112 commented on GitHub (Jun 13, 2024):
Please can I request user tagging (in descriptions and comments)? When a user is tagged, that user should be subscribed to the card for notifications.
Sorry if this is already on the list!
@meltyshev commented on GitHub (Jun 14, 2024):
Thanks for your suggestions! Unfortunately we can't do other tasks in parallel as we don't have resources for that and we'd like to finish the basic stuff first as soon as possible and make a release. But after the release we'll definitely think about the next steps and consider your suggestions.
We've already been asked about the possibility to create a link between tasks and cards, to turn tasks into cards, we found it very interesting. Also, a lot of people ask about the ability to tag users in descriptions and comments - already in the list of next ideas for implementation.
@CodeNamedRobin commented on GitHub (Jul 24, 2024):
Hi @meltyshev, do you have any indication on when the v2 will be made public? Considering right now v1 is still in active development by the community, it would be a hassle if we would need to rewrite any new features we add right now for v2.
@meltyshev commented on GitHub (Jul 24, 2024):
Hi! We record all the added changes and will make sure to transfer them to v2 before its release, so it shouldn't be the case that the second version will be missing something from the first version.
@hwelch-fle commented on GitHub (Aug 29, 2024):
Just want to jump in and say you guys have done a great job. We have about 25 people using Planka every day to manage projects and it's now a household name in our company.
Really excited for v2 as basically everything you've listed in the roadmap is something that has been brought up in our daily use (for almost 2 years now!).
@BowenDraco commented on GitHub (Sep 2, 2024):
Hi together, @meltyshev Thank you and your team for all the hard work on planka.
I'm using it in my little computer store to manage the costumer orders.
It works like a charm :-)
In the Roadmap you wrote :"Much improved attachment handling" - does that mean that we can upload more then one attachment at once in the future?
I have a costumer, who would like to use planka, for his company too, but they need to upload multiple files in one go.
thank you in advanced, and I'm looking forward for the next planka version.
best regards
Marc
@meltyshev commented on GitHub (Sep 4, 2024):
We're referring to adding other types of attachments, such as links, as well as additional options for viewing content - for example, opening text files directly so that you don't always have to download them. But your suggestion sounds great and it's not that hard to add, so we'll try to implement that.
@BowenDraco commented on GitHub (Sep 4, 2024):
That sounds great, I'm looking forward for a new release then. And I use Planka for my company too.
@Sirwinnybob commented on GitHub (Sep 12, 2024):
Will there be a way to archive whole projects?
@vpopescu commented on GitHub (Sep 13, 2024):
Are we still looking at "months away"?
@meltyshev commented on GitHub (Sep 14, 2024):
We’ve added the option to hide projects, and on the home screen you can toggle the display of hidden projects :)
@hwelch-fle commented on GitHub (Sep 17, 2024):
Would like to pose an API question here, I'm currently maintaining the plankapy Python module (still a work in progress) and was wondering if the new version will maintain the old API endpoints or switch to something else.
Will likely branch the project if the API is changing. Also don't know how quickly I'll be able to update it if it is (I'll do my best) so if that's the case it should probably be removed from the docs and resources until I can get it updated.
@meltyshev commented on GitHub (Sep 18, 2024):
Hi! Thanks for maintaining plankapy and thanks for the question.
The API will remain the same, with only new endpoints and fields being added. There are a few minor changes to some endpoints, but they are minimal (it's hard to even remember which ones).
Instead of removing the link from the docs, we could simply mention that plankapy for v2 is in progress and there's no need to rush :)
@lifeinchords commented on GitHub (Sep 20, 2024):
could an enhanced search/chat be implemented as an optional plugin or extension? It would run locally, trained on the json data maybe? Lots of new possibilities, maybe something like
https://github.com/instructlab/instructlab
https://github.com/danswer-ai/danswer?tab=License-1-ov-file#readme
or some sort of integration with OpenAI CGPT, Anthropic Claude, Google Gemini, etc.. via a "bring your own API key" set up
@hwelch-fle commented on GitHub (Sep 22, 2024):
That kinda goes against the whole concept of planka being a lightweight kanban board. No need to shoehorn LLMs into everything.
@vpopescu commented on GitHub (Sep 23, 2024):
Just adding my wish list, since I'm also in search of a product to meet my needs.
I feel like my wishes mostly revolve around being able to see all my board details at a glance, without having to repeatedly open each card, or expand tasks.
@hwelch-fle commented on GitHub (Sep 24, 2024):
Most of these are already in the current release. The description is hidden, but tasks are in the dropdown and tag filters have been implemented for years. As well as due dates.
The only thing that isn't available is seeing all that outside the board, but in most of my use cases (don't know about yours) viewing the board is necessary.
If you do want to try and get some of this, you can use either the Python or PHP APIs available. Just use those to pull the data you need for a board and send out an email or update a spreadsheet somewhere.
Other than that the main usefulness of planka is incredibly fast Kanban for teams. We do 100+ updates to ours and hour and it has never failed. Something that if we didn't have would absolutely kill our productivity.
Think of it as a real-time tracker for intent and then implement your other needs on top of that. Having a more verbose API would help, but even the simple one that exists now is good enough for most instances and if you host the database yourself you can just poll it occasionally to gather metrics.
@vpopescu commented on GitHub (Sep 24, 2024):
I think either I'm confused, or you misunderstood my point:
Tasks are collapsed, which makes them out of sight. If you know how to autoexpand them, please let me know.. I'd like them to stay always expanded. Also, I don't think you can check them off without opening the card editor.
And I was asking about filtering/sorting by priority, not tags. Yes you can use tags for priority, but it becomes hard visually, as the board grows.
How do you see items due this week?
I just think it'd be nice to have a view of immediate actions, if your board is too big. Like, out of my entire board, what is due today, and what is due this week, in a list.
I'd love to be proven wrong and find out i missed something out of my wish list! I realize I'm not the only user, and maybe I'm asking for things other people don't see useful.
@hwelch-fle commented on GitHub (Sep 25, 2024):
I think there was a bit of a misunderstanding. I've always treated priorities like tags so didn't get that you meant an entirely separate system for priority.
Having card interactions on the card itself would be interesting, but when you have dozens of users dealing with dozens of cards I can see misclicks from that view causing issue. Maybe reserve that overview for the admin panel?
That's definitely something I've run into when I've had to deal with 20+ tags on a board that has a lot of changing requirements. Having a priority queue would definitely alleviate that (I'm now in agreement with you on having a separate non-arbitrary flagging system lol).
I might be mistaken, but I think one of the recent updates pushed a list sort context option. I don't use due dates that often so I haven't had to filter by them, but if they aren't in that context option that would be a good addition.
This is something Planka doesn't have anything for right now that's for sure, but I've used other tools to get that information.
We use Metabase to directly watch the Planka boards and have dashboards that update when the Planka database updates. You can also pull the date field to get timeseries data and do fun BInsryff with that solution.
Having it directly in some management panel or overview panel would be nice though.
I did definitely come off a bit aggressively, you can do most of those things in some way currently, but they aren't necessarily as accessible as they would be in other larger systems.
@jpjoux commented on GitHub (Oct 23, 2024):
Hello planka team
Any news concerning a date of v2 or a v2 beta for providing first feedbacks prior a RC?
@drakmail commented on GitHub (Nov 13, 2024):
Any plans for short internal card ids to refer to them in a source code commits?
@meltyshev commented on GitHub (Nov 15, 2024):
Hey! Sorry for the late reply. We're planning to release v2 at the beginning of next year. We've nearly completed all the planned features except public boards, which we can likely add after the release. Additionally, we've also added some other unplanned stuff, so things have been delayed a bit. Please keep in mind that we'll also need some time to migrate all the changes from the current version to the new version.
We don't plan to introduce any new features specifically for v2 at this stage, as that could further delay the release. However, feel free to open a feature request for that :)
@JordanPicton commented on GitHub (Nov 15, 2024):
Sorry to steal your time again. But with transitioning from v1 to v2, is this going to be an easy smooth process or is it going to take some tackling?
I'm currently running mine from a Raspberry Pi within Docker and I'm honestly not the best when it comes to figuring this stuff out. I'm still learning but is it going to be easy or straight forward to update within this case?
@meltyshev commented on GitHub (Nov 15, 2024):
Of course, we'll try to provide a script for a smooth migration and include relevant information in the docs. However, if we happen to forget, the community will likely come up with plenty of script suggestions, so that shouldn't be an issue.
@zmweske commented on GitHub (Nov 16, 2024):
Depending on export/import functionality, that may be the best move- a one-time manual export from v1 and subsequent import into v2. Either way, super pumped for the release! If you need help testing, let us know!
@schihei commented on GitHub (Dec 6, 2024):
Dear all, we currently need a public board, and I wonder if there is an estimate of when version 2 will be released.
@almereyda commented on GitHub (Dec 9, 2024):
After reading the conversation above, I have found this statement from @meltyshev in https://github.com/plankanban/planka/issues/627#issuecomment-2477474899 four comment above yours, in case you missed it:
@JustSamuel commented on GitHub (Dec 12, 2024):
@meltyshev small questions as a contributor. The new functions sounds great, and maybe I'm just a bit cynical, but are there any plans for putting features behind a paywall? Overleaf / Sharelatex used to be open source, and now you have to pay up for anything actually interesting.
@JordanPicton commented on GitHub (Dec 12, 2024):
I believe they talked about having an optional paid version some where, it's either further up in this post or on another post.
@nickbe commented on GitHub (Dec 13, 2024):
Thanks for the question Jordan!
First of all, currently we are thinking about the community and how we can support it as best as we can while at the same time deciding how to deal with the growing number of corporate requests.
All we can say right now is that the community version v2 will continue to evolve here on Github and start with exiting new features not seen so far in v1 and that, at the same time, there will definetely be an enterprise version which is also urgently needed to satisfy the needs of our corporate clients.
As of now, we have not yet decided about the exact license and configuration of the versions that will be available. Once we've finished with all the legal matters and the few remaining features that still needs to get fully implemented for v2 this is also the moment of release for us.
Our major goals for v2 right now are:
@JustSamuel commented on GitHub (Dec 13, 2024):
@nickbe, your comment, combined with the unusual secrecy surrounding v2 (e.g., the absence of a public roadmap), does little to easy my concerns.
To be specific, I’d be more than willing to implement API keys. However, as it stands, there’s virtually nothing preventing you from taking the feature and making it enterprise-exclusive.
You state that “We need to make sure that the community version continues to thrive and prosper.” But how do you plan to achieve this? A thriving and prospering community begins with clear and transparent communication.
What will happen to community contributions, and what will your policy be regarding enterprise-only features?
@JordanPicton commented on GitHub (Dec 13, 2024):
It wasn't me asking about the corporate stuff, I just remember seeing people talk about it somewhere around here haha.
Though I do actually have my own input. Depending on how the corporate license works I would be interested in the additional features that this may include.
Though I can also see this version being something that the team deploys for those who are wanting this license maybe?
There's a few things that could be done. However, if this license is setup in the way of monthly/yearly payments then I would personally stay clear. Though a one off would be something I would consider even as an individual, mainly to support yourselves but also to just keep the project going really.
@nickbe commented on GitHub (Dec 14, 2024):
There's nothing unusual here. I simply refused to publish v2 until all new core features are completely implemented, fully tested and operational and the enterprise options are clear. I loath any kind of software that is buggy, unfinished and not battletested. Releasing v2 for me means using being able to fully use its potential.
And believe me, we are working our asses off toward the initial v2 release and time is short. But we know from a lifetime of experience that you can pull and pinch a plant as long as you like, but this will not make it grow any faster.
Every pull request that we accept for the community version (v1 and all later versions) will automatically become integral part of that community version. At this time we actively working on the details around the enterprise version.
Also if you consider the years of work we've put into Planka then I think most people will understand how serious you have to take funding and organisation to do it. Therefore we need to find a good way to do both - a good community version to which everyone can contribute and also how to earn money with it.
I cannot answer any details about the enterprise features yet because that would mean discussing things that we ourselves are currently discussing with the team, with interested corporate clients, lawyers and consultants. This as well is "work in progress". Once we've figured out how to do it right, we will communicate as open as possible to everyone.
And of course we are more than happy to listen to all your business suggestions.
@jlucki commented on GitHub (Jan 18, 2025):
Only just discovered Planka today, it looks wonderful, thanks for all the hard work you're putting into this!
Is linking cards together/card relationships part of the roadmap? I'm not sure if it falls under maybe one of the existing items, or if it's not planned at all right now? https://github.com/plankanban/planka/issues/622 This issue explains it well. Would be great to have at least a very basic relationships working so you can make some cards tasks of other cards.
@descensus commented on GitHub (Jan 28, 2025):
Looking for this as well. Found no alternative to planka that supports it. Vikunja has this inside the card view, but it really doesn’t do anything.
@el1s7 commented on GitHub (Jan 30, 2025):
This is a cool project, I was looking forwarding to seeing the new version, but I guess the authors are very busy consulting with the lawyers and consultants about the features of an open source project.
@JordanPicton commented on GitHub (Jan 30, 2025):
They said early this year I believe and with that it's not the end of January yet. It'll come though.
@meltyshev commented on GitHub (Feb 14, 2025):
Hey everyone!
A quick update from us: we're in the process of migrating existing features from v1 to v2, and once that's done, we'll finally release it. This will take approximately 2-4 weeks.
License Update
For v2, we've decided to adopt a Sustainable Use License. Nothing will change for regular users, including those using Planka only within their business. In fact, this license even carries fewer risks for some users than AGPL since it doesn't require you to open-source your modifications.
The main restriction is that you can't sell the code (or derivative works) or offer it as a paid service unless you sign an agreement with us. We will provide detailed usage examples later for convenience.
Why This Change?
New Features in v2
Here’s what we’ve added so far:
User Management
Projects & Home Page
Boards & Cards
Improved UX/UI & Navigation
Other Enhancements
And a lot of other small fixes...
Pro Version
In addition, we plan to offer a Pro version for companies with extra features. However, we will announce more details once it's ready.
To clarify, none of the Pro features will be taken from the current v1 version. Everything added via PR is already in the process of being transferred to v2 and will remain publicly available.
@John-Gear commented on GitHub (Feb 14, 2025):
@meltyshev this is unbelievably cool! The list of changes is impressive! Thank you very much for the work you have done. We are looking forward to the v2 release 🫡
@hwelch-fle commented on GitHub (Feb 17, 2025):
Hey @meltyshev ,the new features all look great, I was wondering if it would be possible for you to share the updated REST endpoints for the added features. Or at least share the changes to the REST API as it stands, I'd like to try and get ahead of the changes on
plankapyso it works out of the box when v2 drops. If not I understand and will allow the updated to lag behind the release@madduck commented on GitHub (Feb 17, 2025):
LOVE IT
@JustSamuel commented on GitHub (Feb 17, 2025):
+1 for GEWIS/planka-client
@timshannon commented on GitHub (Feb 19, 2025):
I'm disappointed in the license change. The only reason I started using Planka was because it was open source.
@chmac commented on GitHub (Feb 19, 2025):
I agree. I also find the development in secret super sketchy. Combined with the constant delays, promise of new features, requests to "stay tuned", etc. This is definitely not what I think of as an open source project. I will start looking for alternatives.
@jlucki commented on GitHub (Feb 19, 2025):
I thought v2 would still be open source once released. Hence the license prohibiting selling derivative works. Can this be clarified? Having v2 be closed source would definitely be disappointing.
I am curious, if it continues to be open source, what happens if the community would like to implement one of the "pro" version features to the open source version? It seems like this could open up a conflict of interest for the maintainers.
@mattboll commented on GitHub (Feb 19, 2025):
Hello,
In the first post, meltyshev mentioned "The next Open Source version of PLANKA," but to be clear, a Sustainable Use License is not open source, as defined by the Open Source Initiative ( https://opensource.org/osd ).
Contributing now essentially means working for free for a company.
Of course, you are free to make any decision you want, but I find this quite disappointing.
@FM-96 commented on GitHub (Feb 19, 2025):
I'm kind of confused how that license change is supposed to work. Aren't all the community contributions licensed under the current AGPL license?
So how can they migrate the existing PRs into v2, but then also change the license? Isn't that a violation of the contributions' licenses?
One of the main reasons for using a copyleft license in the first place is so that people can't do exactly this, isn't it? What am I missing here?
@janmashat commented on GitHub (Feb 20, 2025):
How I see, the license can be changed for any contribution that is covered by the CLA:
I give Planka permission to license my contributions on any terms they like. I am giving them this license in order to make it possible for them to accept my contributions into their project.@meltyshev commented on GitHub (Feb 21, 2025):
Guys, I understand your disappointment, but I’ve felt the same way for over a year because that’s just how the world works — if you’re doing something for free, people will try to take advantage of it. Since I dedicate 10+ hours every day to Planka — answering questions, fixing bugs, reviewing/refactoring pull requests, and working on v2 at the same time, I at least want to be able to pay the bills.
How would you feel if companies were already making a profit by hosting Planka while you received nothing (aside from ~30 euros a month in donations ❤️)? They don’t have to fix bugs, add features, or do any real development — just host it, while I’m expected to handle everything else for free. No, thank you. That’s why we started exploring different licensing options and found that many others have faced the same problem.
I’m truly grateful to everyone who has contributed. I completely understand that for them, this license change might feel like a bad decision on our part. But to be honest, I’ve reached a point of frustration where I’d be fine with fewer contributions or even if the project were archived altogether. At least then, I’d finally have more time for myself.
I also want to clarify that the license change doesn't apply to previous commits. You are still free to use the AGPL-licensed code, fork it, maintain it, add new features — nothing is being restricted in that regard.
It won’t be closed-source either — the source code will still be available, and you’re free to modify it. Regarding derivative works, if you modify the code significantly by adding or removing features, the same license still applies, meaning you can’t simply sell the modified code for profit. The same applies to embedding Planka into another app.
I'm the sole maintainer, so there shouldn’t be any conflicts. Moreover, many Pro features won’t be easy to implement, so I doubt anyone would submit a PR with something similar. But in any case, our feature separation is just an estimate, and from time to time, we’ll likely merge some features into the non-Pro version.
Yes, you’re right — that statement is no longer valid and should be crossed out. However, at the time of the announcement we had no plans to change the license.
I feel the same right now that I work for free for other companies. For example, for me it would be even better to be able to make a contract with a contributor and pay for a work, but in the current state I can't even pay myself.
Is this a joke? I have ZERO obligation to you, so I’d be very happy if you find an alternative.
@meltyshev commented on GitHub (Feb 21, 2025):
Hey! Sorry for the late reply, had some health issues. I'll try to get this done over the weekend.
@hwelch-fle commented on GitHub (Feb 21, 2025):
No worries! I understand your frustration. Especially with the use of your hard work in other companies for profit products (if they aren't going to contribute dev time they should at least pay you!).
We use Planka internally and self hosted, I'm not much of a javscript developer, but I'm good with Python so I hope my plankapy contribution is enough of a value add that it gets some people to pay you. I'd be glad to make sure it works on v2 (even with the pro features) if that will help you gain back some sanity.
@John-Gear commented on GitHub (Feb 21, 2025):
@meltyshev I am personally very grateful to you for your titanic work in creating and maintaining Planka. I can safely state that there are no better kanban board analogues on the whole github (and I compared many, if not all available (I will not specify these repositories). Planka is leading and this project has a great future. But, it's the way of the world that people find it easier to appropriate someone else's labour than to create or invent something of their own. Open Source projects are the key to the development of the Internet. Who knows what genius will design/create his invention using your kanban board to organise the process?
@timshannon commented on GitHub (Feb 21, 2025):
To be perfectly clear. I'm super grateful for all of the work you all put into Planka, but I'm still disappointed. The reason I'm so disappointed is because even though there are so many open source alternatives, Planka is far and away the best, and I was hopeful for the future of the application as open source, with a community contributing to it.
A license change that changes the relationship with the community to be inherently one-sided means that the community will likely wither and die. I would've preferred to see see enterprise and cloud hosting features locked away behind a different license while still keeping the core open source, similar to Mattermost, CockroachDB, and many other open source projects.
Best of luck though, I truly hope you are successful with this next iteration. You write some incredibly clean and bug free code, so I will likely be forking the current version for my own use.
@gavtroy commented on GitHub (Feb 22, 2025):
It's more that changes wouldn't be stashed away in private for a year in a typical open source project. The writing has long been on the wall and it does feel like you were stringing us along when you could instead have announced the licence change a year ago. Cynically I'd say you wanted to make sure any community fork would have to start behind, which reduces the "risk" of such a fork in the first place. Together with your comments about fairness and mysterious companies preventing you from making money, yet not offering any services yourself... sorry but it all just seems disingenuous and leaves a sour taste. No you don't owe your community anything but it goes both ways.
@meltyshev commented on GitHub (Feb 22, 2025):
Thanks for your clarification and kind words! From our perspective, we’re working to make the project self-sustainable by building a company around it, ensuring that it won’t just die one day and will continue to receive updates.
But I completely understand all your points. Btw, I believe CockroachDB is now source-available with fully proprietary license.
@meltyshev commented on GitHub (Feb 22, 2025):
The reasons why the development is private:
We couldn’t announce the license change simply because we hadn’t yet considered everything. Just a few months ago, at the Open Source Experience in Paris, we spent the entire day discussing a single topic with many participants — what direction people think we should take and gathering insights from their experiences. During the conference we even considered publishing everything we had including enterprise features under the AGPL.
I never said that companies are preventing us from making money. I just wanted to express my feelings about spending a lot of time maintaining the project, while others can start hosting it without giving anything back.
This is the last reply regarding the license change.
@hwelch-fle commented on GitHub (Feb 22, 2025):
I have noticed that we seem to have forgotten to ask what the pricing will be for the enterprise version.
Are you planning on charging a flat rate, charging per user, selling outright, etc.
I'm assuming that even the enterprise version will have the option of self hosting, as that's kinda the big selling point of Planka currently.
Also this is not a complaint, but my preparing to justify a possible expense in the future to my company.
@meltyshev commented on GitHub (Feb 24, 2025):
@hwelch-fle, @JustSamuel here you go :)
Planka v2 OpenAPI Spec (please note that not all response types are listed).
@meltyshev commented on GitHub (Feb 24, 2025):
Thanks for the question! We'll definitely share more details as soon as we have them, but to be honest, we haven’t even thought about pricing yet. I expect it will be decided in a couple of months.
And yes, we’re definitely planning to offer a self-hosting option, and we’d also like to publish the code itself. However, we still need to consider the best format for doing so.
@akinin commented on GitHub (Feb 26, 2025):
I don't understand why many people are complaining about the license change. After all, the author has already mentioned that the project remains open and free. For personal use and small teams, this is quite enough. For more serious tasks and requirements, there will be a pro version. Personally, almost every day since last March, I open GitHub hoping to see an update and I'm very grateful for the development and support.
It feels like those who are complaining and worrying are the ones who use the product for selfish purposes.
@JustSamuel commented on GitHub (Feb 26, 2025):
I think you're right that selfishness is at play, but the finger is being pointed in the wrong direction. Open source thrives on a culture of sharing and mutual growth. The idea is that when everyone contributes, the entire community benefits. Projects like Planka, built on top of countless free and open Node.js packages, exist because of this philosophy.
People contribute to open-source projects not just for personal gain, but because they believe in giving back—whether through code, documentation, bug reports, or community support. When a project that has benefited from these contributions decides to change its license in a more restrictive way, it sends a different message: "We’ve taken what the community has given us, but now we’ve decided not to give back in the same way."
Of course, the maintainers are legally within their rights to change the license. But just because something is allowed doesn’t mean it feels right. These kinds of changes make potential contributors think twice before investing their time and effort into a project, knowing that their work (or an adaptation thereof) could be locked behind a more restrictive model in the future.
Additionally, when people hear that a project is "open and free," they don't just think about whether the product remains accessible for most people. They expect the license itself to reflect the open-source spirit—one that allows for collaboration, modification, and redistribution without artificial constraints. Restrictive licensing can fracture trust in a project, making developers less willing to engage and contribute.
At the end of the day, this is about expectations and community trust. When a project starts as open source and then pivots to a more restrictive model, it inevitably raises concerns. Not because people feel "entitled" to the work, but because it disrupts the implicit social contract that open-source projects are built on.
@chmac commented on GitHub (Feb 26, 2025):
@JustSamuel Thanks you. I wanted to reply but would not have been as eloquent as you were. I think you nailed the essence of the topic here.
@stevef22 commented on GitHub (Feb 28, 2025):
When is Planka 2.0 going to drop!? Feb is almost over. Thank you
@chmac commented on GitHub (Feb 28, 2025):
Mar 19, 2024: months away
Apr 24, 2024: v2 is still some time away
Jun 1, 2024: We don't have any estimated date
Nov 14, 2024: We're planning to release v2 at the beginning of next year.
Feb 13, 2025: we'll finally release it. This will take approximately 2-4 weeks.
@stevef22 Seems like it's not super clear, but probably close.
@stevef22 commented on GitHub (Feb 28, 2025):
Thanks, Im chomping at the bit to get this release so we can develop it.
@nickbe commented on GitHub (Mar 3, 2025):
From the tone in this thread it seems to me that some of you have neither companies nor employees of your own. And while you are busy discussing something that will be free to use for most of you and that we've created with considerable effort and money spent, I wonder if anyone here has expert knowledge what it means to build up a company. Without us paying for lawyers, tax advisors, company funding and many hours of work, Planka would not have existed in its current and future form at all.
So I would kindly ask you to show the people at Planka Software who are working and paying for something they want to provide, support and release into the wild a little more respect.
Being pushed into haste means being pushed into making mistakes. Bad for us - and bad for the community. Hence we think twice over things we do. Creativity needs time and the constant question about the exact date of release doesn't speed up the process - on the contrary - it slows us down.
Personally I have no sympathy for any kind of rudeness in open source projects whatsoever. And I would like thank those of you who appreciate our project and the work we are doing here. Maks does an incredible job right now and with every comment he writes he throws away valuable time he actually needs for programming.
@Lka1988 commented on GitHub (Apr 9, 2025):
I've been using Planka to keep my ADHD in check with all the projects I have going on, otherwise I'd absolutely lose my mind and never get anything done. Pen and paper don't really cut it for me. I was using Trello for a few months, but they paywalled a lot of basic stuff, so I looked for a lightweight alternative and found this.
I'm looking forward to the new release (was certainly not expecting to see this in my perusing), and as I don't really code at this level, I'll contribute by donating to the project when I can.
Your work is much appreciated here. Take the time you need to get it right (because the current version is rock solid), and release it when you're ready.
@itsdoublearon commented on GitHub (Apr 10, 2025):
Hey crew, just checking to see if search function for comments will be developed soon. At the moment when I search cards it doesn't appear to be searching any comments on cards.
Thanks so much
@LouisACR commented on GitHub (May 2, 2025):
Hello, I just wanted to start by thanking the Planka Team for making this open source project that we all love, we are looking forward to trying out the v2, is there any estimate on a release date ?
Thanks so much
@chmac commented on GitHub (May 2, 2025):
Scroll up a few comments, I summarised the stated release dates so far.
@LouisACR commented on GitHub (May 2, 2025):
Okay thanks, so no news since feb ?
@chmac commented on GitHub (May 2, 2025):
There have been promises that it was coming soon for more than a year, I'm not sure how much value you want to ascribe to the current predictions. But no, there haven't been any updates that I've seen since Feb.
@nickbe commented on GitHub (May 7, 2025):
Hi chmac,
We ourselves are waiting for a couple of things right now. Legal stuff has to get checked. other things are coming up at the last moment - as always. If you don't own your own company then you wouldn't know. But let me say this. The crew behind a software thrives because of the many people who appreciate the work that is being done.
We all are waiting for the release now and it will happen. But it happens when people we ourselves are waiting for give us a go.
From your adress given in Github it seems you're from germany.
Daher: Wir können uns sehr gern in einem kleinen Videocall über Firmengründungen, Softwareentwicklung und den Firmenalltag in einem IT Unternehmen unterhalten. Kein Ding. Ich bin seit 30 Jahren in der IT und rede sehr gern über meine Arbeit. Ich tausche mich tatsächlich auch sehr gerne über Softwareentwicklung mit anderen aus meiner Branche aus. Lass es mich wissen wenn Du Dich unterhalten möchtest, dann schicke ich Dir einen Videocall-Link zu. Grüße nach Berlin.
@almereyda commented on GitHub (May 10, 2025):
💐 Thank you for this nice contribution to the computational commons.
I sense there is much space between strictly free software and open source and as a not-for-profit engaging in educational activities, we are thankful of being able to operate in this grey area. Of course people with commercial interest will have other priorities, but for us the new license works for small-scale deployments to activits and environmental groups. If that is not already something, I don't know.
Grüße aus einer anderen Ecke von Berlin.
@chmac commented on GitHub (Jan 7, 2026):
For anyone else looking for planka alternatives, I just found a couple of good looking candidates via this issue:
The first one, kan, looks especially promising. Already has 4.2k stars. We'll likely migrate from planka v1 to that quite soon.