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.

Very often people find themselves wanting to store secrets in a way that either they can recover even if (for instance) their house burns down, or allow friends and family to recover if they pass away. Existing solutions to this problem are:

Current Situation [bsc#1201271]

Description

The compressed image of e.g. SLE Micro 6.0 is ~ 900Mb. ** The overall goal of this project is to make a smaller footprint (in terms of image size) flavor of the image. This is to be achieved by limiting the target use-case to simple RPi (4, 400, Pi Zero 2) server for home IoT. **

Project Description

Description

The project aims to explore how to design effective system messages and prompts tailored for AI-driven code refactoring tasks. By refining these prompts, we can guide AI models to better understand code structure, identify improvement opportunities, and execute refactorings with minimal manual intervention. The project will delve into creating system messages that balance technical detail with flexibility, enabling AI to perform refactorings that maintain code functionality while improving readability, efficiency, and maintainability.

This Hackweek I would like to finish enhancing of the mysql-packaging git repository [1]. This improvement mainly consists of scripts for a kind of simple continuous integration and git hooks to enforce a few policies for our project. If there is a time I will also take a look at the mysql package itself and check if there is anything to improve.

I heard that MVC is at the top of design pattern. I'm not sure it's true .

Adding some API documentation for Crowbar, which is still missing. There are some API comments along with the Rails controller methods, but some of them are outdated.

I want to understand the basics and architecture of KMS / DRM drivers in the kernel (also in mesa, but this project is more about the kernel-side). I will read docs and attempt to implement a virtual kernel-mode-setting driver (vkms) as described in Documentation/gpu/todo. This would be a KMS driver for a fake modesetting graphics device, just using normal system memory. This can be useful for learning, but judging from dri-developer discussions, also useful for testing hotplug races, plane blending and finding other KMS/DRI infrastructure bugs.

I will implement the ReaR upstream issue https://github.com/rear/rear/issues/1399

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

To ease debugging cgroup relates issues this suggests to:

I want to be able to create some 3D printing models for 3D printers. So starting to search for a good introduction and try it out...