[openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences
James.Bottomley at HansenPartnership.com
Mon Feb 15 15:52:43 UTC 2016
On Mon, 2016-02-15 at 04:36 -0500, Eoghan Glynn wrote:
> > > Honestly I don't know of any communication between two cores at a
> > > +2 party that couldn't have just as easily happened surrounded by
> > > other contributors. Nor, I hope, does anyone put in the
> > > substantial reviewing effort required to become a core in order
> > > to score a few free beers and see some local entertainment.
> > > Similarly for the TC, one would hope that dinner doesn't figure
> > > in the system incentives that drives folks to throw their hat
> > > into the ring.
> > Heh, you'd be surprised.
> > I don't object to the proposal, just the implication that there's
> > something wrong with parties for specific groups: we did abandon
> > the speaker party at Plumbers because the separation didn't seem to
> > be useful and concentrated instead on doing a great party for
> > everyone.
> > > In any case, I've derailed the main thrust of the discussion
> > > here, which I believe could be summed up by:
> > >
> > > "let's dial down the glitz a notch, and get back to basics"
> > >
> > > That sentiment I support in general, but I'd just be more
> > > selective as to which social events should be first in line to be
> > > culled in order to create a better atmosphere at summit.
> > >
> > > And I'd be far more concerned about getting the choice of
> > > location, cadence, attendees, and format right, than in questions
> > > of who drinks with whom.
> > OK, so here's a proposal, why not reinvent the Cores party as a
> > Meet the Cores Party instead (open to all design summit attendees)?
> > Just make sure it's advertised in a way that could only possibly
> > appeal to design summit attendees (so the suits don't want to go),
> > use the same buget (which will necessitate a dial down) and it
> > becomes an inclusive event that serves a useful purpose.
> Sure, I'd be totally agnostic on the branding as long as the widest
> audience is invited ... e.g. all ATCs, or even all summit attendees.
If you make it ATC only, you've just restricted it to no newcomers,
which is exclusive again. I think it wants to be open to all design
summit attendees regardless of ATC status. Since there's no separate
badge, I think you keep the OpenStack summit attendees out by judicious
advertising. Perhaps, say, only advertise on openstack-dev@ and
posters at the actual design summit?
More information about the OpenStack-dev