Instantly share code, notes, and snippets.

View gist:45c47fad9836c1e33e0e308a3d1948aa
<html>
<head>
<title>OSAS Stories</title>
</head>
<body>
<script>
$("form :input").attr("autocomplete", "off");
</script>
View rdo_metrics.md

RDO Communtiy Metrics

The raw statistics for this summary, including graphs, may always be found at http://tm3.org/rdostats/

Downloads

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.

  • Week of August 24, average 4009 downloads per day
  • Week of August 17, average 3410 downloads per day
View bigtent.md

The OpenStack Big Tent

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.

The Problem

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.

View rdo_centos.md

RDO is OpenStack packaged by and for the CentOS community

CentOS cares about OpenStack

View get_meetups.py
#!/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
View kilo-cloud-sig.md

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

View projector.md
View rtfm.md

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

View gist:d62e472eefef2ba7ccae

Improving BarCamp

Apachecon mailing list - populate with registrants? (Ask CCR) What apachecon mailing lists do we still have, and what are the subscriber counts?

Local folks who can make connections with Universities, Govt, or companies willing to donate space.

Documentation for successful barcamp? (Ask Nick)

Incubator

View evp.md

My primary job as EVP has been ApacheCon. Since the last members meeting we have produced ApacheCon Europe in Budapest and we're about to do ApacheCon North America Austin, April 13-17. These are the second and third events that we have done under the Linux Foundation contract.

A major goal of the Linux Foundation contract was to move all logistical support and financial risk to an organization that does these things as their main mission. To this end, we have licensed our brands to LF, and various volunteers have been the ASF liaisons for the CFP process, and various other community-related things.

We are pleased to report that LF continues to take more ownership of these shows, making decisions that are conducive to the financial success of these events, and deferring to us only on matters of brand and content. We continue to discuss what might be the effective ways to fairly represent 200+ projects into this event. Options under consideration include breaking out ApacheCon into topic-specific events (Apa