#274 [Workshop] Fedora CoreOS docs and translation hackfest
Closed: Talk Scheduled 2 years ago by riecatnor. Opened 2 years ago by jlebon.

What is your proposal?

Fedora CoreOS (FCOS) is an automatically updating, minimal, monolithic, container-focused, emerging Fedora edition designed for clusters but also operable standalone, optimized for Kubernetes but also great without it.

Great documentation is key to the success of a project. We would like to hold a hackfest to improve FCOS' docs to make it more complete and accurate.

Some examples of the areas we'll tackle are listed in the GitHub issue tracker for the documentation: https://github.com/coreos/fedora-coreos-docs/issues.

The current documentation is also mostly untranslated and would thus benefit from translations into more languages.

Who in addition to the speaker needs to be in the virtual room for this to succeed?

- Jonathan Lebon (jlebon)
- Timothée Ravier (siosm)

Audience: anyone interested in improving the Fedora CoreOS documentation and learning about it in the process.

Is this a…

2 hours (110 minutes): Workshop

Anything else we need to know?


Who are you?

  • Name: Jonathan Lebon, Timothée Ravier
  • FAS ID: jlebon, siosm
  • IRC Nick, if not FAS ID: jlebon, travier
  • Timezone: EST & CEST

Metadata Update from @riecatnor:
- Issue tagged with: Hackfest - Work Session - Tutorial

2 years ago

In addition to writing new documentation, we can also suggest that people work on translating the current documentation.

Your session has been accepted for Nest with Fedora. Please review the attached schedule (PDF) and advise ASAP if there are any conflicts. The timezone used for the attached schedule is EST. Schedule will be locked by Tuesday August 4th. If you have further questions or need assistance, feel free to email mnordin@redhat.com or drop those inquiries on this ticket. Thanks!


*Note: I see the title is incomplete on the pdf and have updated it to "[Workshop-110] Fedora CoreOS Docs and Translation Hackfest" on my end.

Metadata Update from @riecatnor:
- Issue tagged with: Talk Accepted

2 years ago

Hi! Nest with Fedora is beginning shortly. I want to thank you for speaking at this years contributor conference, your time and effort is appreciated :)

I have outlined the basic process for speakers below. If you have questions, feel free to drop them here and I will do my best to answer them before the event begins.

How to get to your session:
Enter the event
Go to Sessions tab on the left at the correct time
Click your session
Accept permissions for audio/video
You're in!

Sessions are set up as moderated by the speakers. There is a maximum of 10 people on screen at once, though people can leave the screen and different attendees can request permission to join. The speaker(moderator) will have a moderation panel on the bottom left hand side to allow or deny the request. If you feel you need someone besides yourself to help with moderation, please make sure they are registered for the event and provide their full name here. Anyone can watch and participate in the chat. Sessions will be recorded.

To share slides, there is an option at the bottom to share your screen, where you can choose the window/tab to share. To share a video with audio, you can share your screen and play the audio on loud speaker (so your mic picks it up). Screen sharing works just as other video conferencing tools (like Google Meet, Bluejeans etc).

If you have technical issues during your session, contact one of the attendees labelled "Organiser" or myself, Marie Nordin, through the platforms direct message function.


  • riecatnor

Thank you for your participation at Nest with Fedora, it is appreciated. It was a great event and we have received a bunch of positive feedback.

Please attach slides or a link to slides here, and I will close the ticket as complete. If you did not use slides during your session, please comment to let me know.


We did not use slides during our session.

Metadata Update from @riecatnor:
- Issue close_status updated to: Talk Scheduled
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Attachments 1