List of changes that need to be reviewed by all contributors
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- tex
- Domain
- documentation
Research direction
The issue body names no files, tests, or concrete changes. Review the repository's Quarto book and the issue history with contributors to define which changes belong in the list and what completion means before implementation.
Written by the indexing model from the issue text.
Description
This issue has no description.
- Dominant language
- TeX
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from forrtproject/replication-handbook
-
Remove multiverse from table 4.1, instead briefly add in executing reproductions with referencePossibly taken @LukasWallrich claimed this 53 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Remove how to cite from landing page - duplicates footerPossibly taken @LukasWallrich claimed this 53 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
Broken citationsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
forrtproject/replication-handbook#3 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
forrtproject/replication-handbook#58 · 1 comment ·
All issues in forrtproject/replication-handbook
Similar issues
-
triage-needed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
MicrosoftDocs/edge-developer#3970 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
crazy-goat/rabbit-stream#753 ·
Maintainers usually reply within 1 day
-
agent-research-recommend agent-review-finding chore
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
jordansmall/spindrift#4821 · 1 comment ·
Maintainers usually reply within 1 day
-
[workshop-sim] Repair: Add a fallback sample .lock.yml to the Agentic Workflows Intro Activity 1Openfeedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
githubnext/gh-aw-workshop#4328 ·
Maintainers usually reply within 1 day