Guidelines for Reviewers
Devopedia Web App Intro
Rewards Program - Process
Reviewer does this
The Review Process
- Create account or use existing account
- Use same email as in recent communication
- Admin assigns article to reviewer via email
- Reviewer gives comment on the article page
- Open the chatroom by clicking on this icon:
- Author is notified for every new comment
- Author improves article and adds a comment when ready for next review
- Iterate steps 2-4
- Reviewer notifies firstname.lastname@example.org when article is ready for publishing
Comments are truncated to 5000 characters
- For long comments, split them manually into multiple comments
- Number your review points for easy cross-referencing or later discussions with author
- Select the particular version you are reviewing: usually this is the latest version at the time of review
- Select the particular section you are commenting on
- You can edit your own comments: authors and other commenters will be notified
- Comments are public: don't share sensitive information
Core Content Guidelines
Adopted from Wikipedia
Who's the Audience?
REST API to GraphQL Migration
Python Data Types
Qualities of a Good Reviewer
Reviewers should not assume that they know the topic very well. They should investigate facts before commenting.
A good article has to get many things right. A reviewer has to look at the big picture and also the fine details.
For example, a reviewer working with company X should not be biased when reviewing an article related to a product of X.
Reviewers shouldn't be too harsh on authors. Give comments in a neutral tone. Compliment authors when they get something right.
Some authors may not understand the review comments and may require further clarification.
to be considered for a review
Reviewers may at their discretion commence a review
even when the above are not met.
Client-side and server-side
- Maximum word limits
- Summary: 150
- 2000 total
- 200 per Q&A
- 100 per milestone
- Minimum word limits
- 500 to remove warning
- 1200 to publish & pay
- Other limits
- 3+ images/videos/audio
- 3+ Q&A in Discussion
- 3-15 milestones
- 3-8 tags
- 3-6 See Also items
- 3-6 Further Reading items
- 1.5+ references / 200 words
- 1.5+ citations / 100 words
- Warnings when some sub-standard references are used
- Research papers (IEEE, ACM, Elsevier, arxiv, etc.)
- Official docs, videos or tutorials
- Historical records (emails on mailing lists, etc.)
- Press releases
- Tech blogs
- News articles
- Tutorials, videos, etc.
Sources: Good and Bad
Don't prefer those with few claps, likes, shares, views, etc.
Quora or StackOverflow answers
Medium, Dev.to or HackerNoon articles
Examples of good sources
Official sites of tech companies: Intel, NVDIA, RedHat, IBM, Google, MongoDB, etc.
BBC, CNN, Washington Post, The Guardian, etc.
WIRED, The Next Web, ZDNet, CNET, DZone, Android Authority, Computer World, Forbes, etc.
Coursera, Khan Academy, lecture notes, etc.
Some sources are perceived as low quality
data-flair.training, educba.com, edureka.co, geekflare.com, geeksforgeeks.org, guru99.com, javatpoint.com, journaldev.com, simplesnippets.tech, simplilearn.com, techvidvan.com, tutorialspoint.com, w3schools.com
Some acceptable sources
Wikipedia, Analytics Vidhya, vendor blogs, etc.
Adapted from Chicago Manual of Style (Author-Date system)
What to Review
Aspects of a Review
- No factual errors
- No obvious omissions in subject matter
- Content is relevant and properly scoped
- Content is organized in a logical manner
- Text complements embedded media
- Good sources are used as references
- Citations are accurate
- Writing style follows author guidelines
- Content is written for a beginner
- No grammar or spelling errors
- Good use but not overuse of styling
- References and citations are formatted correctly
Tips for Reviewers
Good images & videos
Facts not opinions
Explained, not just defined
Not just copied
Authors use only Google Search and not Google Scholar. Their sources are ad-driven sites, blogs and Wikipedia.
Authors attempt to game the system by including arbitrary citations or images to remove warnings.
Authors don't summarize from multiple sources. They copy and paste from one or two sources, substituting words.
Content is repeated across the article. Content is poorly organized. Disconnected paragraphs: ideas don't flow.
References formatting is improper. Content has sub-headings, which is not preferred.
Study review comments in already published articles:
- If this initiative is successful, we'll introduce more automation and greater promotion of the Reviewers' Network
- Reviewers are not paid for their service right now but Devopedia trustees will look into this later this year
- Reviewers can also be volunteer authors but they can't be paid under the Rewards Program
- Author and reviewer email addresses are kept private: they can communicate only via the chatroom
A big thank you to reviewers
for your expertise and time
Guidelines for Reviewers
By Arvind Padmanabhan