copied in XSTS open-sourcing files and readme from previous attempt #4965
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Looking to open-source some additional XSTS materials related to translation and the NLLB project. Might need feedback/edits for formatting / citation forming / licensing consistency with the rest of the public NLLB site. |
Mortimerp9
reviewed
Feb 6, 2023
| - XSTS protocol execution guidelines for annotators | ||
| - A written document outlining how to conduct the protocol, i.e. instructions to whomever is going to try to do an annotation. | ||
|
|
||
| [`Human_Eval_Training_Set.xlsx`](Human_Eval_Training_Set.xlsx) |
There was a problem hiding this comment.
could this just be a csv/tsv? It would make it easier for people to open it.
Mortimerp9
approved these changes
Feb 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before submitting
What does this PR do?
Fixes # (issue).
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃