www-apachecon-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Will Stevens <williamstev...@gmail.com>
Subject Re: ApacheCon.next
Date Sat, 28 Jan 2017 16:11:42 GMT
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 well.  We
kept asking for things that seemed exceptional and we kept getting them, I
thought we were just getting really lucky.  :)

I am the VP of Apache CloudStack and our PMC has been struggling with
community run conferences.  We have pulled off a few because our CloudStack
Collaboration Conference (CCC) has a pretty good following, so we can drive
attendance and sponsors.  We have also had the LF run a couple for us by
adding a few days to previous ApacheCon venues.  For us, beyond all the
logistics of running a conference, we don't have a commercial entity that
could handle things like, taking money from sponsors etc... This means that
everyone who runs an independent CCC is starting from scratch each time and
never have a system to work from.  As one of the organizers of the last CCC
in Montreal, I can assure you the logistics to pull off a successful
conference are very real.

All to say, I think this is a win-win approach for both the projects and
the ASF.

In our case, we will be trying to use our CCC brand to drive both
attendance and sponsorship. With only the initial announcement and without
contacting any of our usual sponsors, we have already confirmed one sponsor
and a second is working through the details.

Here is what I have put together for this conference so far:
http://us.cloudstackcollab.org/

If anyone wants to borrow/steal my event template for their own conference
details, I am totally fine with that.  The sites are all static sites built
with Hugo and they are publically available on Github.  Be warned that I
was building this template for myself, and I am a developer, so I did
pretty much everything in HTML instead of Markdown.

Miami Conference source: https://github.com/cloudops/us.cloudstackcollab.org

Montreal Conference source:
https://github.com/cloudops/ca.cloudstackcollab.org
(includes speaker template and schedule, etc...)

If you want to host your static site on Github Pages, here is a guide to
get you going: http://swillops.com/blog/hugo-on-gh-pages/

I am glad to see ApacheCon going in this direction.  I feel that it is a
great way for the ASF to help promote the projects who want to participate
and give the users a great opportunity explore other projects.

Cheers,

Will

On Fri, Jan 27, 2017 at 5:37 PM, Rich Bowen <rbowen@rcbowen.com> wrote:

> On Jan 27, 2017 17:07, "Roman Shaposhnik" <roman@shaposhnik.org> wrote:
>
> On Fri, Jan 27, 2017 at 1:40 PM, Shane Curcuru <asf@shanecurcuru.org>
> 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 submissions will end up going to only the LF's main CFP, not to
> > the individual event organizers at all.
> >
> > Or do the PMCs already have more talks they're expecting than they have
> > space for?
>
> I see this very similar to how various devrooms get managed for FOSDEM
> (which I'm also involved in): https://fosdem.org/2017/schedule/tracks/
>
>
>
>
>
> exactly. I'm very much aiming for the fosdem model of a core event and
> independently managed tracks.
>
> There's a common CFP management system, but folks submit with an eye
> towards a particular devroom (or a set of  devrooms). For example, a
> Bigdata
> devroom I am co-organizing this year had its own CFP landing page:
>     https://hpc-bigdata-fosdem17.github.io/
>
> The most challenging bit is figuring out where do you put presentaitons
> that
> span multiple topics. That requires a coordination on the part of the folks
> responsible for putting together a schedule for each devroom. E.g. in
> our case we had a talk about big data graph analytics implemented on top
> of PostgreSQL -- it ultimately ended up in Graph devroom, but it could've
> ended up in either of the 3.
>
> Thanks,
> Roman.
>

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