Return-Path: X-Original-To: apmail-incubator-cloudstack-marketing-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-marketing-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F234EEA1D for ; Wed, 27 Feb 2013 19:24:56 +0000 (UTC) Received: (qmail 56561 invoked by uid 500); 27 Feb 2013 19:24:56 -0000 Delivered-To: apmail-incubator-cloudstack-marketing-archive@incubator.apache.org Received: (qmail 56541 invoked by uid 500); 27 Feb 2013 19:24:56 -0000 Mailing-List: contact cloudstack-marketing-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-marketing@incubator.apache.org Delivered-To: mailing list cloudstack-marketing@incubator.apache.org Received: (qmail 56532 invoked by uid 99); 27 Feb 2013 19:24:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2013 19:24:56 +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.49] (HELO mail-oa0-f49.google.com) (209.85.219.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2013 19:24:51 +0000 Received: by mail-oa0-f49.google.com with SMTP id j6so2000388oag.36 for ; Wed, 27 Feb 2013 11:24:30 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=Zq4PMOeGvo1CV+UfbcBp6ErBMoIZ7CzzkO2sGDuyGNQ=; b=ecVQNJtzHb0mj7fVgqCIL9O6gS2W7iw+A6dlqspZczMaUQ5g5ItmaeEY7hM0EC0GMe 2DcTPSjaujTPHdBCpu+49gRogXCK/iHlfIbKT7GfsJUvLvSf6HL3edugH/92QHqFBGf2 GlkrvSxBnKY5ydqBTajUU6z4450X8Qew2xq+5YTRoCGAsyvniHJzVGLOhIR4i4rXxu/y Piq8jUC3j7wqqwc27OdiOG4uxH05VrzVviUT1+3SW6g65RTffLR8i7ljZ3kPfEFleZSh qd8bbsX7vxuP89n0za9NToTF/wS5rIjiikOpJEKxmuyGO6m44Y71SoOiHOSlZi6qN826 UHjw== X-Received: by 10.60.31.42 with SMTP id x10mr3420623oeh.18.1361993070733; Wed, 27 Feb 2013 11:24:30 -0800 (PST) MIME-Version: 1.0 Received: by 10.76.10.100 with HTTP; Wed, 27 Feb 2013 11:24:10 -0800 (PST) In-Reply-To: <1361992256.24492.140661197789705.4E8F275D@webmail.messagingengine.com> References: <1361992256.24492.140661197789705.4E8F275D@webmail.messagingengine.com> From: David Nalley Date: Wed, 27 Feb 2013 14:24:10 -0500 Message-ID: Subject: Re: [DISCUSS] Draft trademark guidelines To: cloudstack-dev@incubator.apache.org Cc: cloudstack-marketing@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkX3/HzACCRQgli6Y1F1rg4IuUSKslH49JfaoEngrUJVuDiBbEc6hEu4/eJJZ3TMtNkItLA X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Feb 27, 2013 at 2:10 PM, Joe Brockmeier wrote: > On Tue, Feb 26, 2013, at 02:34 PM, David Nalley wrote: >> Hi folks, >> >> Sorry for spamming two lists. >> >> We've been drafting some guidelines and had them reviewed by >> trademarks@ - and wanted to get them out in public for comment and >> discussion. >> >> Draft is here: >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Trademark+Guidelines+(DRAFT) > > So, we're currently missing any guidance on brand usage, not modifying > the logo, etc. Yes - I want this - patches welcome. > > I've added a bit under the domains section, as I'm generally not a fan > of sending people scouring multiple docs for a simple answer. (Which is, > generally in this case, "no".) > > Under non-software goods: > > "Without explicit written permission, goods bearing any of the > CloudStack marks may not be sold." > > Are we explicitly allowing people to manufacture CloudStack-branded swag > to give away? What about co-mingling CloudStack with other marks, etc.? > (e.g., a design that mingles the CloudStack mark with a company logo > which might infer some kind of association between CloudStack and that > company?) > So we aren't explicitly allowing anything. Everything requires EXPLICIT permission from both the (P)PMC and Trademarks@. I was trying to provide a framework for every eventuality - especially since in the end they need two levels of permission. Besides I could see $SDN/Storage/Hypervisor company wanting to tout their CloudStack goodness in a way that doesn't suggest ownership or control. > I'd like change the current language to: > > "Merchandise bearing the CloudStack marks must be explicitly approved in > writing if it is to be sold or given away for promotional purposes. A > design must only be approved one time - it is not necessary to seek > approval to reprint/recreate new merchandise with a design that has been > approved, so long as the permission has not been revoked." > > Suggestions to this language welcome, but what I want to prevent is use > of CloudStack with third party logos where a company/organization is > promoting some proprietary product by giving away - but not selling - > merchandise. > I like the one time approval. > I don't want us to have unreasonable burdens, such as having to seek > approval every time a company reprints an approved design, or makes a > very minimal change to the design, such as printing a CloudStack jersey > with the names of contributors or something - where technically adding a > different name would be a "change" to the design. > > We should also consider having approved designs that anyone could use to > print t-shirts or similar without having to seek approval so long as the > design is used as-is. Do we care if someone starts up a side business > selling CloudStack shirts? > Ohhhh startup idea :) CloudShirts - wear your cloud.