| JayF | I'm struggling a bit to find any public published policy on who is allowed to join embargo-notice | 14:58 |
|---|---|---|
| JayF | Does that exist and I'm bad at google? Or is it just a case-by-case thing | 14:59 |
| zigo | JayF: I don't think there's any... | 15:19 |
| fungi | it's hard to make a clear policy for it, the vmt members come to agreement on each request for representatives of a new organization, but generally it's anyone representing an openstack public cloud or anyone with a publicly-available openstack distribution (either commercial or included in community gnu/linux distros) | 16:43 |
| fungi | and also openstack contributors who work on stable branch management or deployment projects | 16:44 |
| JayF | I think we have some members currently who fit more into the 'large downstream private clouds' and/or 'consultants to large downstream private clouds' | 16:48 |
| JayF | G-Research would like a representative on it, and I'm trying to determine if that would be acceptable | 16:48 |
| fungi | i think we'd just need to talk through what they get out of it. e.g. protecting their internal deployment from malicious employees? | 16:49 |
| fungi | are they going to be using the advance copies of patches directly? | 16:50 |
| JayF | Yes to both of those, basically. Many companies are now treating internal use cases like public clouds, and trying to ensure secure multitenancy. Just because there's not a bill between companies doesn't mean the posture is different :D | 17:02 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!