= Request =
In the Google Summer of Code student meeting on Wednesday, the idea came up of hosting a Fedora [https://taskwarrior.org/docs/#taskd TaskServer] instance for [https://taskwarrior.org/ TaskWarrior].
= Analysis =
TaskWarrior is a popular took for to-do list management and seems to be particularly popular among many members of Fedora Infrastructure. For some students in GSoC, it's also being recommended as the primary way to document tasks being worked on and time spent.
The package, taskd, is available in Fedora, but Ralph (threebean) hosts a version in [https://copr.fedorainfracloud.org/coprs/ralph/taskd/ Copr for EPEL 7].
= Enhancement Recommendation =
This may be a useful tool to have available within Fedora, and it might be considered of the same kind of scope as the Gobby instance (in terms of usability and context for how it's used). One big question to ask is how to handle adding new users (and if there would be an automatic or manual way to do it).
So AFAICT taskwarrior doesn't have the concept of different users, so I think we will want to create and explicitly use a user UDA. https://taskwarrior.org/docs/udas.html
user
well, you can do different users with different certs I think... but then we have to maintain another cert infrastructure.
I'm a bit torn on this as I like and use taskwarrior, but I am not if we want to get into the business of maintaining taskd.
I wonder if perhaps we couldn't do a per GSoC cloud instance. Ie, have a ansible playbook to make a taskd server, it can get used for one cycle and then archived off until the next cycle.
I think I am just going to close this. If there's more interest down the road we can revisit it, but I think everyone should run their own at this point.
Sorry.
:disappointed:
@kevin changed the status to Closed
Closed
Login to comment on this ticket.