Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3D52CE3B1 for ; Tue, 15 Jan 2013 22:26:39 +0000 (UTC) Received: (qmail 37484 invoked by uid 500); 15 Jan 2013 22:26:38 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 37454 invoked by uid 500); 15 Jan 2013 22:26:38 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 37446 invoked by uid 99); 15 Jan 2013 22:26:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Jan 2013 22:26:38 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.219.51] (HELO mail-oa0-f51.google.com) (209.85.219.51) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Jan 2013 22:26:34 +0000 Received: by mail-oa0-f51.google.com with SMTP id n12so733062oag.38 for ; Tue, 15 Jan 2013 14:26:12 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=AnYh6XkjBP4JlNbvXCMfcMPP3occ2B2UMf8TA64K0lE=; b=fFofadSIVBV8CcvBU8/5dZ8Osdq/wtEpQ/u8Si1sjvuxoHoCxWIPdlonsPSnNVRmdW IvMni3r6kjUMuzFsY7xGRrSJa1mI2NrPMFK1nS7MdCT0vEh8k6XLa2SL9e6A64gz+5nL BU75zg5qGZ26dBrjkJhrmcmNIBGOptw0fLmezdbyM04NCUi8Vae01dnEuk7G7lsTzY0z 2AGotBAukrGzwuqU4ip2aoFvdUWBt/0VqXBouoBUpqEm8GyxzhLKh+tt65QZXWk/ajrb Sf+4xBjpymorE9lRqth0Wut2ZpMV2MB/r+iStlQ5nN2Jvbmxt1vXFuITS9kcYKKXwn8p jPNA== Received: by 10.60.169.135 with SMTP id ae7mr55044309oec.82.1358288771934; Tue, 15 Jan 2013 14:26:11 -0800 (PST) MIME-Version: 1.0 Received: by 10.76.173.105 with HTTP; Tue, 15 Jan 2013 14:25:51 -0800 (PST) In-Reply-To: References: <7A92FF96DF135843B4B608FB576BFC3E012DA320C468@SJCPMAILBOX01.citrite.net> From: David Nalley Date: Tue, 15 Jan 2013 17:25:51 -0500 Message-ID: Subject: Re: [IP Clearance: CLOUSTACK 774] Call for review To: cloudstack-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQlpoaQIygLzpSUX2pyHvE/YT3eTBD19e+xDYTMIjrEgyC8rtjZybVWaXJq3eaUMvaYBiHZm X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Jan 15, 2013 at 5:20 PM, Chip Childers wrote: > On Tue, Jan 15, 2013 at 5:07 PM, Animesh Chaturvedi > wrote: >> Folks >> >> Frank has posted CS - 774 code for IP Clearance review at http://people.apache.org/~frankzhang/ . Citrix would like to donate this code to Apache CloudStack. >> >> Dave, Chip can you outline the formal process for IP clearance? Do we call out for VOTE on its inclusion right away or wait for 72 hours? >> >> >> Thanks >> Animesh >> >> > > IMO, I believe that we should be OK to start a VOTE right away for any > of these features where there was a dev list discussion that reached > consensus (i.e.: no outstanding issues / questions). If there was not > consensus, then I think it's only fair to use DISCUSS threads to ask > for consensus before moving forward with a VOTE. > > After discussion, I suggest that we hold a VOTE as a community > (similar to the one I just did for the test suite), as a pre-cursor to > finding an officer or member to help get us through the IP clearance > process. For the record, the process from after we do our VOTE is > documented here: http://incubator.apache.org/ip-clearance/index.html > and http://incubator.apache.org/ip-clearance/ip-clearance-template.html I concur, this makes sense.