Another all too early start of the day, and we all had gathered in the auditorium to hear Aeva Palecek from lulzbot talk about 3d printing. Most every disaster you can think of happened during this presentation, but happily Aeva and Flock staff were able to overcome every obstical and have an entertaining, informative and great talk. Aeva went over her history with 3d printing software and showed off the process all the way to printing a fedora coin on a reprap. Great stuff. I really hope Fedora is now and will continue to be a great platform for 3d printer enthusiasts. The biggest danger from this talk is that now I want to go and buy/make a 3d printer to play with it myself. :) After the keynote (and a quick check to lulzbot that their printers were currently out of stock, but expected back soon) it was off to the Fedora at yahoo talk. Yahoo has rolled out quite a bit of Fedora for their engineers/employees and it was interesting to hear how they set things up and and what issues they ran into. They love that Fedora is all free software. They so far deployed Fedora 17 and then have recently started moving to Fedora 19 (they skipped Fedora 18 because they couldn't justify that quickly upgrading the just deployed Fedora 17 hosts). The release cycle has been a pain point for them, along with some issues with 32bit software running on 64bit installs, and reliability of upgrades. Next was a talk back in the main auditorium on Fedora Badges. We just enabled badges a few days ago and it's live and running along now. See https://badges.fedoraproject.org for your badges and information. I knew everything that the talk went over, but it was a good introduction to our badges setup and how to help out with it. I really hope this helps make Fedora more fun for a lot of people and it's really great to see it up and running. Next was task automation in qa. This talk went over the problems and limitations in the current autoqa setup and a general plan for a next generation framework. Things are generic and high level enough at this point that it should hopefully allow things to be flexible. It also seems possible that this setup could be handy for other groups in Fedora besides QA. Since it's a method of setting up tasks that run on triggers it's more of a cross between continuous integration and a scheduler. For example, projects like Fedora docs might well find it useful to build on every commit in this system. After lunch was a infrastructure hackfest on OAUTH. We have several places where we would like a system that allowed users to get a token to have permissions to run things from command line or cron jobs or other automated tools. We spend pretty much the rest of the afternoon hacking away at this and came out with a plan for implementing something that should do what we need. It's not really OAUTH, but it's similar. It should allow people to do things around auth tokens and keep us secure. Look for more information as we get things implemented and call for early testers. Dinner was at a place called Mynt. Very good food, drinks and conversation. Now to try and sleep and get ready for tomorrow. I have my talk on the life cycle of a package tomorrow as well as lots of fun sounding talks. One thing thats been amazing for me this year is that there has not been a single timeslot where there is not at least one talk I want to attend. Usually it's been a hard decision between two (or even three) talks. :)