www-apachecon-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jan i <j...@apache.org>
Subject Re: Suggested review timeline for apacheCON CORE.
Date Sun, 05 Jul 2015 22:22:07 GMT
On 5 July 2015 at 23:47, Nick Dimiduk <ndimiduk@apache.org> wrote:

> Jan --
> I plan to look at the proposals today. Are there any guidelines for what
> constitutes a track? For instance, I assume there are time fixed slots
> within which all tracks are coordinated. How many slots are there? Is it
> acceptable to double-up in a single slot two talks that look too short for
> a full session? Any other guidelines? Maybe there's a wiki page with this
> information that I haven't seen.
> Help/guidance is appreciated as I've only ever attended a single ApacheCON
> and I've never been a track committee.

The simple guideline is you choose the talks you have asked people to
propose, or talks you want in your track.

You simply order these presentations and give me the order (6 for a full
tack, 3 for a half track).

A presentation is 45-50 minutes, no doubling up is allowed. If a
presentation is too short for 45 minutes, it is rejected.

Looking at the proposals today, as in reviewing them is getting a bit late,
the deadline was sunday.

hope that helps, otherwise ask more.

jan i.

> Thanks,
> Nick
> On Sunday, July 5, 2015, jan i <jani@apache.org> wrote:
>> Hi.
>> Just a polite reminder, it is sunday, and I have not received a single
>> track ?
>> We need to move quickly, to that presenters who are rejected have a
>> chance of applying to big data.
>> rgds
>> jan i.
>> On 30 June 2015 at 11:20, jan i <jani@apache.org> wrote:
>>> Hi all
>>> In just a few hours the CFP for apacheCON CORE will officially close,
>>> then the second batch
>>> of hard work starts. We need to review the talks and put them in a
>>> schedule.
>>> Our timeline is a little bit critical, because some presentations are
>>> submitted for both events, and
>>> if rejected in core the should have a chance in big data, and opposite
>>> if accepted they should be
>>> rejected in big data.
>>> Wednesday July 1, CFP closes officially, and reviews can start.
>>> Thursday July 2, I will write to all who have submitted tutorials etc.
>>> Friday July 3, CFP will be really closed and final csv pulled of the
>>> database
>>> Sunday July 5, Review from track builders (as well as order of tracks)
>>> should be completed
>>>                         (please mail me directly the order of the tracks
>>> with the titles)
>>> Wednesday July 8, first version of schedule should be ready to be
>>> discussed with LF
>>> Friday July 10, CFP big data closes,
>>> Sunday July 12, accept/reject letters to be mailed.
>>> I hope most of you who have build tracks, already know the talks, so
>>> reviewing will be an easy
>>> and fast task.
>>> Help with reviewing all the other talks is HIGHLY appreciated.
>>> I am full time working on apacheCON the next week, so do not hesitate to
>>> mail me if case of
>>> comments or questions.
>>> I will also try to be on IRC as much as possible (#apachecon).
>>> on behalf of the apacheCON team
>>> jan i.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message