Open Stack

On Tue, May 3, 2016 at 10:19 AM, Paul Belanger <pabelanger at redhat.com>
wrote:

> On Tue, May 03, 2016 at 10:01:06AM -0700, Elizabeth K. Joseph wrote:
> > On Mon, May 2, 2016 at 11:55 AM, Spencer Krum <nibz at spencerkrum.com>
> wrote:
> > > I think this is a good conversation to have. I would recommend we start
> > > a thread-per-conference for simplicity. Folks can use this to
> coordinate
> > > attendance, ensure we submit unique presentations, and to help each
> > > other groom presentations. I doubt that anyone on the team would feel
> > > any offense at someone else submitting on infra topics, but
> coordination
> > > sounds good. Whenever we are presenting on an infra topic, being clear
> > > to put credit for building and supporting the technology in the correct
> > > place is something we should be careful to do.
> > >
> > > We've always used the publications repo to archive an collaborate on
> > > talks, but I think our use of that isn't quite correct at this time.
> >
> > Yeah, we don't tend to prepare the presentations until after our talks
> > have been accepted and that's when we use the publications repo.
> >
> > I like using the mailing list as a notification mechanism but I think
> > we should also maintain an etherpad with a listing so we can keep it
> > all organized in the longer term.
> >
> I'd be happy to see a etherpad URL we can use to list conferences and talks
> people are thinking of talking at.
>
> > --
> > Elizabeth Krumbach Joseph || Lyz || pleia2
> >
>
>
I like the coordination, sometimes it is useful if suddenly two folks are
interested in talking at the same conference (either can be a cooler bigger
talk, or each can be more specialized). :)

--Morgan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-infra/attachments/20160503/ca8f9112/attachment.html>