Open Stack

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.

On Mon, May 2, 2016, at 11:31 AM, Paul Belanger wrote:
> Greetings,
> 
> Now that OpenStack Austin has come and gone, I was hoping to continue the
> dialog about speaking opportunity for other conferences. One of my
> personal
> goals this year is to talk more about the tooling we support to other
> people
> and projects. Projects like nodepool, zuulv2.5, grafyaml and bindep come
> to
> mind.
> 
> However, I am reluctant on submitting talks to other conferences without
> giving
> some sort of heads up to everybody. I think how we collaborated on our
> Austin
> talks worked quiet well and what I guess I am asking should we consider
> doing to
> same for other conferences?
> 
> Or I am just being paranoid.
> 
> PB
> 
> _______________________________________________
> OpenStack-Infra mailing list
> OpenStack-Infra at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


-- 
  Spencer Krum
  nibz at spencerkrum.com