forrt.org · forrtproject@gmail.com
FORRT is a global, volunteer-run initiative working to advance open and reproducible research practices in higher education. This page is a work-in-progress map of the GitHub organisation — what lives here, who maintains what, and how things are named. PRs welcome.
| Team | Remit |
|---|---|
| Operations Committee | Cross-cutting coordination across FORRT projects |
| FORRT Engineering | Development and infrastructure across FORRT tools |
| Team Replications | Replication-focused projects (FReD, FLoRA, RJF, …) |
| Team Website | forrt.org maintenance |
| Team AWoP | Academic Wheel of Privilege |
Most projects also have their own informal working groups that aren't modelled as GitHub teams. If you want to get involved, the forrt.org get-involved page is the best starting point.
Repos are loosely grouped by project family. Names below are not exhaustive — see the full repository list.
A curated database of replication attempts plus the tooling around it.
fred— the R packagefred-data— the underlying dataset and ingest pipelinefred-apps— JS apps using FReD / FLoRAfred-explorer— Shiny explorerfred-litsearch— reproducible literature search pipelinefred-repl-extractor— extract replication metadata from articlesfred-preprint-processor— extract references and replications from preprints
A complementary, broader library of replication attempts and tooling that surfaces it in researchers' workflows.
flora-extractor— extraction pipelineflora-explorer— dashboardflora-replication-atlas— landing pages per original DOIflora-zotero— Zotero plugin (privacy-first local matching)flora-chromium— browser extensionflora-preprint-notifier— notify authors of potentially-missing replicationsflora-preprint-notifier-analysis— trial analysisflora-pubpeer— PubPeer integrationplugin-notification-dummy— test page for the plugin install-banner conditional-hide logic
replicatethis— moderated nomination of findings to replicaterjf— Replication Journal Federationjournalranking— rank journals by replication ratemarco— Making Replications Countreplication-handbook— Quarto booklove-replications-week— annual outreach event
forrtproject.github.io— main websitewebpage-staging— staging renders for site PRslighthouse,lighthouse-v1— Lighthouse newsletter / portalforrt-templates— branded templates for FORRT outputscv— source for the FORRT CV; published PDF is auto-pushed to the site
open-research-courseopen-social-psychologyhandbooktransform-to-open-science-bookbest-practices-psychologyglossary-researchre-searchterms— explore variation in open-science terminology
map-community— FORRT community mapmapping-open-science-organizations
tops-archive— Transform to Open Science project, snapshot March 2025fredAnnotator— superseded annotation tool (archived)
All repos use kebab-case (lowercase, hyphen-separated). Project-family prefixes group related work:
| Prefix | Used for |
|---|---|
fred-* |
FReD (FORRT Replication Database) ecosystem |
flora-* |
FLoRA (Library of Replication Attempts) ecosystem |
forrt-* |
Org-level shared assets (templates etc.) |
*-archive |
Snapshotted, no-longer-active projects |
Two exceptions keep non-kebab names because GitHub requires them:
.github (this repo — must be
exactly .github to act as the org profile) and
forrtproject.github.io
(must match the org name to serve at that path).
Brand names in prose and READMEs use mixed case (FReD, FLoRA); the
repository names are always lowercase.
When starting a new repo, prefer:
- The relevant project-family prefix if one applies (
fred-,flora-, …). - kebab-case otherwise.
- A short description and topic tags so it surfaces in the repo list.
- New to FORRT? Start at forrt.org/getinvolved.
- Found something out of date on this page? Open a PR against
forrtproject/.github— this README is rendered on the org profile. - For project-specific contributions, see the README of the relevant repo.