[User-committee] [Product] retiring repo openstack-infra/featuretracker ?
Rochelle Grober
rochelle.grober at huawei.com
Thu Aug 30 17:54:39 UTC 2018
the repos would be good to keep, but locked down. mail list and irc channel *should* go away.
--Rocky
--------------------------------------------------
Rochelle Grober Rochelle Grober
M: +1-6508889722<tel:+1-6508889722>(preferred)
E: rochelle.grober at huawei.com<mailto:rochelle.grober at huawei.com>
2012<tel:2012>实验室-硅谷研究所技术规划及合作部
2012<tel:2012> Laboratories-Silicon Valley Technology Planning & Cooperation,Silicon Valley Research Center
From:Andreas Jaeger
To:Kunzmann, Gerald,arkady_kanevsky at dell.com,ItzShamail at gmail.com,Rochelle Grober,user-committee at lists.openstack.org,Clark Boylan,
Date:2018-08-30 00:27:35
Subject:Re: [User-committee] [Product] retiring repo openstack-infra/featuretracker ?
On 2018-08-30 09:21, Kunzmann, Gerald wrote:
> Dear Andreas, all,
>
> I agree that some parts should be retired.
>
> I however wonder how the outcome of the Product WG (i.e. the development proposals) could be conserved (https://github.com/openstack/development-proposals/tree/master/development-proposals/proposed).
> Those proposals had been references e.g. by other groups and IMHO it would be good to keep the use cases and requirements contained within.
Retirement means the process documented at
https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project
. Basically: Making repo read-only, and pushing a change to delete
everything.
So, those use cases would be accessible (from old revision) but more
difficult to find.
Clark, is there a good way to half-retire it? Just block submissions?
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20180830/e4394cc9/attachment-0001.html>
More information about the User-committee
mailing list