Release v2.0 of the gem and dashboards TODO: https://github.com/influxdata/influxdb-rails/issues?q=is%3Aopen%20is%3Aissue%20project%3Ainfluxdata%2F118

VOVO is a server-client architecture to determine current abuild load on devel-network machines. The goal is to trigger machines on and off depending on build power. It is an attempt to reduce power consumption. Current status:

Learn the grub2 network stack and have fun with ipv6 network booting. :D

Smalltalk is an object-oriented, dynamically typed, reflective programming language and Pharo is a modern, open-source,

When we started brain storming a project for hack week, one of the floated ideas was to remake the 1983 film WarGames, and for lack of available space, a local lot with storage units was proposed. Over the course of the following years, while we planned, we realized that this whole idea would not be the most feasible, but it still felt like we were onto something. Eventually, we settled with keeping the name and changing the scope.

Spacewalk is the upstream project of SUSE Manager. Currently Spacewalk runs on RHEL, CentOS and Fedora, while SUSE Manager runs on SLES.

Currently there is support for TAP being added to OpenQA::Parser::Format However it has basic support, therefore the following is needed:

Logos Competition: openSUSE, Tumbleweed, Leap, Slowroll and Kalpa

The openSUSE Community is considering a new, distinct openSUSE logo to represent the project as well as four new logos for the following openSUSE distributions; Tumbleweed, Leap, Slowroll and Kalpa. There have been discussions of a new openSUSE logo over the years, but the timing to transition to a new logo wasn’t ideal, until now.

Feeling very comfortable with your (open)SUSE desktop? Don't get too comfortable; there's a lot of innovation out there. Try living in a different system for a few days, and see if you can find some innovative paradigms to bring back 'home' with you. Here's a few suggestions: * Feeling really crazy? Try Windows 8

Fresh air and motion helps your brain to come up with new and creative ideas. This hackweek project offers exactly this*. You can expect running exercises along the Nuremberg city wall. Running 25 to 50 meters sidewards, jumping, running stairs, etc. will give your brain new energy.

Project Description

Overall: Existing NFS-HA Consulting solution exists (for SLES15 SP1 and SP2+) and is in production at customers. Goal is to improve this solution, enhance the documentation and make it more robust.

Overview: We're building a mobile to-do list app using React Native and connecting it to a self-hosted Elixir backend. This project aims to create a user-friendly, cross-platform app for task management, with data syncing across devices.

The evfilter project (https://github.com/lhc4/libevfilter/) isn't able to substitute multiple events to one event or vice versa. I want to improve that and repair some other bugs.

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.

For testing Hawk, we're currently using a Vagrant configuration, and for testing HA releases we've been using a set of scripts originally authored by Antoine Ginies as a Hackweek project. My vague idea is to combine Terraform, Salt and a custom web frontend to make a tool that can be used by us as developers but also for others that want to try Hawk or play around with a cluster, for example for the UX team when testing modifications to the Hawk UI. I would base this on the work done by the SUSE Manager team:

I tried to work blockchain into this, just so we could cover the trifecta of buzz words. Sadly I could not maintain saintly and do this. What do I plan on doing? a few things, so please reach out if you would be interested in any one of them. I will update with a list later.

Sometimes you search for a package, and you don't find it because you're not typing it right. Of course there's regex support behind the scenes but it requires conscious effort to make use of.

Motivation

Right now, every time a new team wants a new room in our Jangouts instance, they have to ping me and I have to manually create the room. That means: * Adding some lines to the corresponding config file

Now we are lack of using internal wiki page to solve problem. One of the reason is that we don't know if it contain the solution we need, and it's not convenient to search it manually in wiki page. It's much more slower than using google. In one group, we are most likely facing the same problem during work. So keeping the best solution, which we got from searching engine, in internal wiki is an efficiency way to collect standard workflow.

The current Jangouts UI is limiting us when thinking about adding new features. Some examples: * This (using the whole thumbnail to pin a participant) was implemented, but the result is far from optimal (I have not even deployed it in production).