On this wiki, you will find developer documentation for:

• the p≡p Engine,
• the selection of Adapters developed by the p≡p Foundation, and
• Enigmail/p≡p, the p≡p-enabled Thunderbird plugin

Each project has it’s dedicated pages organized in a folder. Go to All pages to see them all.

Information about p≡p, not specifically about development, can be found in ref - a general reference base.

Engine

• Index
• How to File Bugs and Feature Requests: Keep Your Engine Monkeys Happy
• Engine and Adapter Release Process
• Email Messages, MIME, and Message 2.0 (under construction)
• Testing Sync
• Echo Protocol
• Media keys
• Engine Breakfast Logs
• Uncategorised Development Themes
  • Building the pEp engine (plus enough software to play with it) on debian; the Adapter Build Instructions linked below also deal with some of the same issues and contain relevant information.
  • Managing Expectations for Message Attachments
  • Playing with the Management Database
  • Extracting keys from the Key Database
• p≡p from an application developer’s perspective
• list of projects using the Engine

Adapters

• Change Management
• Adapter Build Instructions (pEpEngine 2.1.x)
  
• Adapter Build Instructions (pEpEngine 3.x WIP)
• Adapter Development

Adapter libraries

• p≡p For Java - pEpJNIAdapter
• p≡p For Python - pEpPythonAdapter
• p≡p JSON Server - pEpJSONServerAdapter
• p≡p COM Server - pEpCOMServerAdapter
• p≡p for Objective-C/Swift - pEpOBJCAdapter

Desktop adapters

• p≡p macOS Desktop Adapter
• p≡p Windows Desktop Adapter

CID / Internal Deployment

• Index

p≡p MIME

• libpEpMIME

Enigmail p≡p

• Index

p≡p for Geary Mailclient

• Geary

p≡p on a Mainframe

• Mainframe

p≡p on windows

• Character encoding on windows

p≡p for Thunderbird

• Thunderbird which is not obvious to find without knowing that the page exists

Code generation

• Minutes and Material