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 6624911963 for ; Fri, 19 Sep 2014 13:37:47 +0000 (UTC) Received: (qmail 66293 invoked by uid 500); 19 Sep 2014 13:37:46 -0000 Delivered-To: apmail-community-dev-archive@community.apache.org Received: (qmail 66130 invoked by uid 500); 19 Sep 2014 13:37:46 -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 66118 invoked by uid 99); 19 Sep 2014 13:37:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Sep 2014 13:37:45 +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 (nike.apache.org: local policy) Received: from [209.85.216.172] (HELO mail-qc0-f172.google.com) (209.85.216.172) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Sep 2014 13:37:17 +0000 Received: by mail-qc0-f172.google.com with SMTP id x13so3045979qcv.17 for ; Fri, 19 Sep 2014 06:37:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:reply-to:organization :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=Y5hRFEQY79bgyd0u+bDl+74Y0/0icymMbrKKadiUz/w=; b=lwI4Ge9o64Ua1ZbK8MxsDZ3st9zGQOFmOs8ZxC1Rpwm6iQL7LcGUXxpKL/99GO+R3k N9a1RvtsYrEIUVrBweY7KSlAPJAdTHxe7sXqMtTt/W1+FdXTqFGiq0HtOfRssZAdyL8i JySr3yhbaECOgMCAyyXqxr58h9qE/c40cIa51J671BsFz3aiMt9S8T1ZPwYODJwsTH3T 4R0OEOXWsa0cL1Z/8JrZ7rj+zDXIwVtNvowb67dBnSRi8gwWT2bAgMmRLTSsrYRosdbG hnV4PGJwVoUJQNinUycVq5ZTnuYPVyeOSrInnUtvSNdcvyP8fIdoOvV+AfshtH68blin xigg== X-Gm-Message-State: ALoCoQmi29nKvIgzxB8yjy/4stDlKrLYaYhvgDOQx/Sh3LI0YMS4ElPhz75/lleSzFGMyYvYAvRK X-Received: by 10.224.46.133 with SMTP id j5mr618612qaf.92.1411133835923; Fri, 19 Sep 2014 06:37:15 -0700 (PDT) Received: from localhost.localdomain (cpe-74-138-17-157.swo.res.rr.com. [74.138.17.157]) by mx.google.com with ESMTPSA id h91sm1408731qge.38.2014.09.19.06.37.14 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 19 Sep 2014 06:37:14 -0700 (PDT) From: Rich Bowen X-Google-Original-From: Rich Bowen Message-ID: <541C3187.1090401@apache.org> Date: Fri, 19 Sep 2014 09:37:11 -0400 Reply-To: rbowen@apache.org Organization: The Apache Software Foundation User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 MIME-Version: 1.0 To: dev@community.apache.org Subject: ApacheCon - How you can help Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Here's the most important ways that you can help with ApacheCon EU right now, in order of importance. * If you are involved in an Apache project that has content at ApacheCon, send messages to your users@ and dev@ list telling them about that content, and telling people that they need to be there. Tell them specifically what talks they need to come for, and what developers they'll get to hang out with at the event. Tell them that they are doing their career a disservice if they don't come to this event. Remind them that committers have a deep discount, so if they're not committers now, here's a *great* reason for them to get on that train for next time. Remind the US audience that if they can't make it to Budapest, they should plan to come to Austin in April. * Reach out to other audiences - Twitter, Facebook, and G+, certainly, but also other non-Apache projects you're involved with that have strong overlap with our content. Again, mention specific talks and people that will be at the event. * If your company cares about or relies on any Apache technology, encourage them to sponsor the event and/or send an employee to the event. Remind them that it's about more than just the technical content - they will get to have first-hand contact with the people that develop the software, and become part of that community, with the possibility to participate in shaping the future of that product. If there's a spark of interest in sponsorship, have them get in touch with me - rbowen@apache.org - and we'll take it from there. * Follow and retweet the @apachecon account. -- rbowen@apache.org http://apache.org/