Closed MadhavJivrajani closed 3 years ago
/sig architecture
/area enhancements /kind cleanup
fyi - communication regarding this has been sent out to leads@kuberentes.io
. The email sent can be found here.
👋🏼 Over the past couple of days, we've worked towards moving design proposals to a separate repository that will be permanently archived. The approach mentioned in the issue description is not followed due to concerns raised on the mailing list and the preferred approach was to create a new repo and permanently archive them.
Post communication on the mailing list, there has been conversation on the #sig-arch slack channel about this and how to proceed. The relevant threads can be found here and here.
Following that, a repo for archival was created and the design proposals were migrated to that while preserving commit history: https://github.com/kubernetes/design-proposals-archive and the design-proposals that currently reside in k/community will contain text that will serve as a redirect to the archival repo: https://github.com/kubernetes/community/pull/6258 (thanks @mrbobbytables!).
Once the archival repo is in good shape, this can be merged and the archival repo should be able to move into permanent archival closing this and https://github.com/kubernetes/community/issues/2565 :)
The relevant k/community PRs are merged: https://github.com/kubernetes/community/pull/6259 https://github.com/kubernetes/community/pull/6258
And the repo has been updated and archived: https://github.com/kubernetes/design-proposals-archive
Closing! /close
@MadhavJivrajani: Closing this issue.
Hi folks, this issue is meant to serve as a tracking issue for the various action items involved leading to moving out design proposals from this repository and subsequently, permanently archiving them.
As a follow up to https://github.com/kubernetes/community/issues/2565, after discussing with sig-arch, this issue is meant for different SIGs to decide upon which design proposals under them should move to devel and which design proposals should find a permanent home in k/enhancements. An example of a design proposals that would be better suited for devel would be as mentioned here: https://github.com/kubernetes/community/issues/2565#issuecomment-758615477.
@johnbelamaric in the sig-arch meeting of 23rd September 2021 (meeting notes) suggested that the following can be done to move design proposals to k/enhacements: If a SIG needs to move any proposals to the enhancements repo, they can create an directory, and put them all under there. Any existing directory structure can be preserved as well under that
archive
directory in their existing keps/archive
directory. As long as the files moved do not contain anykep.yaml
files, the tooling will ignore them.If each SIG could look at the existing design proposals and convey what belongs where, we can get started with the migration.
/cc @kubernetes/sig-architecture