Jargon related to User Roles

From DPWiki
Jump to: navigation, search
DP Official Documentation - General

Organizations and specialized activities develop their own sets of specialized terminology, or jargon, and DP is no exception to that. Accordingly, we have developed some FAQ-like Jargon Guides you can access in order to learn some of our lingo.

The LONG DP Jargon Guide, and the Jargon Guides related to The Guidelines, User Roles, and Workflow contain acronyms and terms you will likely encounter as a new volunteer at DP.

Other Jargon Guides contain terms that are a bit more specialized. The Group Activities Jargon Guide will become especially relevant to you if you start using Jabber. The remaining Jargon Guides shown in the Jargon Navigator box relate to the specific activities mentioned in their titles.

If you come across an acronym or term that isn't mentioned in one of these Jargon Guides, please ask about it in one of the DP forums.

Detailed suggestions on how best to add and edit Jargon-related information can be found at Help:Jargon.

Jargon Guides

CP or CPer

Content Providing/Provision (CP) is the process of providing the page images used in proofreading, either by scanning a book or harvesting the images from an online source.

Also a person who does such work (Content Provider, or CPer).

If you are interested in becoming a CPer, visit Access Requirements.

You can automate some content providing tasks by using guiprep and guiguts. For more information you can see the Content Providing FAQ.

Missing Page Finder

The Missing Page Finders are volunteers who love to spend a lot of time in libraries and don't mind searching for the exact edition of obscure tomes, photographing or scanning the missing pages, and sending the files on to those who need to complete a project. In many ways, these hard workers are the unsung heroes of DP.

See also Missing Page Finders and Missing pages.


The Project Manager (PM) is the person in charge of a project and its progress through the rounds. The ultimate goal of the PM is to help the project be as consistently proofed and formatted as possible for the PPer. One way the PM (usually) does this is by writing Project Comments.

Different PMs have different styles. Some provide a handful of books that they pre-process themselves, then during proofreading monitor the project threads closely, and finally post-process the project themselves; others provide large quantities of books and rely on others to PP them. Other PMs fall somewhere between, perhaps closely following some books, while only glancing in on others, as questions are asked in the project thread.

If you are interested in becoming a PM, visit Access Requirements. If you are a new PM, see the Project Managing FAQ.


Proofer is a commonly used, relatively informal, term for proofreader.

See also proofing, and compare to foofer.


Foofer is an informal term for formatter.

See also formatting, and compare to proofer.


There are various kinds of mentoring that go on at DP. There is mentoring for new Project Managers, mentoring for new Post-Processors, and mentoring for Post-Processors who are new to HTML. There is mentoring done for P1ers and F1ers via the DP-feedback mechanism. There is also a team of volunteers who provide Formatting Mentoring who will work with F1ers who would prefer one-to-one assistance.

The most visible form of mentoring at DP, however, is the mentoring of new proofreading volunteers.

The mentoring of new volunteers comes in two forms.

  • Experienced proofreaders proof Proof-only Mentoring projects, which were originally Newcomers Only projects proofed by new volunteers in P1. The diffs created serve as the primary feedback mechanism for newcomers who prefer this less-detailed, serve-yourself, type of mentoring approach.
  • Experienced proofers with "mentor status" proof mentors only projects in P2, in order to send detailed feedback via Private Message (PM) to the new volunteers who proofed the beginners only projects in P1. The PMs serve as the primary feedback mechanism for beginners who prefer this more-detailed, more full-service, type of mentoring approach.

PP or PPer

Post-Processing (PP) is the process of formatting and reassembling the pages of a project after it has completed the rounds of proofing and formatting. (Also called Post-Proofing.)

Also, a person who does such work (also Post-Proofer, or PPer).

If you are interested in becoming a PPer, visit Access requirements.

See also the Post-Processing FAQ, and Hands-on PPer. For more PPing resources in the DP wiki, see Post-Processing Advice. For LaTeX projects, see LaTeX postprocessing guidelines.

PPV or PPVer

Post-Processing Verification (PPV) is the process of final checking a post-processed text, done by a very experienced PPer. This is the last stage a project goes through at DP before being sent to the PG Whitewashers.

Also, a person who does such work (also PPVer).

Related Resources

SR, SRer, or smoothie

The goal of Smooth Reading (SR) is to read a post-processed text attentively, as for pleasure, with just a little more attention than usual to punctuation, etc. This is not full-scale proofreading, and comparison with the project's scans is not needed. Just read it as your normal, sensitized-to-proofing-errors self, and report any problem that disrupts the sense or the flow of the e-text.

Smooth Reading: also referred to as Smooth-Reading, SRing, smooth-reading, smooth reading, Smoothreading, smoothying, and many other variations.

Smooth Reader: person who Smooth Reads e-texts; also affectionately known as an SRer, smooth-reader, smoothier, smoothyer, smoothie, smoothy, etc.

For more information, see the Smooth Reading FAQ and visit the Smooth Reading Pool.


Project Facilitator (PF) is an administrative position at Distributed Proofreaders, similar to that of Site Administrator. A Project Facilitator's primary function is to help Project Managers, but only when the PMs need it. A PF can do anything a PM can do, with the difference that the PF can do it for all projects.

Visit DP Administrators to see a list of current Project Facilitators, and see this thread for more information.


A developer is a Distributed Proofreaders (DP) volunteer that participates in the development and maintenance of DP's software.


A moderator (also forum moderator) is a Distributed Proofreaders volunteer who oversees the day-to-day operation of the DP Forum.

Squirrel and squirrels

The tireless technical support crew who help keep DP running (by running and running and running...) are usually referred to as the squirrels. Some squirrels have lycra suits, which enable them to perform heroic feats with the DP database. Squirrel.gif
See some history here, and in the link you will find there.

In February 2007 the term "Squirrel" became a formal title, including all System Administrators, db-req and some dphelp folks, and Forum Administrators. See DP Administrators for the current members in those positions.


Jargon Guides

Site Administrators (SA), aka "The Powers That Be" (TPTB), have the ultimate say-so on what happens at DP and on its Website, including the DP Forums and this DP Wiki. Note that because we are a community project, SAs rarely speak from "on high" in their official capacity.

For a little bit of background on the PTB moniker, see this post, especially starting about half-way through it.

Visit DP Administrators to see a list of current and former Site Administrators.

To comment or request edits to this page, please contact lhamilton or hdmtrad.

Return to DP Official Documentation Menu