The goal of Project MySelf is to build a system to collect data about yourself in a safe and private way, so that you control your data and you can decide what happens with it. Read more

Micro-service for - making a report

Writing code is wonderful, but it gets its real value, when it's released and shipped to the world. You know the mantra: "Release early, release often". Releasing code is not hard, but it involves a lot of details, and you want to get them right, because a release is this public statement "Hey, it's done, it works, you can use it." and you can't take a release back, once it's out there. To help with releases there are tons of release scripts which try to automate things. But they usually are quite fragile in case something goes wrong and a pain to test and maintain.

Machinery [1] supports the inspection of os, packages, patterns, repositories, users, groups, services, config-files, changed-managed-files, unmanaged-files. The inspection of disks it's covered yet. The goal of this project is to fill this gap by using libstorage.

or: Static Analysis of nil Values in Ruby Code used in YaST. YaST is written in Ruby. A large part of the code is Ruby that was

YaST code organization is a mess at many levels (files location, namespaces, code dependencies...). Recently we created this gist to put some of the issues on the table Many YaST developers will be at openSUSE Conference, that overlaps with Hackweek. The plan is to lock them all in a room with a blackboard and reach agreements on how the code should be organized in the future. Then use Hackweek to iron the details, document everything in some kind of style guide and, if time permits, even do some experiments about how to adapt the existing code to the new conventions.

Reporting demands on SCC are increasing. Rather than creating hand crafted 'one-shot' reports in response to every request, this project aims to discover whether there is a better way.

Read RoR docs and continue the TODO list from https://events.opensuse.org/conference/oSC16/program/proposal/894 + issues from https://github.com/ChrisBr/rails101/issues as a practice.

The goal of this project is to write a proof of concept of a new philosophy for yast2-storage-ng. Instead of just extending the API offered by libstorage-ng, the idea is wrap libstorage-ng so the Ruby code using yast2-storage-ng does not have direct visibility (unless explicitly desired) on the libstorage-ng classes and methods. If you don't know what all that means, keep reading.

Perl-apparmor is obsolete in the apparmor community. No one is maintaining it. However, opensuse has to keep it to interact with yast, which is the main consumer of perl-apparmor. Getting rid of perl-apparmor would mean: + Creating a new interface (JSON) to interact with outside world (IOW, yast)

After an internal call for help to take over software.opensuse.org deployment, I spend some time studying the code in order to find out what would it mean to take it over. The main reason was a PR from the community that has not been merged, and deployment depending on internal SUSE employees.

Doc as Code with Asciidoctor, Jekyll, and TravisCI

Goals: (Subject to change)

I want to write a new rubocop cop that verifies that a schema.rb file in a Rails project, references a valid migration.

The subject says it. Learning about DHT seems like a fun project.