Acronyms are fun. Everyone at SUSE loves them. Just sometimes… you might not know what one stands for.

Meet SUSE Acronyms!

> This year's Hack Week is open not only for developers but everyone at SUSE!

If this is your first Hack Week and you aren't a developer (yet!) this project is a good place to make your first steps with Git. Just follow the instructions to add an acronym directly on our GitLab (No setup but VPN required) and you can proudly tell your friends and family that you opened a MR today!

If you are a developer and want to do some light Ruby hacking, you are more than welcome to have a look at the TODO of this project. There is still a lot of basic stuff to do and you might even learn one or two new things on the way.

Thanks to my great talent for booking my holidays always for the days where then Hack Week happens, I won't be here the first three days. But I made my whole team maintainers of the repo on GitLab, so they can merge in your acronyms and code changes. On Thursday and Friday I'll be back and can help you out if you struggled with something.

And now, Happy hacking!

Looking for hackers with the skills:

ruby jekyll acronyms

This project is part of:

Hack Week 19

Activity

  • almost 5 years ago: hennevogel liked this project.
  • almost 5 years ago: bmwiedemann liked this project.
  • almost 5 years ago: gfilippetti liked this project.
  • almost 5 years ago: thutterer started this project.
  • almost 5 years ago: thutterer added keyword "ruby" to this project.
  • almost 5 years ago: thutterer added keyword "jekyll" to this project.
  • almost 5 years ago: thutterer added keyword "acronyms" to this project.
  • almost 5 years ago: thutterer originated this project.

  • Comments

    • bmwiedemann
      almost 5 years ago by bmwiedemann | Reply

      I proudly opened a MR today: https://gitlab.suse.de/thutterer/acronyms/merge_requests/2

      • thutterer
        almost 5 years ago by thutterer | Reply

        Thank you! add-emoji

    • thutterer
      almost 5 years ago by thutterer | Reply

      More about the progress of this project can be found in its blog: https://thutterer.io.suse.de/acronyms/news

    Similar Projects

    Recipes catalog and calculator in Rails 8 by gfilippetti

    My wife needs a website to catalog and sell the products of her upcoming bakery, and I need to learn and practice modern Rails. So I'm using this Hack Week to build a modern store using the latest Ruby on Rails best practices, ideally up to the deployment.

    TO DO

    • Index page
    • Product page
    • Admin area -- Supplies calculator based on orders -- Orders notification
    • Authentication
    • Payment
    • Deployment

    Day 1

    As my Rails knowledge was pretty outdated and I had 0 experience with Turbo (wich I want to use in the app), I started following a turbo-rails course. I completed 5 of 11 chapters.

    Day 2

    Continued the course until chapter 8 and added live updates & an empty state to the app. I should finish the course on day 3 and start my own project with the knowledge from it.

    Hackweek 24

    For this Hackweek I'll continue this project, focusing on a Catalog/Calculator for my wife's recipes so she can use for her Café.

    Day 1


    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