Return-Path: X-Original-To: apmail-community-dev-archive@minotaur.apache.org Delivered-To: apmail-community-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 BC77C183D3 for ; Wed, 1 Jul 2015 12:56:06 +0000 (UTC) Received: (qmail 10854 invoked by uid 500); 1 Jul 2015 12:56:06 -0000 Delivered-To: apmail-community-dev-archive@community.apache.org Received: (qmail 10577 invoked by uid 500); 1 Jul 2015 12:56:06 -0000 Mailing-List: contact dev-help@community.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@community.apache.org Delivered-To: mailing list dev@community.apache.org Received: (qmail 10566 invoked by uid 99); 1 Jul 2015 12:56:06 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2015 12:56:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id BCE791A64B3 for ; Wed, 1 Jul 2015 12:56:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.28 X-Spam-Level: * X-Spam-Status: No, score=1.28 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, PLING_QUERY=0.279, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id BdPYSgeaa0ba for ; Wed, 1 Jul 2015 12:55:51 +0000 (UTC) Received: from mail-qk0-f180.google.com (mail-qk0-f180.google.com [209.85.220.180]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 02AD624FF9 for ; Wed, 1 Jul 2015 12:55:50 +0000 (UTC) Received: by qkeo142 with SMTP id o142so28291298qke.1 for ; Wed, 01 Jul 2015 05:55:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=HCDOYe1DBQO3J9bKT36H1mXi3lpmzWmkgR+UJ3RvxEA=; b=Y1qsoBFK0OrLnFMkdVj5QS736nsN1kXu6R4kYS5ATHIdw8lFcpJz3OOWT17cHcNTu1 O+tK0i+5febO1n8bfFxP8Aox5G1RndMRxSGarmpV4jQdILw8+DX+ib96SofFiGGH6JXq 5cdL9HFmyPGbCn8dHp+U9EmsIHCxwaSgqkSW25qNarWogdAoo/Ar73alk0eU1bdTm9Oe od5nSdzLNEXLgRjzsVOnXx0Pvz45GZQpbKKVa4I4blRikkA0JAQQM0C3cTbIdWYyGWv2 rB7Fs48EYcPPCoRXjWC8GkMpWurlx9fqGJNZZwLeDiO3UBX9lHZ7ebRqSZUf6CVTgMqa hn0A== X-Gm-Message-State: ALoCoQkc3vVCCGztZP8CXJqdVQ/SrkwVlmOnPYUBngohdZpgntqkZ4w015N+JAfd8E8lUSLzQXiN X-Received: by 10.55.26.162 with SMTP id l34mr55422683qkh.21.1435755304122; Wed, 01 Jul 2015 05:55:04 -0700 (PDT) Received: from localhost.localdomain (cpe-74-138-23-246.kya.res.rr.com. [74.138.23.246]) by mx.google.com with ESMTPSA id i64sm893766qkh.3.2015.07.01.05.55.02 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Jul 2015 05:55:03 -0700 (PDT) Message-ID: <5593E324.9020007@rcbowen.com> Date: Wed, 01 Jul 2015 08:55:00 -0400 From: Rich Bowen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: dev@community.apache.org Subject: Re: ApacheCON CORE? ApacheCon! References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 07/01/2015 07:43 AM, jan i wrote: > On 1 July 2015 at 13:31, Pierre Smits wrote: > >> ApacheCon in itself doesn't eat into the impact of the joint event 'Apache >> Big Data', as that name doesn't have Con attached to Apache in all >> promotions done up to now... Or dilutes the branding impact of that event. >> > Actually while we discussed it, one of the ideas was "apacheCON: big data", > but > LF preferred "apache big data" and since it is their event they choose. Yes, this is the most important point here, which we will continue to emphasize. We have licensed our marks to LF to put on an event for us, because they are competent professionals and we're not. My job as ApacheCon lead is to ensure that we, the ASF community, stay out of their way and let them do a great event. We, the ASF community, have a long history of tinkering, micromanaging, and generally interfering with conference producers. All well intentioned, of course, but it hasn't worked. It's time to try something new. >> Is there a negative connotation with the name that it would benefit from >> the CORE extension? >> > No just to avoid some confusion. Think of our homepage, travel assistance, > reports etc, that > is all done combined for the 2 events. > > Let me put it like I see it personally, despite contracts, producers etc, > and please bear > in mind, other people have different views. > > to me the total "thing" is apacheCON, that consist of 2 unique events (big > data and core). Yes. For the moment. And the longer-term goal is to build those brands further in order that they can fly on their own. See, for example, what OReilly has done over the last 15 years while we've been protecting our one brand. You can't swing a stick without hitting an OReilly event. And they're doing that with content that they don't own. Also note that LF had done this successfully for years - see http://events.linuxfoundation.org/ for what they have grown the venerable "LinuxCon" name into. No, I absolutely don't believe that we are diluting our brand. -- Rich Bowen - rbowen@rcbowen.com - @rbowen http://apachecon.com/ - @apachecon