One of the PuppetLabs guys is trying to enforce best practices on administering Puppet modules, by using base modules and build services and roles on top of them. That way we can re-use external / third-party modules from forge.puppetlabs.com, ideally without touching them at all. He names that "the Lego approach". Full article.
www.opensuse.org is the single most accessed page in the SUSE/openSUSE universe. With 1.5 million visits per month it generates 2.5 million page views and has around 500 people on the page at any given time. Yet it's one of the oldest, crufty pages we have!
It doesn't concentrate on what it should do: Tell people about the distro so they download it. It's design is 5 years old, it's not mobile, it's not accessible. There is absolutely no interactive, engaging content at all and the technology used goes as far as a shell script/cron to update dynamic content.
A web frontend for the mirrors in the mirrorbrain database to allow the mirror admins to manage their entries themself.
You might know MirrorBrain already: our download redirector and Torrent/Metalink generator used u.a. on download.opensuse.org. It's really a great tool that plays a hidden key role inside the openSUSE infrastructure.
Redmine.suse.de (as an inhouse tool) is very close to be a jump in replacement for Trello.com (the outhouse tool).
Investigate into setting up a redmine-board so that it has exactly (and only) the features a Trello board has,
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!
Currently compute supports only IVM managed pSeries machines. In that case machines are not managed for central place. There shouldn't be a big deal to implement HMC support as IVM commands are pretty much similar to HMC.
Currently, opensuse-quickstart sets up a one-machine Cloud based on OpenStack, either with KVM or virtualisation. In order for bootstrapping further hosts, it would be much easier to set up only a bare-metal cloud on one machine, and PXE boot a 2nd machine via OpenStack Nova/Ironic.
Occasionally, new versions of openQA break things. How do you stop that? MORE TESTING!
Testing openQA by using openQA to ensure the new versions don't break should be a good example of how openQA can test everything and anything, even itself.
Meet up NBG meeting room Paris with fellow Ruby on Rails hackers, throw an editor/shell onto the wall, grab a cup of coffee and refactor OSEM code together.
That way we can share knowledge about setting up the development environment, editor tricks, RSpec patterns, gems or general rails code. Interested? Join us!
We have some internal systems for videoconferencing like Big Blue Button or OpenMeetings. But in my experience none of them can compare to Google Hangouts, which is still the best free (as in free beer) alternative for videoconferencing with integrated screen sharing.
While implementing an alternative to Sqwiggle on previous hackweek, I discovered Janus, a lightweight WebRTC gateway that proved to be a quite capable tool to implement video applications.
A new Puppet Master will be set up for the openSUSE and public SUSE infrastructure. We will need to move the puppet code from the old server to a new Gitlab instance, deploy it to the new box with r10k, and perform syntax, validation and RSpec testing through ci.opensuse.org
The zypprepo was written around 3 years ago, and was based on the yumrepo built-in type/provider. Nowadays zypprepo misses a lot of functionality, which will be automatically inherited if it gets rewritten to be in sync with the current code of yumrepo (as also discussed in its issues #5 and #9). If time permits, solving issue #4 would be also really useful.
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.