PR#32: More Taiga to Pagure updates and necessary process changes. - fedora-magazine

fedora-magazine

#32 More Taiga to Pagure updates and necessary process changes.

Merged 2 years ago by glb. Opened 2 years ago by rlengland.

rlengland/fedora-magazine taiga-pagure into master

More Taiga to Pagure updates and necessary process changes.

Richard England • 2 years ago

802ae86

modules/ROOT/pages/creating-an-image.adoc

file modified

+1 -1

		`@@ -86,6 +86,6 @@`

		`$ 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.`

modules/ROOT/pages/editor-of-the-week.adoc

file modified

+1 -1

		`@@ -26,7 +26,7 @@`
		`* 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.`

modules/ROOT/pages/editorial-add-contributors.adoc

file modified

+4 -12

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

modules/ROOT/pages/getting-access.adoc

file modified

+2 -2

		`@@ -11,8 +11,8 @@`
		`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].`

rlengland commented 2 years ago

More name/link/process changes for the taiga to pagure move

N.B. the file technical-taiga.adoc needs to be replaced with a corresponding page for Pagure. I am not familiar enough with the admin functions and permissions in Pagure to approach this.

glb commented 2 years ago

It doesn't matter to Pagure. Pagure is just a glorified file server in a way. It is really just compliance with the AsciiDoc spec that you would have to worry about. I think $ git rm modules/ROOT/pages/technical-taiga.adoc would work to remove the old file. Then you would have to update modules/ROOT/nav.adoc. I think that should be all there is to it. But you definitely want to test things thoroughly with $ ./build.sh && ./preview.sh before submitting a PR with that big of a change.

Thanks!

Edited 2 years ago by glb

Pull-Request has been merged by glb

2 years ago

glb commented 2 years ago

Oh. I just realized what you were saying. Sorry, I guess it is getting to be a bit too late in the day for me. :P

glb commented 2 years ago

I just had a quick look at the page. It is just three sections.

Adding a new user
Creating a new card (user story)
Adding or removing editors

The first section can go away completely for Pagure. There is nothing the admin needs to do after the user has logged into the system to initialize their profile.

The second section is something you've done a lot of lately.

The third section is just what you did when you added TheEvilSkeleton. Just add the editor as an admin under Settings->Users & Groups.

I think that should be all there is to it.

Thanks!

rlengland commented 2 years ago

Okay, I'll take a look at it,...and see if I can get the preview to work.
Thanks for the hand holding.