Adapt Bootstrap code in OBS to support theming
a project by enavarro_suse
Updated over 1 year ago. 2 hacker ♥️. 1 follower.

Project Description

After the release of Bootstrap 5.3, theming is supported, including dark mode.

Bootstrap variables have to be adapted in the OBS codebase to be able to support theming.

Goal for this Hackweek

Adapt as many variables as possible to comply with Boostrap theming support.

Resources

Bootstrap color system and color modes documentation and migration tips:

  • Color modes: https://getbootstrap.com/docs/5.3/customize/color-modes/
  • Migrating to v5: https://getbootstrap.com/docs/5.3/migration/
  • v5.3.0-alpha2, Color modes: https://getbootstrap.com/docs/5.3/migration/#color-modes
  • v5.3.0-alpha1, Color modes!: https://getbootstrap.com/docs/5.3/migration/#color-modes-1
  • v5.0.0, Color system: https://getbootstrap.com/docs/5.3/migration/#color-system

Join this project

Looking for hackers with the skills:

obs bootstrap design

This project is part of:

Hack Week 23

Activity

  • over 1 year ago: Pharaoh_Atem liked this project.
  • over 1 year ago: enavarro_suse started this project.
  • over 1 year ago: hennevogel liked this project.
  • over 1 year ago: enavarro_suse removed keyword refactoring from this project.
  • over 1 year ago: enavarro_suse added keyword "obs" to this project.
  • over 1 year ago: enavarro_suse added keyword "bootstrap" to this project.
  • over 1 year ago: enavarro_suse added keyword "design" to this project.
  • over 1 year ago: enavarro_suse added keyword "refactoring" to this project.
  • over 1 year ago: enavarro_suse originated this project.


    • Comments

    Be the first to comment!

    Similar Projects

    Research openqa-trigger-from-obs and openqa-trigger-from-ibs-plugin by qwang

    Description

    openqa-trigger-from-obs project is a framework that OSD is using it to automatically sync the defined images and repositories from OBS/IBS to its assets for testing. This framework very likely will be used for the synchronize to each location's openqa include openqa.qa2.suse.asia Beijing local procy scc scc-proxy.suse.asia(although it's not a MUST to our testing) it's now rewriting requests to openqa.qa2.suse.asia instead of openqa.suse.de, the assets/repo should be consistent the format Beijing local openQA is maintaining an own script but still need many manually activities when new build comes, and not consistent to OSD, that will request many test code change due to CC network change

    Goals

    Research this framework in case it will be re-used for Beijing local openQA, and will need to be setup and maintained by ourselves

    Resources

    https://github.com/os-autoinst/openqa-trigger-from-obs/tree/master https://gitlab.suse.de/openqa/openqa-trigger-from-ibs-plugin

    beijing :rainbow machine

    Automation of ABI compatibility checks by ateixeira

    Description

    ABI compatibility checks could be further automated by using the OBS API to download built RPMs and using existing tools to analyze ABI compatibility between the libraries contained in those packages. This project aims to explore these possibilities and figure out a way to make ABI checks as painless and fast as possible for package maintainers.

    Resources

    https://github.com/openSUSE/abi-compliance-checker

    https://github.com/lvc/abi-compliance-checker

    https://sourceware.org/libabigail/

    Fix RSpec tests in order to replace the ruby-ldap rubygem in OBS by enavarro_suse

    Description

    "LDAP mode is not official supported by OBS!". See: config/options.yml.example#L100-L102

    However, there is an RSpec file which tests LDAP mode in OBS. These tests use the ruby-ldap rubygem, mocking the results returned by a LDAP server.

    The ruby-ldap rubygem seems no longer maintaned, and also prevents from updating to a more recent Ruby version. A good alternative is to replace it with the net-ldap rubygem.

    Before replacing the ruby-ldap rubygem, we should modify the tests so the don't mock the responses of a LDAP server. Instead, we should modify the tests and run them against a real LDAP server.

    Goals

    Goals of this project:

    • Modify the RSpec tests and run them against a real LDAP server
    • Replace the net-ldap rubygem with the ruby-ldap rubygem

    Achieving the above mentioned goals will:

    • Permit upgrading OBS from Ruby 3.1 to Ruby 3.2
    • Make a step towards officially supporting LDAP in OBS.

    Resources

    Git CI to automate the creation of product definition by gyribeiro

    Description

    Automate the creation of product definition

    Goals

    Create a Git CI that will:

    • automatically be triggered once a change (commit) in package list is done.
    • run tool responsible to update product definition based on the changes in package list
    • test the updated product definition in OBS
    • submit a pull request updating the product definition in the repository

    NOTE: this Git CI may also be triggered manually

    Resources

    • https://docs.gitlab.com/ee/ci/
    • https://openbuildservice.org/2021/05/31/scm-integration/
    • https://github.com/openSUSE/openSUSE-release-tools

    Learn obs/ibs sync tool by xlai

    Description

    Once images/repo are built from IBS/OBS, there is a tool to sync the image from IBS/OBS to openqa asset directory and trigger openqa jobs accordingly.

    Goals

    Check how the tool is implemented, and be capable to add/modify our needed images/repo in future by ourselves.

    Resources

    • https://github.com/os-autoinst/openqa-trigger-from-obs
    • https://gitlab.suse.de/openqa/openqa-trigger-from-ibs-plugin/-/tree/master?ref_type=heads