The thing is:
I will definitely not fly to the US Bay Area (I would be surprised to hear any
different proposal) for just one day. ApacheCon has the benefit of being a
large conference, that is worth doing such a trip. My company allows me to go,
because of the marketing value of being a speaker at a large international
conference (Or at least for serving my part as part of the Foundation (TAC)).
Being a speaker or even just an attendee on a little 20-person event in some
meeting room at Adobe will definitely not buy me the ticket.
ApacheCon provides the chance for people from all over the world to gather
there and the chance to have those, who can’t afford coming by applying for
TAC.
A separate event will probably just benefit a few people in the area around the
location the event is hosted at, but definitely not be a community thing.
The 30 People thing is also just because I asked for a separately bookable
event. I guess if we make it happen as fully integrated part of ApacheCon that
requirement would be different. After all the reason for me asking for the
separate charge was to make it possible for you (Alex) to only come for the one
day, as you stated, that you wouldn’t like to come for the entire conference.
And I would like to call it “FlexJS Project Summit” even if it’s not 100%
correct. But I think for most people Flex is old and dead. I think we wouldn’t
be talking much about the old Flex SDK, but focus completely on FlexJS, so I
think this would make more people curious to read what we are doing.
Chris
Am 27.01.17, 08:00 schrieb "Alex Harui" <aha...@adobe.com>:
On 1/26/17, 1:49 PM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:
>I’ll definitely volunteer to handle the details … well I guess most
>things are already handled and I’m just waiting on a “Go-consensus”, but
>I think we have that and now it would be up to filling the seats ;-)
>
>I think this would be the best option to finally get the team together
>AND get new people involved.
>
>For me the community over code thing is not restricted to “Flex community
>over Flex code”, but more a total ASF view thing.
>
>For me it’s 1000+ to make it happen.
Well, it is certainly worth pursuing, but I am wondering if there is a
cut-off date where, if we don't have enough seats filled, we can bail out.
I'm not clear it is in the best interests of the Linux Foundation, the
ASF, or even Flex if only 6 people can make it.
I thought I saw that there is only room at ApacheCon for one more
project's summit. It doesn’t seem right that we take up a summit spot if
there are other projects that can bring more people.
I certainly hope there will be a year where there is enough money in Flex
to fill enough seats to have a summit at ApacheCon. Based on early
responses, I'm not clear that 2017 is the year. If we decide not to do a
summit at ApacheCon, I have some alternate proposals for us to consider.
I've purposefully not proposed them so far so as not to dilute attention
from this attempt to have a summit.
Thoughts?
-Alex
