Page MenuHomeSolus

[RFC] Needs New Maintainer: taskwarrior
Closed, ResolvedPublic


Repo: R3006 taskwarrior

As part of a sweeping effort I am doing to reduce outdated package count, begin regularly enforcing maintainership file inclusion in old(er) repos, and increase the likelihood of a package having a maintainer (should it be required, outside of those being handled by Core Team and Global Maintainers), this task is being created to effectively "notify" the current maintainer of the package that it needs to be updated or modified to indicate its maintainership and ensure it is regularly maintained. In the event there is no specific maintainer, either one may be specified that has regularly updated it in the past, or this task shall also be considered an RFC for a new maintainer.

During the patch submission process, the file should be included if it is not already, and have the following content (replace REPLACEME with the correct value):

This file is used to indicate responsibility for the maintenance of this package. Individuals on this list should be the sole modifiers of the package, excluding cases where the Solus Team may need to perform necessary rebuilds, upgrades, or security fixes. This list should not be used for any direct contact usage. If you believe this package requires a package update, follow documentation from In the event this package no longer becomes sufficiently maintained, Core Team reserves the right to request a new maintainer or remove this package from the repository.

  - Email: REPLACEME

Unless the updating of the package or claiming of maintainership is being blocked by other items in the stack, 30 days shall be provided to update the package or claim maintainership. Should the package not see an update by either the maintainer or an individual volunteering to become the maintainer, Core Team reserves the right to remove it from the repository. Please note that simply volunteering for maintainership without providing a patch is not an accepted "solution" to resolving this task or preventing deprecation.

Related Objects

Duplicates Merged Here
T9579: Taskwarrior

Event Timeline

JoshStrobl triaged this task as High priority.Dec 16 2020, 10:33 AM
JoshStrobl created this task.
JoshStrobl added a project: Needs Maintainer.
JoshStrobl moved this task from Backlog to Update Requested on the Software board.
JoshStrobl closed this task as Wontfix.Jan 15 2021, 2:47 PM

As no maintainer has come forth, closing as wontfix and deprecating from the repository. Re-inclusion will need to go through our standard package request process.

I only noticed that this was deprecated after it had been removed from my system, likewise with newsboat.

To what mailing list or notification should one subscribe to be made aware of these deprecations?

@Schteve I agree that it's not ideal atm, but you could e.g. select "Watch Project" here:

Thanks. I think it's the sort of thing that could have done with being covered in a [section of a] blog post.

I think you are overestimating the amount of people that actively read the blog or our blog posts. We had people coming in months after our infrastructure migration blog posts saying they couldn't reach the old package repository. There is no good mechanism at this time of guaranteeing someone sees an RFC. Either way, this task needs to stay on topic. If someone is interested in becoming a maintainer for this package, at the very least a new patch on top of our existing repo will need to be provided.

Hey, I will maintain this package

xulongwu4 added a comment.EditedFeb 18 2021, 2:13 AM

Re-inclusion will need to go through our standard package request process.

@JoshStrobl Thanks for bringing me to this task. I am wondering what would be the process to bring taskwarrior back to the repo. I am willing to maintain this package. However, the repo is deprecated so I can't clone it or submit an update. That is why I created a package request for it. Looking forward to your advice.