Kolla application for Big Tent

Kolla spent 4 IRC meeting hours defining the Kolla mission here [1].
Our mission is clear and well defined.

Kolla provides production-ready containers and deployment tools for
operating OpenStack clouds.

The project uses the ASL 2.0 as declared in the code base [2].

The PTL was chosen by election to be Steven Dake using the standard
OpenStack mechanism [3].

The #kolla IRC channel on freenode is logged and the channel is
notified of such logging [4].  Our public meeting schedule was
decided by vote at [5] and all meeting logs are stored at our wiki.

The project uses public code reviews on the OpenStack infrastructure.
Kolla has been using the +2/+A process requiring two unique core
reviewers to review a patch since project inception.  Our project
does not permit exceptions to the +2/+A process and we have never
approved a patch without two core reviews.

Our gating runs pep8, bashate, and other YAML/JSON syntax checking.
The Kolla team builds all images as a functional CI job to validate
our builds.  In nearly every IRC meeting for the Liberty cycle
continuous integration has been our second topic of discussion.

The PTL serves as liaison between the Kolla community and other
projects for example coordinating our container content with James
Slagle, the TripleO PTL.  Because Kolla deploys most OpenStack
namespaced server projects, we must coordinate and cooperate with
nearly every server project in OpenStack.

The project has openly worked with members of the TripleO community
to integrate kolla/containers into TripleO.  Several PoC patches
exist demonstrating TripleO and Kolla integration [6].

During Paris ODS, we had a one hour design session recorded here [7].
The Kolla team had an open design session at Vancouver ODS during
Ansible Collaboration day.  TripleO hosted several Kolla design
sessions at Vancouver ODS.  We discuss all work in the open, mostly
using IRC.  Based upon open communication between the Kolla core
reveiwer and developement team, the PTL presented the long-term
vision for Kolla during Liberty ODS [8].

Kolla uses IRC very heavily because everyone is very active on IRC.
As a result the Kolla core reviewer team often makes quick decisions.
Our core reviewer team is distributed around the world, so we use the
mailing list to communicate long term planning objectives.  A recent
example of such is the recently held Kolla-Palooza midcycle meetup
on July 28th and July 29th, 2015.  We use the mailing list by
prefixing e-mails to openstack-dev@lists.openstack.org with [kolla]
for long term planning rather than short term decision making.

Kolla has a high degree of diversity in both reviews [9] and
commits [10] with our largest percentage of contributions
originating from unaffiliated contributors.

[1] https://etherpad.openstack.org/p/kolla-manifesto
[2] https://github.com/stackforge/kolla/blob/master/LICENSE
[3] https://wiki.openstack.org/wiki/Kolla/PTL_Elections_March_2015
[4] http://eavesdrop.openstack.org/irclogs/%23kolla/
[5] https://wiki.openstack.org/wiki/Meetings/Kolla
[6] https://review.openstack.org/#/c/178840/
[7] https://etherpad.openstack.org/p/kolla-design
[8] https://www.openstack.org/summit/vancouver-2015/summit-videos/presentation/thanks-docker-the-pro-and-039s-and-con-and-039s-of-containerizing-your-openstack-services
[9] http://stackalytics.com/?project_type=all&module=kolla
[10] http://stackalytics.com/?project_type=all&module=kolla&metric=commits

Change-Id: If6e30574235e61ea6850e364d5ac7d11bc0ee2b4

reference/projects.yaml

@@ -1039,6 +1039,22 @@ Keystone:
         - release:independent
         - type:library
 
+Kolla:
+  ptl: Steven Dake (sdake)
+  irc-channel: kolla
+  mission: >
+    To provide production-ready containers and deployment tools for operating
+    OpenStack clouds.
+  url: https://wiki.openstack.org/wiki/Kolla
+  tags:
+    - team:diverse-affiliation
+  deliverables:
+    kolla:
+      repos:
+        - openstack/kolla
+      tags:
+        - release:independent
+
 MagnetoDB:
   ptl: Ilya Sviridov (isviridov)
   service: Key-Value Store as a Service