Open fsmunoz opened 1 year ago
/assign
@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
?
@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
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.
All sub-projects were contacted and interview docs were shared. Collecting answers.
Update on current content - a checkmark indicates that there are answers, not that it's ready for publishing.
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.
Conformance PR opened https://github.com/kubernetes/contributor-site/pull/431
Conformance blog published.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
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
Code Organization is out! https://www.kubernetes.dev/blog/2024/04/11/sig-architecture-code-spotlight-2024/
Updating the status (a checkmark indicates that there are answers, not that it's ready for publishing)
For API Governance it was suggested to do a voice interview so we'll work on arranging a slot.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
These are actively in progress.
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.