[three]Bean

Back in Rochester after a wild ride at FUDCon. Here's a rundown of my participation (deets):

• Gave a lightning talk on pkgwat and a session on fedmsg.
• Worked out an API design for datagrepper with Ian Weller.
• Figured out a mechanism for end users to validate incoming fedmsg messages talking with Luke Macken.
• Toshio and I brought pkgdb into the fedmsg brood.
• It's been a long time coming, but I updated fedmsg in our production environment to be using zeromq3's TCP_KEEPALIVE features. We'll see if this solves our message dropping problem.
• We moved a new release of the /packages webapp to production which includes my dogpile.cache work.
• Jordan Sissel remotely hooked fedmsg up to the logstash demo.
• Talked with Dennis Gilmore about hooking koji up to fedmsg. We have a plan and it shouldn't be too much longer. Getting messages out of koji was the #1 request I heard at FUDCon.
• Also talked with Dennis about getting fedmsg messages out from secondary arch composes (the rel-eng process) and with Seth Vidal about getting fedmsg messages out from copr and our private cloud. Both situations require bringing messages in from untrusted environments and so will require some new measures. Plan++.
• Lots of discussion about Fedora Badges (the stack for which needs a lot of love). I'll be buckling down more on it once I finish the current phase of fedmsg, but having the discussions out about infrastructure, goals, and scope with the whole group was a good thing.
• Some good bar-time discussion of the GNOME OPW and how to make it more effective!
• Met pingou, the French crew, and really everyone else. The Fedora community is full of some pretty awesome people. :)

I've been waiting on the OpenShift team to crack the WebSocket nut for a while and they finally got it back in December. To try it out, I tried to set up the Moksha Demo Dashboard on two different gears.

It wasn't too tricky. I created two OpenShift "DIY"-type apps, one for the WSGI app and another for the WebSocket server (the moksha-hub). All the work in those two repos is done in the .openshift/action_hooks directories (the code is actually just installed from PyPI). Additionally, the diy/development.ini files hold all the configuration.

It's live now at http://mokshademo-threebean.rhcloud.com/ but it's our same demo as before. Other apps still in the development pipeline should be more interesting when they arrive.

I just finished setting up a fedmsg bot to post updates to identi.ca. You can check it out at @fedmsgbot. There's also this little realtime interface.

Why would this be of any interest?

• You can check @fedmsgbot for a public timeline of the development of Fedora.
• If you do something, and you're proud of it, you can go and "favorite" or "re-tweet" a message.

The code works just as well with Twitter (the bot can tweet to multiple platforms and accounts) but I ran into the daily maximum tweet limit; Twitter's 1000-new-updates-per-day is not enough for fedmsg. I asked Twitter if they'd allow an exception, but was denied. Ah, well.. if you have any workaround ideas, let me know.

The source for this, of course, is in the fedmsg repo.

So, I've been mentoring for some of the Fedora projects a la the GNOME Outreach Program for Women and I realized today that I'd actually met one of the applicants before in person at the Sprints at PyCon 2012. She could only stop in to say "Hi" and couldn't participate though; she was caring for an infant at the time. (Her husband did get to participate).

Since the sprints are where you can build real relationships with upstream(s), develop skills, become inspired, have an impact, find a role model, be a role model, etc.. I thought it would be good for the conference (or some sponsors) to provide quality, on-site childcare at the sprints. I wrote to pycon-organizers and stuff seems to be moving ahead. @jessenoller tweeted:

PyCon US 2013 Survey: 'Would You Use Subsidized Childcare at PyCon?'
http://bit.ly/V0g5jf

A survey. Nice!