Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

EOL kubernetes-incubator #34

Closed
jdumars opened this issue Jun 25, 2018 · 10 comments
Closed

EOL kubernetes-incubator #34

jdumars opened this issue Jun 25, 2018 · 10 comments
Assignees
@spiffxp
Labels
committee/steering Denotes an issue or PR intended to be handled by the steering committee. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@jdumars
Copy link
Member

jdumars commented Jun 25, 2018

  • Clarify the process for approving/vetoing incubator projects and mitigate sponsor shopping
  • Update incubator process to explain new GitHub organization strategy
  • Clarify graduation process
@spiffxp
Copy link
Member

spiffxp commented Jul 16, 2018

/assign
I'd like to instead repurpose this issue to document:

  • if/when kubernetes-incubator repos are moving
  • clarify the step by step process to migrate repos from kubernetes-incubator (or other orgs) to kubernetes-sigs
  • ditto for making new repo

ref: kubernetes/community#1922

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 14, 2018
@spiffxp
Copy link
Member

spiffxp commented Oct 18, 2018

/remove-lifecycle stale
/committee steering
Now that everything in kubernetes-incubator uses the same automation as kubernetes-sigs, moving repos from one place to the other is pretty much a matter of:

  • finding sigs willing to own/sponsor these subprojects
  • migrating members from kubernetes-incubator to kubernetes-sigs

@k8s-ci-robot k8s-ci-robot added committee/steering Denotes an issue or PR intended to be handled by the steering committee. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 18, 2018
@bgrant0607 bgrant0607 changed the title Improve the incubator process EOL kubernetes-incubator Jan 15, 2019
@philips
Copy link
Contributor

philips commented Jan 16, 2019

I think the only way we are going to get this done is by setting an EOL deadline and asking the repo maintainers to find a new home or create a new org that will make them an "associated repo".

Does July 1st seem like enough lead time?

@timothysc timothysc added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. labels Mar 11, 2019
@nikhita
Copy link
Member

nikhita commented Oct 24, 2019

Going to remove help-wanted since the GitHub Admin team is working on this: kubernetes/community#1922.

/remove-help

@k8s-ci-robot k8s-ci-robot removed the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Oct 24, 2019
@parispittman
Copy link
Contributor

4 repos left; next few months

@cblecker
Copy link
Member

cblecker commented Apr 5, 2020

Still four repos, but we have active communication with all sigs and have movement.

@spiffxp
Copy link
Member

spiffxp commented Apr 6, 2020

There are docs that still reference kubernetes-incubator that I'd like to remove

@mrbobbytables
Copy link
Member

I think this may be safe to close at this point.
All AI's in the community tracking issue have been closed: kubernetes/community#1922

The only outstanding issue that I know of is a follow-up item in k/website to update their references: kubernetes/website#24380

@nikhita
Copy link
Member

nikhita commented Oct 19, 2020

Let's close this!

We can track the k/website issue separately IMO. :)

@nikhita nikhita closed this as completed Oct 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@spiffxp spiffxp

Labels
committee/steering Denotes an issue or PR intended to be handled by the steering committee. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
10 participants
@philips @spiffxp @timothysc @jdumars @cblecker @parispittman @mrbobbytables @nikhita @k8s-ci-robot @fejta-bot