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 09E289628 for ; Tue, 9 Dec 2014 09:43:15 +0000 (UTC) Received: (qmail 50740 invoked by uid 500); 9 Dec 2014 09:43:13 -0000 Delivered-To: apmail-community-dev-archive@community.apache.org Received: (qmail 50479 invoked by uid 500); 9 Dec 2014 09:43:13 -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 50264 invoked by uid 99); 9 Dec 2014 09:43:13 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Dec 2014 09:43:13 +0000 Received: from mail-la0-f48.google.com (mail-la0-f48.google.com [209.85.215.48]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 7FC141A00D1 for ; Tue, 9 Dec 2014 09:43:12 +0000 (UTC) Received: by mail-la0-f48.google.com with SMTP id gf13so184128lab.7 for ; Tue, 09 Dec 2014 01:43:10 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.152.170.170 with SMTP id an10mr20786941lac.46.1418118190678; Tue, 09 Dec 2014 01:43:10 -0800 (PST) Received: by 10.112.10.16 with HTTP; Tue, 9 Dec 2014 01:43:10 -0800 (PST) In-Reply-To: References: Date: Tue, 9 Dec 2014 10:43:10 +0100 Message-ID: Subject: Re: ApacheCon Austin "content committee" deadlines From: jan i To: "dev@community.apache.org" Content-Type: multipart/alternative; boundary=089e0117748b01489a0509c55f39 --089e0117748b01489a0509c55f39 Content-Type: text/plain; charset=UTF-8 On Tuesday, December 9, 2014, Lewis John Mcgibbney < lewis.mcgibbney@gmail.com> wrote: > Hi Rich, > > On Mon, Dec 8, 2014 at 2:01 PM, > > wrote: > > > > > > > The earlier you communicate to this list, or to me, how many day/tracks > > you expect to be able to fill, the better. (One day/track is 6 talks, > > except on closing day, when it's probably 5 due to keynotes and lightning > > talks and whatnot.) > > > > I expect to fill two day/tracks with httpd/web/tomcat/trafficserver > stuff. > > > > > Are we gathering this content anywhere right now or is everything on this > list? > It would maybe help to get a document opened which people can use to > propose/organize material? First of all we have the cfp site for the actual talks so that is covered. I would recommend not to have 1 document everybody changes, we tried if for denver and budapest and it caused headache, At this point I suggest every track coordiantes among themself. Once cfp is closed we will have a tool to accept/reject and schedule that actual talks, just my 2ct. jan i > Thoughts? > Thank you > Lewis > -- Sent from My iPad, sorry for any misspellings. --089e0117748b01489a0509c55f39--