Re: ApacheCon status and proceeding forward

2014-02-13 Thread Roman Shaposhnik
Hi Rich! On Wed, Feb 12, 2014 at 5:57 PM, Rich Bowen wrote: > 3) http://tm3.org/actracks/ is days and proposed tracks each day. Now that > I'm done with #2, I'm moving on to #3, taking the completed tracks and > populating the actual schedule in #3. From here, we'll have to either add or > remove

Re: ApacheCon status and proceeding forward

2014-02-13 Thread Kay Schenk
On Wed, Feb 12, 2014 at 5:57 PM, Rich Bowen wrote: > > On 02/12/2014 11:57 AM, Jan Willem Janssen wrote: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Hi, >> >> I'm a bit confused as to what the current status is on the track >> selection for ApacheCon NA. I've seen the proposed tra

Re: ApacheCon status and proceeding forward

2014-02-12 Thread Rich Bowen
On 02/12/2014 11:57 AM, Jan Willem Janssen wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm a bit confused as to what the current status is on the track selection for ApacheCon NA. I've seen the proposed track list, but what do we do with the content of those tracks? And what about

ApacheCon status and proceeding forward

2014-02-12 Thread Jan Willem Janssen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm a bit confused as to what the current status is on the track selection for ApacheCon NA. I've seen the proposed track list, but what do we do with the content of those tracks? And what about the proposals that still are not categorized, is tha