When I talk about Red Hat's involvement in RDO (http://openstack.redhat.com/) the question I often get is, "doesn't that undermine sales of RHEL OSP (Red Hat's paid OpenStack offering)?"
Well, it's complicated.
When I talk about Red Hat's involvement in RDO (http://openstack.redhat.com/) the question I often get is, "doesn't that undermine sales of RHEL OSP (Red Hat's paid OpenStack offering)?"
Well, it's complicated.
Definition: RTFM - Read The F'ing Manual. Occasionally it is ironically rendered as Read The Fine Manual. A phrase uttered at people who have asked a question that we, the enlightened, feel is beneath our dignity to answer, but not beneath our dignity to use as an opportunity to squish a newbie's ego.
Have you noticed that the more frequently a particular open source community tells you to RTFM, the worse the FM is likely to be? I've been contemplating this for years, and have concluded that this is because patience and empathy are the basis of good documentation, much as they are the basis for being a decent person.
First, some disclaimers.
Although I've been doing open source documentation for almost 20 years, I have no actual training. There are some people that do, and there are some amazing books out there that you should read if you care about this stuff.
First, I'd recommend [Conversation and Community](http://www.amazon.com/Conversation-Community-Social-Web-Documentation-ebook/dp/B00C7CC
<html> | |
<head> | |
<title>OSAS Stories</title> | |
</head> | |
<body> | |
<script> | |
$("form :input").attr("autocomplete", "off"); | |
</script> |
Have you ever noticed that the communities where you’re told the most frequently to RTFM - Read The F* Manual - are the same ones where that manual is likely to be awful? I believe that this is, in fact, not merely correlation, but also causation - that is, the attitude results in the poor docs.
There’s a few commonly held beliefs about documentation for software, and in particular open source software: 1) It’s awful, 2) Nobody ever wants to write it. 3) That’s just the way things are, and we can’t do much about it.
The reality, however, is that there are lot of people that want to write documentation, and we, the gatekeepers of open source projects, just make it too hard for them to do it. We put up artificial social barriers. (For example, the myth that documentation is a somehow less important contribution than “real” code.) We put up strange workflows. (Get a checkout. Make your changes. Make a diff. Subscribe to a mailing list. Sen
The raw statistics for this summary, including graphs, may always be found at http://tm3.org/rdostats/
Downloads are always a tricky thing to track, but they are a reasonable proxy for the total size of the community, given certain caveats, and understanding that 1 download != 1 installation.
OpenStack is big and complicated. It's composed of many moving parts, and it can be somewhat intimidating to figure out what all the bits do, what's required, what's optional, and how to put all the bits together.
In the attempt to tame this confusion, the OpenStack Technical Committee defined what's part of the Integrated Release and what's not, so that you, the consumer, know what's in and what's out. One of the unintended side effects of this was that new projects were treated as second class citizens, and had trouble getting resources, developers, and a seat at the table at the developer summit.
As OpenStack continues to grow, this became more and more of a problem.
RDO is OpenStack packaged by and for the CentOS community
CentOS cares about OpenStack
#!/usr/bin/python | |
import datetime | |
from datetime import date | |
import urllib2 | |
import json | |
import time | |
import re | |
# Magic | |
import sys # sys.setdefaultencoding is cancelled by site.py |
The CentOS Cloud SIG is pleased to announce the availability of OpenStack Kilo package repositories for CentOS 7, and Juno repositories for CentOS 6. These are the result of the last few months of work by the Cloud SIG membership, and, of course, we owe a great deal of gratitude to the upstream OpenStack community as well.
The CentOS 7 Kilo repository may be found at http://mirror.centos.org/centos/7/cloud/x86_64/
The Juno CentOS 6 repository may be found at http://mirror.centos.org/centos/6/cloud/x86_64/
The actual -release files will reside in Extras, so that you can yum install centos-release-openstack-kilo
for Kilo and yum install centos-release-openstack-juno
for Juno, without needing to mess with repo configurations.
See also the Juno EL6 QuickStart at http://wiki.centos.org/Cloud/OpenStack/JunoEL6QuickStart
InFocus IN8606HD 1920 x 1080 DLP projector - 2500 ANSI lumens
https://www.google.com/shopping/product/17537202715294238529
$699