You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I feel like one primary aim of this project is to receive high quality evals.
Instead of the docs folder, I propose that the top-level evals/README.md should include directions on how to contribute a simple eval.
I don't propose the entirety of evals/docs/build-eval.md should be moved into evals/README.md; however, I propose something minimal and simple be included.
I recognize it isn't a big effort to go to evals/docs/build-eval.md but I feel like if eval contribution is a primary aim, directions should be at the forefront (versus the periphery).
The text was updated successfully, but these errors were encountered:
I feel like one primary aim of this project is to receive high quality evals.
Instead of the
docs
folder, I propose that the top-levelevals/README.md
should include directions on how to contribute a simple eval.I don't propose the entirety of
evals/docs/build-eval.md
should be moved intoevals/README.md
; however, I propose something minimal and simple be included.I recognize it isn't a big effort to go to
evals/docs/build-eval.md
but I feel like if eval contribution is a primary aim, directions should be at the forefront (versus the periphery).The text was updated successfully, but these errors were encountered: