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

Outline of what content should be in what GitHub repository (ultimately) #260

Closed
cmgrote opened this issue Jul 8, 2021 · 6 comments
Closed
Assignees

Comments

@cmgrote
Copy link
Member

cmgrote commented Jul 8, 2021

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.

@mandy-chessell
Copy link
Contributor

This is about git repositories rather than open metadata repositories?

@cmgrote cmgrote changed the title Outline of what content should be in what repository (ultimately) Outline of what content should be in what GitHub repository (ultimately) Jul 19, 2021
@github-actions
Copy link

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
@github-actions
Copy link

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.

@planetf1
Copy link
Member

This would likely belong in our docs where we have proposed to outline repository usage, and where we should include more process guidance.

@planetf1 planetf1 transferred this issue from odpi/egeria Jan 25, 2022
@planetf1
Copy link
Member

We have a list of repos in egeria-docs, and now have a template for new egeria repos.
Trying to be definitive on when to create repositories has been problematic, though we're erring towards smaller, simpler repos vs monorepos.
Therefore no particular action to be tracked by this issue -> suggest we close @cmgrote

@planetf1 planetf1 removed their assignment Mar 25, 2022
@planetf1
Copy link
Member

No further comments, so closing. please reopen if we need to discuss further

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

3 participants