Updated the dynabench doc to gather requirements and pick out a path forward
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 160
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Description
Assigning to @remg1997
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue only mentions updating the dynabench documentation and gathering requirements; it names no file, test, or entry point. Find the existing dynabench documentation first, then identify the requirements and agreed path that should be recorded; completion is a documented, decided way forward.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100