Skip to content
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

Proposal to standardize the code structure of Dapr repositories #496

Open
pdebruin opened this issue Jun 11, 2024 · 0 comments
Open

Proposal to standardize the code structure of Dapr repositories #496

pdebruin opened this issue Jun 11, 2024 · 0 comments
Assignees

Comments

@pdebruin
Copy link

@marcduiker and I discussed the experience for new users and contributors of Dapr. One of the observations is that currently the contents of repositories is not uniform, which means their experience can vary depending on where they land first. The image shows a table with Dapr repos in columns and their contents in rows below.
image

The proposal part of this issue is open for discussion :-)

For instance, dapr/dapr contains 6 default repo files and the other repos have less. Do we want all repos to have codeowners, governance, and security files?

Another example: should all repos have a folder for documentation? And should it be called docs, daprdocs, sdkdocs, etc?

@marcduiker marcduiker self-assigned this Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants