Project Description

With this project I would like to refresh/update the confluence documentation describing how SUSE Manager maintenance works and how to process a SUSE Manager update round.

Goal for this Hackweek

  • Update the SUSE Manager maintenance confluence pages
    • provide the initial overview to SUSE Manager maintenance for new hires
    • describe how to process a SUSE Manager maintenance round
    • highlight critical steps and peculiarities of SUSE Manager maintenance
    • describe the internal maintsec-tools available for processing SUSE Manager maintenance
    • link planned gitlab issues for improving the automation behind SUSE Manager maintenance

Resources

Internal SUSE Manager maintenance documentation

Contacts

If you are interest to contribute, feel free to reach out (@deneb_alpha).

Looking for hackers with the skills:

susemanager mainteance documentation daps docbook

This project is part of:

Hack Week 21

Activity

  • about 3 years ago: deneb_alpha added keyword "daps" to this project.
  • about 3 years ago: deneb_alpha added keyword "docbook" to this project.
  • about 3 years ago: admehmood liked this project.
  • about 3 years ago: deneb_alpha started this project.
  • about 3 years ago: deneb_alpha added keyword "susemanager" to this project.
  • about 3 years ago: deneb_alpha added keyword "mainteance" to this project.
  • about 3 years ago: deneb_alpha added keyword "documentation" to this project.
  • about 3 years ago: deneb_alpha originated this project.

  • Comments

    • deneb_alpha
      about 3 years ago by deneb_alpha | Reply

      this project had a nice drift add-emoji

      After attending the sessions from https://hackweek.opensuse.org/21/projects/everyone-can-contribute-to-documentation-see-how-you-can-join-the-party I decided to continue to work at my project using DAPS and DocBook.

      Happy hacking and have a lot of fun!

    Similar Projects

    Advent of Code: The Diaries by amanzini

    Description

    It was the Night Before Compile Time ...

    Hackweek 25 (December 1-5) perfectly coincides with the first five days of Advent of Code 2025. This project will leverage this overlap to participate in the event in real-time.

    To add a layer of challenge and exploration (in the true spirit of Hackweek), the puzzles will be solved using a non-mainstream, modern language like D, Crystal, Gleam or Zig.

    The primary project intent is not just simply to solve the puzzles, but to exercise result sharing and documentation. I'd create a public-facing repository documenting the process. This involves treating each day's puzzle as a mini-project: solving it, then documenting the solution with detailed write-ups, analysis of the language's performance and ergonomics, and visualizations.

                                   |
                                 \ ' /
                               -- (*) --
                                  >*<
                                 >0<@<
                                >>>@<<*
                               >@>*<0<<<
                              >*>>@<<<@<<
                             >@>>0<<<*<<@<
                            >*>>0<<@<<<@<<<
                           >@>>*<<@<>*<<0<*<
             \*/          >0>>*<<@<>0><<*<@<<
         ___\\U//___     >*>>@><0<<*>>@><*<0<<
         |\\ | | \\|    >@>>0<*<0>>@<<0<<<*<@<<
         | \\| | _(UU)_ >((*))_>0><*<0><@<<<0<*<
         |\ \| || / //||.*.*.*.|>>@<<*<<@>><0<<<
         |\\_|_|&&_// ||*.*.*.*|_\\db//_
         """"|'.'.'.|~~|.*.*.*|     ____|_
             |'.'.'.|   ^^^^^^|____|>>>>>>|
             ~~~~~~~~         '""""`------'
    ------------------------------------------------
    This ASCII pic can be found at
    https://asciiart.website/art/1831
    
    

    Goals

    Code, Docs, and Memes: An AoC Story

    • Have fun!

    • Involve more people, play together

    • Solve Days 1-5: Successfully solve both parts of the Advent of Code 2025 puzzles for Days 1-5 using the chosen non-mainstream language.

    • Daily Documentation & Language Review: Publish a detailed write-up for each day. This documentation will include the solution analysis, the chosen algorithm, and specific commentary on the language's ergonomics, performance, and standard library for the given task.