Add a SIG Architecture Spotlight article

[fsmunoz]

We have a "Spotlight on..." series to make the work of SIGs better known to contributors. SIG Architecture is not yet covered, and it would be great to have.

This issue is to track this idea, hopefully being closed by the PR with article.

[fsmunoz]

/assign

[k8s-ci-robot]

@fsmunoz: The label(s) /label sig/contributor-experience cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

/label sig/contributor-experience

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.

[fsmunoz]

@dims @derekwaynecarr @johnbelamaric , as discussed in Slack, creating this to make it easier for you to track, hopefully close it soon-ish :)

/assign @dims @derekwaynecarr @johnbelamaric

[fsmunoz]

Refactoring into a series of sub-project articles; depending on the amount of answers it could be 1 or multiple articles. Sub project leads contacted and some initial questions done.

[fsmunoz]

All sub-projects were contacted and interview docs were shared. Collecting answers.

[fsmunoz]

Update on current content - a checkmark indicates that there are answers, not that it's ready for publishing.

• Enhancements (@kikisdeliveryservice )
• Conformance (@Riaankl )
• Production Readiness (@wojtek-t )
• API Governance (@liggitt)
• Code organisation (@MadhavJivrajani , link to document only shared by me recently)

[fsmunoz]

Moving forward with Conformance first, hackmd version done and being reviewed with author. Production Readiness next, and by then the others have recently confirmed ETAs that will fit in the sequence.

[fsmunoz]

Conformance PR opened #431

[chris-short]

Conformance blog published.

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[fsmunoz]

This is a long-term series of which 2 were already published, and we (SIG Contribex Comms) are working in the others.

/remove-lifecycle stale

[chris-short]

Code Organization is out! https://www.kubernetes.dev/blog/2024/04/11/sig-architecture-code-spotlight-2024/

[fsmunoz]

Updating the status (a checkmark indicates that there are answers, not that it's ready for publishing)

• Enhancements (@kikisdeliveryservice )
• Conformance (@Riaankl )
• Production Readiness (@wojtek-t )
• API Governance (@liggitt)
• Code organisation (@MadhavJivrajani , link to document only shared by me recently)

For API Governance it was suggested to do a voice interview so we'll work on arranging a slot.

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[kaslin]

/remove-lifecycle stale

[kaslin]

These are actively in progress.

[kaslin]

Enhancements PR is open, API Governance interview has been conducted, needs transcribing.