Contribute
The blueprint is made by the people who use it. Bring what you know in the form you have it, and it is reviewed, labelled and placed against the element it supports.
Join the community first
Joining as a contributor is the first step into everything else. It is light: a name or chosen name, a way to be reached that is not published unless you choose, and the domains you care about. There is no fee, no application and no test. Reading, searching, the Guide and downloads never need an account.
Join at community.publicprotocol.org
From there: credit by name from the first accepted contribution, an invitation to review after sustained good work, a vote once the contribution threshold is met, and standing for the board after six months as a voter. How the board works
What you can contribute
| What | What happens to it |
|---|---|
| A document | Text, a word-processor document or a PDF. Converted to a page where the licence allows, with the original kept as a download. |
| A file | A spreadsheet, a drawing, a CAD or circuit-board file, an image. Kept with its hash; designs are held with their source files and a bill of materials. |
| A link | An address of something useful that others keep. It becomes a library entry that describes it and links to it; nothing is copied. |
| A repository | A source repository. Described as an entry, with its licence and the activity seen on the date checked. |
| Evidence from a project | Something built or measured in a real place. It becomes a verification record on the entries and elements concerned. |
| A project | A place or pilot working to the blueprint, or a system built on it. Reviewed by a panel the board names, then presented on the projects site. |
| A partner request | An organisation asking to join Public Protocol as a partner. Reviewed by the board. |
| A correction | Something wrong on an entry or a page. Every entry has a link for it. |
A single item
- Fill in the form: what it is, where it came from, who made it, its licence and where that is stated, any interest you have in it, and the domain and stage if you know them.
- The form checks what you entered and produces a submission file, with its provenance. Send that file, and the document or file itself, to contact@praecise.com.
- A draft entry is made with everything you supplied. The rest is assessed in review.
- A reviewer checks, in this order: that it is lawful to list or host; that it is what it says; its maturity; its safety level and hazards; duplicates; the summary; and which elements it supports, supersedes or challenges.
- The outcome is one of four: published with its labels, returned with questions, held for a qualified reviewer, or declined with the reason sent to you.
A bulk drop
- Send a folder, an archive, a spreadsheet of links or a repository address to contact@praecise.com, with one manifest: for each item its title, source, author and licence, and anything else known. A drop without a manifest is accepted, and the manifest is drafted from the files for you to confirm.
- Each file is stored with its hash and one draft is made per item. Sets that belong together, such as a design's files, become one entry. Duplicates are found by hash and by address.
- You receive a report: counts by type, items with no licence, items that look hazardous, items that could not be read.
- The drafts enter the review queue as a batch, accepted item by item or by rule. Items with no clear licence are listed back to you.
What happens next
Every submission has one of these states, and every published entry shows its state, who reviewed it, in what capacity and when.
- ListedListed by Public Protocol's editors at the founding of the catalogue: the source was opened, described in our own words and labelled on the date shown. It goes to the governance board's reviewers with everything else.
- SubmittedReceived and waiting for triage. Only its title, type and date are shown.
- In reviewWith reviewers. The level it is at and the date a decision is due are shown.
- ReviewedApproved. The entry names who reviewed it, in what capacity and when, and links to the decision.
- Proven in useReviewed, and followed in a real place or system, with the evidence.
Nothing under review appears in the blueprint, the library, search, the Guide or the graph. The review queue shows what is with reviewers and when a decision is due.
Terms, in short
You state the licence of what you bring. For your own work, the proposed defaults are CC BY-SA 4.0 for text, CERN-OHL-S-2.0 for designs and AGPL-3.0 for software. Licences in full. You declare any interest: that you make it, sell it or are paid by its maker. Nobody reviews their own or their employer's entry.
Material with no clear licence is not published. Closed formats are accepted alongside an open export.