On Mon, Dec 2, 2019 at 4:19 PM pmkellly@frontier.com <pmkellly@frontier.com> wrote:

On 12/2/19 07:03, Kamil Paral wrote:

> I'm not familiar with kanban/taiga. What is the benefit over using standard
> (Pagure) tickets?

The kanban/taiga is what they use at Fedora Magazine. A Writer starts by
creating an Issue proposing a new article for the magazine. There is a
back and forth commentary and if the proposal gets two +1 votes then the
proposal is transfered to a job ticket in the kanban by one of the Editors.

Then the writer picks up the job ticket and assigns it to them selves if
the Editor didn't already assign it to them. Editors can also create job
tickest for articles they want and a Writer who thinks they can write
the article can pick it up and write it. Once a writer is assigned to a
job ticket they write the article according to their free time or
according a requested time.

When the draft is complete, the writer puts the job ticket into the
review queue and an editor will review it. Then the job ticket can be
put back in the in process queue if it needs a lot of work or it can be
placed in the To Edit queue for other work like having a feature image
added to it and it can wait there for scheduling.

After the image is added and the schedule is decided the job ticket is
placed in the Queued queue.

All through the process from when the writer starts writing the article
to publishing, the actual article is linked to the job ticket.

Thanks, Pat, for the description. Kanban seems to be just a workflow visualization that could be done with custom ticket status or tags the same way (but wouldn't look as pretty as a native kanban UI). Either way, I think this doesn't really apply to blocker discussion tickets. These tickets have a dead simple workflow open -> discuss&vote (separating that would waste a lot of time) -> closed.