Repo for the contributor site

20 views
Skip to first unread message

Jorge Castro

unread,
Jul 17, 2018, 1:31:17 PM7/17/18
to SIG Contributor Experience
Hi everyone,

I'd like to ask for lazy concensus for SIG ContribEx to have a repo under github.com/kubernetes-sigs for the contributor site.


And here is the latest discussions and status: https://discuss.kubernetes.io/t/contributor-site/1184


Ihor Dvoretskyi

unread,
Jul 17, 2018, 1:33:43 PM7/17/18
to Jorge Castro, SIG Contributor Experience
+1 from me.

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-contribex" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-con...@googlegroups.com.
To post to this group, send email to kubernetes-s...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-contribex/CAHKJ1n_cqBGxQLEDB2AKj0mDt_QXK1dYM8%3DFH8P9X5udkCpSLA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Christoph Blecker

unread,
Jul 17, 2018, 1:52:17 PM7/17/18
to kubernetes-sig-contribex
+1

Garrett Rodrigues

unread,
Jul 17, 2018, 2:55:01 PM7/17/18
to Christoph Blecker, kubernetes-s...@googlegroups.com
+1

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-contribex" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-con...@googlegroups.com.
To post to this group, send email to kubernetes-s...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-contribex/ece2a282-474f-469f-bfeb-93ea52ce34d1%40googlegroups.com.

Paris Pittman

unread,
Jul 17, 2018, 3:25:02 PM7/17/18
to Garrett Rodrigues, Christoph Blecker, kubernetes-sig-contribex
+1

On Tue, Jul 17, 2018 at 11:54 AM, 'Garrett Rodrigues' via kubernetes-sig-contribex <kubernetes-s...@googlegroups.com> wrote:
+1

On Tue, Jul 17, 2018 at 10:52 AM Christoph Blecker <cble...@gmail.com> wrote:
+1


On Tuesday, 17 July 2018 10:31:17 UTC-7, Jorge Castro wrote:
Hi everyone,

I'd like to ask for lazy concensus for SIG ContribEx to have a repo under github.com/kubernetes-sigs for the contributor site.


And here is the latest discussions and status: https://discuss.kubernetes.io/t/contributor-site/1184


--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-contribex" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-contribex+unsub...@googlegroups.com.
To post to this group, send email to kubernetes-sig-contribex@googlegroups.com.

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

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



--

Paris Pittman

Kubernetes Community

Open Source Strategy, Google Cloud

345 Spear Street, San Francisco, 94105


Aaron Crickenberger

unread,
Jul 17, 2018, 5:54:53 PM7/17/18
to kubernetes-sig-contribex
To clarify, since nothing linked mentions the name of the repo, I'll assume you're all OK with the repo being named "contributor-site" yes?

re: lazy consensus, what's the deadline?

- aaron


On Tuesday, July 17, 2018 at 12:25:02 PM UTC-7, Paris Pittman wrote:
+1

On Tue, Jul 17, 2018 at 11:54 AM, 'Garrett Rodrigues' via kubernetes-sig-contribex <kubernetes-s...@googlegroups.com> wrote:
+1

On Tue, Jul 17, 2018 at 10:52 AM Christoph Blecker <cble...@gmail.com> wrote:
+1


On Tuesday, 17 July 2018 10:31:17 UTC-7, Jorge Castro wrote:
Hi everyone,

I'd like to ask for lazy concensus for SIG ContribEx to have a repo under github.com/kubernetes-sigs for the contributor site.


And here is the latest discussions and status: https://discuss.kubernetes.io/t/contributor-site/1184


--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-contribex" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-contribex+unsub...@googlegroups.com.
To post to this group, send email to kubernetes-s...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-contribex" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-contribex+unsub...@googlegroups.com.
To post to this group, send email to kubernetes-s...@googlegroups.com.

Carolyn Van Slyck

unread,
Jul 17, 2018, 5:57:48 PM7/17/18
to kubernetes-sig-contribex
I'm cool with "contributor-site" but will also throw out "contributor-playground" 😊

Jorge Castro

unread,
Jul 17, 2018, 8:30:52 PM7/17/18
to Aaron Crickenberger, SIG Contributor Experience
Our charter states three working days for deadlines.

On Tue, Jul 17, 2018 at 2:54 PM Aaron Crickenberger <spi...@gmail.com> wrote:
To clarify, since nothing linked mentions the name of the repo, I'll assume you're all OK with the repo being named "contributor-site" yes?

re: lazy consensus, what's the deadline?

- aaron

On Tuesday, July 17, 2018 at 12:25:02 PM UTC-7, Paris Pittman wrote:
+1

On Tue, Jul 17, 2018 at 11:54 AM, 'Garrett Rodrigues' via kubernetes-sig-contribex <kubernetes-s...@googlegroups.com> wrote:
+1

On Tue, Jul 17, 2018 at 10:52 AM Christoph Blecker <cble...@gmail.com> wrote:
+1


On Tuesday, 17 July 2018 10:31:17 UTC-7, Jorge Castro wrote:
Hi everyone,

I'd like to ask for lazy concensus for SIG ContribEx to have a repo under github.com/kubernetes-sigs for the contributor site.


And here is the latest discussions and status: https://discuss.kubernetes.io/t/contributor-site/1184


--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-contribex" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-con...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-contribex" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-con...@googlegroups.com.

To post to this group, send email to kubernetes-s...@googlegroups.com.



--

Paris Pittman

Kubernetes Community

Open Source Strategy, Google Cloud

345 Spear Street, San Francisco, 94105


--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-contribex" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-con...@googlegroups.com.

To post to this group, send email to kubernetes-s...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-contribex/b7affa89-79d0-499a-ac2f-2c34ebf80951%40googlegroups.com.

parisp...@google.com

unread,
Jul 30, 2018, 1:41:11 PM7/30/18
to kubernetes-sig-contribex
We haven't heard any objections so we are going to continue the repo creation process with steering. 


On Tuesday, July 17, 2018 at 5:30:52 PM UTC-7, Jorge Castro wrote:
Our charter states three working days for deadlines.

On Tue, Jul 17, 2018 at 2:54 PM Aaron Crickenberger <spi...@gmail.com> wrote:
To clarify, since nothing linked mentions the name of the repo, I'll assume you're all OK with the repo being named "contributor-site" yes?

re: lazy consensus, what's the deadline?

- aaron

On Tuesday, July 17, 2018 at 12:25:02 PM UTC-7, Paris Pittman wrote:
+1

On Tue, Jul 17, 2018 at 11:54 AM, 'Garrett Rodrigues' via kubernetes-sig-contribex <kubernetes-s...@googlegroups.com> wrote:
+1

On Tue, Jul 17, 2018 at 10:52 AM Christoph Blecker <cble...@gmail.com> wrote:
+1


On Tuesday, 17 July 2018 10:31:17 UTC-7, Jorge Castro wrote:
Hi everyone,

I'd like to ask for lazy concensus for SIG ContribEx to have a repo under github.com/kubernetes-sigs for the contributor site.


And here is the latest discussions and status: https://discuss.kubernetes.io/t/contributor-site/1184


--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-contribex" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-contribex+unsub...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-contribex" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-contribex+unsub...@googlegroups.com.

To post to this group, send email to kubernetes-s...@googlegroups.com.



--

Paris Pittman

Kubernetes Community

Open Source Strategy, Google Cloud

345 Spear Street, San Francisco, 94105


--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-contribex" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-contribex+unsub...@googlegroups.com.
To post to this group, send email to kubernetes-sig-contribex@googlegroups.com.

Jorge Castro

unread,
Jul 31, 2018, 9:47:23 AM7/31/18
to Paris Pittman, SIG Contributor Experience
Procedure question, the SC has asked that we update sigs.yaml so that it's clear that the repo is managed by contrib-ex. sigs.yaml lists subprojects, technically the community site is a KEP right now, not an actual subproject.

Should the community site be a subproject then? I looked at a few things in kubernetes-sigs and it seems that those are subprojects as they're sponsored by SIGs. 



On Mon, Jul 30, 2018 at 1:41 PM parispittman via kubernetes-sig-contribex <kubernetes-s...@googlegroups.com> wrote:
We haven't heard any objections so we are going to continue the repo creation process with steering. 

On Tuesday, July 17, 2018 at 5:30:52 PM UTC-7, Jorge Castro wrote:
Our charter states three working days for deadlines.

On Tue, Jul 17, 2018 at 2:54 PM Aaron Crickenberger <spi...@gmail.com> wrote:
To clarify, since nothing linked mentions the name of the repo, I'll assume you're all OK with the repo being named "contributor-site" yes?

re: lazy consensus, what's the deadline?

- aaron

On Tuesday, July 17, 2018 at 12:25:02 PM UTC-7, Paris Pittman wrote:
+1

On Tue, Jul 17, 2018 at 11:54 AM, 'Garrett Rodrigues' via kubernetes-sig-contribex <kubernetes-s...@googlegroups.com> wrote:
+1

On Tue, Jul 17, 2018 at 10:52 AM Christoph Blecker <cble...@gmail.com> wrote:
+1


On Tuesday, 17 July 2018 10:31:17 UTC-7, Jorge Castro wrote:
Hi everyone,

I'd like to ask for lazy concensus for SIG ContribEx to have a repo under github.com/kubernetes-sigs for the contributor site.


And here is the latest discussions and status: https://discuss.kubernetes.io/t/contributor-site/1184


--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-contribex" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-con...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-contribex" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-con...@googlegroups.com.

To post to this group, send email to kubernetes-s...@googlegroups.com.



--

Paris Pittman

Kubernetes Community

Open Source Strategy, Google Cloud

345 Spear Street, San Francisco, 94105


--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-contribex" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-con...@googlegroups.com.

To post to this group, send email to kubernetes-s...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-contribex" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-con...@googlegroups.com.

To post to this group, send email to kubernetes-s...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-contribex/27a708cd-ca5e-4df3-a310-3a69d00b6895%40googlegroups.com.

Jorge Castro

unread,
Jul 31, 2018, 10:08:48 AM7/31/18
to Paris Pittman, SIG Contributor Experience
On Tue, Jul 31, 2018 at 9:46 AM Jorge Castro <jo...@heptio.com> wrote:
Should the community site be a subproject then? I looked at a few things in kubernetes-sigs and it seems that those are subprojects as they're sponsored by SIGs. 


"SIG must already have identified all of their existing subprojects and code, with valid OWNERS files, in sigs.yaml" 

Perhaps we can help improve the wording here. If we have something that has to be in a repo, it's code, which must be owned by the SIG, which has to have an OWNERS file, which then has to be listed in a subproject. 

Therefore is it correct to assume that if you're asking for a new repo in kubernetes-sigs that it _has_ to be part of a subproject? The page also says "SIG repositories serve as temporary homes for SIG-sponsored experimental projects or prototypes" but it doesn't say these should also be reflected in sigs.yaml. 

So in hindsight I did this:
- Drafted KEP
- Asked and got approval for KEP in contrib-ex
- Time passes, asked for a repo
- kubernetes-sigs admins asked us for link to concensus on a repo.
- Asked and got approval for repo

Perhaps something like this:
- Draft a KEP, which includes asking for a subproject/repo as part of the proposal
- Ask and propose the entire KEP and its included repos/subprojects to contribex for approval

This would force me as a KEP author to be for explicit about resources I would need up front, and would allow the SIG to just vote on the one thing. 

Brian Grant

unread,
Aug 1, 2018, 3:22:27 PM8/1/18
to Jorge Castro, Jaice Singer DuMars, Aaron Crickenberger, Paris Pittman, kubernetes-s...@googlegroups.com
On Tue, Jul 31, 2018 at 7:08 AM Jorge Castro <jo...@heptio.com> wrote:
On Tue, Jul 31, 2018 at 9:46 AM Jorge Castro <jo...@heptio.com> wrote:
Should the community site be a subproject then? I looked at a few things in kubernetes-sigs and it seems that those are subprojects as they're sponsored by SIGs. 


"SIG must already have identified all of their existing subprojects and code, with valid OWNERS files, in sigs.yaml" 

That was bootstrapping terminology. When the concept of subprojects was formalized, no subprojects were listed there. We were using this as a forcing function to ensure existing subprojects were represented.

Perhaps we can help improve the wording here. If we have something that has to be in a repo, it's code, which must be owned by the SIG, which has to have an OWNERS file, which then has to be listed in a subproject. 

Yes, code, docs, configuration, examples, etc. 

Therefore is it correct to assume that if you're asking for a new repo in kubernetes-sigs that it _has_ to be part of a subproject?

Yes. It might the whole subproject, or part of one.
 
The page also says "SIG repositories serve as temporary homes for SIG-sponsored experimental projects or prototypes" but it doesn't say these should also be reflected in sigs.yaml. 

Yes, that should be added. 

They also might not be temporary.
 

So in hindsight I did this:
- Drafted KEP
- Asked and got approval for KEP in contrib-ex
- Time passes, asked for a repo
- kubernetes-sigs admins asked us for link to concensus on a repo.
- Asked and got approval for repo

Perhaps something like this:
- Draft a KEP, which includes asking for a subproject/repo as part of the proposal
- Ask and propose the entire KEP and its included repos/subprojects to contribex for approval

This would force me as a KEP author to be for explicit about resources I would need up front, and would allow the SIG to just vote on the one thing. 

SGTM

Reply all
Reply to author
Forward
0 new messages