community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jan i <j...@apache.org>
Subject Re: ApacheCon Schedule spreadsheet
Date Wed, 18 Feb 2015 15:19:13 GMT
HI.

The content of Incubator project track is:

#87, Introduction to Zeppelin
#91, Integrating Event Streams and File Data with Apache Flume and Apache
NiFi
#112, Pulsar: Realtime Analytics at Scale leveraging Kafka, Hadoop and Kylin
#183, Apache MRQL (incubating): Advanced Query Processing for Complex,
Large-Scale Data Analysis
#208, Introducing Apache HTrace: an end-to-end tracing framework for
distributed systems
#217, Apache Lens: Cut Data Analytics Silos in your Enterprise (WAIT-LISTED)
#224, Apache Kylin - Extreme OLAP engine for Hadoop

#83, Apache Incubator: where it is coming from and where it is going
Would have been an excellent introduction talk, but it is scheduled for
"community".

If we schedule #83, for "incubator projects", #91 goes to WAIT-LISTED:

rgds
jan i.

On 18 February 2015 at 15:47, jan i <jani@apache.org> wrote:

> Hi
>
> I have added a "incubator projects" track for 1 day (6 talks). I would
> prefer a marketing name like "new and exciting projects", but I do feel it
> is important to give these projects a chance to do marketing for their
> projects.
>
> Rgds
> jan I.
>
>
> On 18 February 2015 at 09:32, Sharan Foga <sharan.foga@gmail.com> wrote:
>
>> Hi Rich
>>
>> Please can I have access to the spreadsheet.
>>
>> Thanks
>> Sharan
>>
>>
>> On 17.2.2015 18:55, Rich Bowen wrote:
>>
>>>
>>>
>>> On 02/17/2015 12:48 PM, Rich Bowen wrote:
>>>
>>>> https://docs.google.com/spreadsheets/d/1k6Fbr7ijMs2PJunN9lhsjq7NjnSXR
>>>> CVXTJHAHRqWshc/edit?usp=sharing
>>>>
>>>>
>>>> This is read-only because it's not the authoritative source, but is a
>>>> copy. There's some overlap between Content and Science. There's also
>>>> some overlap in the Community track.
>>>>
>>>> Please send comments here. Note that we're supposed to notify speakers
>>>> yesterday.
>>>>
>>>
>>> I'm sorry, that was a mistake. I shouldn't share it publicly like that.
>>> Please let me know if you need to see this spreadsheet, and I'll add your
>>> name to the invite list. Making it public just caused too many problems
>>> last time.
>>>
>>> --Rich
>>>
>>>
>>>
>>
>

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