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/
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?
- 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.
- 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.
- Use a custom field
Advantages: Can have multiple choices to represent state (needed, in progress, done). Disadvantages: Not visible without opening the card
- 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@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@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.fedoraproject.o...
On 11/8/19 15:32, 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?
- 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.
- 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.
- Use a custom field
Advantages: Can have multiple choices to represent state (needed, in progress, done). Disadvantages: Not visible without opening the card
- 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/
How about a combination of 2 and 3? You get the high visibility flag to open the card and the state can be shown. The color could explained very briefly at the top of the kanban page perhaps "Blue cards need image".
Have a Great Day!
Pat (tablepc)
On Fri, Nov 8, 2019 at 4:01 PM Ryan Walter rwalt@pm.me wrote:
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.
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@frontier.com pmkellly@frontier.com wrote:
- Use a tag
- Use a custom field
How about a combination of 2 and 3? You get the high visibility flag to open the card and the state can be shown. The color could explained very briefly at the top of the kanban page perhaps "Blue cards need image".
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.
So I thought about this, and:
The image can be basically done at any state — so that goes against creating a new column for that.
Anything that's not visible in the Kanban view, I wouldn't do, because there is no simple way to list articles that need an image. Yes, you can do filter the Kanban view, but that's a bit clunky in Taiga.
I'd go with the label. We don't use them for anything, so if there is a label on a card, it means it needs an image. A disadvantage of this is that it's not obvious that new cards need to be labeled, but the editors could take care of that I believe.
About using both labels and custom fields, that seems like a source for errors and too much unnecessary clicking.
So let's go with the label?
On Fri, Nov 8, 2019 at 10:55 PM Ben Cotton bcotton@redhat.com wrote:
On Fri, Nov 8, 2019 at 4:01 PM Ryan Walter rwalt@pm.me wrote:
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.
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@frontier.com pmkellly@frontier.com wrote:
- Use a tag
- Use a custom field
How about a combination of 2 and 3? You get the high visibility flag to open the card and the state can be shown. The color could explained very briefly at the top of the kanban page perhaps "Blue cards need image".
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 _______________________________________________ Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@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.fedoraproject.o...
On Wed, Dec 4, 2019 at 5:52 AM Adam Samalik asamalik@redhat.com wrote:
So let's go with the label?
Ship it!
On 12/4/19 08:34, Ben Cotton wrote:
On Wed, Dec 4, 2019 at 5:52 AM Adam Samalik asamalik@redhat.com wrote:
So let's go with the label?
Ship it!
So we'll label the ones that need an image "Ship It!" :-)
»» 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@frontier.com pmkellly@frontier.com wrote:
On 12/4/19 08:34, Ben Cotton wrote:
On Wed, Dec 4, 2019 at 5:52 AM Adam Samalik asamalik@redhat.com wrote:
So let's go with the label?
Ship it!
So we'll label the ones that need an image "Ship It!" :-) _______________________________________________ Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@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.fedoraproject.o...
Done! There is now a label "image needed" on cards that need an image.
On Wed, Dec 4, 2019 at 6:20 PM Silvia Sánchez bhkohane@gmail.com wrote:
»» 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@frontier.com pmkellly@frontier.com wrote:
On 12/4/19 08:34, Ben Cotton wrote:
On Wed, Dec 4, 2019 at 5:52 AM Adam Samalik asamalik@redhat.com
wrote:
So let's go with the label?
Ship it!
So we'll label the ones that need an image "Ship It!" :-) _______________________________________________ Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@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.fedoraproject.o...
Fedora Magazine mailing list -- magazine@lists.fedoraproject.org To unsubscribe send an email to magazine-leave@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.fedoraproject.o...
magazine@lists.fedoraproject.org
-
Adam Samalik -
Ben Cotton -
pmkellly＠frontier.com -
Ryan Walter -
Silvia Sánchez