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

Introduce the Taxonomy Caching Service #50

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

derekhiggins
Copy link

Describes concept of a service that is intended to preserve Taxonomy knowledge documents.

Describes concept of a service that is intended to
preserve Taxonomy knowledge documents.

Signed-off-by: Derek Higgins <[email protected]>
Copy link
Member

@hickeyma hickeyma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @derekhiggins for pushing this proposal.

Reading the proposal, it would seem that your primary goal is to preserve a copy of knowledge document(s) that are referenced in a knowledge contribution to the taxonomy repository. If this is the case, then to me it is more a backup/replication service than a cache service. I think the use case is valuable regardless.

I would like to see raised in the proposal:

  • Potential solutions with pros/cons. Would syncing between the source repo and a InstructLab knowledge documents repo be a runner?
  • Data regulation issue with storing the data

@nathan-weinberg
Copy link
Member

@derekhiggins what's going on with this?

@derekhiggins
Copy link
Author

@derekhiggins what's going on with this?

Nothing currently, It was an idea that I thought at the time would be necessary, I'm no longer close enough to the instructlab project to know if it is still relevant. If it isn't we can close it, if it is I can refresh it and help address any outstanding questions but I now longer have the time to work on it that I had when I create this PR.

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

Successfully merging this pull request may close these issues.

3 participants