Ryan, don't know much about the process here. would love to work on this. Attached is a quick draft.

Tried to follow process. Here's a link to updated file for review: https://i.imgur.com/NcISOU2.jpg

Looking good!

How comfortable are you with git? Are you able to fork this project here in pagure, and commit the SVG, and file a pull request?

I have used before in one-off situations but never seriously. If there's a
brief rundown of cli commands specific to the magazine it would be helpful.
I cloned the repository successfully, but forking is somewhat elusive.

I'll take a look tonight, but any guidance or specific resources
appreciated.

Believe I forked appropriately. Tried to commit, but when "git push" receiving the following message:

Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.

Any further resources appreciated. Thanks.

Uncertain of next step. Seems I'm needing to associate a public key with my account here?

Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.

EDIT: Looks like I've added my public key to Pagure, but still getting the same message in cli upon

git push

Believe I've been successful. Confirmation (and/or additional advice appreciated).

Awesome! thanks!

I have merged your PR now!

cheers,
ryanlerch

:clapper: Image added, thanks @kylerconway!

@kylerconway I must not have been rendering the image in my browser correctly – I tried rendering the image locally on my system but it appears like the background is missing. Any way you could take another look and submit a quick fix? Thanks!

Are you meaning the svg or the jpg? I'm seeing it on my end, though perhaps I've done something wrong. Will try to re-push the svg.

Just want to make sure this has worked. Submitted pull request. Anything else I'm missing?

Ryan,

Your guide (below) seemed to be working, but

git push

is saying that "Everything is up-to-date" (even after branch creation, image addition, and commit).

ssh -vT git@pagure.io

results seemingly successfully with

hello kylerconway, this is git@pagure01 running gitolite3 3.6.5-2.el7 on git 1.8.3.1

Not sure why the difficulty now, though it's possible I don't understand branches. Any additional thoughts appreciated. I'm not seeing the branches or the ability to do a PR on pagure.

Thanks for the assistance. It's much appreciated as I'd like to become a regular contributor.

Your guide:

Okies, yeah a clean start might be a good way to go here.

First, i would save a copy of the yubikey file with the background, somewhere away from your git repo. Then, (making sure you have a copy of that file safe), delete your fork here on pagure (in the settings), and then also delete the folder that contains the checkout of your fork on your computer too.

Now, re-fork the fedoramagazine-images repo on pagure, and do the git clone on your local system again.

# git clone ssh://git@pagure.io/forks/kylerconway/fedoramagazine-images.git
# cd fedoramagazine-images

Now, while we are at it, we can add the main repo as an additional remote for your forked repo this will let us easily pull changes from upstream so we don't get out of sync:

# git remote add upstream https://pagure.io/fedoramagazine-images.git

Okies, that is your basic setup done now. When you want to work on a new image, this is the workflow i use, that might be useful to you:

First, do a git status, and make sure you are in your master branch. Now, rebase your master branch with the master branch of the "upstream" aka the main fedoramagazine-images repo:

# git pull --rebase upstream master

Now, create a new branch to work on your image, and checkout it

# git branch yubikeyimage
# git checkout yubikeyimage

now, you are in the yubikeyimage branch, make your changes to the file, or if creating a new image, add your new file, then add it and commit it like normal. When trying to git push, you may get a warning that the branch doesnt exist in orgin, just type the command it gives you, and your new branch should then be visible on your fork on pagure. Then just open up a PR from your new yubikeyimage branch to the master branch on pagure.

When you are done, just switch back in the terminal to the master branch, ready for the next image to be made :)

# git checkout master

Think I may have figured this out. Needed (maybe?) to push the branch with

git push -u origin yubikeyimage

Hopefully this worked. Thanks for help and guidance so far.