Re: Extracting KEPs from kubernetes/community

[Stephen Augustus]

Hey peeps,

This is a reminder that we intend to extract all KEP content from k/community on November 30.

KEPs will be moving to k/enhancements. All in-flight KEP PRs should be wrapped up and merged, the sooner the better. More details below.

Following the migration, we will apply a blockade to the keps directory in k/community. 

Any questions or concerns can be directed to myself (@justaugustus) or Caleb (@calebamiles) on this thread or in #sig-pm. 

-- Stephen Augustus

On Wed, Oct 31, 2018 at 10:22 PM 'Caleb Miles' via Kubernetes developer/contributor discussion <kuberne...@googlegroups.com> wrote:

Hey y'all,

We are continuing to work on improvements to the KEP process in SIG Architecture and we would like to make the incremental step to extract existing KEP content and git history from the Community Repo. We hope to 

• improve the signal to noise ratio for KEP reviewers and approvers and community members interested in KEPs
• provide a stable home for future tooling to address the current challenges with the KEP process

If you are are KEP reviewer or approver

• merge early to document consensus. Do not block merges on full agreement. Do make sure that all PR feedback is addressed through small incremental PRs 
• ensure that KEPs you approve include all required KEP sections according to the template
• instruct authors to not include numbers in their KEP filename or metadata and do not update NEXT_KEP_NUMBER in your PRs due to existing collisions and friction. This will be addressed at a later date
  

If you are a KEP author

• ensure your existing KEPs and PRs follow the template

We aim to extract all existing content by 30 November 2018. Thanks!

Caleb

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-de...@googlegroups.com.
To post to this group, send email to kuberne...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/CAJLGgOLGrX%2BbELWZsy9ovhBD0FdjUevwCY8pCkou_hLVPmXEGg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Stephen Augustus]

Hello wonderful k8s friends!

Just wanted to give you a final reminder that we're extracting KEPs from k/community on November 30th (this Friday)!

We've seen great traction on KEP reviews and lots of merges in the last few weeks, so let's keep up the momentum.

Remember: Merge early and iterate.

Any questions or concerns can be directed to myself (@justaugustus) or Caleb (@calebamiles) on this thread or in #sig-pm. 

-- Stephen Augustus

[Stephen Augustus]

Okay, one last reminder (for realsies this time)...

There's one more hour to review and merge the remaining open KEP PRs.

After 6 pm PT, we will begin closing out the PRs.

-- Stephen Augustus

[Stephen Augustus]

Hey y'all,

The migration has been completed. I've also gone ahead and closed the remaining open KEPs.

Before considering this complete and closing this issue, we need to:

• Tombstone all KEP files in k/community: #3002
• Prevent future KEPs from landing in k/community: kubernetes/test-infra#9435

From there, we will work to improve the KEP process documentation.

To follow along and learn what's coming next, please take a look at the KEP Implementation Tracking project board.

Thanks immensely to everyone who has been diligent in updating, reviewing, and approving KEPs during this transition!

-- Stephen

[Stephen Augustus]

Tombstones and blockade are now in place, so this is complete!

Thanks to everyone who have already begun to file KEP PRs against k/enhancements! :)

-- Stephen

[Joe Beda]

Thanks for driving this Stephen!

You received this message because you are subscribed to the Google Groups "kubernetes-sig-architecture" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-arch...@googlegroups.com.
To post to this group, send email to kubernetes-si...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-architecture/CAFQm5ySZNocvOrVjAQeYyT0nvYvwC%3DnbVqv%2Ben0ENWfALneJOw%40mail.gmail.com.