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

Blogpost for announcing Kubernetes Upstream Community Group Annual Reports #28435

Merged
merged 1 commit into from
Jun 25, 2021
Merged

Blogpost for announcing Kubernetes Upstream Community Group Annual Reports #28435

merged 1 commit into from
Jun 25, 2021

Conversation

divya-mohan0209
Copy link
Contributor

This is a blogpost announcing Kubernetes Upstream Community Group Annual Reports.

cc: @parispittman

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jun 16, 2021
@k8s-ci-robot k8s-ci-robot added area/blog Issues or PRs related to the Kubernetes Blog subproject language/en Issues or PRs related to English language sig/docs Categorizes an issue or PR as relevant to SIG Docs. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jun 16, 2021
@netlify
Copy link

netlify bot commented Jun 16, 2021 •
edited
Loading

✔️ Deploy Preview for kubernetes-io-main-staging ready!

🔨 Explore the source changes: a7c82a6

🔍 Inspect the deploy log: https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/60d608119936b2000824ff39

😎 Browse the preview: https://deploy-preview-28435--kubernetes-io-main-staging.netlify.app

sftim
sftim reviewed Jun 16, 2021
View reviewed changes
Copy link
Contributor

@sftim sftim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

This looks broadly OK to merge. If there's time, I'd like to help with polish.

Some general feedback, plus inline comments.

PS. Markdown is easier to review if it's wrapped - that lets comments be attached to the specific text they apply to.

...t/en/blog/_posts/2021-06-18-Announcing-Kubernetes-Upstream-Community-Group-Annual-Reports.md Outdated

Given the growth and scale of the Kubernetes project, the existing reporting mechanisms were proving to be inadequate & challenging. The sheer number of community groups (37 at the time of writing this), their varied sources & types of data that needed to be incorporated while preparing such updates, & the delivery of those (how many meetings are too many meetings?) clearly were a call to action for exploring better options. There are over 300 GitHub repositories alone and we count more than just commits to these repositories as a contribution. Therefore inspired by the Apache Software Foundation’s open guide to PMC Reporting and the CNCF project Annual Reporting, the Kubernetes project is proud to announce the **Kubernetes Community Group Annual Reports for Special Interest Groups (SIGs) and Working Groups (WGs)**. In its flagship edition, the [2020 Summary report]() focuses on bettering the Kubernetes ecosystem by assessing and promoting the healthiness of the groups within the upstream community.

As of today the existing mechanisms, typically, look at (devstats)[https://k8s.devstats.cncf.io/], GitHub data, issues, to measure the healthiness of a given UG/WG/SIG/Committee. As a project spanning several diverse communities, it was essential to have something that captured the human side of things. With 50,000+ contributors, it’s easy to assume that the project has enough help and this report surfaces more information than /help-wanted and /good-first-issue for end users. This is how we sustain the project. Paraphrasing one of the Steering Committee members, [Paris Pittman](https://github.com/parispittman), “There was a requirement for tighter feedback loops - ones that involved more than just Github data and issues. Given that Kubernetes, as a project, has grown in scale & number of contributors over the years, we have outgrown the existing reporting mechanisms."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe:…

-As of today the existing mechanisms…
+Previously, the mechanisms for the Kubernetes project overall to report on groups and their activities…

?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would write “and” not “&” within speech marks. I can't explain why but it's more idiomatic.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps replace “devstats” with “CNCF devstats” as readers may never have heard of it.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@parispittman would you be happy for us to adopt this draft quote as reported speech (ie, cut out the “Paraphrasing”)?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 to @sftim's comments and suggestions above including previously.. and CNCF devstats.

@sftim
Copy link
Contributor

sftim commented Jun 16, 2021

/retitle [WIP] Blogpost for announcing Kubernetes Upstream Community Group Annual Reports

as the link to the report is not yet included.

@k8s-ci-robot k8s-ci-robot changed the title Blogpost for announcing Kubernetes Upstream Community Group Annual Re… [WIP] Blogpost for announcing Kubernetes Upstream Community Group Annual Reports Jun 16, 2021
@k8s-ci-robot k8s-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 16, 2021
mrbobbytables
mrbobbytables requested changes Jun 17, 2021
View reviewed changes
Copy link
Member

@mrbobbytables mrbobbytables left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made a few first round suggestions, but can you please please please break up the paragraphs so they're not on a single line? It makes it very difficult to leave feedback :(

@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jun 18, 2021
@divya-mohan0209
Copy link
Contributor Author

@parispittman , @mrbobbytables, & @sftim : Please can you review and see if everything looks okay. I will be squashing & rebasing the commit.

mrbobbytables
mrbobbytables previously requested changes Jun 23, 2021
View reviewed changes
Copy link
Member

@mrbobbytables mrbobbytables left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @divya-mohan0209 I made some small fixes and suggestions.

@sftim
Copy link
Contributor

sftim commented Jun 23, 2021

I'd highlight https://github.com/kubernetes/website/pull/28435/files#r657143172 as a must-fix.

@mbbroberg
Copy link
Contributor

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 25, 2021
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 78c1c9d5dedd85cdb33011f996ca563f821634d5

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 25, 2021
@divya-mohan0209
Copy link
Contributor Author

@parispittman @mbbroberg @sftim @mrbobbytables : I have made the necessary changes & am unable to squash the commits as of now since the filenames have changed. Any idea how I can rebase them to reflect only one commit? I am sorry I am bad at git :( I tried searching high and low for this.

@sftim
Copy link
Contributor

sftim commented Jun 25, 2021

Are you happy for me to use my maintainer access to squash those commits in your fork @divya-mohan0209 ?

@divya-mohan0209 @mrbobbytables
Blogpost for announcing Kubernetes Upstream Community Group Annual Re…
a7c82a6 
…ports

Co-authored-by: Tim Bannister <tim@scalefactory.com>

Co-authored-by: Bob Killen <killen.bob@gmail.com>
@divya-mohan0209
Copy link
Contributor Author

@mrbobbytables : THANK YOU for all of your help!
@sftim: Thank you so much for offering, but I was able to get this fixed :)

Please can y'all recheck & let me know if there are any further issues that need fixing or if we can merge this?

@sftim
Copy link
Contributor

sftim commented Jun 25, 2021

/hold
/approve

@divya-mohan0209 do you want to /retitle Blogpost for announcing Kubernetes Upstream Community Group Annual Reports
to mark this ready for review?
@mrbobbytables I'm going to dismiss your previous review as it is stale

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 25, 2021
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sftim

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 25, 2021
@sftim sftim dismissed mrbobbytables’s stale review June 25, 2021 17:06

Review is now stale

@divya-mohan0209
Copy link
Contributor Author

/retitle Blogpost for announcing Kubernetes Upstream Community Group Annual Reports

@k8s-ci-robot k8s-ci-robot changed the title [WIP] Blogpost for announcing Kubernetes Upstream Community Group Annual Reports Blogpost for announcing Kubernetes Upstream Community Group Annual Reports Jun 25, 2021
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 25, 2021
@divya-mohan0209
Copy link
Contributor Author

@sftim: Done, thank you!

@sftim
Copy link
Contributor

sftim commented Jun 25, 2021

after this merges: we could add https://www.cncf.io/wp-content/uploads/2020/12/CNCF-Annual-Report-2020-graphics-New.jpg to the page.
(I'd sooner see it become ready to publish than wait for it to be perfect)

@sftim
Copy link
Contributor

sftim commented Jun 25, 2021

@divya-mohan0209 you are welcome to unhold this whenever you like

@sftim
Copy link
Contributor

sftim commented Jun 25, 2021

Waiting for an LGTM

@parispittman
Copy link
Contributor

/lgtm

🚀

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 25, 2021
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 9ccdf3dae74f23855616c8ee724203b097d53a13

@divya-mohan0209
Copy link
Contributor Author

/remove hold

@mrbobbytables
Copy link
Member

/hold cancel

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 25, 2021
@k8s-ci-robot k8s-ci-robot merged commit 45d5e25 into kubernetes:main Jun 25, 2021
@sftim
Copy link
Contributor

sftim commented Jun 27, 2021

Some fixes for this, plus an image: #28653

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

@mbbroberg mbbroberg mbbroberg left review comments

@parispittman parispittman parispittman left review comments

@sftim sftim sftim left review comments

@mrbobbytables mrbobbytables mrbobbytables left review comments

@castrojo castrojo Awaiting requested review from castrojo

@kbarnard10 kbarnard10 Awaiting requested review from kbarnard10

Assignees

@mbbroberg mbbroberg

@parispittman parispittman

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/blog Issues or PRs related to the Kubernetes Blog subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. language/en Issues or PRs related to English language lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/docs Categorizes an issue or PR as relevant to SIG Docs. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
6 participants
@divya-mohan0209 @sftim @mbbroberg @k8s-ci-robot @parispittman @mrbobbytables