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 F3C7F9EB5 for ; Mon, 15 Dec 2014 14:35:50 +0000 (UTC) Received: (qmail 82945 invoked by uid 500); 15 Dec 2014 14:35:50 -0000 Delivered-To: apmail-community-dev-archive@community.apache.org Received: (qmail 82739 invoked by uid 500); 15 Dec 2014 14:35:50 -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 82727 invoked by uid 99); 15 Dec 2014 14:35:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Dec 2014 14:35:50 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (nike.apache.org: local policy) Received: from [209.85.216.177] (HELO mail-qc0-f177.google.com) (209.85.216.177) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Dec 2014 14:35:24 +0000 Received: by mail-qc0-f177.google.com with SMTP id x3so8655402qcv.36 for ; Mon, 15 Dec 2014 06:34:17 -0800 (PST) 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=AAjRUeEkR6ORl+VFjdnr8GwZRSiVz8+uZwEK+0DGkVQ=; b=Io6UJKY8S03cpWHhiGhRpa9BADDe66HO32eNqZhEU7B8M4ZmLH9cNsVv+hUotknDvJ XwQjsAqATPCgLqVWP+Aqb4IZ+SJeQy5Ml0319BWAyHhzb6V4W0oXR9t/fLyjwrb4CIVR vFOgwludL6wAZCPp+J3i6Hrytk1O8F+Z3JsEoi/iXDsquuLlZcwYjK9UfhMF4s/Vufy0 49RTmHAEPPa8ngc3MF4/gLkQL/6TcYU3/GDCuRDTry3cKVzhP6d7xcVTSzFGnnbL/TNj ovaFBuW3UjlApiBh2HCi298mTo/3wY3XF06A10Ux8EiIxc1rGgCQ5AvarMAf1knkzR8W Mkbg== X-Gm-Message-State: ALoCoQlRQhwrAmkppCa5mdAQ0y2VbRbTIEnvyJDUujWsxx73M9UrOCyfKxbJhWE3kzc44svjtiPc X-Received: by 10.140.101.112 with SMTP id t103mr53051030qge.92.1418654057139; Mon, 15 Dec 2014 06:34:17 -0800 (PST) Received: from localhost.localdomain (cpe-74-138-17-157.swo.res.rr.com. [74.138.17.157]) by mx.google.com with ESMTPSA id u64sm10594729qgd.46.2014.12.15.06.34.14 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 15 Dec 2014 06:34:15 -0800 (PST) Message-ID: <548EF163.20800@rcbowen.com> Date: Mon, 15 Dec 2014 09:34:11 -0500 From: Rich Bowen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: dev@community.apache.org Subject: Re: ApacheCon track descriptions References: <548B62D4.5000008@gmail.com> <548B6728.3060306@gmail.com> In-Reply-To: <548B6728.3060306@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 12/12/2014 05:07 PM, Hadrian Zbarcea wrote: > Geez :). My impression is that some communities just assume it's gonna > happen. Let me send a few email and gauge the interest. If there's > enough (which I assume to be the case), I'll volunteer. Yeah, that's indeed the problem. What we need is people that care about the content to craft what they believe to be an ideal track, and then hassle the right people into submitting those talks. I see that some people are starting to fill out http://wiki.apache.org/apachecon/ACNA2015ContentCommittee and that's awesome. What I'd like to see by early January is a track list (with or without speaker names), and then by the end of January, we need actual tracks, with proposal IDs from the CFP system. In an ideal world, everyone just comes to me with a completed track, and we schedule it. This means that I'm trusting each of you to have the pulse of your particular community, and to be getting input from everyone, so that there's not one person dictating the entire event. (I've heard one too many "RichBowenCon" jokes already, and I'm really not interested in being BDFL of this event, despite all appearances.) I truly want this to be a community event, in all senses - for the community, by the community. > > Cheers, > Hadrian > > > > On 12/12/2014 04:53 PM, Ross Gardler (MS OPEN TECH) wrote: >> If you arrange it, yes :-) >> >> Microsoft Open Technologies, Inc. >> A subsidiary of Microsoft Corporation >> >> -----Original Message----- >> From: Hadrian Zbarcea [mailto:hzbarcea@gmail.com] >> Sent: Friday, December 12, 2014 1:49 PM >> To: dev@community.apache.org >> Subject: Re: ApacheCon track descriptions >> >> Not sure if my previous mail made it to the list. We kinda >> traditionally had a SOA/integration track that attracted a decent >> crowd. Camel, CXF, Karaf some ActiveMQ, (ServiceMix a while back) were >> the main attractions. Do we want such a track this time around? >> >> Cheers, >> Hadrian >> >> >> On 12/12/2014 11:25 AM, Ross Gardler (MS OPEN TECH) wrote: >>> Track organizers you have a small job to do... >>> >>> Sally is working up a marketing campaign to align with ApacheCon. >>> This is a campaign for the foundation not for ApacheCon itself, >>> however it will run during the push for attendees and is intended to >>> both ride on the ApacheCon press and contribute to it. >>> >>> In order to help Sally plan this campaign can you please provide a >>> 3-5 sentence description of your track in the wiki >>> (https://wiki.apache.org/apachecon/ACNA2015ContentCommittee). Don't >>> worry about the details. We'll help flesh out a more "marketing >>> friendly" set of words. We just need some guidance on what your track >>> will contain. >>> >>> As an example here's what I wrote for my cloud track: >>> "The cloud changes everything. The Apache Software Foundation changes >>> everything. This track will focus on how The Apache Software >>> Foundation and, more specifically, the Apache projects are often >>> found at the core of the latest and greatest innovations in IT. >>> Sessions in this track will show how the Apache Way enables the >>> largest and the smallest of companies to work together to redefine >>> IT. We'll also take a look into the future of cloud computing and how >>> Apache projects fit into, even defines, that future." >>> Ross >>> >>> > -- Rich Bowen - rbowen@rcbowen.com - @rbowen http://apachecon.com/ - @apachecon