Return-Path: X-Original-To: apmail-cloudstack-marketing-archive@www.apache.org Delivered-To: apmail-cloudstack-marketing-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C318A11885 for ; Mon, 14 Jul 2014 22:11:31 +0000 (UTC) Received: (qmail 31439 invoked by uid 500); 14 Jul 2014 22:11:31 -0000 Delivered-To: apmail-cloudstack-marketing-archive@cloudstack.apache.org Received: (qmail 31414 invoked by uid 500); 14 Jul 2014 22:11:31 -0000 Mailing-List: contact marketing-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: marketing@cloudstack.apache.org Delivered-To: mailing list marketing@cloudstack.apache.org Received: (qmail 31404 invoked by uid 99); 14 Jul 2014 22:11:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jul 2014 22:11:31 +0000 X-ASF-Spam-Status: No, hits=-2.8 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of Chiradeep.Vittal@citrix.com designates 66.165.176.89 as permitted sender) Received: from [66.165.176.89] (HELO SMTP.CITRIX.COM) (66.165.176.89) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jul 2014 22:11:25 +0000 X-IronPort-AV: E=Sophos;i="5.01,661,1400025600"; d="scan'208,217";a="152430891" Received: from sjcpex01cl03.citrite.net ([10.216.14.145]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 14 Jul 2014 22:10:50 +0000 Received: from SJCPEX01CL02.citrite.net ([169.254.2.117]) by SJCPEX01CL03.citrite.net ([10.216.14.145]) with mapi id 14.03.0181.006; Mon, 14 Jul 2014 15:10:49 -0700 From: Chiradeep Vittal To: "marketing@cloudstack.apache.org" Subject: Re: [VOTE] Proposed patch to the Apache CloudStack Trademark Guidelines Thread-Topic: [VOTE] Proposed patch to the Apache CloudStack Trademark Guidelines Thread-Index: AQHPn4MX11WXEJXJX0uQ3y14n6YscpugIeKA Date: Mon, 14 Jul 2014 22:10:48 +0000 Message-ID: References: <20140714164546.GU72090@Chips-MacBook-Air.local> In-Reply-To: <20140714164546.GU72090@Chips-MacBook-Air.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.4.2.140509 x-originating-ip: [10.13.107.78] Content-Type: multipart/alternative; boundary="_000_CFE9A37049943chiradeepvittalcitrixcom_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_CFE9A37049943chiradeepvittalcitrixcom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable +1 From: Chip Childers > Reply-To: "marketing@cloudstack.apache.org" > Date: Monday, July 14, 2014 at 9:45 AM To: "marketing@cloudstack.apache.org" = > Subject: [VOTE] Proposed patch to the Apache CloudStack Trademark Guideline= s Per the [DISCUSS] thread from last week, here's the formal vote. I'm proposing that (1) the project take on the responsibility to manage our trademark usage approvals, and (2) that the proposed patch to the trademark guidelines should be applied in support of 1. There is one minor edit to the patch in the DISCUSS thread: adding press@ to the intro paragraph about how to contact the project for approval. [ ] +1 - Take on this responsibility as a project and apply the proposed patch. [ ] +/-0 - No strong opinion either way [ ] -1 - Don't take on tm approval and / or don't apply the proposed patch. -chip --_000_CFE9A37049943chiradeepvittalcitrixcom_ Content-Type: text/html; charset="us-ascii" Content-ID: <68AE5FB5BFA3F645B15A724A8E1A6B96@citrix.com> Content-Transfer-Encoding: quoted-printable
+1

From: Chip Childers <chipchilders@apache.org>
Reply-To: "marketing@cloudstack.apache.org" &= lt;marketing@cloudstack.= apache.org>
Date: Monday, July 14, 2014 at 9:45= AM
To: "marketing@cloudstack.apache.org" <marketing@cloudstack.apache= .org>
Subject: [VOTE] Proposed patch to t= he Apache CloudStack Trademark Guidelines

Per the [DISCUSS] thread from last week, here's the formal vote.

I'm proposing that (1) the project take on the responsibility to manag= e
our trademark usage approvals, and (2) that the proposed patch to the<= /div>
trademark guidelines should be applied in support of 1.

There is one minor edit to the patch in the DISCUSS thread: adding
press@ to the intro paragraph about how to contact the project for
approval.

[ ] +1 - Take on this responsibility as a project and apply the pr= oposed
patch.
[ ] +/-0 - No strong opinion either way
[ ] -1 - Don't take on tm approval and / or don't apply the proposed
patch.

-chip

--_000_CFE9A37049943chiradeepvittalcitrixcom_--