-
Notifications
You must be signed in to change notification settings - Fork 656
Update the charter in TAG DevEx #1800
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
6d76ab2
to
00f8ac0
Compare
Any chances to review this PR @angellk @kevin-wangzefeng @kgamanji since it was requested on July 31st? |
Will prioritise the review of the charter this week |
Thanks @kgamanji |
|
||
* Provide guidance and thought leadership on improving developer workflows and experience in cloud native application development | ||
* Promote secure-by-default developer workflows by integrating security and compliance considerations into the developer experience |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to overlap with TAG security, perhaps AI compliance WG. Perhaps better to focus on collaboration with the wider ecosystem and not limit to just these 2 areas
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point, though I think it still makes sense for this TAG to focus on the developer experience angle of security. Perhaps we can rephrase it to:
"Collaborate with TAG Security to improve the developer experience of integrating security considerations into the developer workflow"
* Promote secure-by-default developer workflows by integrating security and compliance considerations into the developer experience | ||
* Collaborate with CNCF projects to surface and resolve developer experience challenges | ||
* Conduct studies, gathering feedback from end users and contributors, and providing recommendations |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would also add collaboration with the TAB for end user feedback and partnership
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestion:
In collaboration with the TAB, conduct studies, gather feedback from end users and contributors, and provide recommendations.
* Conduct studies, gathering feedback from end users and contributors, and providing recommendations | ||
* Facilitate interoperability and standardization across developer tools in the CNCF ecosystem | ||
* Act as a bridge to empower developers and project maintainers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems unfinished. What is the change you'd like to bring to developers and project maintainers?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"... to collaborate and facilitate the project adoption" maybe..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Act as a bridge to empower developers and project maintainers by improving the user experience through clear communication of feedback and input. Provide a dedicated channel for collaboration, and help facilitate broader project adoption.
* Publish guidance and reference materials for effective developer workflows | ||
* Encourage cross-project collaboration to improve consistency and interoperability of tooling | ||
* Foster collaboration around integrating security and compliance into cloud native development workflows to reduce friction and improve adoption of best practices |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ditto as above, overlap with other specific groups
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestion (not specific to security and compliance):
In collaboration with other TAGs, integrate best practices into cloud-native development workflows to reduce friction and improve adoption.
# Alignment with CNCF TOC | ||
|
||
TAG: DevEx will actively coordinate with the CNCF Technical Oversight Committee (TOC) to ensure our efforts align and complement their work. We will also engage with SIGs and CNCF project maintainers to understand how developer experience can be integrated into existing CNCF initiatives. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SIGs are Kubernetes-specific groups. Would also include otehr TAGs, supbrojetcs and initiatives
Everyone is welcome to join TAG: DevEx. Our work is public and community-driven. To participate: | ||
|
||
* Join our meetings and mailing list |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are there any links to these?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Links:
- Charter and TAG Page: https://github.com/cncf/toc/tree/main/tags/tag-developer-experience
- Mailing List: https://lists.cncf.io/g/cncf-tag-developer-experience/
- Slack: Tag TAG Developer Experience Slack
Signed-off-by: danieloh30 <[email protected]>
Signed-off-by: danieloh30 <[email protected]>
e5a58d2
to
b4faf6d
Compare
@kgamanji After our TAG leaders reviewed and discussed your comments, the PR has been updated. Please review the revision and feel free to address any outstanding conversations. @angellk @kevin-wangzefeng It would be great if you could add any comments or feedback. |
No description provided.