Join our mailing lists

No readers like this yet.

Get email updates

Sign up here to get highlights and updates delivered to your inbox.

We're asking for only your email address—we like to keep these things simple. The newsletter is sent through Red Hat's email subscription services, which is why it has a URL.

After signing up, you may want to add highlights at opensource dot com to your email filters.

Community discussion list

Do you want to help out with but aren't sure how? Interested in seeing some of the behind-the-scenes work that's going on? We've created a community mailing list that is open to anyone and everyone.

You can subscribe to the list at:

This list is for the community, which includes the people who write, edit, moderate, maintain, publish, design, think about, make plans, sets policy and governance, and otherwise do the work that makes this a community practicing the open source way.

This list is not meant to substitute or supplement the discussions that occur on It is meant to be the location where administrivia and such topics are discussed. The list and archives are open to the general community, as is the open source way.

It's important to reiterate that conversations that could happen on should continue to happen there—it's a more open forum than a mailing list. Appropriate discussions for the mailing list have more to do with execution of the site than with the stories we're telling on it.

We welcome you to subscribe and start participating, share your ideas, and help improve our community.

Jason Hibbets is a Community Director at Red Hat with the Digital Communities team. He works with the Enable Architect, Enable Sysadmin, Enterprisers Project, and community publications.


nice, i'm in :)

I would love to get on board with helping out as a drupal developer & systems administrator for

Paul Booker

Paul, this is great news. I've been trying to figure out the best to make the feedback visible and create a list of things to do to improve the site. The one catch is that we have support through Acquia on the site, which is great, but might limit some of the things we can do. Limits were meant to be broken though.

I'm definitely open to ideas and suggestions.

Hi Jason,

Apologies for the late reply.

It would be great to open up site development to our community by

1. creating a tarball of all code that is static i.e dupal core & contributed modules
2. placing bespoke code into a version control system i.e glue modules & theme
3. providing a sanitized version of the database
4. keeping track of issues with a bug tracking system
5. providing a staged version of the site under an apache .HTACCESS directory

Paul Booker

Since you recently interviewed Tim Rayner (Coalition of the Willing) I have been spending more time here, and I like what I am seeing. Under the Coalition banner we've been advancing a discussion on Open Stewardship, and I think is already modeling some important aspects of that approach. Keep up the good stewardship!

Thank you for keeping the further developments of the site and community as open source as possible. I'm thrilled to be a part of the community and as an active reader I'm always looking for ways to get more involved. I hope to "give back" in the next couple of years by helping in some ways. So far its mostly been by promoting this site to friends and social media community.

So thanks again,


Thanks for your support. Every little bit helps, whether it's sharing a good article with a co-worker or just pointing friends to the site as a resource to understand how open source can be applied beyond technology.

And we are always open to new ideas for the site and content. Thanks for being part of the community.


I've got a couple nit-picks to discuss in here ;)

We like constructive feedback, so please let us know how we can make things better.

I want to continue to be kept informed in Red Hats efforts to spearhead opensource worldwide and to share these ideas in my community.

Creative Commons LicenseThis work is licensed under a Creative Commons Attribution-Share Alike 3.0 Unported License.