nextcloud / nextcloud/deck

Kanboard support

Open
#6,845 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement integration
Dominant language
JavaScript
Stars
1.4k
Forks
354
Avg merge
1d 10h
Merged PRs (30d)
43

Description

Is your feature request related to a problem? Please describe.
For the last few years I've been thinking about the benefits of Nextcloud Deck team partnering with the Kanboard project team. Note, I do not work for, or know, anyone at Kanboard. This might be handled in a manner similar to Roundcube partnership. Why, because Kanboard is also coded in PHP and the team has effectively completed a massive swath of functionality on the Deck project roadmap / Nice to have's.

To be honest, I have no idea of if they want to partner up, but I do know that Kanboard is rock solid as a kanban platform. And, they have been in maintenance mode for years because of how far they have gone.
Take a look at their absolutely epic API and configuration documentation

I don't want to spam mention your issues, but they could potentially help you address a ton of things, like going in reverse order of oldest Deck requests:

Public Sharing #14 
Swimlanes support#32
Archiving Stacks #34
and on up the list.

Thanks either way for considering. Best of luck and great work on Deck. ❤

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the Deck roadmap issues linked in the proposal, including Public Sharing #14, Swimlanes #32, and Archiving Stacks #34, alongside Kanboard's API and configuration documentation. The issue does not define a specific implementation or a measurable completion condition; partnership interest and scope would need to be established first.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.