-
-
Notifications
You must be signed in to change notification settings - Fork 327
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
[v2][Enhancement] Improve project and code documentation using LLMs #207
Comments
I would love to work on this enhancement. |
Hey @chirag4862, good to hear that! Docs are crucial for a good adoption of the OMRChecker and I hope you'll be able to help them improve. Please go through the current wiki and share which part of it you'd like to work on. |
@Udayraj123 we can improve documentation by following steps
Also I would like to work on this issue since. |
This is awesome. I'm assigning the task to you. Let me know if you need any clarification. Let's do it file by file I suppose. One more pointer is the schema/code differences in dev vs master branch. I think you can proceed by documenting the dev branch code since I will be releasing the v2 soon. |
Unassigning due to unavailability, discussed in discord |
Is your feature request related to a problem? Please describe.
LLMs like ChatGPT can help make our project documentation easier to understand and fill any missing gaps.
Describe the solution you'd like
We should leverage code understanding capabilities of the LLMs to greatly improve documentation. We can -
Describe alternatives you've considered
Developers have to refer to the provided samples to learn how to use each of the flags present in our template/evaluation schemas
Additional context
We are also planning to move it into a dedicated docs/pages folder in future. Also exploring using docs generators like Docusaurus for more elaborate project and code documentation.
Note: please share your queries and approaches on discord for quicker discussions:
The text was updated successfully, but these errors were encountered: