Last checked against sources:

Contribute

pap.md is only as good as its sources. If you spot something wrong, find coverage we missed, or see the PAP spec go live before we do, tell us on GitHub. Every accepted change gets logged on the status page.

The site's code isn't public, but the content conversation is. It all happens ingithub.com/fabricioctelles/pap.md, which holds issue templates and plain Markdown copies of the fact pages (timeline, partners, FAQ, press, spec status) that you can edit in a pull request.

Report a correction

Found a wrong date, a misattributed quote or a claim with no source? That's the most useful thing you can send.

  1. Open a correction issue.
  2. Title it [Correction] Page: what's wrong, for example [Correction] Partners: NiCE quote.
  3. Include the page URL, the text as it stands, what it should say, and a link to the source that proves it.

No source, no change. That rule applies to us too.

Add a source or news

New partner, new interview, a company saying it will or won't support PAP. Open asource issue titled [Source] Outlet: headlinewith the link, the publish date and one line on what it adds. Rewrites of Sierra's post don't make the cut; first-hand statements and real analysis do.

Spotted the spec?

The v0.1 specification is the thing everyone's waiting for. If you see it published, open aspec alert titled [Spec] v0.1 publishedwith the link. We'll verify it, update the tracker and start the annotated read.

Suggest a page or comparison

Want PAP compared with another protocol, or a question answered in the FAQ? Open acontent idea titled [Idea] … and say who the page would help.

Edit the content directly

Comfortable with pull requests? Go straight to the files.

  1. Fork fabricioctelles/pap.md.
  2. Edit the relevant file in content/. Keep tables as tables, and put the source link next to anything you add.
  3. Open a pull request. The template asks for your sources and whether you're affiliated with anyone involved in PAP.

We port accepted changes into the site by hand, so your PR may be closed with a link to the commit on pap.md rather than merged as is.

What gets accepted

  • Sourced facts. Link a primary source when there is one: Sierra, Meta, a partner's own post, the spec.
  • No guesses. No endpoints, scope names, licenses or dates that haven't been published.
  • Opinions labelled. Analysis is welcome when it says it's analysis.
  • No promotion. Product pitches, affiliate links and "we support PAP" claims without a public statement get closed.
  • Disclose ties. If you work for Sierra, Meta, a partner or a competing protocol, say so. It doesn't disqualify you; hiding it does.

How review works

A maintainer reads every issue and pull request, checks the source and replies, usually within a few days. Accepted changes go live on the site, get a line in thechangelog and the RSS feed, and we're happy to credit you there by your GitHub handle if you'd like.

By contributing, you agree that your text can be published on pap.md under the license stated in the repository. pap.md is independent and not affiliated with Sierra, Meta or any PAP partner.

pap.md is independent and not affiliated with Sierra, Meta or any PAP partner. Facts here come from the sources listed on each page.