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(a)lists.fedoraproject.org > To unsubscribe send an email to magazine-leave(a)lists.fedoraproject.org > 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@lists.fedoraprojec...

On Fri, Nov 8, 2019 at 4:01 PM Ryan Walter <rwalt(a)pm.me&gt; wrote: The workflow for images is, in practice, much simpler than articles. Someone makes it and it's done. Conceivably there can be some back-and-forth, but that doesn't happen much in practice. I wouldn't want to have separate user story cards because then it becomes really hard to tie them together. On Fri, Nov 8, 2019 at 4:05 PM pmkellly(a)frontier.com <pmkellly(a)frontier.com&gt; wrote: That would get us the best of both worlds, but I'm worried it would result in indeterminate state when the editor updates one but forgets to update the other. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

On Wed, Dec 4, 2019 at 5:52 AM Adam Samalik <asamalik(a)redhat.com&gt; wrote: Ship it! -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

»» So we'll label the ones that need an image "Ship It!" Sounds like a good way to create chaos and confusion. I like it, we're too orderly. :-D On Wed, 4 Dec 2019 at 14:48, pmkellly(a)frontier.com <pmkellly(a)frontier.com&gt; wrote: