Mailing-List: contact dev-help@community.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@community.apache.org
MIME-Version: 1.0
In-Reply-To: <54DA18D0.9030207@rcbowen.com>
References: <54D9C378.5010509@gmail.com>
	<54DA0E9C.4020908@rcbowen.com>
	<CAK2iWdTQHMGhYPM__x870SqZoYHAgOsSyxvZfiVYdaBV8kksoQ@mail.gmail.com>
	<54DA18D0.9030207@rcbowen.com>
Date: Tue, 10 Feb 2015 15:58:02 +0100
Message-ID: 
 <CAK2iWdQ_Ukh4XaMnLT5nXG0JzVHBE=-VNA4TvGBWLEMx2ZEpKg@mail.gmail.com>
Subject: Re: Proposed Track Details for Apachecon NA
From: jan i <jani@apache.org>
To: "dev@community.apache.org" <dev@community.apache.org>
Content-Type: multipart/alternative; boundary=001a11c3da0a126f53050ebd1dee

--001a11c3da0a126f53050ebd1dee
Content-Type: text/plain; charset=UTF-8

On Tuesday, February 10, 2015, Rich Bowen <rbowen@rcbowen.com> wrote:

>
>
> On 02/10/2015 09:14 AM, jan i wrote:
>
>>
>> I agree with Rich, but before this turns into (once again) too many
>> variations over the same theme, can we agree on ONE common way to keep the
>> trakcs together.
>>
>> I am happy to be the one that coordinates and updates the track schedule
>> with input from all of you. But of course we can also do it the usual way
>> that everybody does everyrhing.
>>
>> just my 2ct.
>> rgds
>> jan i
>>
>> ps. Do not misunderstand me, you guys (including Ross) does a brilliant
>> job
>> in track building, I justthink we need some coordination. Rick will surely
>> tell me if I interfere wongly in the process.
>>
>>  >
>>>
>>
>
> C. Craig Ross <ccr@linuxfoundation.org> is maintaining the One True
> Spreadsheet, because he's going to be the one that does the final online
> schedule, printed schedule, speaker notifications, and so on. He has shared
> that spreadsheet with me, and can also share it with you if you like, but
> I'm not making any edits there - just funneling information to Craig.

he has shared with me as well, but I agree with you, no edits just tunnel
information. I need it for TAC later to schedule which applicants cover
which talks.


> I would like to have something more efficient, more interractive, and
> easier to use, but I don't want to end up with the fiasco and confusion
> that we've had for the last two events.

+1 no 3 day total stress this time please.

>
> I'm open to any suggestion, but we need to be sure that we keep Craig in
> the loop for any decisions in this area, since he is ultimately responsible
> for session scheduling for this event, and we don't want to further
> complicate things.

+1, let us follow the riad of letting Craig do the work.


we just need to find a way of how to get all the tracks scheduled not in
the hands of you, pierre and ross. And not forgetting accepting/rejecting
all these talks, which is something I supoose Craig will have a hard time
doing.


rgds
jan i

>
> This is why I have not made my own copy of the data anywhere, other than
> "my" track, which I'm coordinating in a doc that I'll turn back over to
> Craig as soon as it solidifies.
>
>
> --
> Rich Bowen - rbowen@rcbowen.com - @rbowen
> http://apachecon.com/ - @apachecon
>


-- 
Sent from My iPad, sorry for any misspellings.

--001a11c3da0a126f53050ebd1dee--