cncf
/
toc
mirror of https://github.com/cncf/toc.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update dapr-graduation-due-diligence.md w minor edit from @philliphoff

This commit is contained in:
Karena Angell 2024-10-25 12:49:18 -06:00 committed by GitHub
parent 478e9377c1
commit 4d599787a2
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
projects/dapr/dapr-graduation-due-diligence.md
View File

@ -36,7 +36,7 @@ The following recommendations were provided to the project that are non-blocking
- The [Dapr component lifecycle certification](https://docs.dapr.io/operations/components/certification-lifecycle/) could use a single page for a quick lookup of component states in the lifecycle as well as a documented process to deprecate and eventually remove items that are no longer supported.
- The [Security Reporting Process](https://docs.dapr.io/operations/support/support-security-issues/) should be enhanced to include an [embargo](https://contribute.cncf.io/maintainers/security/security-guidelines/#34-embargo-policy) and private security notification process etc. In addition, we feel that tagging a release clearly as "security-fixes-only" will help users to prioritize an upgrade.
- Documentation updates to better cover Day 2 operations, more complex examples especially for people who are developers but not experts in cloud native were cited in some of the adopter interviews. Also a much clearer distinction/description of relationship with service meshes would be welcome as well (when do you use one vs another or one with another!).
- Dapr has grown by leaps and bounds beyond its Dotnet roots across Javascript, Python and Java based workloads and should continue to work towards making all the platforms be on par in terms of adoption. Other investments would be better upgrades, and simplified certificate rotation especially when users have lots of clusters to deal with (without needing an additional product/service)
- Dapr has grown by leaps and bounds beyond its .NET roots across Javascript, Python and Java based workloads and should continue to work towards making all the platforms be on par in terms of adoption. Other investments would be better upgrades, and simplified certificate rotation especially when users have lots of clusters to deal with (without needing an additional product/service)
- In terms of expanding beyond converting end users into contributors, it would be good to look at mentoring programs like GSoC, LFX etc as well as end users typically focus on what exactly they need and we need folks who look at the overall system and focus on the core as well.
### Adoption Evaluation