From c5dc9c7eca452f82d5a90f6b3965bfec6d46d6ad Mon Sep 17 00:00:00 2001 From: Gregory Bartholomew Date: Dec 29 2021 02:45:37 +0000 Subject: [PATCH 1/18] Kanban column renamed from 'Queued' to 'Scheduled' --- diff --git a/graphics-sources/fedora-magazine-workflow.svg b/graphics-sources/fedora-magazine-workflow.svg index 8de741c..5c35467 100644 --- a/graphics-sources/fedora-magazine-workflow.svg +++ b/graphics-sources/fedora-magazine-workflow.svg @@ -2,20 +2,20 @@ + inkscape:version="1.1 (c68e22c387, 2021-05-23)" + sodipodi:docname="fedora-magazine-workflow.svg" + xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" + xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns="http://www.w3.org/2000/svg" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:cc="http://creativecommons.org/ns#" + xmlns:dc="http://purl.org/dc/elements/1.1/"> - - - - - - - - - - - - - - - - - - + inkscape:window-width="1920" + inkscape:window-height="1015" + inkscape:window-x="0" + inkscape:window-y="0" + inkscape:window-maximized="1" + showguides="false" + inkscape:pagecheckerboard="0" /> @@ -262,7 +179,6 @@ image/svg+xml - @@ -271,7 +187,8 @@ inkscape:groupmode="layer" id="layer1"> - - - + + Edit & Image - Edit & Image + by editors - - by editors + + Publishing - Publishing + by editors - - by editors + + Review - Review + by editors - - by editors + + Writing - Writing + by a writer - - by a writer + + Article proposal - Article proposal + by anyone - - - by anyone + + + idea - - idea + + article spec - - article spec + + in progress - - in progress + + review - - review + + to edit - - to edit + + queued - - scheduled + + published - - - - - - - - published + + + + + + + + Clarification - Clarification + by editors - - - - - - - - by editors + + + + + + + + 1 - 1 + 3 - 3 + 5 - 5 + 2 - 2 + 4 - 4 + 6 - + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:14.1111px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;fill:#ffffff;stroke-width:0.264583px">6 Article proposal + y="222.92404" + style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Bold';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">Article proposal by anyone idea + x="454.72266" + y="227.47343" + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">idea 1 + style="fill:#f9f9f9;fill-opacity:1;stroke:none;stroke-width:0.7;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" /> + style="fill:#e6e6e6;fill-opacity:1;stroke:none;stroke-width:1;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" /> Clarification by editors + y="298.3587" + style="font-weight:normal;font-size:7.05555556px;line-height:1.25;text-align:end;text-anchor:end;stroke-width:0.264583px;-inkscape-font-specification:'Nimbus Roman, Normal';font-family:'Nimbus Roman';font-style:normal;font-stretch:normal;font-variant:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal">by editors + d="m 421.09827,283.46118 c -5.35781,2.13739 -6.67873,5.87881 -6.68073,8.72284 -0.002,2.77139 1.65365,4.9102 6.08542,7.79855" + style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:2.265;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1;marker-end:url(#marker13200)" /> 2 idea + x="454.72266" + y="283.9823" + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">idea article spec + style="fill:#e6e6e6;fill-opacity:1;stroke:none;stroke-width:1;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" /> Writing by a writer + y="381.66806" + style="font-weight:normal;font-size:7.05555556px;line-height:1.25;text-align:end;text-anchor:end;stroke-width:0.264583px;-inkscape-font-specification:'Nimbus Roman, Normal';font-family:'Nimbus Roman';font-style:normal;font-stretch:normal;font-variant:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal">by a writer article spec in progress + x="445.28943" + y="377.6868" + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">in progress review + d="m 421.09827,356.69357 c -5.35781,2.13738 -6.67873,5.87881 -6.68073,8.72281 -0.002,2.77139 1.65365,4.9102 6.08542,7.79855" + style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:2.265;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1;marker-end:url(#marker10762)" /> + style="fill:#214478;fill-opacity:1;stroke:none;stroke-width:0.7;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" /> 3 + x="337.68964" + y="380.58008" + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:14.1111px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;fill:#ffffff;stroke-width:0.264583px">3 + style="fill:#f9f9f9;fill-opacity:1;stroke:none;stroke-width:0.7;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" /> Review + y="467.84222" + style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Bold';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">Review by editors @@ -1200,317 +1072,303 @@ sodipodi:nodetypes="csc" inkscape:connector-curvature="0" id="path14866" - d="m 421.09827,466.04696 c -5.35781,2.13739 -6.67873,5.87881 -6.68073,8.72283 -0.002,2.77139 1.65365,4.9102 6.08542,7.79855" - style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:2.2650001;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1;marker-end:url(#marker13104)" /> + d="m 421.09827,472.38915 c -5.35781,2.13739 -6.67873,5.87881 -6.68073,8.72283 -0.002,2.77139 1.65365,4.9102 6.08542,7.79855" + style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:2.265;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1;marker-end:url(#marker13104)" /> 4 in progress + x="445.28943" + y="450.90689" + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">in progress review to edit + x="451.69232" + y="493.92084" + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">to edit + style="fill:#f9f9f9;fill-opacity:1;stroke:none;stroke-width:0.7;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" /> Publishing + y="625.21753" + style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Bold';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">Publishing by editors + style="fill:#214478;fill-opacity:1;stroke:none;stroke-width:0.7;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" /> 6 + x="337.4921" + y="632.14539" + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:14.1111px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;fill:#ffffff;stroke-width:0.264583px">6 queued + sodipodi:role="line">scheduled published + x="446.92627" + y="639.73077" + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">published + style="fill:#e6e6e6;fill-opacity:1;stroke:none;stroke-width:1;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" /> Edit & Image by editors + y="560.36456" + style="font-weight:normal;font-size:7.05555556px;line-height:1.25;text-align:end;text-anchor:end;stroke-width:0.264583px;-inkscape-font-specification:'Nimbus Roman, Normal';font-family:'Nimbus Roman';font-style:normal;font-stretch:normal;font-variant:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal">by editors to edit + x="451.69232" + y="545.97424" + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">to edit queued + sodipodi:role="line">scheduled + d="m 421.09827,545.46705 c -5.35781,2.13739 -6.67873,5.87881 -6.68073,8.72284 -0.002,2.77139 1.65365,4.9102 6.08542,7.79855" + style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:2.265;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1;marker-end:url(#marker13200)" /> 5 diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-1.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-1.jpg index 03c83a1..14eb83f 100644 Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-1.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-1.jpg differ diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-2.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-2.jpg index a4f401d..68fa2fd 100644 Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-2.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-2.jpg differ diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-3.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-3.jpg index 73a1bd6..86b2436 100644 Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-3.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-3.jpg differ diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-4.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-4.jpg index 9e30879..cdca23b 100644 Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-4.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-4.jpg differ diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-5.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-5.jpg index f6d457f..7426150 100644 Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-5.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-5.jpg differ diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-6.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-6.jpg index d01f880..d544b10 100644 Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-6.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-6.jpg differ diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow.jpg index eafd865..866655a 100644 Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow.jpg differ diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc index 4aabb24..a979741 100644 --- a/modules/ROOT/pages/editorial-meetings.adoc +++ b/modules/ROOT/pages/editorial-meetings.adoc @@ -95,7 +95,7 @@ Assign an editor and a cover image designer to each article so it can be moved f === 5/ Publishing schedule #topic 5/ Publishing schedule - #info Looking at the 'queued' and 'to edit' columns, decide the publishing schedule for the next week period. + #info Looking at the 'to edit' column, decide the publishing schedule for the next week. #info If there is not enough content, we might also need to look at the 'in progress' or even the 'article spec' columns come up with additional content. #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban diff --git a/modules/ROOT/pages/workflow-edit-image.adoc b/modules/ROOT/pages/workflow-edit-image.adoc index 2de9cf9..dacdca8 100644 --- a/modules/ROOT/pages/workflow-edit-image.adoc +++ b/modules/ROOT/pages/workflow-edit-image.adoc @@ -18,7 +18,7 @@ Since multiple people will be potentially completing this step, they need to coo When done, indicate that in the comments. -If the cover image has been also done (that would be indicated in the comments), move the card to the __Queued__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. +If the cover image has also been done (that would be indicated by the absence of the __needs image__ tag), schedule the article in WordPress and move the card to the __Scheduled__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. == Creating a cover image @@ -29,9 +29,9 @@ Since multiple people will be potentially completing this step, they need to coo **Create a cover image** for the article. See the xref:creating-an-image.adoc[Creating a featured image] page for instructions. -When done, indicate that in the comments. +When done, indicate that by removing the __needs image__ tag. -If the cover image has been also done (that would be indicated in the comments), move the card to the __Queued__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. +If the editing has also been done (that would be indicated in the comments), schedule the article in WordPress and move the card to the __Scheduled__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. == Workflow **Previous step:** xref:workflow-review.adoc[Review] diff --git a/modules/ROOT/pages/workflow-publishing.adoc b/modules/ROOT/pages/workflow-publishing.adoc index c474122..51b0782 100644 --- a/modules/ROOT/pages/workflow-publishing.adoc +++ b/modules/ROOT/pages/workflow-publishing.adoc @@ -8,9 +8,10 @@ A member of the Editorial board either publishes or schedules an article for pub == Publishing an article -Articles that are ready to be published are in the __Queued__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. +Articles that are ready to be published are in the __Scheduled__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. -After publishing or scheduling them in Wordpress, move the card to the __Scheduled__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. +In preperation for the weekly editorial board meeting, the editor of the week will move cards for articles that have been published for at least one week from the __Scheduled__ column to the __Published (Archived)__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. +The cards are left in the __Scheduled__ column for at least one week so the author can use it to request post-publication revisions if necessary. That's it! diff --git a/modules/ROOT/pages/workflow.adoc b/modules/ROOT/pages/workflow.adoc index baaeed8..a901677 100644 --- a/modules/ROOT/pages/workflow.adoc +++ b/modules/ROOT/pages/workflow.adoc @@ -13,7 +13,7 @@ Content on the Fedora Magazine is created using a 6-step workflow: 5. xref:workflow-edit-image.adoc[Edit & Image] by Editors 6. xref:workflow-publishing.adoc[Publishing] by Editors -An initial proposal lands in the __idea__ state. After some clarification, a specific article goes through 6 states starting as an __article spec__, progressing as __in progress__, __review__, __to edit__, __queued__, and finally ends up being __published__. Each step in the workflow has its own page in this documentation that provides guidance. +An initial proposal lands in the __idea__ state. After some clarification, a specific article goes through 6 states starting as an __article spec__, progressing as __in progress__, __review__, __to edit__, __scheduled__, and finally ends up being __published__. Each step in the workflow has its own page in this documentation that provides guidance. == Tracking From 0ab0e2505d98561b59e8ac694138da75e31c04f6 Mon Sep 17 00:00:00 2001 From: Alessio Date: Dec 29 2021 02:45:37 +0000 Subject: [PATCH 2/18] libera.chat instead of freenode Link to libera.chat instead of freenode --- diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc index a979741..f59361b 100644 --- a/modules/ROOT/pages/editorial-meetings.adoc +++ b/modules/ROOT/pages/editorial-meetings.adoc @@ -6,7 +6,7 @@ The goal of this meeting is to set and execute a publishing schedule of appropri :hash: # -Meetings happen every week in the https://webchat.freenode.net/?channels=fedora-meeting[{hash}fedora-meeting] channel on freenode. See the https://apps.fedoraproject.org/calendar/meeting/9224/[Fedora Magazine Editorial board meeting] in the Fedora calendar. +Meetings happen every week in the https://web.libera.chat/#fedora-meeting[{hash}fedora-meeting] channel on libera.chat. See the https://apps.fedoraproject.org/calendar/meeting/9224/[Fedora Magazine Editorial board meeting] in the Fedora calendar. Meetings are chaired by that week's xref:editor-of-the-week.adoc[Editor of the Week]. If the meeting time changes, be sure to update the link in this paragraph. From e99e207fac3316473435300adc4c08c79144383e Mon Sep 17 00:00:00 2001 From: Richard England Date: Dec 29 2021 02:45:37 +0000 Subject: [PATCH 3/18] Change Taiga references to Pagure. Modified process steps. --- diff --git a/modules/ROOT/pages/workflow-article-proposal.adoc b/modules/ROOT/pages/workflow-article-proposal.adoc index 0e2dd51..7d38869 100644 --- a/modules/ROOT/pages/workflow-article-proposal.adoc +++ b/modules/ROOT/pages/workflow-article-proposal.adoc @@ -12,7 +12,7 @@ Proposals can be ideas or specific pitches (an example is below). Proposing an a Join the community in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum] and submit your idea as a new topic. -TIP: If this is your first proposal, and you also plan to write an article, you can help us speed the process up by logging into our https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Taiga board] — click on the "OpenID Connect" button on the login form to log in with your Fedora Account. That is required before you can be added to the board as a writer. +TIP: If this is your first proposal, and you also plan to write an article, you can help us speed the process up by logging into our https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure] — Select the __Log In__ button to log in with your Fedora Account. That is required before we can assign and article to you. == A specific pitch example diff --git a/modules/ROOT/pages/workflow-clarification.adoc b/modules/ROOT/pages/workflow-clarification.adoc index 531c065..199583e 100644 --- a/modules/ROOT/pages/workflow-clarification.adoc +++ b/modules/ROOT/pages/workflow-clarification.adoc @@ -16,9 +16,11 @@ Opinions and additional relevant information is welcome from anyone. If an editor is happy with the proposal, all they need to do is to reply "+1". Proposals with two or more +1's are approved. -When a proposal is approved, a new card is created in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga], in the __Article Spec__ column. +When a proposal is approved, a new card is created in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure], in the __IDEAS__ column. -When the card is created, add the __Role: Editorial board member__ group to the Watchers. This ensures editors are emailed when the card status changes, so someone can react. +When the card is created, add the __Assigne__, under the METADATA column. This ensures the author is emailed when the card status changes. + +Select __Create Issue__ and when the new card has been created, select the "pencil" icon in the METADATA column and add the *Tags* __article__ and __needs-image__. Do not add the tags before the new card has been created. This card now represents a specific article and goes through all the other steps of the workflow. diff --git a/modules/ROOT/pages/workflow-edit-image.adoc b/modules/ROOT/pages/workflow-edit-image.adoc index dacdca8..03f8688 100644 --- a/modules/ROOT/pages/workflow-edit-image.adoc +++ b/modules/ROOT/pages/workflow-edit-image.adoc @@ -10,7 +10,7 @@ Members of the Editorial Board provide both of those. == Editing -Articles that require editing are in the __To Edit__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. +Articles that require editing are in the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure]. Since multiple people will be potentially completing this step, they need to coordinate in comments in the card. @@ -18,20 +18,17 @@ Since multiple people will be potentially completing this step, they need to coo When done, indicate that in the comments. -If the cover image has also been done (that would be indicated by the absence of the __needs image__ tag), schedule the article in WordPress and move the card to the __Scheduled__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. - +If the cover image has also been done indicate that in the comments as well and remove the __needs-image__ tag by selecting the "pencil" icon in the METADATA colum and removing the tag. == Creating a cover image -Articles that require a cover image are in the __To Edit__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. +Articles that require a cover image are in the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure]. Since multiple people will be potentially completing this step, they need to coordinate in comments in the card. **Create a cover image** for the article. See the xref:creating-an-image.adoc[Creating a featured image] page for instructions. -When done, indicate that by removing the __needs image__ tag. - -If the editing has also been done (that would be indicated in the comments), schedule the article in WordPress and move the card to the __Scheduled__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. +When done, indicate that the image is complete in the comments and remove the __needs-image__ tag by selecting the "pencil" icon in the METADATA colum and removing the tag. == Workflow **Previous step:** xref:workflow-review.adoc[Review] diff --git a/modules/ROOT/pages/workflow-publishing.adoc b/modules/ROOT/pages/workflow-publishing.adoc index 51b0782..ad07578 100644 --- a/modules/ROOT/pages/workflow-publishing.adoc +++ b/modules/ROOT/pages/workflow-publishing.adoc @@ -8,10 +8,9 @@ A member of the Editorial board either publishes or schedules an article for pub == Publishing an article -Articles that are ready to be published are in the __Scheduled__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. +Articles that are ready to be published are in the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure]. -In preperation for the weekly editorial board meeting, the editor of the week will move cards for articles that have been published for at least one week from the __Scheduled__ column to the __Published (Archived)__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. -The cards are left in the __Scheduled__ column for at least one week so the author can use it to request post-publication revisions if necessary. +After publishing or scheduling them in Wordpress, move the card to the __SCHEDULED__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure]. This essentially archives the card. That's it! diff --git a/modules/ROOT/pages/workflow-review.adoc b/modules/ROOT/pages/workflow-review.adoc index c93b8c2..0fe5876 100644 --- a/modules/ROOT/pages/workflow-review.adoc +++ b/modules/ROOT/pages/workflow-review.adoc @@ -8,16 +8,15 @@ The Editorial Board makes a decision whether the article is ready to go. == Reviewing an article -Articles that are ready for review are in the __Review__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. +Articles that are ready for review are in the __REVIEW__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure]. === When article is good to go -If the article is good to go, a member of the Editorial Board simply moves it to the __To Edit__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. - +If the article is good to go, a member of the Editorial Board simply moves it to the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure]. === When article needs changes -If the article needs changes, a member of the Editorial Board provides feedback in the comments section of the respective card, and moves it back to the __In Progress__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. +If the article needs changes, a member of the Editorial Board provides feedback in the comments section of the respective card, and moves it back to the __IN-PROGRESS__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure]. == Workflow **Previous step:** xref:writing-an-article.adoc[Writing] diff --git a/modules/ROOT/pages/workflow.adoc b/modules/ROOT/pages/workflow.adoc index a901677..a9c80fe 100644 --- a/modules/ROOT/pages/workflow.adoc +++ b/modules/ROOT/pages/workflow.adoc @@ -13,10 +13,10 @@ Content on the Fedora Magazine is created using a 6-step workflow: 5. xref:workflow-edit-image.adoc[Edit & Image] by Editors 6. xref:workflow-publishing.adoc[Publishing] by Editors -An initial proposal lands in the __idea__ state. After some clarification, a specific article goes through 6 states starting as an __article spec__, progressing as __in progress__, __review__, __to edit__, __scheduled__, and finally ends up being __published__. Each step in the workflow has its own page in this documentation that provides guidance. +An initial proposal lands in the __idea__ state. After some clarification, a specific article goes through 5 states starting as an __IDEAS__, progressing as __IN-PROGRESS__, __REVIEW__, __TO-EDIT__, and finally ends up being __SCHEDULED__. Each step in the workflow has its own page in this documentation that provides guidance. == Tracking Proposals in the **__idea__** state are among the general discussion in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum]. Everyone is welcome to submit one! -Articles in **all other states** are represented as cards in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban section of the Fedora Magazine Taiga], each state having its own column on the board. Join our team either as a xref:contributing.adoc[writer] or as an xref:editorial.adoc[editor], and help us make wonderful content read by tens of thousands of readers every week! +Articles in **all other states** are represented as cards in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure], each state having its own column on the board. Join our team either as a xref:contributing.adoc[writer] or as an xref:editorial.adoc[editor], and help us make wonderful content read by tens of thousands of readers every week! From b672c1d3ec837a0500730998904c00aa90278a2a Mon Sep 17 00:00:00 2001 From: Richard England Date: Dec 29 2021 02:45:37 +0000 Subject: [PATCH 4/18] Updated Taiga references to Pagure and ammended process steps --- diff --git a/modules/ROOT/pages/writing-an-article.adoc b/modules/ROOT/pages/writing-an-article.adoc index 0ef289c..86b1f32 100644 --- a/modules/ROOT/pages/writing-an-article.adoc +++ b/modules/ROOT/pages/writing-an-article.adoc @@ -6,21 +6,22 @@ image::fedora-magazine-workflow-3.jpg[,100%,] Anyone with good writing skills is welcome to write an article for the Fedora Magazine! -__Writing an article requires write access to our https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Taiga board] (so you can indicate progress) and optionally to our https://fedoramagazine.org/admin[Wordpress instance] (if you choose to write it there). Read the xref:getting-access.adoc[Getting Access] page for more information.__ +__Writing an article requires write access to our +https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure] (so you can indicate progress and exchange information with the editors) and to our https://fedoramagazine.org/admin[Wordpress instance] (where the articles are written). Read the xref:getting-access.adoc[Getting Access] page for more information.__ == Writing an article === 1. Choose what to write -**Choose** any article you like in the __Article Spec__ column in the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban board in Fedora Magazine Taiga]. +**Choose** any article you like in the __IDEAS__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure]. -**Assign** the card you've chosen to yourself by opening the card and clicking on __Assign to myself__ on the right hand side. +**Assign** the card you've chosen to yourself by opening the card and selecting the "Pencil" icon in the METADATA c olumn on the right hand side. Click on the "None-Take" option under __Assignee__ will assign the card to you. -**Move it to __In Progress__** by simply dragging the card to the appropriate column. +**Move it to __IN-PROGRESS__** back in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure]. Simply drag the card to the appropriate column. === 2. Write it -**Write** your article either https://fedoramagazine.org/admin[in the Magazine Wordpress] (create a new article there) or anywhere you prefer. Wordpress, however, will be the easiest for the editors to review and publish later. Read the xref:writing-guidelines.adoc[Writing Guidelines] page for specific guidance about our preferred writing style. +**Write** your article in https://fedoramagazine.org/admin[in the Magazine Wordpress] (create a new article there). Read the xref:writing-guidelines.adoc[Writing Guidelines] page for specific guidance about our preferred writing style. https://fedoramagazine.org/how-to-structure-your-article/[Here’s a template you can use] to structure your article well, and make it as useful as possible to readers. Make sure you set the article status from __Pitch__ to __Draft__ once you receive approval. @@ -28,11 +29,11 @@ As you write your draft, try to understand and follow the xref:writing-guideline === 3. Mark it as done -**Move it to __Review__** when done with writing. Please include a link to Wordpress or to the text in the card before moving it to the __Review__ column so the Editors can access it. +**Move it to __REVIEW__** when done with writing. Please include a link to the Wordpress Preview for your article in the comments on the card before moving it to the __REVIEW__ column so the Editors can access it. And that's it! -Please note that in some cases the editors might require a change in your article. In that case, you'll receive feedback in the card, and it'll be moved back to the __In Progress__ column. In that case, please make the requested change and move it back to __Review__ when you're done. +Please note that in some cases the editors might require a change in your article. In that case, you'll receive feedback in the card, and it will be moved back to the __IN-PROGRESS__ column. Please make the requested change and move it back to __REVIEW__ when you are done. == Workflow **Previous step:** xref:workflow-clarification.adoc[Clarification] From 02cd3f792ae425fe7cd9e6118bf7c74cfcc1029a Mon Sep 17 00:00:00 2001 From: Richard England Date: Dec 29 2021 02:45:37 +0000 Subject: [PATCH 5/18] More Taiga to Pagure updates and necessary process changes. --- diff --git a/modules/ROOT/pages/creating-an-image.adoc b/modules/ROOT/pages/creating-an-image.adoc index bb20367..f3c5e07 100644 --- a/modules/ROOT/pages/creating-an-image.adoc +++ b/modules/ROOT/pages/creating-an-image.adoc @@ -86,6 +86,6 @@ Now use the helpful make target we’ve provided. This creates the correct sized $ make using-inkscape.jpg -Now you can post this file, using-inkscape.jpg, online, and then provide that URL in the comments section of your article's Taiga card for review. +Now you can post this file, using-inkscape.jpg, online, and then provide that URL in the comments section of your article's Pagure card for review. If the image is approved, and if it might be reused for later articles, then consider creating a pull request against the upstream repository to have your work archived for reuse. diff --git a/modules/ROOT/pages/editor-of-the-week.adoc b/modules/ROOT/pages/editor-of-the-week.adoc index d923b41..cbe339d 100644 --- a/modules/ROOT/pages/editor-of-the-week.adoc +++ b/modules/ROOT/pages/editor-of-the-week.adoc @@ -26,7 +26,7 @@ The Editor of the Week is expected to: * Routinely moderate comments (2-3 times a day is ideal) * Ensure the publication schedule is followed * Welcome new contributors -* Convert approved proposals to Taiga cards +* Convert approved proposals to Pagure cards * Chair the weekly xref:editorial-meetings.adoc[Magazine Editorial Board meeting] Note that Editors who are not the Editor of the Week may still perform the tasks above. diff --git a/modules/ROOT/pages/editorial-add-contributors.adoc b/modules/ROOT/pages/editorial-add-contributors.adoc index bf4b42d..ce241a3 100644 --- a/modules/ROOT/pages/editorial-add-contributors.adoc +++ b/modules/ROOT/pages/editorial-add-contributors.adoc @@ -2,18 +2,10 @@ A contributor must have a FAS account before starting. Once they do, editors should help them get necessary access to join the team. -The editor needs to be a member of the "admin" group in the Taiga team to complete this step. +The editor needs to be an "admin" in the Fedora Magazine Pagure site to complete this step. -== Adding to Taiga +== Adding to Pagure -Ask the contributor to login to the https://teams.fedoraproject.org[Taiga instance], using the OpenID option and their FAS account username and password. +Ask the contributor to login to the https://pagure.io/fedora-magazine-newsroom/boards/articles[Pagure instance], using the OpenID option and their FAS account username and password and let you know when they have done so by leaving a comment in their article card. -Find the user's email address. If you don't have that, you can find it through their contribution in the Magazine; their username there is also their FAS username. In Freenode IRC you can use this command: - -`/msg zodbot fasinfo ` - -Go to the https://teams.fedoraproject.org[Taiga instance] and in the Magazine project, go to __Admin__ > __Members__ in the navigation bar, and use the control to add a __New Member__. Enter the new contributor's FAS email address. - -Once added, provide the appropriate role, which is usually __Writer__ for a new contributor. - -Now you can assign the new user to Taiga cards as well, and they'll receive notifications as appropriate. \ No newline at end of file +Now you can assign the new user to Pagure cards, and they'll receive notifications as appropriate. diff --git a/modules/ROOT/pages/getting-access.adoc b/modules/ROOT/pages/getting-access.adoc index da19b6d..6785a1c 100644 --- a/modules/ROOT/pages/getting-access.adoc +++ b/modules/ROOT/pages/getting-access.adoc @@ -11,8 +11,8 @@ Note that contributors are required to sign the Fedora Project Contributor Agree https://fedoramagazine.org/wp-admin/[Sign in to the Fedora Magazine WordPress dashboard] using your Fedora Account. **3. Sign in to the Kanban board**: -https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Sign in to the Kanban board] using your Fedora Account. -This does NOT grant write access. It is, so the account is known to the system and can be manually granted privileges by an administrator after step 4. +https://pagure.io/fedora-magazine-newsroom/boards/articles[Sign in to the Pagure Kanban board] using your Fedora Account. +This does NOT grant write access. It is so the account is known to the system, cards can be assigned to you, and you can be manually granted privileges by an administrator after step 4. **4. Join the Magazine forum and introduce yourself**: Join the discussion in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum]. From 6b771ad5fe20fb899a0fc6ebd473696c8a30b902 Mon Sep 17 00:00:00 2001 From: Gregory Bartholomew Date: Dec 29 2021 02:45:37 +0000 Subject: [PATCH 6/18] Remove step six (publish) from the workflow --- diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-1.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-1.jpg index 14eb83f..488d742 100644 Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-1.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-1.jpg differ diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-2.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-2.jpg index 68fa2fd..84ce00f 100644 Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-2.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-2.jpg differ diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-3.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-3.jpg index 86b2436..ab31d68 100644 Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-3.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-3.jpg differ diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow.jpg index 866655a..85c88f4 100644 Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow.jpg differ diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index 359432f..bf295c4 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -5,7 +5,6 @@ ** xref:writing-an-article.adoc[3 Writing] ** xref:workflow-review.adoc[4 Review] ** xref:workflow-edit-image.adoc[5 Edit & Image] -** xref:workflow-publishing.adoc[6 Publishing] * xref:writing-a-pitch.adoc[Proposing Articles] * xref:contributing.adoc[Contributing as a Writer] ** xref:getting-access.adoc[Getting Access] diff --git a/modules/ROOT/pages/workflow-edit-image.adoc b/modules/ROOT/pages/workflow-edit-image.adoc index 03f8688..f8b5aeb 100644 --- a/modules/ROOT/pages/workflow-edit-image.adoc +++ b/modules/ROOT/pages/workflow-edit-image.adoc @@ -32,5 +32,3 @@ When done, indicate that the image is complete in the comments and remove the __ == Workflow **Previous step:** xref:workflow-review.adoc[Review] - -**Next step:** xref:workflow-publishing.adoc[Publishing] diff --git a/modules/ROOT/pages/workflow-publishing.adoc b/modules/ROOT/pages/workflow-publishing.adoc deleted file mode 100644 index ad07578..0000000 --- a/modules/ROOT/pages/workflow-publishing.adoc +++ /dev/null @@ -1,18 +0,0 @@ -= Publishing Articles - -include::partial$workflow-change-banner.adoc[] - -image::fedora-magazine-workflow-6.jpg[,100%,] - -A member of the Editorial board either publishes or schedules an article for publishing. - -== Publishing an article - -Articles that are ready to be published are in the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure]. - -After publishing or scheduling them in Wordpress, move the card to the __SCHEDULED__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure]. This essentially archives the card. - -That's it! - -== Workflow -**Previous step:** xref:workflow-edit-image.adoc[Edit & Image] diff --git a/modules/ROOT/pages/workflow.adoc b/modules/ROOT/pages/workflow.adoc index a9c80fe..13b4896 100644 --- a/modules/ROOT/pages/workflow.adoc +++ b/modules/ROOT/pages/workflow.adoc @@ -4,14 +4,13 @@ include::partial$workflow-change-banner.adoc[] image::fedora-magazine-workflow.jpg[,100%,] -Content on the Fedora Magazine is created using a 6-step workflow: +Content on the Fedora Magazine is created using a 5-step workflow: 1. xref:workflow-article-proposal.adoc[Article Proposal] by Anyone 2. xref:workflow-clarification.adoc[Clarification] by Editors 3. xref:writing-an-article.adoc[Writing] by a Writer 4. xref:workflow-review.adoc[Review] by Editors 5. xref:workflow-edit-image.adoc[Edit & Image] by Editors -6. xref:workflow-publishing.adoc[Publishing] by Editors An initial proposal lands in the __idea__ state. After some clarification, a specific article goes through 5 states starting as an __IDEAS__, progressing as __IN-PROGRESS__, __REVIEW__, __TO-EDIT__, and finally ends up being __SCHEDULED__. Each step in the workflow has its own page in this documentation that provides guidance. From eec3df135e87c2406d4c7085361e2dac061d03c7 Mon Sep 17 00:00:00 2001 From: Gregory Bartholomew Date: Dec 29 2021 02:45:37 +0000 Subject: [PATCH 7/18] Update the template svg --- diff --git a/graphics-sources/fedora-magazine-workflow.svg b/graphics-sources/fedora-magazine-workflow.svg index 5c35467..34cbcb9 100644 --- a/graphics-sources/fedora-magazine-workflow.svg +++ b/graphics-sources/fedora-magazine-workflow.svg @@ -7,7 +7,7 @@ viewBox="0 0 210 297" id="svg2" version="1.1" - inkscape:version="1.1 (c68e22c387, 2021-05-23)" + inkscape:version="1.1.1 (3bf5ae0d25, 2021-09-20)" sodipodi:docname="fedora-magazine-workflow.svg" xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd" @@ -94,20 +94,6 @@ - - - + id="g12442" + inkscape:export-filename="/home/gregory/fedora-magazine-workflow.png" + inkscape:export-xdpi="96" + inkscape:export-ydpi="96"> + style="fill:#f9f9f9;fill-opacity:1;stroke:none;stroke-width:0.661068;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" /> Edit & Image by editors - - Publishing - by editors + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">by editors Writing by a writer + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">by a writer idea + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">idea (proposed) article spec + sodipodi:role="line">idea (approved) scheduled - - published - @@ -562,7 +491,7 @@ sodipodi:role="line">Clarification by editors + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">by editors - 4 - 6 + id="g12572" + inkscape:export-filename="/home/gregory/fedora-magazine-workflow-1.png" + inkscape:export-xdpi="96" + inkscape:export-ydpi="96"> idea + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">idea (proposed) 1 + id="g14372" + inkscape:export-filename="/home/gregory/fedora-magazine-workflow-2.png" + inkscape:export-xdpi="96" + inkscape:export-ydpi="96"> Clarification by editors + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">by editors idea + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">idea (proposed) article spec + sodipodi:role="line">idea (approved) + id="g15528" + inkscape:export-filename="/home/gregory/fedora-magazine-workflow-3.png" + inkscape:export-xdpi="96" + inkscape:export-ydpi="96"> Writing by a writer + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">by a writer article spec + sodipodi:role="line">idea (approved) to edit - - - Publishing - by editors - - - 6 - - scheduled - - published - - Date: Dec 29 2021 02:45:37 +0000 Subject: [PATCH 8/18] Update the chat links to point to the new Matrix chat server --- diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc index f59361b..4fe40fa 100644 --- a/modules/ROOT/pages/editorial-meetings.adoc +++ b/modules/ROOT/pages/editorial-meetings.adoc @@ -6,7 +6,8 @@ The goal of this meeting is to set and execute a publishing schedule of appropri :hash: # -Meetings happen every week in the https://web.libera.chat/#fedora-meeting[{hash}fedora-meeting] channel on libera.chat. See the https://apps.fedoraproject.org/calendar/meeting/9224/[Fedora Magazine Editorial board meeting] in the Fedora calendar. +Meetings happen every week in the https://matrix.to/#/#magazine:fedoraproject.org?web-instance%5Belement.io%5D=chat.fedoraproject.org[{hash}magazine:fedoraproject.org] Matrix channel on chat.fedoraproject.org. +See the https://apps.fedoraproject.org/calendar/meeting/9224/[Fedora Magazine Editorial board meeting] in the Fedora calendar. Meetings are chaired by that week's xref:editor-of-the-week.adoc[Editor of the Week]. If the meeting time changes, be sure to update the link in this paragraph. diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc index 52792e6..c1e6c56 100644 --- a/modules/ROOT/pages/index.adoc +++ b/modules/ROOT/pages/index.adoc @@ -21,8 +21,10 @@ We really need your help on the Magazine. Consider xref:contributing.adoc[writin We also have regular xref:editorial-meetings.adoc[editorial board meetings]. -* IRC Channel: https://web.libera.chat/?channels=#fedora-magazine[#fedora-magazine] +:hash: # + * Forum: https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum] +* Matrix Channel: https://matrix.to/#/#magazine:fedoraproject.org?web-instance%5Belement.io%5D=chat.fedoraproject.org[{hash}magazine:fedoraproject.org] diff --git a/modules/ROOT/pages/writing-guidelines.adoc b/modules/ROOT/pages/writing-guidelines.adoc index 84a4aee..aabad66 100644 --- a/modules/ROOT/pages/writing-guidelines.adoc +++ b/modules/ROOT/pages/writing-guidelines.adoc @@ -96,4 +96,6 @@ If the shot is large, like a large browser window, app, or whole screen, choose == Other hints -Got an idea for better writing? Discuss with the editors on IRC Freenode at the #fedora-magazine channel. +:hash: # + +Got an idea for better writing? Discuss with the editors in the https://matrix.to/#/#magazine:fedoraproject.org?web-instance%5Belement.io%5D=chat.fedoraproject.org[{hash}magazine:fedoraproject.org] Matrix channel on chat.fedoraproject.org. From e0c5678d377be60d766e7cde4406967301750396 Mon Sep 17 00:00:00 2001 From: Richard England Date: Dec 29 2021 02:45:37 +0000 Subject: [PATCH 9/18] Typos corrected and Taiga URL changed to Pagure on one page --- diff --git a/modules/ROOT/pages/adding-a-writer.adoc b/modules/ROOT/pages/adding-a-writer.adoc index e0f88b9..62404f0 100644 --- a/modules/ROOT/pages/adding-a-writer.adoc +++ b/modules/ROOT/pages/adding-a-writer.adoc @@ -2,9 +2,9 @@ include::partial$workflow-change-banner.adoc[] -When a new writer joins the Magazine, they usually want to track their work in our kanban. Whether they take an existing article or suggest their own, an editor needs to add them to the kanban's list of permissions. +When a new writer joins the Magazine, they usually want to track their work in our kanban. -. Ask the writer to login to link:https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[the kanban instance] if they have not done so already. +. Ask the writer to login to link:https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Pagure instance] if they have not done so already. This will require that they have a Fedora Account System (FAS) login. . Find out the writer's Fedora Account System information. For instance, using link:https://fedoraproject.org/wiki/Zodbot[Zodbot] you can use the command `fasinfo `. . Follow the xref:technical-taiga.adoc#_adding_a_new_user[adding a new user] instructions . Optionally xref:technical-wordpress.adoc#_changing_a_users_role[promote the account] to the Author role in WordPress diff --git a/modules/ROOT/pages/workflow-clarification.adoc b/modules/ROOT/pages/workflow-clarification.adoc index 199583e..037d34f 100644 --- a/modules/ROOT/pages/workflow-clarification.adoc +++ b/modules/ROOT/pages/workflow-clarification.adoc @@ -18,7 +18,7 @@ If an editor is happy with the proposal, all they need to do is to reply "+1". P When a proposal is approved, a new card is created in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure], in the __IDEAS__ column. -When the card is created, add the __Assigne__, under the METADATA column. This ensures the author is emailed when the card status changes. +When the card is created, add the __Assignee__, under the METADATA column. This ensures the author is emailed when the card status changes. Select __Create Issue__ and when the new card has been created, select the "pencil" icon in the METADATA column and add the *Tags* __article__ and __needs-image__. Do not add the tags before the new card has been created. diff --git a/modules/ROOT/pages/writing-an-article.adoc b/modules/ROOT/pages/writing-an-article.adoc index 86b1f32..d2591f4 100644 --- a/modules/ROOT/pages/writing-an-article.adoc +++ b/modules/ROOT/pages/writing-an-article.adoc @@ -15,7 +15,7 @@ https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the F **Choose** any article you like in the __IDEAS__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure]. -**Assign** the card you've chosen to yourself by opening the card and selecting the "Pencil" icon in the METADATA c olumn on the right hand side. Click on the "None-Take" option under __Assignee__ will assign the card to you. +**Assign** the card you've chosen to yourself by opening the card and selecting the "Pencil" icon in the METADATA column on the right hand side. Click on the "None-Take" option under __Assignee__ will assign the card to you. **Move it to __IN-PROGRESS__** back in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure]. Simply drag the card to the appropriate column. From 7affa4da5500fe4bea2a31f734728339c0115fb8 Mon Sep 17 00:00:00 2001 From: Gregory Bartholomew Date: Dec 29 2021 02:45:37 +0000 Subject: [PATCH 10/18] Show in workflow diagram that WordPress publishes the article --- diff --git a/graphics-sources/fedora-magazine-workflow.svg b/graphics-sources/fedora-magazine-workflow.svg index 34cbcb9..292b273 100644 --- a/graphics-sources/fedora-magazine-workflow.svg +++ b/graphics-sources/fedora-magazine-workflow.svg @@ -11,6 +11,7 @@ sodipodi:docname="fedora-magazine-workflow.svg" xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" @@ -145,15 +146,15 @@ inkscape:pageopacity="0.0" inkscape:pageshadow="2" inkscape:zoom="0.65388608" - inkscape:cx="1631.7827" - inkscape:cy="1192.8683" + inkscape:cx="1726.6005" + inkscape:cy="2459.9086" inkscape:document-units="mm" inkscape:current-layer="layer1" showgrid="false" inkscape:window-width="1920" - inkscape:window-height="1015" + inkscape:window-height="1020" inkscape:window-x="0" - inkscape:window-y="0" + inkscape:window-y="32" inkscape:window-maximized="1" showguides="false" inkscape:pagecheckerboard="0" /> @@ -173,446 +174,362 @@ inkscape:groupmode="layer" id="layer1"> + height="48.11499" + x="308.18182" + y="201.04749" + rx="4.99999" + ry="4.99999" /> + height="21.155079" + x="-434.09418" + y="214.58308" + rx="5" + ry="5" + transform="scale(-1,1)" /> Edit & Image + y="222.92404" + style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Bold';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">Article proposal by editors + id="tspan14622" + sodipodi:role="line">by anyone Review + id="tspan14628" + x="438.82303" + y="227.47343" + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">idea (proposed) + + by editors + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:14.1111px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;fill:#ffffff;stroke-width:0.264583px" + y="229.85188" + x="337.47092" + id="tspan14636" + sodipodi:role="line">1 + + + Writing + id="tspan14748" + sodipodi:role="line">Clarification by a writer - - Article proposal + y="298.3587" + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">by editors + + by anyone - + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:14.1111px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;fill:#ffffff;stroke-width:0.264583px" + y="296.93176" + x="337.47092" + id="tspan14772" + sodipodi:role="line">2 idea (proposed) idea (approved) + + + + y="354.36618" + x="-434.09418" + height="42.857365" + width="103.00813" + id="rect14668" + style="fill:#e6e6e6;fill-opacity:1;stroke:none;stroke-width:1;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" /> + Writing in progress + id="tspan14676" + x="396.99249" + y="381.66806" + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">by a writer review + y="356.56238" + x="438.87241" + id="tspan14682" + sodipodi:role="line">idea (approved) to edit + id="tspan14688" + x="445.28943" + y="377.6868" + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">in progress scheduled - - - + y="399.52756" + x="451.36777" + id="tspan14694" + sodipodi:role="line">review - - Clarification - by editors - - - - - - 1 3 - 5 - 2 - 4 + id="g28831" + inkscape:export-filename="/home/gregory/Repositories/fedora-magazine/modules/ROOT/assets/images/fedora-magazine-workflow-4.png" + inkscape:export-xdpi="170.37" + inkscape:export-ydpi="170.37"> + y="429.69043" + x="308.18182" + height="81.465591" + width="305.3287" + id="rect15153" + style="fill:#f9f9f9;fill-opacity:1;stroke:none;stroke-width:0.7;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" /> @@ -620,453 +537,2186 @@ xml:space="preserve" style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:0%;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;letter-spacing:0px;word-spacing:0px;text-anchor:end;fill:#000000;fill-opacity:1;stroke:none;stroke-width:0.264583px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1" x="396.90152" - y="222.92404" - id="text14616">Article proposal + y="467.84222" + style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Bold';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">Review by anyone + id="tspan14862" + sodipodi:role="line">by editors + + + + 4 idea (proposed) - - + id="tspan14720" + x="445.28943" + y="450.90689" + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">in progress + 1 + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px" + y="472.74765" + x="451.36777" + id="tspan14726" + sodipodi:role="line">review + + to edit + + id="g186097" + inkscape:export-filename="/home/gregory/fedora-magazine-workflow.png" + inkscape:export-xdpi="170.37" + inkscape:export-ydpi="170.37"> + id="rect15064" + style="fill:#f9f9f9;fill-opacity:1;stroke:none;stroke-width:0.661068;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" /> Clarification + id="tspan13098" + sodipodi:role="line">Edit & Image + by editors + + Review + by editors + + Writing + by a writer + by editors - - + id="tspan12890" + x="396.90152" + y="36.90889" + style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Bold';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">Article proposal 2 + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px" + y="45.26368" + x="396.99249" + id="tspan12894" + sodipodi:role="line">by anyone + idea (proposed) idea (approved) - - - - Writing + ry="5" /> by a writer + id="tspan8101" + x="444.76117" + y="83.10939" + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">in progress idea (approved) + y="104.95016" + x="450.83951" + id="tspan8111" + sodipodi:role="line">review in progress + id="tspan8121" + x="451.16406" + y="126.12334" + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;stroke-width:0.264583px">to edit + scheduled + + + + + + + Clarification + review + x="523.56708" + y="55.740646" + id="text12882">by editors - + id="path13198" + d="m 421.09827,125.61616 c -5.35781,2.13739 -6.67873,5.87881 -6.68073,8.72284 -0.002,2.77139 1.65365,4.9102 6.08542,7.79855" + style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:2.265;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1;marker-end:url(#marker13200)" /> + + + + + 1 3 - - - - + 5 Review - by editors - - - + id="tspan13616" + x="591.20636" + y="54.407677" + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:14.1111px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;fill:#ffffff;stroke-width:0.264583px">2 4 - + in progress - + id="tspan1119" + x="558.07574" + y="142.45032" + style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Bold';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">Publication review - - to edit + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px" + y="150.80511" + x="562.35132" + id="tspan1123" + sodipodi:role="line">by WordPress + + Edit & Image by editors + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7.05556px;line-height:1.25;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Normal';font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-east-asian:normal;text-align:end;text-anchor:end;stroke-width:0.264583px">by editors to edit + 5 + + Publication + by WordPress + + diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow-5.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow-5.jpg index 7426150..b43c7c4 100644 Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow-5.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow-5.jpg differ diff --git a/modules/ROOT/assets/images/fedora-magazine-workflow.jpg b/modules/ROOT/assets/images/fedora-magazine-workflow.jpg index 85c88f4..4deea88 100644 Binary files a/modules/ROOT/assets/images/fedora-magazine-workflow.jpg and b/modules/ROOT/assets/images/fedora-magazine-workflow.jpg differ From 385475a349c31b25b1ff6c8b76d8bbbdb4b951ed Mon Sep 17 00:00:00 2001 From: Richard England Date: Dec 29 2021 02:45:38 +0000 Subject: [PATCH 11/18] More fixes for types etc. --- diff --git a/modules/ROOT/pages/adding-a-writer.adoc b/modules/ROOT/pages/adding-a-writer.adoc index 62404f0..94814e9 100644 --- a/modules/ROOT/pages/adding-a-writer.adoc +++ b/modules/ROOT/pages/adding-a-writer.adoc @@ -5,6 +5,6 @@ include::partial$workflow-change-banner.adoc[] When a new writer joins the Magazine, they usually want to track their work in our kanban. . Ask the writer to login to link:https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Pagure instance] if they have not done so already. This will require that they have a Fedora Account System (FAS) login. +. Have the writer gfet a Fedora Account, if they don’t already have one. They can link:https://accounts.fedoraproject.org/#register[sign up here]. Remind them that contributors are required to sign the Fedora Project Contributor Agreement (FPCA). . Find out the writer's Fedora Account System information. For instance, using link:https://fedoraproject.org/wiki/Zodbot[Zodbot] you can use the command `fasinfo `. -. Follow the xref:technical-taiga.adoc#_adding_a_new_user[adding a new user] instructions -. Optionally xref:technical-wordpress.adoc#_changing_a_users_role[promote the account] to the Author role in WordPress +. Follow these ihstructions to xref:technical-wordpress.adoc#_changing_a_users_role[promote the account] to the Author role in WordPress. diff --git a/modules/ROOT/pages/workflow-article-proposal.adoc b/modules/ROOT/pages/workflow-article-proposal.adoc index 7d38869..d445e9b 100644 --- a/modules/ROOT/pages/workflow-article-proposal.adoc +++ b/modules/ROOT/pages/workflow-article-proposal.adoc @@ -12,7 +12,7 @@ Proposals can be ideas or specific pitches (an example is below). Proposing an a Join the community in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum] and submit your idea as a new topic. -TIP: If this is your first proposal, and you also plan to write an article, you can help us speed the process up by logging into our https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure] — Select the __Log In__ button to log in with your Fedora Account. That is required before we can assign and article to you. +TIP: If this is your first proposal, and you also plan to write an article, you can help us speed the process up by logging into our https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure] — Select the __Log In__ button to log in with your Fedora Account. That is required before we can assign an article to you. == A specific pitch example From dfc0480bbb8c6098120695e98f8c08726e7e15bf Mon Sep 17 00:00:00 2001 From: Richard England Date: Dec 29 2021 02:45:38 +0000 Subject: [PATCH 12/18] typos and clarifications --- diff --git a/modules/ROOT/pages/adding-a-writer.adoc b/modules/ROOT/pages/adding-a-writer.adoc index 94814e9..cfcae05 100644 --- a/modules/ROOT/pages/adding-a-writer.adoc +++ b/modules/ROOT/pages/adding-a-writer.adoc @@ -7,4 +7,4 @@ When a new writer joins the Magazine, they usually want to track their work in o . Ask the writer to login to link:https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Pagure instance] if they have not done so already. This will require that they have a Fedora Account System (FAS) login. . Have the writer gfet a Fedora Account, if they don’t already have one. They can link:https://accounts.fedoraproject.org/#register[sign up here]. Remind them that contributors are required to sign the Fedora Project Contributor Agreement (FPCA). . Find out the writer's Fedora Account System information. For instance, using link:https://fedoraproject.org/wiki/Zodbot[Zodbot] you can use the command `fasinfo `. -. Follow these ihstructions to xref:technical-wordpress.adoc#_changing_a_users_role[promote the account] to the Author role in WordPress. +. Follow these instructions to xref:technical-wordpress.adoc#_changing_a_users_role[promote the account] to the Author role in WordPress. diff --git a/modules/ROOT/pages/workflow-article-proposal.adoc b/modules/ROOT/pages/workflow-article-proposal.adoc index d445e9b..31f2c88 100644 --- a/modules/ROOT/pages/workflow-article-proposal.adoc +++ b/modules/ROOT/pages/workflow-article-proposal.adoc @@ -12,7 +12,7 @@ Proposals can be ideas or specific pitches (an example is below). Proposing an a Join the community in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum] and submit your idea as a new topic. -TIP: If this is your first proposal, and you also plan to write an article, you can help us speed the process up by logging into our https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure] — Select the __Log In__ button to log in with your Fedora Account. That is required before we can assign an article to you. +TIP: If this is your first proposal, and you also plan to write an article, you can help us speed the process up by logging into our https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure] — Select the __Log In__ button to log in with your Fedora Account. That is required before an article can be assign to you. == A specific pitch example From 427dd655a417a80ad1983b721c602f79eb64a32e Mon Sep 17 00:00:00 2001 From: Richard England Date: Dec 29 2021 02:45:38 +0000 Subject: [PATCH 13/18] another typo --- diff --git a/modules/ROOT/pages/adding-a-writer.adoc b/modules/ROOT/pages/adding-a-writer.adoc index cfcae05..47b3593 100644 --- a/modules/ROOT/pages/adding-a-writer.adoc +++ b/modules/ROOT/pages/adding-a-writer.adoc @@ -5,6 +5,6 @@ include::partial$workflow-change-banner.adoc[] When a new writer joins the Magazine, they usually want to track their work in our kanban. . Ask the writer to login to link:https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Pagure instance] if they have not done so already. This will require that they have a Fedora Account System (FAS) login. -. Have the writer gfet a Fedora Account, if they don’t already have one. They can link:https://accounts.fedoraproject.org/#register[sign up here]. Remind them that contributors are required to sign the Fedora Project Contributor Agreement (FPCA). +. Have the writer setup a Fedora Account, if they don’t already have one. They can link:https://accounts.fedoraproject.org/#register[sign up here]. Remind them that contributors are required to sign the Fedora Project Contributor Agreement (FPCA). . Find out the writer's Fedora Account System information. For instance, using link:https://fedoraproject.org/wiki/Zodbot[Zodbot] you can use the command `fasinfo `. . Follow these instructions to xref:technical-wordpress.adoc#_changing_a_users_role[promote the account] to the Author role in WordPress. From db033708a1c2943a67acc8cfcf40000b0d51c1fe Mon Sep 17 00:00:00 2001 From: Richard England Date: Dec 29 2021 02:45:38 +0000 Subject: [PATCH 14/18] Typo's (I really am not seeing what I type :-/ ) --- diff --git a/modules/ROOT/pages/adding-a-writer.adoc b/modules/ROOT/pages/adding-a-writer.adoc index 47b3593..b1a95e4 100644 --- a/modules/ROOT/pages/adding-a-writer.adoc +++ b/modules/ROOT/pages/adding-a-writer.adoc @@ -5,6 +5,6 @@ include::partial$workflow-change-banner.adoc[] When a new writer joins the Magazine, they usually want to track their work in our kanban. . Ask the writer to login to link:https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Pagure instance] if they have not done so already. This will require that they have a Fedora Account System (FAS) login. -. Have the writer setup a Fedora Account, if they don’t already have one. They can link:https://accounts.fedoraproject.org/#register[sign up here]. Remind them that contributors are required to sign the Fedora Project Contributor Agreement (FPCA). +. Have the writer set up a Fedora Account, if they don’t already have one. They can link:https://accounts.fedoraproject.org/#register[sign up here]. Remind them that contributors are required to sign the Fedora Project Contributor Agreement (FPCA). . Find out the writer's Fedora Account System information. For instance, using link:https://fedoraproject.org/wiki/Zodbot[Zodbot] you can use the command `fasinfo `. . Follow these instructions to xref:technical-wordpress.adoc#_changing_a_users_role[promote the account] to the Author role in WordPress. From 7c5dd11e6ca3ea2f08251bcaae0fbd2a4c5b2ca9 Mon Sep 17 00:00:00 2001 From: Richard England Date: Dec 29 2021 02:45:38 +0000 Subject: [PATCH 15/18] Reconciled process with Pagure. Added new Pagure tech page --- diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index bf295c4..c59e2d2 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -18,5 +18,5 @@ ** xref:adding-a-writer.adoc[Adding a Writer] * xref:technical.adoc[Technical Notes and Processes] ** xref:technical-theme.adoc[Maintaining the Theme] -** xref:technical-taiga.adoc[Taiga Operations] +** xref:technical-pagure.adoc[Pagure Operations] ** xref:technical-wordpress.adoc[WordPress Operations] diff --git a/modules/ROOT/pages/contributing.adoc b/modules/ROOT/pages/contributing.adoc index aeea037..4353704 100644 --- a/modules/ROOT/pages/contributing.adoc +++ b/modules/ROOT/pages/contributing.adoc @@ -5,10 +5,11 @@ include::partial$workflow-change-banner.adoc[] Fedora Magazine welcomes new writers to contribute their skill by writing an article or two... or five! There are several ways you can find something to write about: * We have a list of specific topics to start with — so you don't need to come up with new ideas to write. +See the __IDEAS__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Kanban board]. * You can also xref:writing-a-pitch.adoc[propose an article] if you have your own idea. Either way, your writing goes out to tens of thousands of readers that visit Fedora Magazine every week! If this is your first contribution, you will need to xref:getting-access.adoc[get access] first. -**Need help on how to write better? See the xref:writing-an-article.adoc[Editorial Workflow - Writing] page for guidance.** \ No newline at end of file +**Need help on how to write better? See the xref:writing-an-article.adoc[Editorial Workflow - Writing] page for guidance.** diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc index 4fe40fa..bfb4d3b 100644 --- a/modules/ROOT/pages/editorial-meetings.adoc +++ b/modules/ROOT/pages/editorial-meetings.adoc @@ -55,11 +55,11 @@ First, let's look back at the previous week in terms of pageviews. This data can #topic 2/ In progress followup #info Looking at the 'in progress' column, is there something that's been finished? Anything to follow up on with its author? - #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban + #link Board: https://pagure.io/fedora-magazine-newsroom/boards/articles Review anything that's in progress. If an article is stuck in progress for a long time without an update, contact the author and ask them if they still plan to finish their work. -Anything that's already finished can be moved to the Finished column. +Anything that's already finished and commented so by the author can be moved to the "REVIEW" column. You may also want to check the QA calendar for upcoming test days so that we can expect a new post submission. These tend to come in with very short notice, so the Editor of the Week should use their best judgment in deciding when to publish. @@ -78,17 +78,19 @@ This is generally only important a few weeks before the Beta and Final releases, === 3/ Finished articles to review #topic 3/ Finished articles to review - #info Looking at the 'review' column, let's decide which articles are good to go. Move each either to the 'to edit' (finished) or to the 'in progress' (needs more work) and provide feedback. - #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban + #info Looking at the 'REVIEW' column, let's decide which articles are good to go. Move each either to the 'TO-EDIT' or to the 'IN-PROGRESS' (needs more work) and provide feedback. + #link Board: https://pagure.io/fedora-magazine-newsroom/boards/articles -Authors mark their articles as finished by moving them to this column. Review the articles and ehtier move them to the To Edit column, or in case they need some additional work, ask the author in the card about it and move it back the In Progress. +Authors mark their articles as finished by adding a comment announcing that fact. Review the articles +and ethier move them to the 'TO-EDIT' column, or in case they need some additional work, ask the +author in the card about it and move it back to 'IN-PROGRESS'. === 4/ Articles to edit #topic 4/ Articles to edit - #info Looking at the 'to edit' column, assign an editor and a cover image creator. - #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban + #info Looking at the 'TO-EDIT' column, assign an editor and a cover image creator. + #link Board: https://pagure.io/fedora-magazine-newsroom/boards/articles Assign an editor and a cover image designer to each article so it can be moved forward. @@ -96,9 +98,9 @@ Assign an editor and a cover image designer to each article so it can be moved f === 5/ Publishing schedule #topic 5/ Publishing schedule - #info Looking at the 'to edit' column, decide the publishing schedule for the next week. - #info If there is not enough content, we might also need to look at the 'in progress' or even the 'article spec' columns come up with additional content. - #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban + #info Looking at the 'TO-EDIT' column, decide the publishing schedule for the next week. + #info If there is not enough content, we might also need to look at the 'IN-PROGRESS' or even the 'IDEAS' columns to come up with additional content. + #link Board: https://pagure.io/fedora-magazine-newsroom/boards/articles Setting the publishing schedule for the upcoming week period is one of the main goals of this meeting. @@ -115,7 +117,7 @@ This can be generated by a script. Run: $ podman run --rm -it asamalik/magazine-schedule -The script consumes data from the individual cards, so please make sure the date, and the assignees are set properly. +The script consumes data from the individual cards, so please make sure the date, and the editorrial assignees are set properly. Find more information about the script in the https://github.com/asamalik/magazine-schedule[asamalik/magazine-schedule github repository]. diff --git a/modules/ROOT/pages/getting-access.adoc b/modules/ROOT/pages/getting-access.adoc index 6785a1c..0bd1cb6 100644 --- a/modules/ROOT/pages/getting-access.adoc +++ b/modules/ROOT/pages/getting-access.adoc @@ -12,11 +12,12 @@ https://fedoramagazine.org/wp-admin/[Sign in to the Fedora Magazine WordPress da **3. Sign in to the Kanban board**: https://pagure.io/fedora-magazine-newsroom/boards/articles[Sign in to the Pagure Kanban board] using your Fedora Account. -This does NOT grant write access. It is so the account is known to the system, cards can be assigned to you, and you can be manually granted privileges by an administrator after step 4. +This does NOT grant write access. It is so the account is known to the system and cards can be assigned to you. **4. Join the Magazine forum and introduce yourself**: Join the discussion in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum]. This is where we discuss everything to do with the Fedora Magazine. Introduce yourself and tell us that you wish to contribute to the Fedora Magazine. -A Fedora Magazine editor will then grant you access to create and edit posts, and submit them for review. +The Fedora Magazine editors monitor this Discourse forum and will be able to help you and answer any Fedora +Magazine related questions. diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc index c1e6c56..e93236b 100644 --- a/modules/ROOT/pages/index.adoc +++ b/modules/ROOT/pages/index.adoc @@ -2,7 +2,7 @@ include::partial$workflow-change-banner.adoc[] -http://fedoramagazine.org[Fedora Magazine] is a WordPress-based site which delivers all the news of the Fedora Community. (It replaced the older publication, Fedora Weekly News.) +http://fedoramagazine.org[Fedora Magazine] is a __WordPress-based__ site which delivers all the news of the Fedora Community. (It replaced the older publication, Fedora Weekly News.) == What does the Magazine publish? diff --git a/modules/ROOT/pages/technical-pagure.adoc b/modules/ROOT/pages/technical-pagure.adoc new file mode 100644 index 0000000..fe99339 --- /dev/null +++ b/modules/ROOT/pages/technical-pagure.adoc @@ -0,0 +1,76 @@ += Pagure Operations + +== Adding a new user + +If an author has not accessed Pagure before, they must login +with their https://accounts.fedoraproject.org/#register[FAS account]. +The https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine site is here]. +They will need to select the *Log in* button in the upper right corner of the page. +This will allow the editors to assign cards to them. + +There is nothing more to do administratively. + +== Creating a new card (user story) + +When a proposal is approved, follow these steps. + +. From the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban page], +select the *New issues* button (upper right corner). +. Enter the title of the article in the top text box +. Enter details of the proposal in the bottom text box. __Include a link to the proposal +discussion__, where appropriate +. If an author has been identified and has logged in to Pagure, select the *Assignee* +text box in the METADATA column at the right and locate their name +. Select *Create Issue* at the bottom of the page + +When the new issue has been created, continue with these steps. + +. Select the "pencil icon" at the top of the METADATA column at the right +. In the *Tags* selection field select "article" and "needs-image" +. Select *Update* at the bottom of the METADATA column. + +The new card should appear at the bottom of the Kanban *IDEAS* column. If it does +not you can add it by selecting the *+* at the top of the *IDEAS* column and entering the +new "Issue" number. + +If you do not know the "Issue" number, select *Issues* at the top of the Kanban +page and locate it in the list of issues. + +== Changing the state of the cards + +Authors must indicate, in the comments of each card, when they feel the state needs +to change from __IDEAS__ to __IN-PROGRESS__ to __REVIEW__. + +The editors will change the state by "dragging" the cards on the Kanban page as needed. + +The editors will determine when the articles are ready to move to __TO EDIT__, drag +the cards on the Kanban board, and add a comment to that effect to inform the author. + +== Adding editors + +Editors should be admins on the board. You must be an Administrator to add an editor. + +Use the following steps. + +. On the Kanban page, select the *Settings* tab at the top of the Pagure page +. Select *Users & Groups* from the list in the left column on this page +. Select *add user* +. Type in the FAS "Username" in the first text field, to search. Note that the user must +have logged into Pagure prior to this operation for the name to be available +. Set the next field (a selection field) to *Admin* +. Select *Add* + +== Removing editors + +You must be an Administrator to remove an editor. + +Use the following steps. + +. On the Kanban page, select the *Settings* tab at the top of the Pagure page. +. Select *Users & Groups* from the list in the left column on this page. +. Locate the name of the admin to remove and select the red "trash can" icon at the right +of the name + + +NOTE: Update the https://pagure.io/group/fedora-magazine[Pagure group] membership as well +so that the docs and images repos have the correct permissions. diff --git a/modules/ROOT/pages/technical.adoc b/modules/ROOT/pages/technical.adoc index e079614..53d1341 100644 --- a/modules/ROOT/pages/technical.adoc +++ b/modules/ROOT/pages/technical.adoc @@ -2,4 +2,6 @@ The Magazine site itself is simply a https://wordpress.org[WordPress site]. Like any website, it may require maintenance from time to time. +Pagure is the system used to track the status of cards ("Issues") for the articles. + One system that sometimes requires changes or fixes is the https://pagure.io/fedoramagazine-theme[Magazine theme]. There is a process to xref:technical-theme.adoc[modify, test, and deploy theme changes]. diff --git a/modules/ROOT/pages/workflow-article-proposal.adoc b/modules/ROOT/pages/workflow-article-proposal.adoc index 31f2c88..f8acab7 100644 --- a/modules/ROOT/pages/workflow-article-proposal.adoc +++ b/modules/ROOT/pages/workflow-article-proposal.adoc @@ -12,7 +12,7 @@ Proposals can be ideas or specific pitches (an example is below). Proposing an a Join the community in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum] and submit your idea as a new topic. -TIP: If this is your first proposal, and you also plan to write an article, you can help us speed the process up by logging into our https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure] — Select the __Log In__ button to log in with your Fedora Account. That is required before an article can be assign to you. +TIP: If this is your first proposal, and you also plan to write an article, you can help us speed the process up by logging into our https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure] — Select the __Log In__ button to log in with your Fedora Account. That is required before an article can be assigned to you. == A specific pitch example diff --git a/modules/ROOT/pages/workflow-clarification.adoc b/modules/ROOT/pages/workflow-clarification.adoc index 037d34f..bea2929 100644 --- a/modules/ROOT/pages/workflow-clarification.adoc +++ b/modules/ROOT/pages/workflow-clarification.adoc @@ -16,11 +16,9 @@ Opinions and additional relevant information is welcome from anyone. If an editor is happy with the proposal, all they need to do is to reply "+1". Proposals with two or more +1's are approved. -When a proposal is approved, a new card is created in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure], in the __IDEAS__ column. +When a proposal is approved, a new card is created by an editor in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure], in the __IDEAS__ column. -When the card is created, add the __Assignee__, under the METADATA column. This ensures the author is emailed when the card status changes. - -Select __Create Issue__ and when the new card has been created, select the "pencil" icon in the METADATA column and add the *Tags* __article__ and __needs-image__. Do not add the tags before the new card has been created. +When the card is created, and the author is known, the owner is assigned in the __Assignee__ field, under the METADATA column. This ensures the author is emailed when the card status changes. This operation is performed by the editor. This card now represents a specific article and goes through all the other steps of the workflow. diff --git a/modules/ROOT/pages/workflow-edit-image.adoc b/modules/ROOT/pages/workflow-edit-image.adoc index f8b5aeb..82d2b63 100644 --- a/modules/ROOT/pages/workflow-edit-image.adoc +++ b/modules/ROOT/pages/workflow-edit-image.adoc @@ -10,25 +10,26 @@ Members of the Editorial Board provide both of those. == Editing -Articles that require editing are in the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure]. +Articles that require editing are in the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure]. -Since multiple people will be potentially completing this step, they need to coordinate in comments in the card. +Since multiple people will be potentially completing this step, they need to coordinate with comments on the card. -**Edit** the article for potential grammatical and spelling errors. +The editors will **Edit** the article for potential grammatical and spelling errors. +When done, they indicate that in the comments. -When done, indicate that in the comments. - -If the cover image has also been done indicate that in the comments as well and remove the __needs-image__ tag by selecting the "pencil" icon in the METADATA colum and removing the tag. +If the cover image has also been done that will be indicated in the comments as well and the __needs-image__ tag will be removed from the METADATA column. == Creating a cover image -Articles that require a cover image are in the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure]. +Articles that require a cover image are in the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure]. -Since multiple people will be potentially completing this step, they need to coordinate in comments in the card. +Since multiple people will potentially be completing this step, they need to coordinate with comments on the card. -**Create a cover image** for the article. See the xref:creating-an-image.adoc[Creating a featured image] page for instructions. +To **Create a cover image** for the article, see the xref:creating-an-image.adoc[Creating a featured image] +page for instructions. This function is usually done by an editor but the author may take on this task if +they have a specific idea. Please carefully read over xref:creating-an-image.adoc[Creating a featured image] for restriction on form and source for any image used. -When done, indicate that the image is complete in the comments and remove the __needs-image__ tag by selecting the "pencil" icon in the METADATA colum and removing the tag. +When the image is done this will be indicated in the comments and the __needs-image__ tag will be remove from the METADATA column by an editor. == Workflow **Previous step:** xref:workflow-review.adoc[Review] diff --git a/modules/ROOT/pages/workflow-review.adoc b/modules/ROOT/pages/workflow-review.adoc index 0fe5876..934dab5 100644 --- a/modules/ROOT/pages/workflow-review.adoc +++ b/modules/ROOT/pages/workflow-review.adoc @@ -8,15 +8,15 @@ The Editorial Board makes a decision whether the article is ready to go. == Reviewing an article -Articles that are ready for review are in the __REVIEW__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure]. +Articles that are ready for review are in the __REVIEW__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure]. === When article is good to go -If the article is good to go, a member of the Editorial Board simply moves it to the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure]. +If the article is good to go, a member of the Editorial Board simply moves it to the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board]. === When article needs changes -If the article needs changes, a member of the Editorial Board provides feedback in the comments section of the respective card, and moves it back to the __IN-PROGRESS__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure]. +If the article needs changes, a member of the Editorial Board provides feedback in the comments section of the respective card, and moves it back to the __IN-PROGRESS__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board]. == Workflow **Previous step:** xref:writing-an-article.adoc[Writing] diff --git a/modules/ROOT/pages/workflow.adoc b/modules/ROOT/pages/workflow.adoc index 13b4896..656720d 100644 --- a/modules/ROOT/pages/workflow.adoc +++ b/modules/ROOT/pages/workflow.adoc @@ -12,10 +12,12 @@ Content on the Fedora Magazine is created using a 5-step workflow: 4. xref:workflow-review.adoc[Review] by Editors 5. xref:workflow-edit-image.adoc[Edit & Image] by Editors -An initial proposal lands in the __idea__ state. After some clarification, a specific article goes through 5 states starting as an __IDEAS__, progressing as __IN-PROGRESS__, __REVIEW__, __TO-EDIT__, and finally ends up being __SCHEDULED__. Each step in the workflow has its own page in this documentation that provides guidance. +An initial proposal lands in the __idea__ state. After some clarification, a specific article goes through 5 states. Starting as an __idea__, it progresses to __in progress__, __review__, __to edit__, and finally ending up being __scheduled__. Each step in the workflow has its own page in this documentation that provides guidance. == Tracking Proposals in the **__idea__** state are among the general discussion in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum]. Everyone is welcome to submit one! -Articles in **all other states** are represented as cards in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure], each state having its own column on the board. Join our team either as a xref:contributing.adoc[writer] or as an xref:editorial.adoc[editor], and help us make wonderful content read by tens of thousands of readers every week! +Articles in **all other states** are represented as cards in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure]. Each state has its own column on the board with the appropriate title. + +Join our team either as a xref:contributing.adoc[writer] or as an xref:editorial.adoc[editor], and help us make wonderful content read by tens of thousands of readers every week! diff --git a/modules/ROOT/pages/writing-an-article.adoc b/modules/ROOT/pages/writing-an-article.adoc index d2591f4..bfe5405 100644 --- a/modules/ROOT/pages/writing-an-article.adoc +++ b/modules/ROOT/pages/writing-an-article.adoc @@ -7,21 +7,25 @@ image::fedora-magazine-workflow-3.jpg[,100%,] Anyone with good writing skills is welcome to write an article for the Fedora Magazine! __Writing an article requires write access to our -https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure] (so you can indicate progress and exchange information with the editors) and to our https://fedoramagazine.org/admin[Wordpress instance] (where the articles are written). Read the xref:getting-access.adoc[Getting Access] page for more information.__ +https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Pagure] (so you can indicate progress and exchange information with the editors) and to our https://fedoramagazine.org/admin[Wordpress instance] (where the articles are written). Read the xref:getting-access.adoc[Getting Access] page for more information.__ == Writing an article === 1. Choose what to write -**Choose** any article you like in the __IDEAS__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure]. +**Choose** any article you like in the __IDEAS__ column in the +https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure]. +Or, https://docs.fedoraproject.org/en-US/fedora-magazine/workflow-article-proposal/[propose your own]. -**Assign** the card you've chosen to yourself by opening the card and selecting the "Pencil" icon in the METADATA column on the right hand side. Click on the "None-Take" option under __Assignee__ will assign the card to you. +**Assign** Open a topic, if necessary in the the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum], and let the editors know you would like to be the author of an article. +Make certain you tell them the number. If you have been in contact with the editors regarding an article, simply let them know in your ongoing conversation. -**Move it to __IN-PROGRESS__** back in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure]. Simply drag the card to the appropriate column. +The editors will assign the article to you and move it to **__IN-PROGRESS__** in the +https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Kanban board]. === 2. Write it -**Write** your article in https://fedoramagazine.org/admin[in the Magazine Wordpress] (create a new article there). Read the xref:writing-guidelines.adoc[Writing Guidelines] page for specific guidance about our preferred writing style. +**Write** your article https://fedoramagazine.org/admin[in the Magazine Wordpress] (create a new article there). Read the xref:writing-guidelines.adoc[Writing Guidelines] page for specific guidance about our preferred writing style. https://fedoramagazine.org/how-to-structure-your-article/[Here’s a template you can use] to structure your article well, and make it as useful as possible to readers. Make sure you set the article status from __Pitch__ to __Draft__ once you receive approval. @@ -29,11 +33,11 @@ As you write your draft, try to understand and follow the xref:writing-guideline === 3. Mark it as done -**Move it to __REVIEW__** when done with writing. Please include a link to the Wordpress Preview for your article in the comments on the card before moving it to the __REVIEW__ column so the Editors can access it. +When you feel you are done writing the article and it is ready for review, state that in a comment on your card in Pagure. The editors will **Move it to __REVIEW__**. Please make certain you include a link to the Wordpress Preview for your article in the comments on the card so the Editors can access it. And that's it! -Please note that in some cases the editors might require a change in your article. In that case, you'll receive feedback in the card, and it will be moved back to the __IN-PROGRESS__ column. Please make the requested change and move it back to __REVIEW__ when you are done. +Please note that in some cases the editors might require a change in your article. In that case, you'll receive feedback in the card, and it will be moved back to the __IN-PROGRESS__ column. Please make the requested change and let the editors know in the comments. They will move it back to __REVIEW__. == Workflow **Previous step:** xref:workflow-clarification.adoc[Clarification] From 2cd51350455acb94f3b23393dab0cd0d4c4f84a7 Mon Sep 17 00:00:00 2001 From: Richard England Date: Dec 29 2021 02:45:38 +0000 Subject: [PATCH 16/18] Process changes updated due to Pagure transition. Pagure page added. --- diff --git a/modules/ROOT/pages/contributing.adoc b/modules/ROOT/pages/contributing.adoc index 4353704..215ef9f 100644 --- a/modules/ROOT/pages/contributing.adoc +++ b/modules/ROOT/pages/contributing.adoc @@ -5,7 +5,7 @@ include::partial$workflow-change-banner.adoc[] Fedora Magazine welcomes new writers to contribute their skill by writing an article or two... or five! There are several ways you can find something to write about: * We have a list of specific topics to start with — so you don't need to come up with new ideas to write. -See the __IDEAS__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Kanban board]. +See the _ideas_ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Kanban board]. * You can also xref:writing-a-pitch.adoc[propose an article] if you have your own idea. Either way, your writing goes out to tens of thousands of readers that visit Fedora Magazine every week! diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc index bfb4d3b..4f92a8a 100644 --- a/modules/ROOT/pages/editorial-meetings.adoc +++ b/modules/ROOT/pages/editorial-meetings.adoc @@ -59,7 +59,7 @@ First, let's look back at the previous week in terms of pageviews. This data can Review anything that's in progress. If an article is stuck in progress for a long time without an update, contact the author and ask them if they still plan to finish their work. -Anything that's already finished and commented so by the author can be moved to the "REVIEW" column. +Anything that's already finished and commented so by the author can be moved to the "review" column. You may also want to check the QA calendar for upcoming test days so that we can expect a new post submission. These tend to come in with very short notice, so the Editor of the Week should use their best judgment in deciding when to publish. @@ -78,18 +78,18 @@ This is generally only important a few weeks before the Beta and Final releases, === 3/ Finished articles to review #topic 3/ Finished articles to review - #info Looking at the 'REVIEW' column, let's decide which articles are good to go. Move each either to the 'TO-EDIT' or to the 'IN-PROGRESS' (needs more work) and provide feedback. + #info Looking at the 'review' column, let's decide which articles are good to go. Move each either to the 'to-edit' or to the 'in-progress' (needs more work) and provide feedback. #link Board: https://pagure.io/fedora-magazine-newsroom/boards/articles Authors mark their articles as finished by adding a comment announcing that fact. Review the articles -and ethier move them to the 'TO-EDIT' column, or in case they need some additional work, ask the -author in the card about it and move it back to 'IN-PROGRESS'. +and ether move them to the _to-edit_ column, or in case they need some additional work, ask the +author in the card about it and move it back to _in-progress_. === 4/ Articles to edit #topic 4/ Articles to edit - #info Looking at the 'TO-EDIT' column, assign an editor and a cover image creator. + #info Looking at the 'to-edit' column, assign an editor and a cover image creator. #link Board: https://pagure.io/fedora-magazine-newsroom/boards/articles Assign an editor and a cover image designer to each article so it can be moved forward. @@ -98,8 +98,8 @@ Assign an editor and a cover image designer to each article so it can be moved f === 5/ Publishing schedule #topic 5/ Publishing schedule - #info Looking at the 'TO-EDIT' column, decide the publishing schedule for the next week. - #info If there is not enough content, we might also need to look at the 'IN-PROGRESS' or even the 'IDEAS' columns to come up with additional content. + #info Looking at the 'to-edit' column, decide the publishing schedule for the next week. + #info If there is not enough content, we might also need to look at the 'in-progress' or even the 'ideas' columns to come up with additional content. #link Board: https://pagure.io/fedora-magazine-newsroom/boards/articles Setting the publishing schedule for the upcoming week period is one of the main goals of this meeting. diff --git a/modules/ROOT/pages/getting-access.adoc b/modules/ROOT/pages/getting-access.adoc index 0bd1cb6..f0e1fcf 100644 --- a/modules/ROOT/pages/getting-access.adoc +++ b/modules/ROOT/pages/getting-access.adoc @@ -12,7 +12,11 @@ https://fedoramagazine.org/wp-admin/[Sign in to the Fedora Magazine WordPress da **3. Sign in to the Kanban board**: https://pagure.io/fedora-magazine-newsroom/boards/articles[Sign in to the Pagure Kanban board] using your Fedora Account. -This does NOT grant write access. It is so the account is known to the system and cards can be assigned to you. + +This is so the account is known to the system and you can edit card meta-data. If an editor has already +created a card for your idea, you should be able to assign the card to yourself. You will have to request +that the card's overall status (i.e. the column that it is in on the board) be changed by leaving a comment +in the card's comment section. Only the editors can update the card's status/column. **4. Join the Magazine forum and introduce yourself**: Join the discussion in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum]. diff --git a/modules/ROOT/pages/technical-pagure.adoc b/modules/ROOT/pages/technical-pagure.adoc index fe99339..0c008ce 100644 --- a/modules/ROOT/pages/technical-pagure.adoc +++ b/modules/ROOT/pages/technical-pagure.adoc @@ -5,7 +5,7 @@ If an author has not accessed Pagure before, they must login with their https://accounts.fedoraproject.org/#register[FAS account]. The https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine site is here]. -They will need to select the *Log in* button in the upper right corner of the page. +They will need to select the _Log in_ button in the upper right corner of the page. This will allow the editors to assign cards to them. There is nothing more to do administratively. @@ -15,35 +15,35 @@ There is nothing more to do administratively. When a proposal is approved, follow these steps. . From the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban page], -select the *New issues* button (upper right corner). -. Enter the title of the article in the top text box +select the _New issues_ button (upper right corner). +. Enter the title of the article in the top text box. . Enter details of the proposal in the bottom text box. __Include a link to the proposal -discussion__, where appropriate -. If an author has been identified and has logged in to Pagure, select the *Assignee* -text box in the METADATA column at the right and locate their name -. Select *Create Issue* at the bottom of the page +discussion__, where appropriate. +. If an author has been identified and has logged in to Pagure, select the _Assignee_ +text box in the METADATA column at the right and locate their name. +. Select _Create Issue_ at the bottom of the page. When the new issue has been created, continue with these steps. -. Select the "pencil icon" at the top of the METADATA column at the right -. In the *Tags* selection field select "article" and "needs-image" -. Select *Update* at the bottom of the METADATA column. +. Select the _pencil icon_ at the top of the METADATA column at the right. +. In the _Tags_ selection field select _article_ and _needs-image_. +. Select _Update_ at the bottom of the METADATA column. -The new card should appear at the bottom of the Kanban *IDEAS* column. If it does -not you can add it by selecting the *+* at the top of the *IDEAS* column and entering the -new "Issue" number. +The new card should appear at the bottom of the Kanban _ideas_ column. If it does +not you can add it by selecting the *+* at the top of the _ideas_ column and entering the +new Issue number. -If you do not know the "Issue" number, select *Issues* at the top of the Kanban +If you do not know the Issue number, select _Issues_ at the top of the Kanban page and locate it in the list of issues. == Changing the state of the cards Authors must indicate, in the comments of each card, when they feel the state needs -to change from __IDEAS__ to __IN-PROGRESS__ to __REVIEW__. +to change from _ideas_ to _in-progress_ to _review_. The editors will change the state by "dragging" the cards on the Kanban page as needed. -The editors will determine when the articles are ready to move to __TO EDIT__, drag +The editors will determine when the articles are ready to move to _to-edit_, drag the cards on the Kanban board, and add a comment to that effect to inform the author. == Adding editors @@ -52,13 +52,13 @@ Editors should be admins on the board. You must be an Administrator to add an ed Use the following steps. -. On the Kanban page, select the *Settings* tab at the top of the Pagure page -. Select *Users & Groups* from the list in the left column on this page -. Select *add user* -. Type in the FAS "Username" in the first text field, to search. Note that the user must -have logged into Pagure prior to this operation for the name to be available -. Set the next field (a selection field) to *Admin* -. Select *Add* +. On the Kanban page, select the _Settings_ tab at the top of the Pagure page. +. Select _Users & Groups_ from the list in the left column on this page. +. Select _add user_. +. Type in the FAS Username in the first text field, to search. Note that the user must +have logged into Pagure prior to this operation for the name to be available. +. Set the next field (a selection field) to _Admin_. +. Select _Add_. == Removing editors @@ -66,10 +66,10 @@ You must be an Administrator to remove an editor. Use the following steps. -. On the Kanban page, select the *Settings* tab at the top of the Pagure page. -. Select *Users & Groups* from the list in the left column on this page. -. Locate the name of the admin to remove and select the red "trash can" icon at the right -of the name +. On the Kanban page, select the _Settings_ tab at the top of the Pagure page. +. Select _Users & Groups_ from the list in the left column on this page. +. Locate the name of the admin to remove and select the red trash can icon at the right +of the name. NOTE: Update the https://pagure.io/group/fedora-magazine[Pagure group] membership as well diff --git a/modules/ROOT/pages/workflow-clarification.adoc b/modules/ROOT/pages/workflow-clarification.adoc index bea2929..ed3a5d9 100644 --- a/modules/ROOT/pages/workflow-clarification.adoc +++ b/modules/ROOT/pages/workflow-clarification.adoc @@ -16,7 +16,7 @@ Opinions and additional relevant information is welcome from anyone. If an editor is happy with the proposal, all they need to do is to reply "+1". Proposals with two or more +1's are approved. -When a proposal is approved, a new card is created by an editor in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure], in the __IDEAS__ column. +When a proposal is approved, a new card is created by an editor in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure], in the __ideas__ column. When the card is created, and the author is known, the owner is assigned in the __Assignee__ field, under the METADATA column. This ensures the author is emailed when the card status changes. This operation is performed by the editor. diff --git a/modules/ROOT/pages/workflow-edit-image.adoc b/modules/ROOT/pages/workflow-edit-image.adoc index 82d2b63..68e430e 100644 --- a/modules/ROOT/pages/workflow-edit-image.adoc +++ b/modules/ROOT/pages/workflow-edit-image.adoc @@ -10,7 +10,7 @@ Members of the Editorial Board provide both of those. == Editing -Articles that require editing are in the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure]. +Articles that require editing are in the __to-edit__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure]. Since multiple people will be potentially completing this step, they need to coordinate with comments on the card. @@ -21,15 +21,15 @@ If the cover image has also been done that will be indicated in the comments as == Creating a cover image -Articles that require a cover image are in the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure]. +Articles that require a cover image are in the __to-edit__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure]. Since multiple people will potentially be completing this step, they need to coordinate with comments on the card. To **Create a cover image** for the article, see the xref:creating-an-image.adoc[Creating a featured image] page for instructions. This function is usually done by an editor but the author may take on this task if -they have a specific idea. Please carefully read over xref:creating-an-image.adoc[Creating a featured image] for restriction on form and source for any image used. +they have a specific idea. Please carefully read over xref:creating-an-image.adoc[Creating a featured image] for restrictions on form and source for any image used. -When the image is done this will be indicated in the comments and the __needs-image__ tag will be remove from the METADATA column by an editor. +When the image is done this will be indicated in the comments and the __needs-image__ tag will be removed from the METADATA column by an editor. == Workflow **Previous step:** xref:workflow-review.adoc[Review] diff --git a/modules/ROOT/pages/workflow-review.adoc b/modules/ROOT/pages/workflow-review.adoc index 934dab5..b980412 100644 --- a/modules/ROOT/pages/workflow-review.adoc +++ b/modules/ROOT/pages/workflow-review.adoc @@ -8,15 +8,15 @@ The Editorial Board makes a decision whether the article is ready to go. == Reviewing an article -Articles that are ready for review are in the __REVIEW__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure]. +Articles that are ready for review are in the __review__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure]. === When article is good to go -If the article is good to go, a member of the Editorial Board simply moves it to the __TO-EDIT__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board]. +If the article is good to go, a member of the Editorial Board simply moves it to the __to-edit__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board]. === When article needs changes -If the article needs changes, a member of the Editorial Board provides feedback in the comments section of the respective card, and moves it back to the __IN-PROGRESS__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board]. +If the article needs changes, a member of the Editorial Board provides feedback in the comments section of the respective card, and moves it back to the __in-progress__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board]. == Workflow **Previous step:** xref:writing-an-article.adoc[Writing] diff --git a/modules/ROOT/pages/workflow.adoc b/modules/ROOT/pages/workflow.adoc index 656720d..76540b0 100644 --- a/modules/ROOT/pages/workflow.adoc +++ b/modules/ROOT/pages/workflow.adoc @@ -4,7 +4,7 @@ include::partial$workflow-change-banner.adoc[] image::fedora-magazine-workflow.jpg[,100%,] -Content on the Fedora Magazine is created using a 5-step workflow: +Content on the Fedora Magazine is created using a five-step workflow: 1. xref:workflow-article-proposal.adoc[Article Proposal] by Anyone 2. xref:workflow-clarification.adoc[Clarification] by Editors @@ -12,12 +12,12 @@ Content on the Fedora Magazine is created using a 5-step workflow: 4. xref:workflow-review.adoc[Review] by Editors 5. xref:workflow-edit-image.adoc[Edit & Image] by Editors -An initial proposal lands in the __idea__ state. After some clarification, a specific article goes through 5 states. Starting as an __idea__, it progresses to __in progress__, __review__, __to edit__, and finally ending up being __scheduled__. Each step in the workflow has its own page in this documentation that provides guidance. +An initial proposal lands in the __idea__ state. After some clarification, a specific article goes through five states. Starting as an __idea__, it progresses to __in progress__, __review__, __to edit__, and finally ending up being __scheduled__. Each step in the workflow has its own page in this documentation that provides guidance. == Tracking -Proposals in the **__idea__** state are among the general discussion in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum]. Everyone is welcome to submit one! +Proposals in the _idea_ state are among the general discussion in the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum]. Everyone is welcome to submit one! -Articles in **all other states** are represented as cards in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure]. Each state has its own column on the board with the appropriate title. +Articles in all other states are represented as cards in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban section of the Fedora Magazine Pagure]. Each state has its own column on the board with the appropriate title. Join our team either as a xref:contributing.adoc[writer] or as an xref:editorial.adoc[editor], and help us make wonderful content read by tens of thousands of readers every week! diff --git a/modules/ROOT/pages/writing-an-article.adoc b/modules/ROOT/pages/writing-an-article.adoc index bfe5405..42da94a 100644 --- a/modules/ROOT/pages/writing-an-article.adoc +++ b/modules/ROOT/pages/writing-an-article.adoc @@ -13,14 +13,14 @@ https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Pagur === 1. Choose what to write -**Choose** any article you like in the __IDEAS__ column in the +**Choose** any article you like in the __ideas__ column in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Kanban board of the Fedora Magazine Pagure]. Or, https://docs.fedoraproject.org/en-US/fedora-magazine/workflow-article-proposal/[propose your own]. **Assign** Open a topic, if necessary in the the https://discussion.fedoraproject.org/c/project/magazine[Fedora Magazine Discourse forum], and let the editors know you would like to be the author of an article. Make certain you tell them the number. If you have been in contact with the editors regarding an article, simply let them know in your ongoing conversation. -The editors will assign the article to you and move it to **__IN-PROGRESS__** in the +The editors will assign the article to you and move it to _in-progress_ in the https://pagure.io/fedora-magazine-newsroom/boards/articles[Fedora Magazine Kanban board]. === 2. Write it @@ -33,11 +33,11 @@ As you write your draft, try to understand and follow the xref:writing-guideline === 3. Mark it as done -When you feel you are done writing the article and it is ready for review, state that in a comment on your card in Pagure. The editors will **Move it to __REVIEW__**. Please make certain you include a link to the Wordpress Preview for your article in the comments on the card so the Editors can access it. +When you feel you are done writing the article and it is ready for review, state that in a comment on your card in Pagure. The editors will move it to _review_ in the Kanban board. Please make certain you include a link to the WordPress preview for your article in the comments on the card so the Editors can access it. And that's it! -Please note that in some cases the editors might require a change in your article. In that case, you'll receive feedback in the card, and it will be moved back to the __IN-PROGRESS__ column. Please make the requested change and let the editors know in the comments. They will move it back to __REVIEW__. +Please note that in some cases the editors might require a change in your article. In that case, you'll receive feedback in the card, and it will be moved back to the _in-progress_ column. Please make the requested change and let the editors know in the comments. They will move it back to _review_. == Workflow **Previous step:** xref:workflow-clarification.adoc[Clarification] From 96184895bb91dbc50883052cf9355df197aa03cb Mon Sep 17 00:00:00 2001 From: Richard England Date: Dec 29 2021 02:45:38 +0000 Subject: [PATCH 17/18] Removing the Taiga setup/admin page --- diff --git a/modules/ROOT/pages/technical-taiga.adoc b/modules/ROOT/pages/technical-taiga.adoc deleted file mode 100644 index 18d5023..0000000 --- a/modules/ROOT/pages/technical-taiga.adoc +++ /dev/null @@ -1,55 +0,0 @@ -= Taiga Operations - -== Adding a new user - -If an author has not written for us before, you will have to add them to Taiga. - -NOTE: Because we use OpenID authentication, the new member will have to log in to teams.fedoraproject.org with their Fedora account _before_ you can add them. - -To add a new user: - -. Click *Admin* (the gear icon) on the left-hand panel -. Click *Members* -. Click the *+New Member* button in the upper-right corner -. Search by name or email address in the text box -. Click the desired account -. Select the *Writer* role from the *Choose a role* drop-down -. Click the *Invite* button - -The user is now added to the Magazine board and can be assigned to cards. - -If the invite was mistakenly issued before the user had logged in to teams.fedoraproject.org, use the following steps to get Taiga to reconnect the invite with the user's OpenID. - -. Click *Admin* (the gear icon) on the left-hand panel -. Click *Members* -. Find the *Pending* invite at the end of the Members list -. Click the big red button at the end of the row (the trash can icon) -. Redo the "To add a new user" steps above _after_ the user has logged in - -== Creating a new card (user story) - -When a proposal is approved, follow these steps. - -. From the https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban[Kanban page], click the *+* button in the *Article Spec* column -. Enter the title of the article in the top text box -. Enter details of the proposal in the bottom text box, including a link to the proposal discussion where appropriate -. Click *Add tag* and type "needs image" and click that tag -. If an author has been identified and has an account in Taiga, click *Assign* and assign them -. Click *Create* -. Click the card you just created -. Click the *Add watchers* button -. Type "Editor" in the search box -. Click *Role: Editorial board member* to add all editors as watchers -. Click the *Add* button - -== Adding or removing editors - -To add or remove an editor, in Taiga: - -. Click *Admin* (the gear icon) on the left-hand panel -. Click *Members* -. Find the member in question -. Select the desired role in the *Role* drop-down -. Toggle the *Admin* slider (Editors should be admins on the board, non-editors should not) - -NOTE: Update the https://pagure.io/group/fedora-magazine[Pagure group] membership as well so that the docs and images repos have the correct permissions. From 3b873bc666e66597562fff97225b90c89ba200c9 Mon Sep 17 00:00:00 2001 From: Richard England Date: Dec 29 2021 06:55:30 +0000 Subject: [PATCH 18/18] changed the editorial-meeting page to reflect the tasks.txt (used by zinebot) --- diff --git a/modules/ROOT/pages/editorial-meetings.adoc b/modules/ROOT/pages/editorial-meetings.adoc index 4f92a8a..39d0679 100644 --- a/modules/ROOT/pages/editorial-meetings.adoc +++ b/modules/ROOT/pages/editorial-meetings.adoc @@ -22,8 +22,8 @@ To start the meeting, run the following set of commands. #startmeeting Magazine editorial board #meetingname magazine - #topic Roll call - #chair glb rlengland theevilskeleton cverna asamalik + #topic roll call + #chair zinebot glb rlengland theevilskeleton People will then join using a `.hello2` or a `.hello NICK` command. @@ -33,18 +33,18 @@ This is the standard agenda. Announcing it in advance helps newcomers understand #topic Agenda #link https://docs.fedoraproject.org/en-US/fedora-magazine/workflow/ - #info -- 1/ Last week's stats -- - #info -- 2/ In progress followup -- - #info -- 3/ Finished articles to review -- - #info -- 4/ Articles to edit -- - #info -- 5/ Publishing schedule -- - #info -- 6/ Editor of the Week -- - #info -- 7/ Open floor -- + #info -- 1/ last week's stats -- + #info -- 2/ articles in progress -- + #info -- 3/ articles to review -- + #info -- 4/ articles to edit -- + #info -- 5/ publishing schedule -- + #info -- 6/ editor of the week -- + #info -- 7/ open floor -- === 1/ Last week's stats - #topic 1/ Last week's stats + #topic 1/ last week's stats First, let's look back at the previous week in terms of pageviews. This data can be obtained in the https://fedoramagazine.org/admin[Fedora Magazine Wordpress]. On the https://fedoramagazine.org/wp-admin/index.php[Dashboard], scroll down to Stats by Jetpack. @@ -53,8 +53,8 @@ First, let's look back at the previous week in terms of pageviews. This data can === 2/ In progress followup - #topic 2/ In progress followup - #info Looking at the 'in progress' column, is there something that's been finished? Anything to follow up on with its author? + #topic 2/ articles in progress + #info Looking at the 'in-progress' column, is there something that's been finished? Anything to follow up on with its author? #link Board: https://pagure.io/fedora-magazine-newsroom/boards/articles Review anything that's in progress. If an article is stuck in progress for a long time without an update, contact the author and ask them if they still plan to finish their work. @@ -70,16 +70,16 @@ These tend to come in with very short notice, so the Editor of the Week should u Also check the release schedule for upcoming tasks. This is generally only important a few weeks before the Beta and Final releases, but it doesn't hurt to check just to keep it in mind. - #info Review release schedule + #info Check the release schedule. #link https://fedorapeople.org/groups/schedule/f-/f--magazine-tasks.html (where is the release being developed) === 3/ Finished articles to review - #topic 3/ Finished articles to review - #info Looking at the 'review' column, let's decide which articles are good to go. Move each either to the 'to-edit' or to the 'in-progress' (needs more work) and provide feedback. - #link Board: https://pagure.io/fedora-magazine-newsroom/boards/articles + #topic 3/ articles to review + #info Looking at the 'review' column, let's decide which articles are good to go. Move each either to the 'to-edit' (finished) column or to the 'in-progress' (needs more work) colunn and provide feedback. + #link board: https://pagure.io/fedora-magazine-newsroom/boards/articles Authors mark their articles as finished by adding a comment announcing that fact. Review the articles and ether move them to the _to-edit_ column, or in case they need some additional work, ask the @@ -88,7 +88,7 @@ author in the card about it and move it back to _in-progress_. === 4/ Articles to edit - #topic 4/ Articles to edit + #topic 4/ articles to edit #info Looking at the 'to-edit' column, assign an editor and a cover image creator. #link Board: https://pagure.io/fedora-magazine-newsroom/boards/articles @@ -97,8 +97,8 @@ Assign an editor and a cover image designer to each article so it can be moved f === 5/ Publishing schedule - #topic 5/ Publishing schedule - #info Looking at the 'to-edit' column, decide the publishing schedule for the next week. + #topic 5/ publishing schedule + #info Looking at the 'to-edit' column, decide the publishing schedule for the upcoming week. #info If there is not enough content, we might also need to look at the 'in-progress' or even the 'ideas' columns to come up with additional content. #link Board: https://pagure.io/fedora-magazine-newsroom/boards/articles @@ -133,7 +133,7 @@ When the schedule is set and agreed upon, announce it by: Before the end of the meeting, we need to select next week's xref:editor-of-the-week.adoc[Editor of the Week]. - #topic 6/ Editor of the Week + #topic 6/ editor of the Week Announce the volunteer using: @@ -141,7 +141,7 @@ Announce the volunteer using: === 7/ Open floor - #topic 7/ Open floor + #topic 7/ open floor === Meeting ends