Data from the PostgreSQL Job Task Analysis survey.

I shortened some questions and answers to better fit on the page; see original data if you are concerned about potential shifts in meaning. In many cases, I re-ordered the answers in a way that makes sense to me. Again, please see the original data if this concerns you.  Not all data has been graphed.  Graphs created in OpenOffice Calc.  I would have rather used Gnuplot, but I preferred the horizontal bar chart style & gnuplot can’t do that yet without a lot of gymnastics.

PostgreSQL JTA - Graphs

You need:
root/sudo access to a statically-addressed Ubuntu machine.  (It will need to be on whenever your router is on in order to get anything good out of this.)
Enable access to your Cisco router.

Part 1: Set up your log host.

Step 1: before editing any of the files discussed below, be sure to back them up, e.g.:
cp /etc/syslog.conf /etc/syslog.conf.dontmessthisup

Step 2: edit /etc/syslog.conf to include this:
#router logging
local6.debug                    /var/log/cisco.log

This means “send all messages from facility local6, with a priority of debug or greater, to /var/log/cisco.log”.

(Note that the default facility for Cisco is local7; if you want/need to use the Cisco default, change the above accordingly.)

Step 3: create the log file I specified above:
sudo touch /var/log/cisco.log
(more…)

Last night, an incredible number of people showed up to Code-N-Splode to hear about Git.

I was not at all prepared for that number of people, but grateful that a couple experts were on hand to help - Sarah Sharp, Audrey Eschright and Michael Schwern (and others) all contributed to the discussion. Thanks for all the great questions! I’m looking forward to Sarah’s advanced tutorial next month.

We love feedback - I’ve got alerts, RSS feeds and filters up the wazoo to let me know what people are saying. And the new feedback system for OSCON totally rocks!  We got messages about how we did instantly, and there’s nothing better for improving your presentation than getting constructive criticism right away.

But there was one message that really stuck in our craw!  Someone thought we had emphasized the social aspects of running user groups way too much.

Here’s the thing: user groups are social. The primary mission of a user group is to (wait for it…): Meet Other People.

That’s the difference between a lecture, or a class, or a job. Maybe you are coming to the meeting because you want to learn something from the topic, but the primary goal of a user group has to be about the people who are there and facilitating ways for those people to make one-to-one connections.

User groups are a way to, on a very small scale, enable the type of connections you can make at conferences. Except user groups target a very specific topic, and can in some cases be a better bet for meeting people concerned about the same things as you are in your industry!

And usually, user groups meet after hours during a person’s free time - time that they could be spending with their family, friends or just chilling out. Respect that donation of time and make it worth a person’s while! A bit of technical information never lasts as long as a new colleague or friend.