Tahoe-LAFS is an open-source decentralized cloud storage system. It distributes your data across multiple servers. Even if some of the servers fail or are taken over by an attacker, the entire file store continues to function correctly, preserving your privacy and security.

With all the changes in the qa_virtauto world, our local CI testing has become rather fragile. This project is all about stabilizing the CI testing and ensuring all builds are fully tested - without manual intervention. :)

Small non profit organisations or activist groups need a Web presence that is easy to maintain by several authors. When using a CMS they do not have the resources to secure the CMS from the various possible attacs most CMSes are notorious for. Defacement or placing malicious content can damage the reputation of such non profit organisations.

Develop a proof of concept frontend based on React and Material-UI as an alternative to the JSP/Struts based frontend currently available.

...because openQA isn't going anywhere anytime soon.

Features I'd like to implement:

Description

Project Description

We're always struggling at home with the lunches and dinners. Most of the time we realize that by the end of the week that our diet has diverged from what WHO and many other organizations suggest. My idea is to create a scalable database of meals, a web interface and some logic that generates a balanced meal plan for a 5-day or 7-day week.

Project Description

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.

Description

Description

As a proud SUSE Engineer, I consider openSUSE is the best open-source distro out there just like all of us.

In previous Hackweeks, we've gone to warp speed in our virtualization CI testing through:

A utility to make beautifully printed maps from OpenStreetMap data.

Basically $topic, as of the latest release of ceph, we have some not so trivial support to pull off something like this at least for metadata, need to see if data sync is also permitted, and then probably hook it to sync to AWS itself

port notmuch/muchsync to android, with some java ui on top

There are customer use cases where sharing information via internet or uploading data somewhere is not acceptable for security reasons: this avoid the usage of some tool like the most famous Google Analytics, and prevent developers from understanding how the web application is used by the customers. I don't want to reinvent the wheel and re-implement a copy of Google Analytics, but getting inspired from it, the goal is to reuse information that we already have to extrapolate an analysis of the WebApp customer usage.