This project is about advancing the tool you're currently browsing. It got started back in Hack Week 9 to retire all the weird tools we've used in the past to track ideas. As you can see it has gone far but is still far from done. There are lots of features missing and bugs to be fixed on github. Get going!

All other distributions have scanmem/gameconqueror packages. scanmem is a command line memory scanner to locate variables in memory and GameConqueror is the Python/GTK3 front-end for it which also provides game trainer features. But it is not only a game cheating tool. It can also help testing applications, debugging memory issues, watching variables in memory or it can be used for reverse-engineering. Hackers also use it for things like ping spoofing. As the upstream maintainer of this tool I'd like to bring it to openSUSE and maintain it there.

Previous hackweeks spent on research (project/220), other alternatives. This time I'm

We need statistical analysis and key performance indicators to describe the lifetime of maintenance and release requests in IBS, for example: - How long does an update take starting from the time the first maintenance request is created and stopping at the time the update is released to customers?

kanku is designed to give you a better integration of your kiwi images built by the Open Build Service (OBS) in your development and testing workflow. The idea is to refactor kanku-scheduler so it can use distributed workers for more scalability using the following technologies:

Mission: Our company org chart consists mostly of teams + their project managers. teams.suse.com is an application that gives an overview about the various SUSE team resources like org-chart, office locations, mission descriptions, links to team pages/blogs etc. It should combine the various data sources that are already there (eguide, floor, externaltools etc.) and provide a way to enrich this data.

During the last GSoC, Jangouts was ported to work on Angular 2. Among other goodies, like the component-based approach or ditching the $scope thingie, Angular 2 leverages the use of observables thanks to its integration with RxJS. However, when the project started, our student (who did a great job) had to fight^Wwork with a beta version of Angular 2 and, unfortunatelly, the API changed before the release of the final version.

Currently the upstream LTP is executed by a hacked up and old runltp script that executes even worse and fairly old mess called ltp-pan which in turn actually executes the test cases. This whole thing is a unmaintainable mess that should have been replaced with something simpler a long time ago. It should also have a few more features that has been requested in the meantime and not implemented since nobody wants to touch the code. For instance executing the test cases on a different machine via ssh and writing the results locally. Another feature I've been thinking about for quite some time is a parallel test execution, since most of the test cases in fact could be executed in parallel which could easily speed up the test run twice. There are other tests that cannot, mostly stress tests, but also test cases that modify global system state, i.e. system time, make use of sysv IPC, use loop devices, etc. These kind of tests should be annotated somehow so that we do not end up with a test cases competing for a global resources in a parallel test run.

Create a task tracking tool that would suit my needs (and enrich the pool of such author-only-optimized software). - TUI interface

GeekoScreen - an open-source based whiteboard

Idea