-
Notifications
You must be signed in to change notification settings - Fork 437
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
Pull Request and Issue templates make generic references to "model" #1107
Comments
Alternatively, we can ask them to specify which model they used or suggest they copy/paste the output that mentions that. Because today's Granite is presumably going to be a fair bit different from next year's Granite, and the goal with the taxonomy repo is to collect skills/knowledge that are useful somewhere, and not necessarily only skills that are useful for one particular model today. Or is there an expectation that we prune skills/knowledge that are no longer useful for one particular model today? Because I can see maintenance savings in that kind of pruning, but also a chance at making some potential user with a not-all-that-smart base model sad, and balancing the maintenance cost vs. potential use seems hard. |
I agree with @wking that we should ask people which model they used (including the version). Getting that info makes it possible to implement various policies later on. |
T4R - generally we support users using one of two models in InstructLab -
merlinite
andgranite
- but various Pull Request and Issue templates just ask users about "model" inputs and outputs - we should make this clearer as to what users should actually be using for their taxonomy contributionsThe text was updated successfully, but these errors were encountered: