What: updates and tweaks to the principles #789
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TheFoxAtWork
changed the title
dzolotusky
approved these changes
Feb 24, 2022
rochaporto
reviewed
Feb 25, 2022
|
cc @dims |
dims
reviewed
Mar 22, 2022
PRINCIPLES.md
Outdated
| @@ -15,22 +16,32 @@ Approved by GB on: Dec 5, 2017 | |||
|
|
|||
| ## TOC Operating Principles | |||
|
|
|||
| Now that CNCF has been active for over a year we want to start writing down what we have learned. Future TOCs can still make changes, but there will at least be documented precedent. | |||
| As part of our continued community engagement and iterations on the work done, the following list of principles serve to provide an understanding of how the TOC intends to work with projects, effectively the guiding star the the TOC in their work. It also provides insight into what the TOC is looking for continuity and evolution across each seated TOC. Since the CNCF's inception we have endevoured to capture the lessons learned and interate on these principles to service the foundation, the community, and the projects. | |||
There was a problem hiding this comment.
As part of our continued community engagement, the following list of principles serve to provide an understanding of how the TOC intends to work with projects, effectively serving as the guiding star for the TOC. It also provides insight into what the TOC is looking for in terms of continuity and evolution over time. Since the CNCF's inception we have endeavoured to capture the lessons learned and iterate on these principles to serve the foundation, the community, and the projects.
dims
reviewed
Mar 22, 2022
PRINCIPLES.md
Outdated
| As part of our continued community engagement and iterations on the work done, the following list of principles serve to provide an understanding of how the TOC intends to work with projects, effectively the guiding star the the TOC in their work. It also provides insight into what the TOC is looking for continuity and evolution across each seated TOC. Since the CNCF's inception we have endevoured to capture the lessons learned and interate on these principles to service the foundation, the community, and the projects. | ||
|
|
||
| 1. We are project-centric. | ||
| 1. We exercise minimal viable governance to enable community driven success. |
dims
reviewed
Mar 22, 2022
PRINCIPLES.md
Outdated
|
|
||
| 1. We are project-centric. | ||
| 1. We exercise minimal viable governance to enable community driven success. | ||
| 1. Do no harm by enabling robust, well engineered projects and supportive processed to be leveraged for greatest adoption likelihood. |
There was a problem hiding this comment.
supportive processed->support processesbe leveraged for greatest adoption likelihood->to increase the likelihood of success
dims
reviewed
Mar 22, 2022
PRINCIPLES.md
Outdated
| 1. Do no harm by enabling robust, well engineered projects and supportive processed to be leveraged for greatest adoption likelihood. | ||
| 1. No kingmakers. Similar or competitive projects are not excluded for reasons of overlap. | ||
| 1. No single stack. Encourage interoperability for the emergence of a variety of stacks and patterns to serve the community and adopters. | ||
| 1. Promote interfaces over standards for real world use. |
There was a problem hiding this comment.
interfaces -> interfaces and defacto implementations ?
dims
reviewed
Mar 22, 2022
PRINCIPLES.md
Outdated
| 1. No kingmakers. Similar or competitive projects are not excluded for reasons of overlap. | ||
| 1. No single stack. Encourage interoperability for the emergence of a variety of stacks and patterns to serve the community and adopters. | ||
| 1. Promote interfaces over standards for real world use. | ||
| 1. Users don't need to look beyond the CNCF for cloud native app tooling. |
There was a problem hiding this comment.
don't need is too strong. could we dilute it a bit?
dims
reviewed
Mar 22, 2022
PRINCIPLES.md
Outdated
| 1. No single stack. Encourage interoperability for the emergence of a variety of stacks and patterns to serve the community and adopters. | ||
| 1. Promote interfaces over standards for real world use. | ||
| 1. Users don't need to look beyond the CNCF for cloud native app tooling. | ||
| 1. We help high-quality high-velocity cloud native open source projects which are the main driver of customer adoption and success. |
There was a problem hiding this comment.
not sure about this as i don't understand. Can we drop this?
dims
reviewed
Mar 22, 2022
PRINCIPLES.md
Outdated
|
|
||
| Via the “no kingmakers” principle and “what is a project”, the CNCF may support several projects which show how a ‘stack’ is a solution to certain use cases. For example, some stacks might use a container orchestrator. Other stacks might show how to integrate monitoring with other “observability” technologies, for cloud native apps regardless of their orchestration model. | ||
| The TOC picks projects with a real chance of achieving widespread use, and it does not pick a winner in each category. Via the “no kingmakers” principle and “what is a project”, the CNCF may support several projects which show how a ‘stack’ is a solution to certain use cases. For example, some stacks might use a container orchestrator. Other stacks might show how to integrate monitoring with other “observability” technologies, for cloud native apps regardless of their orchestration model. |
Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
This PR contains a proposal for Backstage to the CNCF Incubation stage. Description: Backstage is an open platform for building developer portals. Open sourced in March 2020 and donated as a CNCF Sandbox project in September 2020. An open platform for building developer portals. Powered by a centralised software catalog, enabling product teams to ship high-quality code quickly — without compromising autonomy. Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Signed-off-by: Aditya Sirish <aditya@saky.in> Co-authored-by: Santiago Torres-Arias <santiago@nyu.edu> Co-authored-by: Christian Rebischke <chris@shibumi.dev> Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Signed-off-by: David Korczynski <david@adalogics.com> Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Why: * language and phrasing made them dated when they are still relevant * annual review This change addresses the need by: * adjusting terminology, structure, etc. * providing consistence phraseology around the principles so they are of uniform voice. Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
This change addresses the need by: * @dzolotusky comments fully resolved Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Why: * language and phrasing made them dated when they are still relevant * annual review This change addresses the need by: * adjusting terminology, structure, etc. * providing consistence phraseology around the principles so they are of uniform voice.
This change addresses the need by: * @dzolotusky comments fully resolved
* Add Katie Gamanji to TOC, thanks Alena Signed-off-by: Davanum Srinivas <davanum@gmail.com> * Sort by term starting date Signed-off-by: Davanum Srinivas <davanum@gmail.com> Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Signed-off-by: Davanum Srinivas <davanum@gmail.com> Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
…udEvents and Dapr at the moment. (cncf#811) Signed-off-by: JieDing <dingjwilliams@gmail.com> Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Signed-off-by: Chip Zoller <chipzoller@gmail.com> Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
* Update README.md * Update EMERITUS.md Co-authored-by: Chris Aniszczyk <caniszczyk@gmail.com> Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Signed-off-by: Johannes <johannes.braeuer@dynatrace.com> Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Signed-off-by: jetzlstorfer <juergen.etzlstorfer@dynatrace.com> Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Signed-off-by: Johannes <johannes.braeuer@dynatrace.com> Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Signed-off-by: Johannes <johannes.braeuer@dynatrace.com> Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Signed-off-by: jetzlstorfer <juergen.etzlstorfer@dynatrace.com> Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Signed-off-by: jetzlstorfer <juergen.etzlstorfer@dynatrace.com> Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Signed-off-by: jetzlstorfer <juergen.etzlstorfer@dynatrace.com> Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Signed-off-by: jetzlstorfer <juergen.etzlstorfer@dynatrace.com> Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Signed-off-by: jetzlstorfer <juergen.etzlstorfer@dynatrace.com> Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Signed-off-by: jetzlstorfer <juergen.etzlstorfer@dynatrace.com> Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Why: * The existing information we provide is not clear and does not capture the variety and nuances necessary to ascertain project maturity from adoption. This change addresses the need by: * Updating the FAQs * correcting references to that area of the FAQs * clarifying in the proposal process around adopters and how the TOC interacts with them * updating all other references to 'users' and 'end users' to coincide with the clarification in FAQs. * adding links to the appropriate FAQ section about adopters to existing files. Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
…ting out the clarity need!) Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Co-authored-by: Richard Hartmann <RichiH@users.noreply.github.com> Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
…tions and clarification. Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
TheFoxAtWork
force-pushed
the
413-principles-update
branch
from
e95a4c5
to
6104ad4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why: #413
This change addresses the need by: