Blog posts format of “Meet Our Contributors”

[idealhack]

We had the initiative to have another "meet our contributors" streaming for APAC regions (#4086) and have started talking to people about it.

During the discussion back in KubeCon San Diego and several meetings of APAC planning in SIG Contributor Experience, we got the idea that some contributors might be too shy to be on a live video session, and maybe we could start with blog posts or podcasts first. This will also help us get the word out and have more active contributors from APAC regions.

We might want to focus on countries/regions per post, also it would be great to have one about contributors from or in India during the Kubernetes forums in Bengaluru and Delhi in mid-Feb.

A discussion with SIG Docs blog subproject owners is needed too, of course.

Some 5W1H questions would be like:

• who are you and what do you do?
• how did you get started with Kubernetes?
• when and why did you start contributing?
• who did you meet in the community and what did you learn?
• what were some best memories when you work in the community?
• what has happened in your career since your first contribution?
• do you encourage other people to join the community, why?

I'll update this issue to include more tasks as the planning goes.

/assign
/sig contributor-experience

[idealhack]

cc @kubernetes/sig-contributor-experience-apac-coordinators

[parispittman]

@idealhack we are building a marketing team and will have bloggers assigned so we can help! we've got some guidelines that we are bootstrapping and sig-docs folks are involved as well. #4459

notes from the meeting https://docs.google.com/document/d/1IlHAJ131akGhI5ffF4OoVW0PrsVY4C0BB8l-UyQaQVo/edit

[tao12345666333]

SGTM!

blog posts will be a good start.

[nikhita]

From April 23 APAC meeting, @idealhack to create a google doc to start collaborating on questions we can ask on the blog post.

We'll also be using the doc to draw a list of folks who would like to help out with the blog posts (per country/region) and folks we'd like to interview. This should help us with estimating timelines for scheduling the blog posts (thanks @palnabarun for the idea!)

[idealhack]

thanks for all the discussions today, the doc is here: https://docs.google.com/document/d/1zB-FOvfbnKbiWlGgInnDB06hDfLsTQuuKsXQCqc-lL0/edit

[palnabarun]

/assign

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[Pensu]

/remove-lifecycle stale

[palnabarun]

/milestone v1.20

[k8s-ci-robot]

@palnabarun: You must be a member of the kubernetes/community-milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Community Milestone Maintainers and have them propose you as an additional delegate for this responsibility.

In response to this:

/milestone v1.20

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[nikhita]

Deadlines/milestones planned (osting from last meeting's notes):

Collection of responses - October 8th
Collating responses and writing the blogs - October 22nd
Publishing the series - November 15th

[mbbroberg]

Hey @Pensu, did this happen? If so, link up the posts here and we'll close this out! Else, we can push to 1.21. Thanks!

[palnabarun]

Hi @mbbroberg 👋🏽, we are still collecting responses. We have a meeting in a few hours to discuss the progress of the blog series. On that note, I think it is better to be pushed to 1.21.

/milestone v1.21

[k8s-ci-robot]

@palnabarun: You must be a member of the kubernetes/community-milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Community Milestone Maintainers and have them propose you as an additional delegate for this responsibility.

In response to this:

Hi @mbbroberg 👋🏽, we are still collecting responses. We have a meeting in a few hours to discuss the progress of the blog series. On that note, I think it is better to be pushed to 1.21.

/milestone v1.21

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[palnabarun]

Ah! I am not a member of @kubernetes/community-milestone-maintainers. 😅

@mbbroberg Please feel free to milestone this issue to v1.21.

[mbbroberg]

You bet @palnabarun! Thanks for what you're doing 👋

[harkiratsm]

/assign

[k8s-ci-robot]

@harkiratsm: GitHub didn't allow me to assign the following users: harkiratsm.

Note that only kubernetes members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[bradmccoydev]

Hey I can help out with this, I know some people in Australia, as the list doesn't have too many people on it yet

[anubha-v-ardhan]

@bradmccoydev Absolutely! We always want more people for help!

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[Debanitrkl]

The blog post series is live
/remove-lifecycle stale

[Debanitrkl]

/close

[k8s-ci-robot]

@Debanitrkl: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.