Return-Path: X-Original-To: apmail-apachecon-discuss-archive@minotaur.apache.org Delivered-To: apmail-apachecon-discuss-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B3A009EC3 for ; Wed, 30 May 2012 20:40:22 +0000 (UTC) Received: (qmail 10323 invoked by uid 500); 30 May 2012 20:40:22 -0000 Delivered-To: apmail-apachecon-discuss-archive@apache.org Received: (qmail 10251 invoked by uid 500); 30 May 2012 20:40:22 -0000 Mailing-List: contact apachecon-discuss-help@apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: apachecon-discuss@apache.org Delivered-To: mailing list apachecon-discuss@apache.org Received: (qmail 10240 invoked by uid 99); 30 May 2012 20:40:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 May 2012 20:40:22 +0000 X-ASF-Spam-Status: No, hits=-0.5 required=10 tests=FREEMAIL_ENVFROM_END_DIGIT,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ch.ko123@googlemail.com designates 209.85.160.50 as permitted sender) Received: from [209.85.160.50] (HELO mail-pb0-f50.google.com) (209.85.160.50) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 May 2012 20:40:18 +0000 Received: by pbbrr4 with SMTP id rr4so495478pbb.23 for ; Wed, 30 May 2012 13:39:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=EzCmJJx+CfqgWW53B6DOKFPQh6hn6ooZRKIajE6iyFk=; b=mAcsudeHHSXOptikmjmsV5JC9sNs/4xgZFZn4gwAo/Y/maX2jChpkMxj+Xu9u0dTzG o/qkXmcyQmJxtLvSUlDDt1kut+ghI7JaUPyzinbzB4pEAfuBZpjbreh+4QT9dk41tFlK jX9ejU5QzTIS9Ljl114q/ydnbRghKHi7mBB/9275oBWFAJmuKbVOJEcLGMv+Ck6Xp+k8 8Yhm0+PDhbegQShOUqb6bAz0dfuFKbzVzh0kP06JdGakWNESFApJzyI1XVvTYUQ3x8fl uP9dxFHObQZdXOh8c34Hush67jyfnmWCrzviKFXlo5Zh5qspiC9EQ43+MhjsXNIaarJR OXCg== Received: by 10.68.202.130 with SMTP id ki2mr53351653pbc.52.1338410397761; Wed, 30 May 2012 13:39:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.40.3 with HTTP; Wed, 30 May 2012 13:39:37 -0700 (PDT) In-Reply-To: <4FC60D13.9030201@apache.org> References: <4FC60D13.9030201@apache.org> From: Christine Koppelt Date: Wed, 30 May 2012 22:39:37 +0200 Message-ID: Subject: Re: Things we need to do for ApacheCon EU To: apachecon-discuss@apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Hi As the ASF is an organization where people work in independent distributed groups I like the idea of having this reflected in the conference. What about distributing the conference program planning? My Idea is: groups of at least three committers can come up with a program proposal for one room for one day. Such proposals could be for example: a day full of invited talks about semantic web and natural language processing, an Open Space about the future of the ASF, a BarCamp about OpenOffice and so on. If there are more proposals than free slots there should be a public, transparent process for selection. There needs to be a small group of organizers who care about infrastructure (presentation materials, food, maybe keynotes, etc.) and communication (eg. coordinating the website and a CFP), but the program is the sole responsibility of the selected groups. A lot of organizers will also mean high demands on communication, coordination and preparation, but I think it's manageable. Kind Regards Christine 2012/5/30 Nick Burch : > Hi All > > I did send an email a few weeks ago about the next steps, but as a few > people have contacted me privately to ask about what needs doing, I fear it > may have got lost in the noise... Plus it didn't have everything, so here > goes again! > > There are currently several things that anyone can (and needs to be!) > helping with, and a few bits largely specific to those near the venue. > > On the everyone front, we need to decide exactly what kind of conference we > want to fill this lovely SAP sponsored space with. Do we want big tracks > (200/300 people), or small ones (5*100), or some days with one setup and > some days others? What sort of tracks do we want to put on? Do we want to do > a day or two for certain popular project areas, or do we want to do one > track for the whole time for a popular area, with smaller ones around it? > What things (if any) do we want to put on in the evening? What things might > we want to try in Portland next year, which we should be attempting to > test/pilot in Europe? > > (Once we have answers for these, then we'll have the structure around which > to run the CFP) > > For those in Germany, we need to start putting together some resources for > attendees, especially around accommodation. I know there isn't much near the > venue, but it'd be good to get / find a list of what that is. We also want > to provide information on what bigger towns/cities nearby people could be > looking at for staying it, and how long (+ how late!) they'd be looking at > for public transport. We may also want to look at hiring something nearby > that's cheap for people to stay in (especially TAC funded attendees, > committers who are paying for themselves etc). It'd be good to know what > options there might be (hostels, church halls etc). For now, I'd suggest we > start capturing this sort of information on the wiki[1], and we can worry > about if that's the best place or not later! > > Cheers > Nick > > [1] http://wiki.apache.org/apachecon/