flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Tynjala <joshtynj...@gmail.com>
Subject Re: [ApacheCon] Let's make it happen :-)
Date Tue, 31 Jan 2017 16:12:41 GMT
I agree that FlexJS Summit is a better name.

- Josh

On Tue, Jan 31, 2017 at 8:00 AM, Christofer Dutz <christofer.dutz@c-ware.de>

> Ok gyus … good news,
> So in general we are all set to make our first Flex Summit happen … the
> ASF would be happy, if we did it and the LF doesn’t have any objections.
> The procedure would be that we come up with a schedule of 5-6
> Talks/Events. That means we would not be using the official CFP system.
> However, if someone was to submit anything Flex related in the CFP this
> would be forwarded to us for being taken into consideration. That makes
> planning a lot easier as we can discuss the details here and won’t have to
> hope for our talks to be selected.
> Also we were asked on what day the summit should be. Tuesday, Wednesday or
> Thursday. As I understood Harbs, that it would be better for him to attend
> later in the Week I would suggest Thursday, but as probably Justin and I
> would be submitting something related to IoT I would do a quick check to
> make sure the IoT Summit is not on Thursday ;-)
> The Linux Foundation would like to know if the Summit should be called
> “Flex Summit” … I would prefer “FlexJS Summit” to sort of promote that the
> summit would have a focus on FlexJS and eventually make people curious, but
> I think we should decide here quickly so the LF can get started.
> Also the LF would need a short introduction/summary … I would start
> writing such an introduction and post it here for further discussion, if
> that’s ok with you?
> Last not least I am currently discussing options with the LF for enabling
> Summit Sponsors with a separate pricing, allowing companies to explicitly
> sponsor project summits and not the entire ApacheCon. I’ll keep you guys
> and hereby potential sponsors updated on that.
> Really excited about this :-)
> Chris

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