Re: RFC: Representing "image needed" in Taiga

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hey Ben,

Tagging the post seems like one of the top options in my opinion. We can easily documents what colors mean which and is viewable at a glance.

Also, if creating an Image is a task of itself. Would it be reasonable to consider it its own card and then have that card reference the original article spec? A image workflow is a bit similar from my understanding. Needs to be created, viewed, and potentially edited.

Cheers,

rwaltr

-------- Original Message --------
On Nov 8, 2019, 2:32 PM, Ben Cotton wrote:

> One weakness of the current editorial workflow[1] is that there's no
> obvious way to indicate that an article needs a featured image. There
> are four possibilities I see. What does the team think?
>
> 1. Create a new column
> Advantages: Easy to see which articles need images so that people can
> easily claim those.
> Disadvantages: Adds another step to the flow and doesn't represent
> well that images can be done in parallel to editing.
>
> 2. Use a tag
> Advantages: Color coding means the card indicates the article needs an
> image in most view.
> Disadvantages: It's not clear what the color coding means unless you
> already know.
>
> 3. Use a custom field
> Advantages: Can have multiple choices to represent state (needed, in
> progress, done).
> Disadvantages: Not visible without opening the card
>
> 4. Use a task within the user story
> Advantages: Can be assigned and have it's own state. We could also
> potentially do the same for editing, though that might be redundant.
> Disadvantages: Not visible without opening the card.
>
> [1] https://docs.fedoraproject.org/en-US/fedora-magazine/workflow/
>
> --
> Ben Cotton
> He / Him / His
> Fedora Program Manager
> Red Hat
> TZ=America/Indiana/Indianapolis
> _______________________________________________
> Fedora Magazine mailing list -- magazine@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to magazine-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/magazine@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
Fedora Magazine mailing list -- magazine@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to magazine-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/magazine@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Users]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Devel]     [EPEL Announce]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Review]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [ET Management Tools]     [Yum Users]     [Fedora Art]     [Fedora ARM]

  Powered by Linux