[meta][K8s][API][Extended Maintenance][Operation Docs] Change SIG to Advisory status

Rico Lin rico.lin.guanyu at gmail.com
Thu Nov 28 05:14:20 UTC 2019


On Fri, Nov 22, 2019 at 4:21 PM Andreas Jaeger <aj at suse.com> wrote:
>
>
> What will happen with these two documents if the Operation Docs SIG
> becomes advisory state?
>
> Should we retire the repos and delete the content?
>
As mentioned in patch review, I will try to get Chris or Sean to provide
input to this ML


> I don't know whether the other SIGS own any deliverables, where we need
> to discuss what to do with them,
We don't allow SIGs to own any deliverables at the current stage. as
defined in [1]
``Project team is required when planning for release a deliverable service``

>
> Andreas
>
> > [...]
> --
>  Andreas Jaeger aj at suse.com Twitter: jaegerandi
>   SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg
>    (HRB 36809, AG Nürnberg) GF: Felix Imendörffer
>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126

[1]
https://governance.openstack.org/tc/reference/comparison-of-official-group-structures.html#produces-the-software-project-teams

--
May The Force of OpenStack Be With You,
Rico Lin
irc: ricolin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20191128/40a94569/attachment.html>


More information about the openstack-discuss mailing list