Open Stack

Just my $.01 opinion.

The first seems to be more along the lines of HPC in my mind. The second
seems like it might fit in the Private & Hybrid Cloud category, however
that category also has many items at present... so it might also make sense
to leave it in Telecom & NFV even though I think the intersection between
the proposed topic and the track is not the best alignment.

I agree regarding the track names. After reading through the abstracts in
Private & Hybrid, I can't but help wonder if how many could fit into a
Cloud Security or Incident Response category, which could actually lead to
some interesting community overlaps if fostered over time.

-Julia

On Tue, Feb 13, 2018 at 1:49 PM, Amrith Kumar <amrith.kumar at gmail.com>
wrote:

> I submitted track change requests for
>
> this talk <https://www.openstack.org/track-chairs/browse/20657>, and this
> talk <https://www.openstack.org/track-chairs/browse/20749>
>
> to Public Cloud from Telecom & NFV.
>
> The changes were rejected with the message that they weren't "Public cloud
> specific". They are certainly more appropriate in Public cloud than in
> Telecom & NFV; for example, I could ask the question "How are these Telecom
> & NFV specific".
>
> How do you want us to handle these kinds of track change requests?
>
> A more generic issue that I'm seeing is that with these track names
>
> Private & Hybrid Cloud
> Public Cloud
> Container Infrastructure
> Edge Computing
> OpenDev CI/CD
> HPC/GPU/AI
> Telecom & NFV, and
> Open Source Community
>
> it may become hard to decide where to slot some topics.
>
> Thanks,
>
> -amrith
>
>
> _______________________________________________
> Openstack-track-chairs mailing list
> Openstack-track-chairs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-track-chairs/attachments/20180213/741b2fc2/attachment.html>