-
Notifications
You must be signed in to change notification settings - Fork 30
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
Outline of what content should be in what GitHub repository (ultimately) #260
Comments
This is about git repositories rather than open metadata repositories? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions. |
1 similar comment
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions. |
This would likely belong in our docs where we have proposed to outline repository usage, and where we should include more process guidance. |
We have a list of repos in egeria-docs, and now have a template for new egeria repos. |
No further comments, so closing. please reopen if we need to discuss further |
To capture an overall strategic outline of what repositories we should have, and what content should be in each. Should form a "roadmap" that we gradually drive towards with separating out the core repository content + provide initial documentation for what all the repositories are, why the exist, and where to go for what.
The text was updated successfully, but these errors were encountered: