This is somehow related with our team's work(https://fate.suse.com/323437), We want to write a set of restful API for any components in HA product stack use to control the cluster.

Ai and Machine learning play important role in our life, I'd like to learn it.

I'd like to write a webservice comparable e.g. to Evernote or NextCloud. Emphasis of the project is that the server only provides storage for the actual data and keys; en- and decryption is to be performed by the client.

Currently Salt is using supportconfig utility alongside with the SUSE Manager installation. Every single bugreport for Salt, that contains its logs are always useless that regard. It might work for SUSE Manager, but for Salt it doesn't. And even after asking user to switch the cluster into a debug mode or even trace mode, it is still far away from being useful enough, so the supporter don't need to dance with the tambourine around the fire, guessing what ghost just munged what component.

At SUSE/openSUSE we are using (at least some times) Etherpad, whose functionality is really limited and looks as taken from the past. After taking a look to other possible Open Source alternatives, I think there is at the moment any which offers all the feature I would like to have. Because of that I would like to contribute to JetPad, with the idea of using it privately and that it can also be used by SUSE/openSUSE.

Intel Chen Yu developed a user land utility:

Hacking on the advanced open source computer algebra system -- FriCAS, which has a long history that dates back to 1965. It has not aged very well: 108 C files has been edited only 66 times in the past decade, and full of compiler warnings;

The Bard music manager is a command line tool to organize local music I've been developing over the last years (in Hackweek 15 it was called finddupmusic). It parses your local music collection and stores the metadata in a sqlite database, then it can generate audio fingerprints and recognize similar/duplicated songs. It can also be used to play music (using internally mpv), set ratings, fix metadata, etc.

On a smaller internet connection or offline the development experience can be severely degraded. This has a big impact on hackathons or other events where multiple people want to get the same content. Workarounds over USB sticks are less usable than an automated way can be. A content addressable transport that can work on a local network without internet would be better.