FUDCon Day 2 – Update

I’ve attended spot’s barcamp session on the new applications the infrastructure team is working on. Some remarks:

Gamification

Gamification is a very interesting idea for a community based project. The new tagger page is making use of these concepts, so the more tags people tag, the more badges they earn. We even might have a “Fedora Contributor Network”, where we’ll have ranking boards for Fedora based on their accomplishments. Well done, guys!

Software centers, App Markets or whatever

The concept of a place that is a one stop shop for your software needs is not a new idea, and definitely organizations have been building successful models around it. I for one would like to see such a software center in Fedora.

Spot argues that it is a successful model for people looking for earning money out of it, but I beg to differ: In Fedora, we are interested in a subset of these goals: we want people to browse the available apps in our repos [1], and install that software with the least hassle possible (ideally with 1 click), with great search capabilities, and possibly reviews and other cool things around it.

Anyway, I understand why the team didn’t come after this model in the first pass. I’d like to see things going on this direction, although such an undertaking is huge work, and brings obvious concerns over scalability and maintainability. Still, good to think about it…

[1] We don’t even have to introduce the concept of ‘repos’ to people, making things easy to grasp to less-technically inclined people.

FUDCon Blacksburg 2012 day 2

So, here we are gathered for FUDCon day 2, where the bar camp sessions are going to happen. I expect to give my Fedora test automation talk soon. The purpose of the presentation, simply put, is to show how we can get good concepts from open test initiatives and apply them to Fedora. If you’re attending FUDCon and is interested, please drop by

My autotest TODO list during FUDCon

I probably didn’t mention, but packaging autotest is been a tough task, mostly because:

• Autotest uses a “self contained directory” design
• Makes sense for its purposes, but no go for packagers
• Web interface depends on gwt, which is hard to package properly

As a result, it’s been a long ongoing task with upstream to make it more packaging friendly. But, we’re almost there. I promise

I’ve started to assemble my TODO list for the FUDCon days. It shouldn’t be that difficult to get this done between one presentation and another:

• https://github.com/autotest/autotest/issues/88
• https://github.com/autotest/autotest/issues/89
• https://github.com/autotest/autotest/issues/140

I hope to come up with more stuff, let’s see…

FUDCon Blacksburg – 2012

Here I am in Blacksburg, at the VirginiaTech campus for the 1st day of FUDCon. It’s always good to see again the fine ladies and gentlemen that bring you Fedora I’m in the Secondary Arch hackfest, where TODO list items for the Power version of Fedora 17 are being discussed:

• KVM feature, feature process + deadlines (I’m interested in this one)
• F17 schedule
• Build boxes
• Test team status – bugzilla review with the IBM team
• Road map and release engineering

It’s gonna be an interesting conference

Going to FUDCon Blacksburg 2012

Hello [peeps|ninjas|folks]:

I’m getting ready to go to FUDCon Blacksburg next week, where I’ll talk about the current Fedora test automation initiatives, as well as work with the brave folks of the QA team to put all nails needed in the coffin of the task ‘autotest packaging’. I’ll be around, so if you are interested in test automation, let’s talk about it!

See you in about a week,

Lucas

Autotest moved to github

It’s been a while that the Autotest open source project services were managed on a machine, test.kernel.org. We’ve been using SVN during the the inception of the project (mar 2006), and the move to a distributed source control system was long overdue. Also, we were short on maintainers for the project, so we needed some better governance policies to ensure autotest would run smoothly even with people not able to work on it anymore.

With the recent security incident involving kernel.org, our domains were taken out of DNS as the administrators of the domain were working to fix the security breach, that made our life a bit… hard, to say the least. All the infrastructure we were relying on, our trac instance, that comprised wiki, source code visualization, timeline view, and our patchwork instance, gone.

So, this inconvenient situation triggered the work to fix most of those aforementioned problems. Now we:

• Moved to git
• Moved to a source code hosting facility, so we spent less time maintaining infrastructure and focusing on delivering a kickass code base for our users
• The new infrastructure also has a code review mechanism, better than using patchwork
• An interesting look at how to contribute changes to the project (github pull requests)
• The wiki now is a git repo, with plain files written in reStructuredText
• We added new maintainers for the project and now are in the process

I’m personally very happy with the improvements we’ve implemented, but there’s quite a bit of stuff to be done. So, be welcome to our new project page:

http://autotest.github.com/

We will make autotest.kernel.org to point to this domain, stay tuned

Hello Planet Fedora!

Hi guys, my name is Lucas Rodrigues, and I’m the maintainer of Autotest, the base software for Fedora’s AutoQA. I am a Red Hat engineer working full time in test automation, and I’m very happy to help the Fedora with its testing infrastructure. This is my first post to Planet Fedora, and my idea is to blog about the Autotest project and other thoughts about test automation, and well, of course, Fedora

Autotest 0.13.1 released!

We are proud to announce a new release of autotest, 0.13.1. This is a
fairly boring bugfix release, so nothing really new here, just more of
the same.

What is autotest?

Autotest is a framework for fully automated testing. It is designed
primarily to test the Linux kernel, though it is useful for many other
purposes such as qualifying new hardware, virtualization testing and
general user space program testing under linux platforms. It’s an
open-source project under the GPL and is used and developed by a number
of organizations, including Google, IBM, Red Hat, and many others. You
can see results of kernel test runs on

http://test.kernel.org/tko/

Release repository:

http://test.kernel.org/releases/0.13.1/

Release notes:

http://autotest.kernel.org/wiki/Release0.13.1

Autotest project main page:

http://autotest.kernel.org/

Want to hack on autotest? Please refer to:

http://autotest.kernel.org/wiki/DownloadSource

http://test.kernel.org/cgi-bin/mailman/listinfo/autotest

Please report any issues on our bug tracking system:

http://autotest.kernel.org/newticket

In order to be able to open tickets on our bug tracking system, refer
to:

http://autotest.kernel.org/wiki/SiteAminContact

Happy birthday Linux!

Linus Torvalds, 25 August 1991 on comp.os.minix (original message)

I’m doing a (free) operating system (just a hobby, won’t be big and professional like gnu) for 386(486) AT clones. This has been brewing since april, and is starting to get ready.

Cheers! Happy to be part of the greater Linux ecosystem

Getting ready for KVM Forum and LinuxCon, 2011 edition!

Hi guys,

I’ve been pretty busy preparing myself to speak at 2 events in Vancouver, Canada, LinuxCon 2011 and KVM Forum 2011. If you want to check out what I’m up to there, here are the slides for both presentations:

• LinuxCon 2011 slides – Autotest: The kernel test framework
• KVM Forum 2011 slides – Making KVM autotest useful for developers

It will surely be an awesome and hectic week there See you guys in Vancouver!