[k8s blog] series: SIG profiles/storytelling

[parispittman]

put a story/human touch to our special interest groups. do interviews and tell stories around:

• their formation
• key challenges
• successes
• what they look for in new / retaining contributors
• funny / cool / TIL antidotes
• shoutout individuals / profile the folks doing the work

List of community groups for reporting:

• [x] scalability (@vonguard ref: 19628)
• [x] wg-k8s-infra (@celanthe; finished)
• [ ] network (needs someone to pick up)
• [ ] node (needs someone to pick up)
• [ ] cluster life (needs someone to pick up)
• [ ] API Machinery
• [ ] Apps
• [ ] Architecture
• [ ] Auth
• [ ] Autoscaling
• [ ] CLI
• [ ] Cloud Provider
• [ ] Contributor Experience
• [ ] Docs
• [ ] Instrumentation
• [ ] Multicluster
• [ ] Release
• [ ] Scheduling
• [ ] Service Catalog
• [ ] Storage
• [ ] Testing
• [ ] UI
• [x] Usability
• [x] Windows

[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

[fejta-bot]

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

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 rotten

[vonguard]

/remove-lifecycle rotten

On Thu, Sep 5, 2019 at 11:27 AM fejta-bot notifications@github.com wrote:

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta https://github.com/fejta. /lifecycle rotten

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/kubernetes/community/issues/3654?email_source=notifications&email_token=AAAPJQAIU53YXW2F3HPP6CDQIFFSNA5CNFSM4HJEGZG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6AHXQA#issuecomment-528513984, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAPJQFZHX423MDSO7XWTRTQIFFSNANCNFSM4HJEGZGQ .

[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

[mrbobbytables]

/remove-lifecycle stale

[onlydole]

Template for questions has been started - let me know if you need edit access, or want to see anything else from these blog posts.

[celanthe]

I reached out to the k8s-infra working group today to see about getting an interview on the books sometime over the next two weeks, with a goal of publishing our next blog post sometime over the next 2-3 weeks. :)

As of today 3/20/20 I shared the template questions and added some of my own, and shared w/one of the WG leads. Progress!

[samudralavamshi54]

Reached out to Sig Cluster life cycle posted it on their slack for interview time if not shared the template doc, will follow up and update.

Thanks to @onlydole @celanthe for templating the required communication

[samudralavamshi54]

Got the responses from SIG cluster lifecycle, will work with @onlydole to format it .

[samudralavamshi54]

reached out to next group SIG node will update

[onlydole]

Thank you, @samudralavamshi54! Feel free to raise up in Slack and I'll be happy to help!

[celanthe]

An update on this for those that can't attend today's meeting 4/3/20, got all feedback from SIG chairs, and am going to draft this blog post with the goal of publishing it in mid-April sometime. :)

[mbbroberg]

SIG Windows is claimed! @kaslin has that as a new contributor to upstream marketing team.

Tips to get started:

• Jump in the Slack channel and offer to get on the phone and talk through what's going on
• "Is there something that your SIG is really looking for right now?"
  • Contributors? Users? Awareness?
  • Whatever they offer ends up as the call to action for the article
• Start writing! Wherever works for you: Markdown preferred if you're familiar (Hackmd.io or a PR), though Google Docs are always welcome as well

[hh]

/cc @hh

[celanthe]

Another update from me--The first post in my K8s-infra-wg blog series has been sent for review to @onlydole and @mbbroberg :)

[mbbroberg]

Here's the latest update on available writing. cc @celanthe @kaslin @vonguard.

• [x] scalability (@vonguard; finished)
• [x] wg-k8s-infra (@celanthe; finished)
• [x] Windows by @kaslin
• [ ] Network
• [ ] Node
• [ ] Cluster lifecycle
• [ ] API Machinery
• [ ] Apps
• [ ] Architecture
• [ ] Auth
• [ ] Autoscaling
• [ ] CLI
• [ ] Cloud Provider
• [ ] Contributor Experience
• [ ] Docs
• [ ] Instrumentation
• [ ] Multicluster
• [ ] Release
• [ ] Scheduling
• [ ] Service Catalog
• [ ] Storage
• [ ] Testing
• [ ] UI
• [x] Usability

[celanthe]

@mbbroberg I would be very interested in taking on a piece about SIG-Docs after I finish my next post in the series on the Infra WG. I can tentatively commit to this in August, I am aiming for a one-post-per-month cadence currently as my bandwidth allows.

[nyuday]

@mbbroberg I’d like to try creating a piece about SIG-Usability.

[vonguard]

@mbbroberg I'm still interested in writing about SIG Networking but I was completely unable to get anyone on the team to schedule an interview

[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

[onlydole]

/remove-lifecycle stale

[mbbroberg]

Hey all! The team at contrib comms is working to shift this issue toward a system that fits into our editorial workflow. The objective is to make a document that helps facilitate asynchronous interviews with SIGs so profiling takes a little less effort for new authors.

Here is where we're putting that together: https://docs.google.com/document/d/17zSSDRYoVySbxev2_9r1x89YzFtRH-5DUrz-Q3VAGuo/edit

It will include the thoughtful questions Taylor put together and link to the great articles already published on this topic. The goal will be to add a non-issue based tracker only once someone has a draft in progress to this project: https://github.com/orgs/kubernetes/projects/41

When we get it done, my thought is we can close this issue and keep this program (of SIG profiling) as a standard practice of our Upstream Marketing group.

Feedback or edits welcome of course! Feel free to add questions, notes, or start to structure the doc if you get there before @kaslin and I get a chance to do so.

[mbbroberg]

We have a new issue to complete the shift to an async format. Thank you to everyone who's been helped the community through these articles to date!

/close

[k8s-ci-robot]

@mbbroberg: Closing this issue.

In response to [this](https://github.com/kubernetes/community/issues/3654#issuecomment-802933103): >We have a new issue to complete the shift to an async format. Thank you to everyone who's been helped the community through these articles to date! > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.