If you’ll be joining us at OSCON this year, be sure and check out the Evolution of Community panel featuring yours truly.
Over the past ten years, nothing has impacted business more than community. Whether through the openness of software development spurred by Linux or the dismantling of media empires through blogging, the rise of communities has been the driving force in how we work and live today. But what’s next? For open source developers, what has to happen to maintain and grow the communities they’ve built? What happens to communities when successful projects are acquired by big corporate behemoths? What happens to communities when their projects fail?
I just can’t get enough of the code swarm visualization project. Michael Ogawa used Processing to create an “organic visualization” of well known open source projects like Python and PostgreSQL. It shows commits, by developer over time. Clouds of influence drift in and out of the core ring, branches tug one another back and forth as the code explodes across cyberspace.
I tried it full screen and zoned out so bad I got the munchies. So it’s my new Calgon. I like to load up some vintage Apache and play a quick round of “Spot the Hyperic Exec[tm]“. Watch it, and see who comes cannonballing right into the angry heart of the swarm. If you listen closely, you can hear him scream “Leeroy Jenkins!” before being engulfed by the flaming core.
This is my first blog post as the Director of Community Management for Hyperic, so I suppose I should begin with an introduction. I’m Jeremy Hogan, and I’m a hacker. If something works, I want to pull it apart and see how. If it’s broken, I have a compulsive need to try and fix it. Open source is my crack.
My first real tech job was as a web slinger in the mid-90s. Back when open source was called “right click > view source”. I got wind of this Linux thing and went to work for Red Hat. There I got to use my LAMP, network and sysadmin skills in anger for some bleeding edge customers in enterprise support. And believe you me, there was plenty of the bleeding.
From time to time, I think about what the definition of a small company is vs a big company. Many know I came from Siebel, a big company that was swallowed up by an even bigger company Oracle. I have been at Hyperic for a couple years now, and when I started we were assuredly small. 13 people and one plant small. Since then, we’ve hit many milestones to consider ourselves almost mid-sized… but today was a new one.
Marty Messer, our esteemed Director of Customer Success has been recently deluged with the same request from some of our top customers, “do you know anybody we can hire?”
Once again, SourceForge.net is holding its annual community choice awards. As a former SourceForge.net worker bee, it’s great to be able to utilize what we built at VA Linux all those years ago.
So, if you’re a fan of Hyperic HQ - and if you’re not, you really should be - nominate us in one of the categories. Click the image to the left, and the rest is up to you!
Since the introduction of the HQU Plugin Framwork, we’ve seen a lot of activity in the Hyperic community around using this new capability to take HQ places it’s never been before. I might be biased, but quite honestly the idea alone of HQU makes me a bit giddy. Anytime I see this kind of power being put in the hands of users and administrators I know something good is happening. No longer are users tied to official release schedules to bring new functionality to HQ. No longer is the intended use of HQ the only use of HQ. No longer are the tools of production held solely by the select few. Power to the people!
The latest edition of the Hyperic newsletter is now out! Read about the Hyperic HQ 3.2.3 release, our partnership with Terracotta, the new Oracle Application Server, the Velocity Conference, and much more!
Today, Hyperic is sharing an exciting new plugin as part of our ongoing preview of Hyperic HQ 4.0. The beauty of this plugin is it actually supports TWO products:
As a relative new-comer to the Hyperic Engineering team, I would like to use this opportunity to introduce myself to the community. I spent the previous two years as a platform engineer working on the Oracle Communication and Mobility Server. At Oracle, I helped integrate the J2EE and SIP application servers, exposing management and configuration features via Java Management Extensions (JMX).