I think this would make a great quick-doc. Would someone like to take this on? We’ll be happy to help you learn the necessary skills. It’s a great way to contribute and learn lots at the same time.
The thing with the magazine is that posts cannot be updated later. They’re published and represent information at that point in time. They’re more for outreach/marketing—not so much for actual technical documentation.
I think an article on “Installing kernel from Koji” would fit really well here:
Here’s my draft for submission. I have condensed it into a brief article for all to review.
@ankursinha FYI. Looking forward to guidance on the next steps on getting this into the quick-doc
[draft] quick-doc 1 - installing kernels from Koji
Koji is the build system Fedora developers use to build software for inclusion into Fedora. If there is a need to install a kernel different from the one that gets installed by default, these can be obtained from Koji.
The koji package makes this process much easier.
Install the koji package
$ sudo dnf install koji
Download and install the kernel
Below is a one-liner that creates a new unique temporary directory, downloads RPMs to it and installs them. This assumes we are working with the x86_64 architecture.
cd $(mktemp -d) && koji download-build --arch=x86_64 --arch=noarch kernel-5.12.18-200.fc33 && sudo dnf install *
This eliminates the need to clean up after installation and the risk of installing unwanted rpms accidentally.
Quick-docs follow the standard “pull request” model. Would you be familiar with that, otherwise I can give detailed instructions on how to go about it.
Followed the guidance (How to contribute). Forked the pagure.io repo ( in my account space - don’t know if you will be able to view it). Then cloned the fork. Made the changes locally. Built and previewed locally using podman. Committed the change locally.
But I can’t push the change up to the remote (i.e. remote of my fork). I cloned over https. Does it work only over ssh?
I’ll set up ssh keys later anyway for future contributions. Just wondering if I could push this change over https for now.
[jetstream@workspace quick-docs]$ git commit -m "Added quickdoc for installing kernel from Koji"
[master 17fbd57] Added quickdoc for installing kernel from Koji
2 files changed, 44 insertions(+)
create mode 100644 modules/ROOT/pages/kernel/installing-koji-kernel.adoc
[jetstream@workspace quick-docs]$ git push
fatal: unable to access 'https://pagure.io/forks/jetstream/fedora-docs/quick-docs.git/': The requested URL returned error: 403
I did expect a username/password prompt, but no. Maybe something wasn’t quite right in the way I had done it. Thanks @ankursinha for the reference link.
Had a read but couldn’t get it into my head. Eventually managed to set up ssh keys, so was able to push the changes.