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. Thanks, Nick On Sunday, July 5, 2015, jan i <[email protected]> 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 <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> 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. >> > >
