Open hasheddan opened 3 years ago
Thanks for opening this, Dan! /priority important-soon /milestone v1.21
+1 Thanks for pointing this out dan, I certainly would like to get some some of these well established (and understood!) to start implementing them. Sometimes I get lost and I feel waste too much time reinventing the wheel.
@hasheddan when do we want to work on this issue? Seems not part of our roadmap planning but we may wire it into some side-effort.
Fun discussion w/ @wilsonehusin and some of the team on Twitter: https://twitter.com/stephenaugustus/status/1359354950019657730?s=20
Let's try and tackle this as a priority for v1.21.
/assign @puerco @wilsonehusin /unassign @hasheddan @saschagrunert /milestone v1.22
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-contributor-experience at kubernetes/community. /lifecycle stale
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-contributor-experience at kubernetes/community. /lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closing this issue.
I was thinking about this again, thanks to @helayoty! (ref: https://twitter.com/helayoty/status/1497366986841460738) /reopen
@kubernetes/release-engineering -- Thoughts here?
@justaugustus: Reopened this issue.
/unassign @wilsonehusin @puerco /assign @justaugustus @helayoty
Heba, I'm going to take an initial pass using the awesome Crossplane one @hasheddan linked: https://github.com/crossplane/crossplane/blob/master/CONTRIBUTING.md
From there, we can iterate on improvements together!
/unassign @wilsonehusin @puerco /assign @justaugustus @helayoty
Heba, I'm going to take an initial using the awesome Crossplane one @hasheddan linked: https://github.com/crossplane/crossplane/blob/master/CONTRIBUTING.md
From there, we can iterate on improvements together!
While it's so hard now to top this amazing work, I totally agree.
Heba, I'm going to take an initial pass using the awesome Crossplane one @hasheddan linked: https://github.com/crossplane/crossplane/blob/master/CONTRIBUTING.md
First pass: https://github.com/kubernetes/sig-release/pull/1862
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
@justaugustus the first pass form your last comment is merged.
Would a follow up for this be to reference the k/sig-release
contributing doc on all sig release repos in the CONTRIBUTING.md
so its clear there is sort of one central contributing guide for sig release.
Would that be basically every project in https://github.com/kubernetes/community/tree/master/sig-release#subprojects?
What would you like to be added:
As the functionality and number of packages in
krel
continues to grow, we are starting to see divergence in how new features are implemented, tested, and maintained. We should add style guidelines and quality standards so that someone is completely new to the project can make contributions that are easily reviewed and integrated without degrading quality.Why is this needed:
There are a few key areas that we have determined as important to maintain quality and consistency:
This is not an all-inclusive list, but can serve as a good starting point for a document that we can continually iterate on.
/assign @hasheddan @saschagrunert