Open Stack

Good discussions! Agree that it is sometimes unclear and hard to find a 
suitable track for sessions - interesting sessions for that matter - but 
can become less interesting in the wrong track due to the fact that it 
isn't 100 % relevant.

Have a couple of sessions that are very generic around specific 
OpenStack projects - is that a per definition private, hybrid or public 
cloud? Is it OpenSource community? How would you folks categorize a 
session like that?

I will make a choice here, but interesting to hear what the rest of you 
thinks!

Cheers,
Tobias


On 2018-02-13 23:46, Jimmy McArthur wrote:
> Removing Speaker Support and all the cc's since you're all subscribe 
> to the Track Chair list :)
>
> To answer Gary's question... We actually had a pretty even 
> distribution of submissions this go round. Obviously Private Cloud and 
> Public Cloud have a higher number of submissions, but based on what 
> we've seen, it feels like we're getting closer to a good set of tracks.
>
> That said, this is exactly the type of feedback we're looking for. So 
> please let us know if you feel we could be adding or subtracting 
> tracks as the process goes on.
>
> Gary Kevorkian (gkevorki) wrote:
>>
>> You know you can count on me for my $.02...
>>
>> Have we over-pivoted from a very high level of granularity in the 
>> tracks (Boston and Sydney Summits) to now having all the talks fall 
>> into one of eight?
>>
>> #JustAsking
>>
>> ttp://www.cisco.com/c/dam/m/en_us/signaturetool/images/banners/standard/09_standard_graphic.png
>>
>>
>>
>> 	
>>
>> Gary Kevorkian
>>
>> EVENT MARKETING MANAGER
>>
>> gkevorki at cisco.com <mailto:gkevorki at cisco.com>
>>
>> Tel: +3237912058
>>
>>
>>
>>
>> ttp://www.cisco.com/c/dam/m/en_us/signaturetool/images/twitter-16x16.png 
>> <http://wwwin.cisco.com/c/cec/organizations/gmcc/services-tools/twitter.com/GARY805>
>>
>>
>> ttp://www.cisco.com/c/dam/m/en_us/signaturetool/images/icons/webex.png 
>> <http://cisco.webex.com/meet/gkevorki>ttp://www.cisco.com/c/dam/m/en_us/signaturetool/images/icons/sparks.png 
>> <https://ciscospark.com/gkevorki>ttp://www.cisco.com/c/dam/m/en_us/signaturetool/images/icons/jabber.png 
>> <http://reachme.cisco.com/call/gkevorki>
>>
>> 	
>> 	
>>
>> Cisco Systems, Inc.
>>
>> United States
>>
>> Cisco.com <http://www.cisco.com/>
>>
>>
>> ttp://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif
>>
>> 	
>> 	
>>
>> Think before you print.
>>
>> This email may contain confidential and privileged material for the 
>> sole use of the intended recipient. Any review, use, distribution or 
>> disclosure by others is strictly prohibited. If you are not the 
>> intended recipient (or authorized to receive for the recipient), 
>> please contact the sender by reply email and delete all copies of 
>> this message.
>>
>> Please click here 
>> <http://www.cisco.com/c/en/us/about/legal/terms-sale-software-license-agreement/company-registration-information.html> for 
>> Company Registration Information.
>>
>> 	
>>
>> *From: *Julia Kreger <jkreger at gmail.com>
>> *Date: *Tuesday, February 13, 2018 at 2:28 PM
>> *To: *Amrith Kumar <amrith.kumar at gmail.com>
>> *Cc: *"speakersupport at openstack.org" <speakersupport at openstack.org>, 
>> "Openstack-track-chairs at lists.openstack.org" 
>> <Openstack-track-chairs at lists.openstack.org>
>> *Subject: *Re: [Openstack-track-chairs] Track change requests ...
>>
>> 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 
>> <mailto: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
>>     <mailto:Openstack-track-chairs at lists.openstack.org>
>>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs
>>
>> _______________________________________________
>> Openstack-track-chairs mailing list
>> Openstack-track-chairs at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs
>
>
>
> _______________________________________________
> 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/20180214/60f30806/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 5635 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-track-chairs/attachments/20180214/60f30806/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 578 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-track-chairs/attachments/20180214/60f30806/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 729 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-track-chairs/attachments/20180214/60f30806/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 613 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-track-chairs/attachments/20180214/60f30806/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 751 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-track-chairs/attachments/20180214/60f30806/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 144 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-track-chairs/attachments/20180214/60f30806/attachment-0011.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3945 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.openstack.org/pipermail/openstack-track-chairs/attachments/20180214/60f30806/attachment-0001.bin>