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

Document List of Organizations #1407

Closed
mattfarina opened this issue Nov 15, 2017 · 34 comments
Closed

Document List of Organizations #1407

mattfarina opened this issue Nov 15, 2017 · 34 comments
Assignees
@idvoretskyi
Labels
committee/steering Denotes an issue or PR intended to be handled by the steering committee. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience.

Comments

@mattfarina
Copy link
Contributor

I was attempting to look for a list of the GitHub organizations that are part of Kubernetes and couldn't find any form list. This caught my attention because of CLA checking and formalities. From the Prow configuration I captured:

  • kubernetes
  • kubernetes-incubator
  • kubernetes-security

There are other organizations that exist including, but not limited to:

  • kubernetes-ui
  • kubernetes-client
  • kubernetes-up-and-running
  • kubernetes-incubator-retired
  • kubernetes-digitalocean-terraform
  • kubernetes-helm
  • kubernetes-contrib

And... possibly others.

Are there any others aside from the top 3 that are part of the Kubernetes project?
@k8s-github-robot k8s-github-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Nov 15, 2017
@cblecker cblecker added committee/steering Denotes an issue or PR intended to be handled by the steering committee. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. labels Nov 15, 2017
@cblecker
Copy link
Member

cc: @kubernetes/steering-committee

@k8s-github-robot k8s-github-robot removed the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Nov 15, 2017
@dankohn
Copy link
Contributor

dankohn commented Nov 15, 2017

For DevStats, we do the following.

For data starting from 2015-01-01 it is:
https://github.com/cncf/devstats/blob/master/projects.yaml
Which lists organizations: "kubernetes,kubernetes-client,kubernetes-incubator,kubernetes-helm"
Before 2015-01-01 this is a special config:
https://github.com/cncf/devstats/blob/master/kubernetes/kubernetes.sh
It lists single repos (not orgs): "GoogleCloudPlatform/kubernetes,kubernetes,kubernetes-client"
The same repos "GoogleCloudPlatform/kubernetes,kubernetes,kubernetes-client" are also included for 2015-01-01 - 2015-08-14

If we're missing some, we'll correct.

@bgrant0607
Copy link
Member

kubernetes-ui, kubernetes-up-and-running, kubernetes-digitalocean-terraform, and kubernetes-contrib are not ours.

@spiffxp
Copy link
Member

spiffxp commented Jan 2, 2018

I've been using #1527 to try and cover all repos that are part of this project. Thus far I have opened PR's for all repos in:

Based on discussion above and some educated guesses from this github user search it seems like I'm missing:

There are also a number of kubernetes-foo orgs that have no (public) repos or members, but I suspect we preemptively created, or are holding for future use. Including, but not limited to:

And let's not forget kubernetes-tacos

@spiffxp
Copy link
Member

spiffxp commented Jan 2, 2018

There are also orgs for repos/subprojects I believe to be part of kubernetes that don't have "kubernetes-" in their name, eg:

@spiffxp spiffxp mentioned this issue Jan 2, 2018
Merged
@mattfarina
Copy link
Contributor Author

mattfarina commented Jan 2, 2018 •
edited
Loading

For reference, Helm started out in the helm org. This is prior to the existence of the CNCF. Once helm became popular it was invited to merge with deployment manager in a new helm v2 that lived in the Kubernetes org. Sometimes after that the CNCF was founded and Kubernetes became a CNCF project.

The helm org comes from the history of helm.

As far as I know, everything in the helm org aside from helm-www is obselete. helm-www is used to generate the helm.sh website.

@spiffxp spiffxp mentioned this issue Jan 5, 2018
Merged
@chrislovecnm
Copy link
Contributor

@spiffxp I have not idea who owns https://github.com/kops org ... @justinsb any idea?

@bgrant0607
Copy link
Member

bgrant0607 commented Jan 9, 2018 via email

@idvoretskyi
Copy link
Member

/assign

@idvoretskyi
Copy link
Member

@mattfarina @spiffxp @bgrant0607

FYI, I'm working on collecting all the GitHub organizations, that include the word "kubernetes" in their naming (to proceed with the further actions).

To reconfirm, all the orgs below are the "official" Kubernetes ones, right?

cc @kubernetes/steering-committee @dankohn

@lukaszgryglicki
Copy link
Member

lukaszgryglicki commented Jan 9, 2018 •
edited
Loading

This returns 645 users: https://github.com/search?utf8=✓&q=kubernetes&type=Users
And this returns 105: https://github.com/search?utf8=✓&q=kubernetes-&type=Users

But please take a look, it also searches for users tags, name, description etc.
So returned list contains all users (mean users or orgs) that has "kubernetes" anywhere in their profile.
This is not the orgs list
Attached screenshots:
screen shot 2018-01-09 at 20 36 24
screen shot 2018-01-09 at 20 36 27

I think this is the real list of orgs having "kubernetes" in their name.
Google BigQuery, analyses from 2014-01-01:

select
  org.login as org,
  count(1) as cnt
from
  [githubarchive:month.201801],
  [githubarchive:year.2017],
  [githubarchive:year.2016],
  [githubarchive:year.2015],
  [githubarchive:year.2014]
where
  LOWER(org.login) like '%kubernetes%'
group by
  org
order by
  cnt desc,
  org
;

Results are here (sorted by the number of events on a given org desc):
https://docs.google.com/spreadsheets/d/1DU0qSu3_DgWjWteEwGHF2MHKS-XmSyvuIpjQKP3BTA8/edit?usp=sharing

It returns 49 orgs:


org | cnt
-- | --
kubernetes | 1428629
kubernetes-incubator | 94878
kubernetes-client | 2843
kubernetes-ui | 1559
kubernetes-helm | 1404
kubernetes-nightly | 816
kubernetes-csi | 600
kubernetes-up-and-running | 426
kubernetes-infra | 157
kubernetes-digitalocean-terraform | 145
hpcc-docker-kubernetes | 96
kubernetes-for-developers | 90
DevOps-with-Kubernetes | 81
missioncriticalkubernetes | 79
Kubernetes-Examples | 71
kubernetes-dep-experiment | 51
kubernetes-enterprise-logging-workshop | 44
kubernetes-cookbook | 37
kubernetes-incubator-retired | 33
Kubernetes-Italy | 29
kubernetes-v1-3 | 27
kubernetes-contrib | 26
kubernetes-graveyard | 24
kubernetesbook | 24
hpcc-kubernetes | 23
kubernetes-cn | 16
kubernetescn | 16
kubernetes-fa | 15
kubernetesbootcamp | 15
kubernetes-v1-1 | 12
kubernetes-spb | 10
Kubernetes-Appliances | 9
Kubernetes-Milano | 9
google-kubernetes | 9
box-kubernetes | 8
kubernetes-storage | 8
kubernetes-barcelona | 7
kubernetes-v1-4 | 6
kubernetes-cluster-automation | 5
kubernetes-retired | 5
kubernetes-matrix | 4
kubernetes-1-3-3 | 2
kubernetes-on-raspberry-pi | 2
kubernetes-sig-testing | 2
Kubernetes-yamless | 1
kubernetes-bootcamp | 1
kubernetes-raspberry | 1
kubernetes-v1-2 | 1
rich-kubernetes | 1

@idvoretskyi
Copy link
Member

idvoretskyi commented Jan 9, 2018 via email

@spiffxp
Copy link
Member

spiffxp commented Jan 9, 2018

I've heard no disagreement that these orgs are considered part of the project:

I am relatively confident this should be considered part of the project. eg: this repo bills itself as part of the the Kubernetes implementation of CSI and has commits from a member of @kubernetes/sig-storage-*

These orgs are part of the project, intended for code that is no longer maintained (goal is to replace "graveyard" with "retired")

Based on feedback from Brian, this is a private org that is part of the project:

Based on feedback from Brian, we are squatting on these orgs:

I recently created orgs corresponding to ours sigs, so we are squatting on:

@mattfarina
Copy link
Contributor Author

@spiffxp aside from the sig specific ones, shall I update #1569 with the rest? Only being conservative on the sig ones until the steering committee makes a call on a proposal for those.

@idvoretskyi
Copy link
Member

@lukaszgryglicki any idea why some organizations (eg. kubernetes-sig-foo, as @spiffxp mentioned) are not returned after your query?

@lukaszgryglicki
Copy link
Member

lukaszgryglicki commented Jan 10, 2018 •
edited
Loading

@idvoretskyi
Copy link
Member

Based on the spreadsheet by @lukaszgryglicki, I've create a spreadsheet to track the "kubernetes" orgs on GitHub - https://docs.google.com/spreadsheets/d/1MQwsWGuQvJc_RepCFgQ9HleQD2m3-_2k8utGcPaVHKY/edit#gid=289132963

@spiffxp - can you please review and update if needed?

@lukaszgryglicki
Copy link
Member

should I update DevStats config (https://github.com/cncf/devstats/blob/master/projects.yaml#L6) when this is approved, confirmed and made official, right?

@spiffxp
Copy link
Member

spiffxp commented Jan 11, 2018

I discussed this during sig-architecture meeting this morning. I would like to have sign off from @bgrant0607 on whether we have captured the list of orgs that are part of the project today, and I need help from @thockin to further collect the list of orgs we are squatting on today.

@idvoretskyi
Copy link
Member

I've shared the spreadsheet above with the @kubernetes/steering-committee. @spiffxp @thockin @bgrant0607 can you update it if you have any extra data?

@idvoretskyi
Copy link
Member

@lukaszgryglicki yes, please.

@bgrant0607
Copy link
Member

@spiffxp Do you agree the spreadsheet is what I should update and sign off on?

@bgrant0607
Copy link
Member

The list here: #1407 (comment)
looks right to me, and I updated the spreadsheet to match that (modulo formatting).

kubernetes-incubator-retired and kubernetes-graveyard should be folded into kubernetes-retired

@mattfarina
Copy link
Contributor Author

I'll update the PR based on that list.

@thockin
Copy link
Member

thockin commented Jan 20, 2018

I am squatting on a lot, but it's not obvious to me how to get a list...

@bgrant0607
Copy link
Member

@thockin

https://github.com/thockin

you should see icons for all your orgs under Organizations on the lower left. Hover over the icons

@cblecker
Copy link
Member

cblecker commented Jan 20, 2018 •
edited
Loading

@thockin @bgrant0607 They're also listed on https://github.com/settings/organizations for the logged in user, and on the https://api.github.com/user/orgs api endpoint (requires an authentication token)

@idvoretskyi
Copy link
Member

@thockin and feel free to update https://docs.google.com/spreadsheets/d/1MQwsWGuQvJc_RepCFgQ9HleQD2m3-_2k8utGcPaVHKY/edit#gid=289132963

@spiffxp
Copy link
Member

spiffxp commented Jan 22, 2018

I would like to see us PR in the list of orgs we're squatting on with instructions to contact steering@kubernetes.io, instead of using a spreadsheet as the source of truth

@mattfarina
Copy link
Contributor Author

We shouldn't have community documentation in a spreadsheet as folks can't search for it. +1 for a PR with that direction from @spiffxp

@idvoretskyi
Copy link
Member

@spiffxp I can submit a PR. Where is the best place for it?

@idvoretskyi idvoretskyi mentioned this issue Feb 7, 2018
Closed
@idvoretskyi
Copy link
Member

PTAL #1754

@idvoretskyi
Copy link
Member

@mattfarina is it effectively fixed by #1923?

@mattfarina
Copy link
Contributor Author

I think this can be considered closed now. Any additional changes can happen separately from this issue.

/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@idvoretskyi idvoretskyi

Labels
committee/steering Denotes an issue or PR intended to be handled by the steering committee. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests