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 2B6689EDE for ; Mon, 15 Dec 2014 14:39:07 +0000 (UTC) Received: (qmail 91996 invoked by uid 500); 15 Dec 2014 14:39:07 -0000 Delivered-To: apmail-community-dev-archive@community.apache.org Received: (qmail 91718 invoked by uid 500); 15 Dec 2014 14:39: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 91701 invoked by uid 99); 15 Dec 2014 14:39:06 -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:39:06 +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.54] (HELO mail-qa0-f54.google.com) (209.85.216.54) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Dec 2014 14:38:40 +0000 Received: by mail-qa0-f54.google.com with SMTP id k15so712473qaq.41 for ; Mon, 15 Dec 2014 06:38:19 -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=ajhEra0MPsTYom2htNUY4G+mddmJOJ8JTe1jZjKcpOA=; b=iwVcUu2K2QcAf6oL8hxL3BXj4kEh6Zca/7WZMirLRLLcPX5zMHjFQWhsFsBZ65J6eP Y7YMALDsUBi+M5ysyFRo075NocxxkkWVC3ojfGy+tiGFYnQdP+KFhujWbo773LJC6zbH tBSqtVN/du7JHP08bM5r8+0dDUkiSjk25G9/2IphoksbOHK9EUIQYDtuN5x2VfoF01i6 5Jz3OmWS2PMv0huJeLUI9qThY9hRS46ZWnu5OyqxXBJl++4zfCgDu87goRQuTnRvuoJK Tn0SOx1hoDT9RqidUyP/MDIoYy7U92I0tglW5u3NuNPGZhvxHot64j7bnvqNevzMefie vTAg== X-Gm-Message-State: ALoCoQmc4V9X4qp5FXh1kU8dCQNF5LDg3cS6gMQD72sII4MN/8/SyGnJZ+qhE4y+Pz+85yNx8PNM X-Received: by 10.224.25.79 with SMTP id y15mr56004437qab.78.1418654299664; Mon, 15 Dec 2014 06:38:19 -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 8sm10617234qgf.36.2014.12.15.06.38.17 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 15 Dec 2014 06:38:18 -0800 (PST) Message-ID: <548EF257.1050308@rcbowen.com> Date: Mon, 15 Dec 2014 09:38:15 -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: Content tracks vs standalone talks References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 12/14/2014 04:10 AM, Andrus Adamchik wrote: > Hi, I am considering submitting an Apache Cayenne talk for ACNA. To be precise, the talk will be about building model-driven REST applications with Apache Cayenne and LinkRest (a framework based on Cayenne, and a potential incubator candidate). > > Following discussion about tracks on this list, I've been wondering where do standalone talks fit here? Is it imperative to find an appropriate track for the talk, and what happens if it doesn't cleanly fit anywhere? > > Appreciate guidance/insight on this. At the moment, we don't have enough tracks to fill all of the space, so there will be a lot of room remaining for "standalone" talks. However, if you can affiliate with a track, you'll benefit from additional marketing efforts, which is good for everyone. Hopefully in the coming days, we'll have some clear track definition statements, and it might be more obvious whether one of the tracks is the right home for your talk. But, if not, yes, we'll have lots of room for these additional talks. The additional benefit of these standalone talks is that they give a way for unrepresented projects to have a voice in the event, and that's awesome, too. --Rich -- Rich Bowen - rbowen@rcbowen.com - @rbowen http://apachecon.com/ - @apachecon