A public registry of researchers volunteering to review for top software engineering journals.
Journal editors spend significant time finding qualified reviewers. This registry lets researchers proactively signal availability and expertise, making it easier for editors to find suitable reviewers for submissions.
Registered reviewers may be contacted by editors of participating journals when a submission matches their expertise.
Transparency is a core rationale: all registration requests and acceptance decisions are made publicly via pull requests. Anyone can see who applied, what was submitted, and what decision was made. This makes the registry auditable and builds trust in the process.
Three profile links are mandatory. All three must be present and valid before a registration is accepted.
What is needed: A link to your Google Scholar profile.
Why: Google Scholar provides a verifiable publication record. It lets editors assess your research output, citation impact, and topical expertise at a glance.
What is needed: A link to your LinkedIn profile.
Why: LinkedIn provides professional identity context — institutional affiliation, career history, and (optionally) identity verification. It supplements the academic record from Google Scholar.
What is needed: A link to your ORCID profile (https://orcid.org/XXXX-XXXX-XXXX-XXXX).
Why: ORCID is the standard persistent researcher identifier used by journals and publishers. It is required to unambiguously identify you across name changes and institutional moves.
Submit a pull request — do not send requests by email. All registrations are handled publicly via pull requests for transparency.
To register, open a pull request that adds exactly one new .txt file under requests/. Name the file after yourself, e.g. jane-doe.txt.
Use this exact three-line format:
GoogleScholar: https://scholar.google.com/citations?user=XXXXXXXXXXXXXXX
LinkedIn: https://www.linkedin.com/in/your-profile
ORCID: https://orcid.org/0000-0000-0000-0000
Rules:
- The file must contain exactly these three fields, in this order:
GoogleScholar,LinkedIn,ORCID. - Each field must appear exactly once, on a single line, as
Field: value. GoogleScholarmust be anhttps://scholar.google.com/citations?user=...URL.LinkedInmust be anhttps://www.linkedin.com/in/...orhttps://www.linkedin.com/pub/...URL.ORCIDmust be anhttps://orcid.org/URL with a valid 16-digit identifier inXXXX-XXXX-XXXX-XXXXformat.
An automated check runs on every pull request to validate the format. Fix any reported errors before the PR can be merged.