Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: domain of steve.wilson@citrix.com
 designates 66.165.176.63 as permitted sender)
From: Steve Wilson <steve.wilson@citrix.com>
To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
Subject: CloudStack Quality Process
Thread-Topic: CloudStack Quality Process
Thread-Index: AQHQDZq+rwyUPdi8hE6uZJeEUNBjhQ==
Date: Mon, 1 Dec 2014 19:12:27 +0000
Message-ID: <D0A1FD99.21C4C%steve.wilson@citrix.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_D0A1FD9921C4Cstevewilsoncitrixcom_"
MIME-Version: 1.0

--_000_D0A1FD9921C4Cstevewilsoncitrixcom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi Everyone,

It was great to get to see a number of you at the recent CCC in Budapest.  =
While I was there, I got to meet face to face with individuals working for =
several companies that have a real stake in the commercial success of the C=
loudStack project.

After joining Citrix (and becoming involved in CloudStack) about a year ago=
, I=92ve come to believe that we need to do more to mature our quality prac=
tices around this codebase.  We all like to say #cloudstackworks (and it=92=
s true), but this is a massive codebase that=92s used in the most demanding=
 situations.  We have large telecommunications companies and enterprises wh=
o are betting their businesses on this software.  It has to be great!

There has been quite a bit of discussion on the mailing list in recent mont=
hs about how we improve in this area.  There is plenty of passion, but we h=
aven=92t made enough concrete progress as a community.  In my discussions w=
ith key contributors as CCC, there was general agreement that the DEV list =
isn=92t a good forum for hashing out these kinds of things.  Email is too l=
ow-bandwidth and too impersonal.

At CCC, I discussed with several people the idea that we commission a small=
 sub team to go hash out a proposal for how we handle the following topics =
within the ACS community (which can then be brought back to the larger comm=
unity for ratification):

  *   Continuous integration and test automation
  *   Gating of commits
  *   Overall commit workflow

We are looking for volunteers to commit to being part of this team.  This w=
ould imply a serious commitment.  We don=92t want hangers on or observers. =
This will entail real work and late night meetings.  We=92re looking for pe=
ople who are serious contributors to the codebase.

>From Citrix, David Nalley and Animesh Chaturvedi have booth told me they=92=
re willing to commit to this project.  They=92ve both managed ACS releases =
and have a really good view into the current process =97 and I know both ar=
e passionate about improving our process.  From my CCC discussions, I belie=
ve there are individuals from Schuberg Philis, Shape Blue and Cloud Ops who=
 are willing to commit to this process.

If you are willing to be part of this team to drive forward our community, =
please reply here.

Thanks,

-Steve

Steve Wilson
VP & Product Unit Manager
Cloud Software
Citrix
@virtualsteve

--_000_D0A1FD9921C4Cstevewilsoncitrixcom_--