magazine/fedora-magazine
1
1
Fork 0
Code Issues 3 Pull requests Projects Releases Packages Wiki Activity Actions

Process changes updated due to Pagure transition. Pagure page added.

Browse source
This commit is contained in:
Richard England 2021-12-15 16:06:04 -08:00
commit 4f13d87c39
9 changed files with 56 additions and 52 deletions
Download patch file Download diff file Expand all files Collapse all files

2
modules/ROOT/pages/contributing.adoc
View file

@ -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!

14
modules/ROOT/pages/editorial-meetings.adoc
View file

@ -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.

6
modules/ROOT/pages/getting-access.adoc
View file

@ -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].

54
modules/ROOT/pages/technical-pagure.adoc
View file

@ -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

2
modules/ROOT/pages/workflow-clarification.adoc
View file

@ -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.

8
modules/ROOT/pages/workflow-edit-image.adoc
View file

@ -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]

6
modules/ROOT/pages/workflow-review.adoc
View file

@ -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]

8
modules/ROOT/pages/workflow.adoc
View file

@ -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!

8
modules/ROOT/pages/writing-an-article.adoc
View file

@ -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]