Ha! You got me on that one. You are right my talks are cloud, I was avoiding evaluating my own talks in the interests of impartiality. Doh!
Actually the one I really want to give fits well in the DevOps track I just proposed so I'll add it there for everyone's consideration (enjoy your travels) Ross -----Original Message----- From: Rich Bowen [mailto:rbo...@rcbowen.com] Sent: Thursday, February 19, 2015 7:37 AM To: dev@community.apache.org Subject: Re: ApacheCon Schedule On 02/19/2015 09:12 AM, Ross Gardler (MS OPEN TECH) wrote: > I can fill that community track with the TEALS session that we previously > discussed. I owe details of that to Joe as track chair, I'll send under > separate cover shortly. If we don't want that one there are a couple I can > point to that I like. > > Regarding your open slots I have a 5 session DevOps track already prepared. > I'll send that separately too. I can easily solicit a sixth session if you > want. Thanks. I'll have a look on Friday. Gotta go get on a plane now. > > Regarding the likely influx of "why wasn't my talk selected" you can > expect one from me ;-) Looks like all your talks are in the Cloud area. I'd talk to the Cloud track chair if I were you. ;-) > > Ross > > -----Original Message----- > From: Rich Bowen [mailto:rbo...@rcbowen.com] > Sent: Thursday, February 19, 2015 6:06 AM > To: dev > Subject: ApacheCon Schedule > > For those not involved in the process so far, I appreciate your patience, and > your suffering in the dark. Making the schedule public too early caused > significant logistical problems last two times (people thinking they knew > things that they didn't know, and making travel plans accordingly), and we > want to avoid that nightmare this time around. > > For those involved in the process so far: > > It looks like we're done with the ApacheCon schedule. Sort of. We've got > 7 tracks, three days, which I think is probably just the right volume. > > Please look at the DRAFT schedule, and comment in this thread. I, for one, > think we have a kickin' schedule. > > Problems that I think still need solving: > > * We have an empty spot in the community track. Given that community is what > we *do*, it seems that we could come up with 6 community talks to schedule, > and have a few fallbacks. If folks could look through the not-yet-accepted > list with me and see what you can find, that would be awesome. > > * We have 16 open slots. We don't need to fill all of them - we need to leave > 6 or 7 slots open for vendor-sponsored talks (Don't worry, these will NOT be > product pitches) which will show up over the coming weeks. > (LF's problem, not ours.) But I think we can probably put together a few > half-day tracks if we put our minds to it. We have an entire day/track on > Wednesday, if someone still thinks that they can put together a complete > track (6 talks). > > * We need more wait-listed talks. We currently have 6 waitlisted talks, and > I'm probably going to take several of those right now to fill in some empties. > > * We have the problem that's not a problem, which is that we had 239 > submissions, and have only accepted 115 talks - less than half. So we'll get > a LOT of "why wasn't my talk accepted" emails, and I never have very good > answers to that, because the answer really is, this time, too much content, > too little space. But the questions will come, and that's a very unsatisfying > answer to people that have put time and effort into crafting talk abstracts. > > > If you would like to help with any of these things, please get in touch with > me. Or, just step up and claim it and do it. > > Note that I will be flying for much of today, and at a conference > Friday-Sunday, so if I'm not responsive, please ping Jan Iversen, who can > also help you out with this - although apparently I can't make him Owner of > the Google Doc, so actually sharing the doc with you will be delayed, unless > you respond in the next 3 hours. > -- Rich Bowen - rbo...@rcbowen.com - @rbowen http://apachecon.com/ - @apachecon
