Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[MetaROR] Ch3 Choosing the Target Study — author revisions

Open
#16 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
tex
Domain
documentation

Research direction

Review Chapter 3 with the MetaROR reviews (R1, R2) and internal notes, then check issue #37 and commit 60e9e79 for the revisions already handled. Done means confirming the remaining structural reorganisation is tracked under the stated scope issue rather than making changes here.

Written by the indexing model from the issue text.

Description

metaror-review

Author revisions for Chapter 3 (Choosing the Target Study) from the MetaROR reviews (R1, R2) and internal notes.

  • Move the generalizability/boundary-conditions paragraph out of the Uncertainty section — it disrupts the flow. (R1) (in #37)
  • Clarify whether "Uncertainty > Theoretical contribution" and "Uncertainty > Availability of reproductions and replications" are intended as enumerated subsections or parts of the Uncertainty discussion. (R2) (in #37)
  • Add a brief mention of "replication packages" with a forward reference to Section 5.1. (R2) (in #37)
  • Reconsider citing Soto as evidence of a field's high replicability — at most it tests a small subset of the field. (Lukas) (already removed in 60e9e79)

Handled in other issues:

  • Move Section 4.1 (Post-Publication Conversations) into Chapter 3; reconsider whether Section 3.4 (Researcher Bias) fits Chapter 3 → Structural reorganisation & scope
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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from forrtproject/replication-handbook

All issues in forrtproject/replication-handbook

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.