[Permission Request] Dayquence as a separate Obsidian Community Plugin

[zczs520]

Hi Callum,

I'm the maintainer of Dayquence:

https://github.com/zczs520/tasknotes

First, I want to sincerely thank you for creating and maintaining TaskNotes.

TaskNotes is an excellent plugin, and I especially appreciate its local-first
design, the one-note-per-task model, portable Markdown data, Bases integration,
calendar support, time tracking, and the amount of care that has gone into its
architecture and documentation.

It provided a remarkably strong foundation for managing tasks without locking
users into a proprietary database. I would not have been able to build
Dayquence in its current form without the work that you and the TaskNotes
contributors have already done.

About Dayquence

Dayquence is a free, non-commercial community project derived from TaskNotes.
It began as a version adapted to my personal task-planning and review workflow,
and gradually developed its own interface, interaction patterns, and priorities.

My goal is to make Dayquence available in the official Obsidian Community
Plugins directory, mainly so users can install it safely and receive updates
more conveniently.

Dayquence will remain free and non-commercial.

Changes in Dayquence

Compared with the upstream TaskNotes version from which it was derived,
Dayquence currently includes changes such as:

• A redesigned task creation and editing workflow with immediate task creation,
  automatic saving, and faster access to the underlying Markdown note.
• A substantially redesigned Kanban experience with a more visual layout,
  task search, date filters, configurable swimlanes, quick rescheduling, and
  task creation that inherits the current column and swimlane properties.
• A new time-statistics experience with day, week, month, and year views,
  timelines, heatmaps, task rankings, tag distribution, and access to
  individual time entries.
• Redesigned active-task and time-tracking controls, including a more accessible
  floating/status-bar workflow.
• Improvements to task cards, metadata presentation, progress indicators,
  scheduling controls, and task context actions.
• Improvements to task creation defaults, project and subtask workflows,
  custom task properties, and Chinese natural-language task entry.
• New first-run guides in Chinese and English to help users understand the
  task, Kanban, calendar, Pomodoro, and time-review workflows.
• A separate Dayquence identity, documentation, release process, visual style,
  and independently maintained roadmap.
• Additional unit and integration tests covering the new task modal, Kanban,
  time-statistics, active-task, scheduling, and property workflows.

These changes currently span more than 150 files, including several thousand
lines of new application code, tests, and styles. However, I fully recognize
that Dayquence is still derived from TaskNotes and that its foundation exists
because of your work and the work of the TaskNotes community.

Attribution and independent maintenance

I understand that Obsidian's developer policy requires explicit, publicly
verifiable approval from the original author before a fork can be listed in
the Community Plugins directory.

Before submitting Dayquence, I plan to:

• Change the plugin ID from tasknotes to the unique ID dayquence.
• Make sure Dayquence can coexist with and be clearly distinguished from the
  official TaskNotes plugin.
• Clearly state in the README that Dayquence is derived from TaskNotes.
• Credit you and all TaskNotes contributors prominently.
• Preserve the original MIT copyright and license notices.
• Link prominently to the official TaskNotes repository and documentation.
• Document the differences between TaskNotes and Dayquence clearly.
• Provide a migration path for existing Dayquence users.
• Take independent responsibility for maintenance, compatibility, security
  fixes, documentation, and user support.
• Avoid presenting Dayquence as an official TaskNotes release or as being
  endorsed by you unless you explicitly state otherwise.

Permission request

Would you explicitly approve Dayquence being submitted and listed as a
separate Obsidian Community Plugin derived from TaskNotes?

For clarity during the Obsidian review process, a response such as the
following would provide the public confirmation they require:

Yes, I explicitly approve Dayquence being submitted and listed as a separate
Obsidian Community Plugin derived from TaskNotes.

I completely understand if you would prefer that I not submit it separately.
If so, I will respect your decision and continue distributing it through BRAT,
or consider redesigning the project as a companion plugin using the TaskNotes
public API.

Regardless of your decision, thank you again for building TaskNotes and making
it available as open-source software. It is an impressive project, and I am
genuinely grateful for the time, thought, and effort you and the contributors
have invested in it.

Best regards,

zhuxiaocong

[callumalpass]

Hi @zczs520 . Thank you for getting in touch about this. Yes, I'm absolutely happy for you to list Dayquence as a separate plugin derived from TaskNotes!