I’m working as a freelancing software developer and I’m always open for getting hired to work on open source projects like deck. If you are interested, just contact me.
In terms of crowd funding, I might setup a Patreon profile like @brantje did for the passman app, but I need to check what other platforms are out there that might make sense. That would of course allow me to spend some more time, working on deck. I’ll keep you updated on that.
Just wondering… Could a stack be considered as a todo-list, for synchronization with standard CalDav apps ? (I’m quite clueless, it would probably not make much sense as one would need 1 agenda per stack to get the todo-list linked to the given agenda…
I think WeKan https://wekan.github.io/ is so much further in development already. They are enterprise grade. Why reinvent the wheel?
Also Escubaer just one comment above suggested the app Kanboard which I have never heard of, but also seems to be further in development.
I just noticed a bug in deck (cards can not be moved to stacks that are empty) but I am not going to report it on github because I hope you will join forces with some of the existing kanban apps and bring it to nextcloud — please!!!
So I originally also had a look on how we could integrate with existing solutions, but I’ve not found a nice solution that will make it feel like a native Nextcloud app. For wekan in special there is a whole different server stack required for deployment, so setting this up besides Nextcloud is a huge effort for sysadmins. (See Install and Update · wekan/wekan Wiki · GitHub) Yes, for kanboard that would be easier, but you still have to maintain two different software installations.
Another reason for creating a separate app was that other external integrations like web mail clients we had in the past were also lacking a lot in terms of user experience and the integration with Nextcloud. I guess the Nextcloud mail app was developed for a similar reason.
There is no reason for me someone may not start working on integrating one of those solutions to Nextcloud, it was just that I expected it to work nicer if I start with a native app. (And I also mainly started this as a learning project for angular js )
I hope I could clarify things a bit.
That bug will be fixed in the next bugfix release.
great that you want to start contributing. I would suggest to pick some good first issues we have to get familiar with the source code and development in the deck project.
If you have any questions, feel free to ask at the corresponding github issue or join #nextcloud-deck on freenode irc.