Document ways to contribute to FCOS

[jlebon]

We should have a section somewhere (or maybe in the tracker?) for how to get more involved with FCOS. Some ideas, in order of commitment:

• attend community meetings and provide input
• help with community support on Matrix and the forum
• help with testing (e.g. test day, bug fixes)
• help with fixing bugs/adding features/new platforms (see https://github.com/coreos/fedora-coreos-tracker/issues?q=is%3Aissue+is%3Aopen+label%3Astatus%2Fpending-action)
• be part of the FCOS release rotation

[travier]

More platforms

I started writing a disk image "convert" script to help with the new emerging platform flow.

It should make it easier for folks to test platforms for which we don't produce official FCOS images but have support for in Afterburn and Ignition.

Right now, the following platforms are almost ready and only need a bit of polish to go over the finish line:

• https://github.com/coreos/fedora-coreos-tracker/issues/1324
• https://github.com/coreos/fedora-coreos-tracker/issues/1701

Those need a bit more work but should be a reasonably small amount of work:

• https://github.com/coreos/fedora-coreos-tracker/issues/414
• https://github.com/coreos/fedora-coreos-tracker/issues/866

This one is more complex, but already has PRs in progress for afterburn & ignition:

• https://github.com/coreos/fedora-coreos-tracker/issues/736

---

Misc fixes

I also have this list of "things to fix" that should be accessible to get started:

• https://github.com/coreos/fedora-coreos-tracker/issues/572
  • Packaging fixes and testing
• https://github.com/coreos/fedora-coreos-tracker/issues/607
  • Rewrite Python script in a compiled language or find another workaround
• https://github.com/coreos/fedora-coreos-config/issues/1826
  • Small kola test
• https://github.com/coreos/fedora-coreos-tracker/issues/677
  • Fix alternatives on ostree based systems
  • https://docs.fedoraproject.org/en-US/fedora-coreos/alternatives/
  • https://github.com/fedora-sysv/chkconfig/issues/9
  • https://gitlab.com/fedora/bootc/tracker/-/issues/7
• https://github.com/containers/toolbox/issues/714

[hrismarin]

I can try to start work on the first three points, i.e:

• attend community meetings and provide input

• help with community support on Matrix and the forum

• help with testing (e.g. test day, bug fixes)

Since these points are already mentioned in FAQ: What are the communication channels around Fedora CoreOS?, I'm not sure if they would be a section in the docs and what information they should provide. Any advice would be greatly appreciated.

[jlebon]

@hrismarin Thanks for your interest!

Hmm, I wonder if it should just be a top-level "Contributing" page listed last (i.e. right after FAQ) in the nav bar.

[hrismarin]

I'm also in favor of this being a top-level "Contribute" page listed last. I will start working on the first three topics as I am aware of them.

I can also try to write about fixing bugs/adding features/new platforms.

I'm also particularly interested in being part of the FCOS release rotation. Unfortunately, what I know about it is only what I've read in the Matrix room when the team folks are coordinating. I think that's not much and I didn't explore further because I didn't even know that someone who wasn't part of the team could be part of the FCOS release rotation. Could you please direct me to where I can learn about the process so I can try to write about it and (hopefully) be a part of it, if I have the necessary skills of course.

Thank you!

[jlebon]

@hrismarin Nice! Maybe let's discuss this in the community meeting today. We'll need to come up with some sort of process for adding community members to the rotation. Probably something analogous to https://fedoraproject.org/wiki/Infrastructure/GettingStarted and https://fedoraproject.org/wiki/Infrastructure_Apprentice.

That said, a lot of contributions can be done from GitHub (certainly, bug fixes, features, and platform enablement) and that's actually where we need the most help.

[c4rt0]

This was discussed at Fedora community meeting yesterday. We will add a new top level contributing page to our docs.