Extracting KEPs from kubernetes/community

[Caleb Miles]

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

[LeoY]

Hi Caleb,

What to do now to new KEP authors? Should I still post to community repo and follow a currently described (in [1]) KEP number creation process (by date)?

[1] https://contributor.kubernetes.io/keps/0001-kubernetes-enhancement-proposal-process/

Regards,

Leonid

--
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.

--

Regards,
        Leo
---------------------------------------------------------
I declare that I operate by "Crocker's Rules"

[Caleb Miles]

Yes, Leonid continue to use the community repo. Do not include number information with your KEP.

[LeoY]

What is a template or method I should use to define KEP number then?

Leonid

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/8d60a315-3ca4-4190-95dc-baf2fa87930b%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Stephen Augustus]

Hey Leo,

No need to define either the KEP number in the filename, nor the the next number file, due to the current collisions we have (https://github.com/kubernetes/community/issues/2245).

Outside of that, please continue to follow the process defined in the KEP template (https://github.com/kubernetes/community/blob/master/keps/0000-kep-template.md).

Feel free to tag Caleb (@calebamiles) and myself (@justaugustus) in your PR, if you have any questions on the format.

Best,

Stephen

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/CALuHfSMVunTqrKCP1HS_uxNeq6G5UUBZN3Pn1qdtstsOfF_VSA%40mail.gmail.com.

[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

--

[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

[LeoY]

Hi Stephen,

I have a KEP #2891 for quite a lot of time unmerged despite recent "ping" sent to reviewer (@d-nishi). Is there any way for quick approve and merge?

Leonid

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/CAFQm5yQKsA1cihF7Ayfe3%3D6QXLnC4Ur%3Di-7X1r4%3DxNm8k73iew%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

[Nishi Davidson]

Leo,

Apologies. The timing for this KEP has not been ideal. Last few weeks have been hectic. Will look at your KEP today to discuss. 

Cheers,

Nishi.

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/CALuHfSPcXpKjZH_WAVQSQCNRH_-6-uDkjN9MYSHoMJuuvqNnyw%40mail.gmail.com.

[Stephen Augustus]

Merged! Thanks for pinging again on this, Leo.

Sorry for the wait.

[LeoY]

No problem. What are the next steps to to work with it? For example, there were few questions raised that i would like to follow up.

Leonid

[Stephen Augustus]

Stay tuned. After migrating the KEPs over, we will improve the repo and process documentation, add issue templates, and guidance on how to move forward.

In the meantime, I'd suggest capturing the feedback from the initial KEP submission and starting to talk that over with the relevant SIG leadership to get ideas on what the next iteration of the KEP should look like.

Also, keep in mind that with KubeCon NA looming, a lot of us will be [unavailable|slower in responding] to review requests.

-- Stephen

[LeoY]

Do I manage these discussions over this mail group, the merged PR or there is another format?

Leonid

[Stephen Augustus]

(sending k-dev to bcc, adding sig-aws)

I'll leave it to the individual SIGs to decide how to capture feedback during this transition, but mailing list will probably work fine as a first step.

[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.

[uablrek]

Hi

Where did the ipv4/ipv6 dual-stack KEP go?

I can't find it in the advised link; https://github.com/kubernetes/enhancements

It is not in the sig-network folder.

Regards,

Lars Ekman

[Stephen Augustus]

It was not merged before the 11/30 deadline and will need to be resubmitted to k/enhancements: https://github.com/kubernetes/community/pull/2254

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/596a87d0-a47d-4522-a133-fb6c85bfe150%40googlegroups.com.

[John Griffith]

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/596a87d0-a47d-4522-a133-fb6c85bfe150%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

 

Hey Lars, 

Note that the in flight for the Keps PRs were closed.  You'll have to move that one yourself, it's still in github of course though [1].  I'm assuming that's the one you're looking for.

[1]: https://github.com/kubernetes/community/pull/2254

John

[Antonio Ojea]

I've moved it, new PR is  https://github.com/kubernetes/enhancements/pull/648