Discussion: Ideas, introductions and notes for Taskserver ccsync in GSoC'26

[its-me-abhishek]

Description
This discussion thread is for brainstorming features, integrations, and UX enhancements that we could implement for ccsync as part of GSoC 2026. Everyone is encouraged to propose, refine, and discuss ideas in preparation. The discussion might be related to any of these ideas or new ones, and their implementations, etc. Please do not share your personal information, proposals, art, anything that might be useful, etc. here.

Contributors can also use this thread to briefly introduce themselves and/or represent their interests or skills relevant to GSoC 2026 with CCSync.

Expected Output

• A list of proposed ideas, feature requests, integration plans, UX suggestions, and contributor interests for GSoC 2026 (not all ideas may be implemented).
• Clarification, refinement, and prioritization of possible directions for ccsync
• Placeholder only: no implementation or assignment of work unless ideas are moved to tracked issues, after further review

Feature & UX Ideas for now (all these are part of the same project)

1. Data Visualization & UX (Medium/High Priority)

   • Kanban & Calendar Views using projects: Moving beyond lists to project-based boards and time-based scheduling.
   • Task Graph Flow Diagram: A semantic graph (using Cytoscape.js or D3.js) showing dependencies, project clusters, and tag relationships.
   • Advanced Theming: High-contrast modes, adjustable typography, and persistent light/dark themes.

2. Ecosystem & Integrations (Medium/High Priority)

   • Centralized Sync Hub: Expanding 2-way sync for Google Tasks (priority), Google Calendar, Jira, and Joplin.
   • Code Host Integration: Integration with GitHub/GitLab issues via Bugwarrior.
   • Notification Engine: External reminders via Email, Slack, or Telegram (likely by extending the backend CLI).
   • Updated Documentation for all the new changes

3. Core & Performance (Medium)

   • PWA Support: Offline usage via Web Workers for a desktop/mobile app-like experience.
   • Account Portability: Tools for bulk transfer, deletion, or UUID migration between accounts.
   • Mock Demo Instance: A "Try Before You Login" feature using a mock frontend implementation that doesn't require real auth.

4. Task Graph Flow Diagram Idea: Semantic “task graph” with visual connections

   • Nodes = tasks, Edges = dependencies/project/tag sharing
   • Different line styles for each relation, interactive exploration (Cytoscape.js/D3.js)
   • Node color/border for project/priority, hover/click for task info, mini-map overview, filters for graph layers
   • Optional: visual effects (aging, completion, AI “theme” nodes)
   • Implementation path: preprocess tasks in browser, render with react-cytoscapejs, style by edge type, add filtering/interactions.

Feel free to DM me on Zulip for any discussion related to proposals, etc.

Important Links

• https://ccextractor.org/

NOTE: This list is not exhaustive; additional ideas may be proposed, and some items listed here may be deprioritized or removed over time. The scope (hours required) can thus be decided for the project once these are finalized. Please use this thread strictly for discussion and brainstorming. Since this is not a tracked issue, it is not assignable, and contributors are requested not to start implementation work based on these ideas at this stage.

[its-me-abhishek]

Another thread relevant for Discussions related to integrations #142

[Hell1213]

hey @its-me-abhishek ,
I am Rajat. I’ve been contributing to CCsync for a while now across frontend and UI work, some backend-related changes, and a bit of developer workflow/tooling.

I’m interested in participating in GSoC 2026 with CCsync and will be following this thread to understand priorities and help refine ideas, especially around integrations and building things that are realistic to implement and ship within a GSoC timeline.

Looking forward to the discussions here.

[jnakaigen]

Hi @its-me-abhishek and community! I'm Janaki. I'm a student interested in contributing to CCSync for GSoC 2026. While I'm new to this specific codebase, I have experience with TypeScript and REST APIs. I'm currently setting up the development environment locally and looking through the documentation to see where I can help with initial small fixes or improvements. I'm particularly interested in the Ecosystem & Integrations ideas mentioned above!

[Sparshagarwal29]

Hi @its-me-abhishek and everyone,

I’m Sparsh, a student interested in getting involved with CCSync and learning more about the project in the context of GSoC 2026. I’ve recently started exploring the repository and documentation to understand how the system is structured
I have experience working with TypeScript, web technologies, and REST-based services, and I’m in the process of setting up the project locally so I can start engaging with the code more directly. I’m open to contributing across different areas of the project and helping out with initial fixes or improvements as ideas evolve here.

Looking forward to following the discussion and learning from the community

[Vasist10]

Hi @its-me-abhishek ,
I am vasist ,I’ve been contributing to CCSync recently and wanted to express my interest in the GSoC 2026 discussions.
I’m particularly interested in backend and sync architecture (task modeling, adapters, conflict handling), and I’m following this thread to better understand possible directions and where I can be helpful.
Looking forward to learning more and contributing!

[SGI-CAPP-AT2]

@its-me-abhishek, I think we should use taskchampion crate instead of using taskwarrior command line tool.
There is problem of having no control on uuid when task is created. Whenever task is created at mobile application we do not have a robust key to access it.
This problem can be eliminated by using taskchampion crate.

[its-me-abhishek]

@SGI-CAPP-AT2
When you say “no control on UUID,” are you referring to the pre-sync state where the task hasn’t received a UUID yet?

I checked the taskchampion docs Task struct, and it seems like this pre-sync issue can be addressed by using the crate directly. Maybe using the same backend, using ffi or similar stuff.

Also, I’m quite a bit unsure whether adopting taskchampion adds another layer of friction for users especially those who already have taskc servers set up with on their systems, and use CCSync as a web/app extension. I think this Remote ServerConfig could fix this (need to test this out)

My thoughts: One simpler workaround could be to automatically trigger a re-sync right after task creation, so the backend returns the fully populated task (with UUID) instead of the skeletal pre-sync task. The tradeoff would be one extra API call per task creation.

Curious about how you might be thinking of implementing this. IMO we can and should go through this in case the performance, response rates by using crates are better than that add-re-sync workflow else the current implementation seems to be fine and can be fixed via that workaround. One thing I am concerned about is that -- that CLI implementation is kinda hard to go obsolete and is more robust (as TW2.0 got deprecated earlier and so did taskd). For example- if and when TW3.0+taskchampion combination is deprecated similar to that TW2.0, we can switch to that version by just patching how the sync works, which might not be the case with taskchampion crate.

EDIT: username tag and some context