Three ways in
Ask, correct, or hand us something we do not have.
Each form prepares a structured email in your own mail application. Nothing is uploaded by this website, and nothing appears on the site until an editor has reviewed it.
How submissions are handled
- 01It reaches a queue, not the siteThe form prepares an email in your own mail application. Nothing reaches an editor until you choose to send it.
- 02Your mail stays under your controlThe page does not transmit or store the form. Your mail provider processes it only after you send the prepared message.
- 03Credit is opt-inIf your submission results in a change you are credited by the name you give us, unless you tell us not to.
- 04Corrections move the reviewed dateWhen a correction lands, the affected page’s reviewed date changes and the change is noted in the next Pulse issue.
Form 01
Ask PerlCoders a question
Answered in a Pulse issue or commissioned as a guide. Questions that name a concrete situation get better answers than questions that name a technology.
Form 02
Submit a correction
The most useful corrections name a page, name the claim, and cite a source. Six Timeline entries are currently marked unverified — a primary source for any of them closes it.
Form 03
Submit a historical artifact
Old scripts, screenshots, mailing-list captures, catalogue pages. Rights information is a hard requirement, not a nicety: without a rights holder and a status we record the reference and do not display the material.
Other ways to reach us
Discussion happens on GitHub, where it is public and archived. Pull requests against the content collections are welcome and are the fastest route for a well-sourced Timeline correction.
Contributor template
A correction that arrives in this shape needs no follow-up questions.
Page: /timeline/#cgi-emerges
Claim: "CGI takes shape around NCSA httpd, c. 1993"
Problem: date is approximate and unsourced
Source: <primary source URL>
Proposed: <the corrected sentence>
Credit: <name, or "none">