Skip to content

Instantly share code, notes, and snippets.

@rbowen
Last active August 29, 2015 14:11
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save rbowen/217b4d5b32c4060bdef6 to your computer and use it in GitHub Desktop.
Save rbowen/217b4d5b32c4060bdef6 to your computer and use it in GitHub Desktop.
RDO Packaging - blog post

When we started the RDO project back in April of 2013, the main focus was on producing a distribution of OpenStack that made it easy to deploy on CentOS, Fedora, and Red Hat Enterprise Linux. While we put time into making it easy for the community around that distribution to grow and support itself, most of the technical work was done inside Red Hat, and there were parts of it that weren't very visible to the community.

It's time to prioritize opening up the RDO development process, and making the technical governance of the project available to the entire community.

https://www.flickr.com/photos/rbowen/15981888051/

A month ago in Paris, at the OpenStack Summit, 40 or 50 RDO enthusiasts gathered to discuss the RDO community, and what we can do to make it more inclusive. The number one thing that was asked for was more documentation around the process, and transparency into the CI results, so that everyone can see what's going on, and know where they can jump in.

Our first step in this direction is to document the packaging process. This document is still a work in process, but we felt it was more important to get it out into the open than to wait until it was perfect. So here it is: http://redhat-openstack.github.io/openstack-packaging-doc/rdo-packaging.html

If you want to get more involved in the RDO community, this is a great place to get started. We're hoping that people that are interested in specific parts of OpenStack will step up to package those bits. The more people that are doing this, the faster we can move on everything. Everyone benefits. And more eyes on all of the moving parts ensures greater quality all around.

The second step that we've taken this week, in an attempt to address the second concern, came via the CentOS community. CentOS has recently spun up a new server specifically for community CI, so that open source communities can verify their builds on CentOS. The full details of this server may be seen on the CentOS development list archives, at http://lists.centos.org/pipermail/centos-devel/2014-December/012454.html and the details of the hardware itself may be seen at http://wiki.centos.org/QaWiki/PubHardware We're in the process of putting some of RDO's CI on that infrastructure, so that it can be more transparent, and more accessible for non-redhatters to participate.

If you'd like to be involved in that process at all, be sure to join the rdo-list mailing list - https://www.redhat.com/mailman/listinfo/rdo-list - and also the centos-devel mailing list - http://lists.centos.org/mailman/listinfo/centos-devel - where the CentOS side of this conversation will be happening.

We know that the community is the most important component of the RDO project, and we want to do everything we can to open things up for you to participate, and the tools to solve your own problems. If there's anything more that we can do to improve your experience in the community, we want to work towards that. Please get on rdo-list and tell us how we can do things better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment