Comments (16)
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
from steering.
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
from steering.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
from steering.
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen
.
Mark the issue as fresh with/remove-lifecycle rotten
.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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.
from steering.
/reopen
/remove-lifecycle rotten
from steering.
@justaugustus: Reopened this issue.
In response to this:
/reopen
/remove-lifecycle rotten
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.
from steering.
Sounds like a fair amount of these things could be owned by the to-be-formed Release Engineering subproject, under SIG Release.
from steering.
@jdumars how do you think we should work through this list? I don't know where some of these things currently live or who initially created them.
My only hunch is we identify the people who created the thing and ask them what SIG it should belong to and then just start assigning SIGs to own them.
from steering.
I believe @parispittman mentioned there was a spreadsheet on this one that we can follow up on during next meeting.
from steering.
re: Blog - Katlyn will help define policy and sig-docs will own as a sub-project.
from steering.
TODO: Follow up on this issue if we should close it out and open new ones.
from steering.
ref: kubernetes/community#3524 (comment) for the blog
from steering.
- build system (make, bazel, godep, etc.)
does feel like a natural thing to try to pull under SIG Release's nascent Release Engineering subproject.
from steering.
@tpepper that was absolutely my intent in pushing for that (although godep is fuzzy and seems more like code org IMO)
from steering.
Choice of common tool and processes around healthy deps management fall in a broad build/test/release/support flow so will have multiple stakeholder SIGs and WGs imho.
from steering.
https://docs.google.com/spreadsheets/d/1Pmlj5nN_QJ3rRlc-HKOLfRdYY5qCWPMjnNPAdZZ22tg/edit#gid=0
from steering.
Related Issues (20)
- Community Annual Report Feedback HOT 14
- DMARC failing on kubernetes.io HOT 11
- checklist for publishing '21 annual reports summary HOT 3
- Iterate on charter changes around committee membership/elections HOT 6
- Steering onboarding - @mrbobbytables, @palnabarun, @BenTheElder HOT 9
- Formalize SC Visa Support Letters HOT 5
- Collect usage metrics for minikube HOT 13
- Steering member transition: @parispittman --> @cpanato HOT 5
- Document private communication channels HOT 6
- celebrating orgs with full time maintainers HOT 5
- Logo for Kueue, subproject of SIG Scheduling HOT 17
- V2 Contributor Badge HOT 27
- Election Officers for 2023 for Approval HOT 9
- Document rule around CoCC and SC HOT 2
- Update Steering members following 2023 election cycle HOT 3
- Logo for Jobset, subproject of SIG Scheduling HOT 4
- DMCA Takedown for "Ingress" docs HOT 5
- Include SIG Leads as voting CNCF Maintainers HOT 21
- Proposal: Enable gitvote for steering repo HOT 9
- Considerations around Steering and potential Conflict of Interest HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from steering.