Re: ApacheCon.next

2017-02-14 Thread Will Stevens
I also have potential sponsors who are not sponsoring because the base price is too high. We are trying to offer anyone who sponsors with a note of CloudStack or CCC (with any type of sponsorship) equal visibility in the CCC track. The sponsor ends up just sponsoring ApacheCon, but we are going t

Re: ApacheCon.next

2017-02-14 Thread Christofer Dutz
Unfortunately, I have some additional info I think could be interesting for others. As far as I understood it, it was planned that the sub-events allow more fine-grained sponsoring. I already had two companies that were generally willing to sponsor the FlexJS summit. Unfortunately, the LF do

Re: ApacheCon.next

2017-01-31 Thread Rich Bowen
On Jan 30, 2017 19:08, "Roman Shaposhnik" wrote: Hi! I don't think this question has come up on this thread yet, so here it is: what are our thinking about sponsorship? Right now we have two separate sponsorship buckets: Bigdata and Core. Do we plan to keep it that way? Suppose there's somebody

Re: ApacheCon.next

2017-01-30 Thread Will Stevens
I am bringing my sponsors for CCC on as core sponsors and I am being notified by the LF when a sponsor specifies that they are sponsoring CCC. These sponsors are not treated any differently by apachecon, but I am giving them extra visibility in our community and will be giving them special visibili

Re: ApacheCon.next

2017-01-30 Thread Roman Shaposhnik
Hi! I don't think this question has come up on this thread yet, so here it is: what are our thinking about sponsorship? Right now we have two separate sponsorship buckets: Bigdata and Core. Do we plan to keep it that way? Suppose there's somebody interested in sponsoring Apache XXX (where XXX !=

Re: ApacheCon.next

2017-01-28 Thread Will Stevens
Hey Rich, I had a chance to read through your doc last night. I fully support what you are trying to do here. I talked to Angela at ApacheCon Seville, to try to setup something like this for CloudStack in Miami. I didn't realize that the big picture for ApacheCon was going in this direction as w

Re: ApacheCon.next

2017-01-28 Thread Rich Bowen
On Jan 28, 2017 05:16, "Dennis Kieselhorst" wrote: > As you might imagine, I've spent a LOT of time over the last 15 years > thinking about what ApacheCon is, and should be. Moving from a handful > of projects all in generally the same technology space, to 300 projects > across all areas of tech

Re: ApacheCon.next

2017-01-28 Thread Dennis Kieselhorst
> As you might imagine, I've spent a LOT of time over the last 15 years > thinking about what ApacheCon is, and should be. Moving from a handful > of projects all in generally the same technology space, to 300 projects > across all areas of technology, has put a great strain on our ability to > pr

Re: ApacheCon.next

2017-01-27 Thread Rich Bowen
On Jan 27, 2017 17:07, "Roman Shaposhnik" wrote: On Fri, Jan 27, 2017 at 1:40 PM, Shane Curcuru wrote: > Excellent stuff! > > Will there be any coordination between CFPs? We do have a few general > talks that are still valuable, either from great speakers on topics that > are always popular or

Re: ApacheCon.next

2017-01-27 Thread Roman Shaposhnik
On Fri, Jan 27, 2017 at 1:40 PM, Shane Curcuru wrote: > Excellent stuff! > > Will there be any coordination between CFPs? We do have a few general > talks that are still valuable, either from great speakers on topics that > are always popular or because they help our communities. But I imagine >

Re: ApacheCon.next

2017-01-27 Thread Rich Bowen
On 01/27/2017 04:40 PM, Shane Curcuru wrote: > Excellent stuff! > > Will there be any coordination between CFPs? We do have a few general > talks that are still valuable, either from great speakers on topics that > are always popular or because they help our communities. But I imagine > a few

Re: ApacheCon.next

2017-01-27 Thread Shane Curcuru
Excellent stuff! Will there be any coordination between CFPs? We do have a few general talks that are still valuable, either from great speakers on topics that are always popular or because they help our communities. But I imagine a few submissions will end up going to only the LF's main CFP, no

Re: ApacheCon.next

2017-01-27 Thread Rich Bowen
On 01/27/2017 04:18 PM, Leif Hedstrom wrote: > That much said, I would have loved to see tracks which are less project > specific, and more feature specific. Like, how to use H2 in the Apache > Ecosystem. But, I’m not sure how the response was for that? If it seemed > useful, would there be ro

Re: ApacheCon.next

2017-01-27 Thread Leif Hedstrom
> On Jan 27, 2017, at 6:18 AM, Rich Bowen wrote: > > (With apologies to people who have already seen this discussion > elsewhere. I figured more eyes on it was better.) > > As you might imagine, I've spent a LOT of time over the last 15 years > thinking about what ApacheCon is, and should be. M

Re: ApacheCon.next

2017-01-27 Thread Roman Shaposhnik
+1 I really like this new direction! Thanks, Roman. On Fri, Jan 27, 2017 at 5:18 AM, Rich Bowen wrote: > (With apologies to people who have already seen this discussion > elsewhere. I figured more eyes on it was better.) > > As you might imagine, I've spent a LOT of time over the last 15 years >

Re: ApacheCon.next

2017-01-27 Thread Rich Bowen
On 01/27/2017 02:20 PM, Leif Hedstrom wrote: > Roger, I will talk to the PMC chairs. Is there a preference from ACNA / > LinuxFoundation? I’m fairly certain we would prefer Mon-Tue, or even Tue-Wed > if LF is ok with that. > >> Events that are outside of the main event (chronologically) will h

Re: ApacheCon.next

2017-01-27 Thread Leif Hedstrom
> On Jan 27, 2017, at 12:17 PM, Rich Bowen wrote: > > > > On 01/27/2017 01:58 PM, Leif Hedstrom wrote: >> >>> On Jan 27, 2017, at 6:18 AM, Rich Bowen wrote: >>> >>> (With apologies to people who have already seen this discussion >>> elsewhere. I figured more eyes on it was better.) >>> >>>

Re: ApacheCon.next

2017-01-27 Thread Rich Bowen
On 01/27/2017 01:58 PM, Leif Hedstrom wrote: > >> On Jan 27, 2017, at 6:18 AM, Rich Bowen wrote: >> >> (With apologies to people who have already seen this discussion >> elsewhere. I figured more eyes on it was better.) >> >> As you might imagine, I've spent a LOT of time over the last 15 years

Re: ApacheCon.next

2017-01-27 Thread Leif Hedstrom
> On Jan 27, 2017, at 6:18 AM, Rich Bowen wrote: > > (With apologies to people who have already seen this discussion > elsewhere. I figured more eyes on it was better.) > > As you might imagine, I've spent a LOT of time over the last 15 years > thinking about what ApacheCon is, and should be. M