The following openSUSE services might be effected:

• all openSUSE wiki instances, e.g. en.opensuse.org
• the wordpress instances like news.opensuse.org and lizards.opensuse.org
• the forums at forums.opensuse.org

• Update coordination: One or more maintenance groups can decide if and when to start or release an update. This includes also the tracking of new, running and processed updates.
• QA and Review integration: The current state of an update is always visible and trackable. Review processes can be integrated.
• Release Management: Isolated build and tested updates can be released or revoked via OBS mechanism.
• Multiple code stream support: An issue can be handled for multiple code streams.
• Documentation support: The documentation of an update for the end-user is integrated

This functionality is already used for doing the maintenance updates for the openSUSE distributions. The features can be used all together or in parts for own products.

In addition OBS 2.3 provides

• A greatly improved web interface, including user management, syntax highlighted source editor and improved source diff review views
• Improved Cross Build Support via Qemu
• Functionality to hide entire projects
• Issue tracking support, tracking documented fixes in external bugzilla, fate and CVE instances in packages.

It is recommended to read the Release Notes before updating an instance. OBS packages can be found in the openSUSE Tools project or as an appliance which can be used on hardware or in VM.

Your Open Build Service team

About Open Build Service

The Open Build Service (OBS) is an open and complete distribution development platform. It provides the infrastructure to easily create, release and maintain software for openSUSE and other Linux distributions on different hardware architectures. It is developed under the umbrella of the openSUSE project, but is licensed under GPL and used by other open source projects like MeeGo or Tizen. It is also used by universities, ISVs and companies like Intel, Dell, and SGI.

Support Offerings for Open Build Service

After receiving a new disk array, and restoring backups onto it, download.opensuse.org is back up.  The openSUSE Build Service is currently syncing all its repos to it, and then a full mirror rescan will be carried out so that the latest software is on all the mirrors that download redirects to. The temporary redirection has been removed.  The outage is to be discussed at today’s openSUSE Project Meeting.

–

It’s going to be a quiet May 1 for openSUSE users and contributors, due to a rare two-disk failure on download.opensuse.org, the central site for accessing openSUSE distribution releases and packages.  To work-around the failure, temporarily change your repository URLs using YaST Software Repositories or zypper (or edit the files in /etc/zypp/repos.d) to a nearby mirror.  Normally, requests to download.opensuse.org are redirected automatically to a mirror by the Mirrorbrain software running there.  On Monday, the disk hardware on download failed beyond the level its redundancy is designed to handle.  We are working to restore the system as soon as possible, and will post updates as soon as we have more information.

51 proposals, 12 students accepted

Big thanks to every student who dedicated their time thinking up and writing awesome proposals: we received a total of 51 proposals! This year Google allocated 12 students slots to openSUSE. This means we had a very hard time deciding! What projects will benefit openSUSE most, what will teach the student most? Do we mentor new students or give people already familiar with openSUSE a chance to dedicate some real time? There are practical considerations too. We don’t have mentors for all projects, or multiple students per mentor. Some mentors can only mentor in the evening, others only during the day – we have to watch time zones too.

But we’ve managed to extract 12 proposals out of the brilliance thrown at us and these students now will have to geeko up for their awesome summer job!

Selected projects

• Adding an Ambassador/Event plugin to openSUSE Connect -  Athanasios-Ilias Rousinopoulos will be adding event calendering to openSUSE connect, to make it easier to plan openSUSE events.
• Writing a better looking 1-Click Install client -  Saurabh Sood will be working on replacing the existing YAST-based 1-click installer with something much nicer looking.
•  Completing AppStream/Software-Center support for openSUSE -  Matthias Klumpp will be working on Appstream
• Improving the MongoDB destination driver for syslog-ng -  Eun Kyung will be enhancing syslog-ng’s Mongo support.
• Fixing/implementing automated kernel/glibc tests -  Marios Makris will be improving Linux Test Project coverage.
• openSUSE Karma plugin for openSUSE Connect -Priyanka Menghani will add a “karma” plugin to openSUSE Connect, similar to the “reputation” score on StackExchange.
• Further work on the osc2 client -  Marcus Hüwe is going to continue his existing work on the next-generation osc client for the Open Build Service.
• Popularity contest for RPM (popcorn) - Akshit Khurana will be working on popcorn, which will be optionally installed on openSUSE systems and provide us with statistics about which packages are popular.
• Redesigning fdisk to be more extensible and implement GPT support -Davidlohr Bueso will be cleaning up and refactoring everyone’s favorite disk utility, fdisk.
• Scanny, a security scanner for Ruby code - Piotr Niełacny will be be working on scanny, a tool designed to alert developers to security errors in their Ruby code.
• An upstream/downstream tracker -  N.B.Prashanth will write an “upstream/downstream” tracker tool that will track the differences between upstream versions and distro packages.
• Writable snapshot support for ext4 snapshots -  Yongqiang Yang will extend ext4 to support writeable snapshots.

The next steps

Now it is time to get in touch with your community, start speaking to people around you, discuss your ideas, read documentation, code and have loads of fun!

The Boosters Team

The openSUSE Boosters, widely known as the Ecstatic Eleven, is a team of people helping contributors to take off in our project. No matter if an ambassador needs help with organizing an event, an admin needs assistance with implementing a new service, or a developer needs guidance to bring his code into our distribution: the Boosters are here to work with all contributors to reach their goals and to enable them to bring this project forward. But the Boosters are not a bunch of lone fighters; the team always works together, in an agile fashion, on its milestones and every member is equally important and responsible for the success – and of course for celebrating it. It is a team of young, clever, spirited people from different backgrounds, countries and talents that want to collaborate. A team that wants to make a difference in this world by helping each other and our project to become even more awesome.

+ You

As you can imagine the Boosters goal requires people who are willing to explore the vast possibilities a FOSS project like ours offers. Boosters are as comfortable in front of an huge audience on a conference as behind an editor in a GIT repository. As the possibilities to contribute to openSUSE are endless a Booster must be agile, open minded and willing to take on tasks that require to learn completely new things. Be it a programming language, an application framework, how to give an interview to the press or what questions to ask in a questionnaire survey. Boosters are not afraid of anything and there is nothing they are not willing to do to attract and nurture contributors.

= Love?

Does that sound like it’s your thing? If yes, you will find a tight-knit team here that lives and breathes collaboration. A gang of FOSS aficionados that share your passion, hard workers and a wild bunch to have a lot of fun with. And equally important you’ll start with an employer that will bring your FOSS career forward: SUSE, which has been around for 20 years and is the original provider of the enterprise Linux distribution that powers thousands of organizations around the world across physical, virtual and cloud environments. A company that has been a leader and an active participant for years in tons of open source projects and open standards. Sounds great? It’s awesome, guaranteed!

So what are you waiting for? Head over to suse.com/company/careers, check out the position and apply. We’re looking forward to hear from you!

Introducing Heinlein

Heinlein Support has specialized in Linux servers and e-mail services for over 20 years. They share their knowledge and their experience at the Heinlein Academy, during personal consultations, through their hosting services, and through their appliance and software products.

Peer Heinlein said:

After working with SUSE technologies since 1994, we’re very happy to have a chance to contribute something back to the openSUSE Community. For our customers, the (open)SUSE-platform has always been a very reliable distribution for business and enterprise use cases.

Supporting openSUSE

We are happy to announce that Heinlein Support is sponsoring the openSUSE project by providing infrastructure to run the project.

Henne Vogelsang told us:

I believe Peer and his crew will help us to take our mail infrastructure to the next level and I’m happy that we have the opportunity to work together with them. I mean that guy wrote a book about postfix and has tons of hands-on experience with mail infrastructure, how awesome is that?

GoWhat

According to the description from the go-lang website:

Go is a programming language and environment that makes it easy to build simple, reliable, and efficient software.

Go is an expressive, concurrent, garbage collected general/systems programming language that is type safe and memory safe. It has pointers but no pointer arithmetic. Go has fast builds, clean syntax, garbage collection, methods for any type, and run-time reflection. It feels like a dynamic language but has the speed and safety of a static language.

In a discussion on python vs go you’ll find that

Clearly Go is a superior weapon if the goal is to shoot everyone in the foot at the same time. The GIL in python forces you to shoot each person in the foot in sequence :).

(by Kyle Lemons)

In other words, go is optimized for concurrent programming – getting the most out of our modern multi-core systems.

GoGetting

To install go, one can use the new graphical interface at software.opensuse.org by going to software.opensuse.org/package/go. Get the documentation here (go-doc) and if you’re a VIM user, also get go-vim. From a commandline, Factory users can do a simple zypper in go go-doc go-vim. If you’re on openSUSE 12.1 or other versions you’ll need the devel:languages:go project. Lots of additional stuff there of course. Note that adding go via the software.opensuse.org route will add the devel:languages:go repository to your list, allowing you to pull in any of the extras easily.

GoSetup

You’ll have to know and set a few thingies now:

• Either source /etc/profile.d/go.sh or open a new terminal to import the Go env vars into your environment. Your $GOPATH will be set to $HOME/go so either override this in your profile or create the directory.
• Go libraries and packages installed from the openSUSE repo are installed to $GOROOT and the system bindir. Any extra packages or binaries you install using the “go” tool will be installed to $GOPATH and $GOBIN (if it’s set).
• Currently $GOBIN for non root users defaults to $GOPATH/bin, we currently don’t add that location to your $PATH so you will either have to add it in your profile or set another location for $GOBIN (such as $HOME/bin). See the golang documentation for more information.

GoGo

It’s time to get Going now. An excellent way to check if everything is setup OK is to install and run the Go Tour! If you have a viable Go environment the following two commands will execute without error.
go get code.google.com/p/go-tour/gotour
gotour
When you have a working environment, the following documentation is a great resource for first time Go hackers:

• Golang Documentation
• For experienced C, C++ and Java hackers I also recommend the Go FAQ.
• Go language community support: Mailing List and #go-nuts on freenode

GoFun

More information on the current Go setup in openSUSE can be found on this wiki page. Thanks to Graham Anderson for the information there and this article.

If you would like to just play with Go before installing it, there’s a pretty cool tour set up on the golang website: click here to start. You can edit the code and run it live on the site!

Funny images of the go mascotte courtesy of the golang.org website.

To download the openSUSE 12.2 Milestone 3, go directly to the download directory.

To download openSUSE 12.1, go directly to the 12.1 download directory.

For everything else, please wait until the server is fully up again.

Update 2012-04-12 19:37 UTC: Everything should be up again.

Like the M2, there has been a bit of a delay getting this testing milestone out. Some kernel changes made it initially impossible to build the 32bit version of openSUSE but these have been fixed. Download it from software.opensuse.org/developer. As usual, a list of the most annoying bugs is being maintained and you can see the list of bugs and/or file a new one in Bugzilla. Read on for some details on the release and how to help!

The roadmap aims Milestone 4 for April 26th.

Factory development

openSUSE, as you might know, is being developed in Factory. Factory is a project on the openSUSE Build Service against which you can build a package. If it works fine, you can submit it to Factory and keep it working there.

List of failures in Factory - help get rid of them!

Status: in!

Factory has now received the latest versions of GNOME 3.4, KDE SC 4.8.2 (with numerous KDE PIM bugfixes!) and finally LibreOffice 3.5.2 has landed as well.

In a recent blog openSUSE contributor ‘tittiatcoke’ gave an update on Plymouth support in openSUSE. Plymouth itself is merged and integration into other packages is nearly finished, the issues are being worked out through some team efforts, for this milestone plymouth is not yet the default. The latest status can be tracked on this wiki page. Currently the team works on openSUSE branding to complete the new boot experience.

The integration of grub2 as bootloader has seen further steps and we ask for testing of grub2. Unfortunately the LiveCDs cannot install grub2 in this milestone (see most annoying bugs for a workaround).

Status: Close…

We’re very close to getting GCC 4.7 in – the latest status update concluded that a bug in GCC 4.7 blocks zypper from being build. This will be fixed in the 4.7.1 release expected in June but to facilitate testing a patch will probably be applied on 4.7.0 to have it in the next milestone.

USRMove and tmp-on-tmpfs is still being debated, a final decision has not been made yet but it looks like we’ll wait with this for at least another release.

Improved software search

Software search

The software search improvements being tested over the last weeks have moved to software.opensuse.org and users looking for software to install on their openSUSE system can now enjoy the new UI, featuring screen shots and more extensive information about the applications available.

Help out!

Of course you’re wondering how you can help. This can start with testing. Go to software.opensuse.org/developer, download Milestone 3 and try it out on your system! You can then check the
most annoying bugs to see if your problems are there, if not, you can see the list of bugs and/or file a new one in Bugzilla. If the bug you find is very serious, add it tho the list of annoying bugs!

If you are a packager (or want to be one!) there is of course also plenty to do. Fixing bugs in packages is a nice way of learning the ways of packaging (see the Packaging portal for documentation). You can read about how to do this here, via a simple set of stepps which in openSUSE are commonly known as ‘BURP-ing’.

Factory Workflow

If you’re already a packager for openSUSE, don’t forget to get your packages in Factory or start to maintain one!

Thanks!

We’d like to thank everyone working on openSUSE for being so cool. Special hugs to the top-ten factory contributors over the last 6 weeks (according to some scripting by AJ):

• Vincent Untz
• Stephan Kulow
• Dirk Mueller
• Dominique Leuenberger
• Jan Engelhard
• Sascha Peilicke
• Marcus Schäfer
• Ciaran Farrell
• Ralph Lang
• Cristian Rodriguez

Note that the list above doesn’t credit the hard work being done by the Packman team or people building packages outside of factory!