All issues and suggestions related to "factsheet"
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 176
- Forks
- 74
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 21
Description
We group here all suggestions and issues to be solved related to factsheet.
1. Phase level factsheets
Currently fact sheet is part of the competition. Sometimes we want separate factsheet for phases e.g. for phase 1 we ask for model name. For phase 2 we ask for model name, phase 1 score, etc.
Do you think it makes sense to move the factsheet to phases? --> Yes
2. Ordering
- #1371
Factsheet has no ordering, some users have requested the ordering (item added first should be shown first). I think we should add the ordering feature to factsheet.
3. Renaming "factsheet" to something else
The factsheet name is not suitable for the purpose it is used. Maybe we should rename it to submission meta-data or submission form or something relevant.
4. Make factsheet information available to scoring program
- #1385
5. Bugs
- #1387
- #1402
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
Review the related issues #1371 and #1385, along with bugs #1387 and #1402, before selecting a focused part of this umbrella request. Separate the phase-level factsheets, ordering, naming, scoring-program access, and bug work into scoped issues with an independently verifiable outcome.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100