The wikis are now using the new authentication system.
If you did not migrate your account yet, visit


Jump to: navigation, search

#1 Ivo

My idea is to create a little team for video tutorial

  1. I can make the registration and editing video
  2. a English speaker
  3. a VPS or VM online where we can make tests and recorder videos

Docs team decide whats arguments would be better if they had a video tutorial in addition to the written guide.

The videotutorial team simply has to follow the instructions written in the guide and record the video with an audio support of the speaker in English

To do it professionally, we need to design a workflow and a style that is always the same for all videos.

#2 Adrien

  • Ivo's idea about a video team is great
  • I would like to build on his idea by helping him and others to make a videos mini-series for helping new users land peacefully on openSUSE territory.
  • I start from the assumption that new users will have issues or choices to make which make their experience difficult and or unpleasant. The idea is to take nothing for granted; not focus on tricks or aesthetics but on the basics, to help people get their config as suits their needs, and build trust.
  • Under this assumption, here my take on Ivo's idea introduced above: we make videos are for absolute linux beginners and absolute opensuse beginners, tackling the following topics:
    • Leap vs Tumbleweed? What to take into account when settling for your first openSUSE distribution?
    • How to prepare your disk in view of installing a new Linux distro? With a special focus on openSUSE of course, but considering dual- or multi- booting with Windows and / or different Linux distros too, with focus on partitioning, touching on a variety of topics such as file systems, encryption, subvolumes, etc.
      • worth mentioning, perhaps not covering: exotic partitioning schemes
    • How to keep your system up-to-date and safe? Basics of zypper, YaST & snapper, installing and using flatpacks and snaps, touching on basic workflow to backup and restore your data, snapper and 1-2 third-party tools.
      • worth mentioning, perhaps not covering: setting up VMs, testing in containers
    • How to troubleshoot your issues with openSUSE KDE? How to tell user settings isues vs. DE issues vs. distro issues? Explaining distro paths structure and user settings (dotfiles). Basics of the booting process UEFI->GRUB->kernel image->system file->systemd services->display manager->DE workspace. Giving some methods for locating where an issue occurs and how to fix it from there. Kernel parameters, journalctl, and other utilities. Some resources for getting help and best practice on how to phrase questions.
      • worth mentioning, perhaps not covering: permission issues, DE debugging tools, systemd debugging tools, how to navigate and report bugs
  • We should keep an open mind on using different media, not just video footage (self-contained interactive slides can be useful too); interactive slides might turn out to be much easier to update and maintain than videos
  • May or may not be related to the refreshed/revamped doc: How about doing semantic analysis on all the Discord rooms, Telegram groups and Forums affiliated with openSUSE to make a cluster chart of all the issues people run into?

#3 Attila

  • Purpose/future of the Wiki and Documentation? I would probably keep both and weed out/"rebrand" the Wiki as something community oriented and all new docs would go to Documentation which would need a proper main page to include:
    • Installation guide for Leap and TW,
    • Docs for applications specific to openSUSE, like snapper, transactional-updates, health-checker, rebootmgr and opi along with the currently listed items on the Wiki main page,
    • Distribution overview, that would include the differences compared to other distros and the benefits of using openSUSE,
    • Contribution options,
    • FAQ,
    • Include international communities and links to their channels.

Would be also great if we could extend documentation to Kubic and MicroOS as well. Currently these are poorly documented or not documented at all.


(Ideas for what the doc team could be working on, for prioritization and discussion)

  • Your idea here ...