pyp2p

Blueprint assignments for “0.1”

  1. Series 0.1
  2. Assignments

This listing shows the assignment of work for blueprints currently associated with 0.1. The drafter is responsible for getting the specification correctly written up and approved. The approver is usually the person who would sign off on the specification.

1 → 17 of 17 specifications First • Previous • Next • Last
Priority Name Definition Delivery Assignee Drafter Approver
5 Essential Support for Endpoint Addresses 0 Approved 11 Implemented Matthieu Brucher
5 Essential Implement a basic endpoint service 0 Approved 11 Implemented Matthieu Brucher
5 Essential The Hello message starts the TCP communications 0 Approved 11 Implemented Matthieu Brucher
5 Essential Creation and parsing of message headers 0 Approved 11 Implemented Matthieu Brucher
5 Essential Create an advertisement for internal configuration 0 Approved 11 Implemented Matthieu Brucher
5 Essential Advertisement for TCP transport 0 Approved 4 Blocked Matthieu Brucher
5 Essential Implementation of the Net Peergroup 3 Drafting 4 Blocked Matthieu Brucher
5 Essential A standard peer group 3 Drafting 6 Slow progress Matthieu Brucher
5 Essential Implementation of the World Peergroup 3 Drafting 4 Blocked Matthieu Brucher
5 Essential Implement the TCP transport layer 5 New 4 Blocked Matthieu Brucher
4 High Advertisement documentation 0 Approved 12 Informational Matthieu Brucher
4 High ID documentation 0 Approved 12 Informational Matthieu Brucher
4 High Basic connection to a peer 4 Discussion 0 Unknown Matthieu Brucher
3 Medium Each advertisement must have help methods 0 Approved 11 Implemented Matthieu Brucher
3 Medium Hello World tutorial 0 Approved 4 Blocked Matthieu Brucher
2 Low Implement the UUID factory 0 Approved 11 Implemented Matthieu Brucher
2 Low Documentation on the Message implementation 3 Drafting 12 Informational
1 → 17 of 17 specifications First • Previous • Next • Last