| 10 | | This document is an index of all BitTorrent Enhancement Proposals (BEPs). |
| 11 | | One of the BitTorrent.org editors assigns a BEP number and updates |
| 12 | | this index appropriately. The processed is modelled after |
| 13 | | the PEP process used in the python community. Each document has a |
| 14 | | number that never changes and the history of document is maintained |
| 15 | | |
| | 10 | This document indexes all BitTorrent Enhancement Proposals (BEPs). |
| | 11 | When a new proposal is submitted, one of the BitTorrent.org editors |
| | 12 | assigns a BEP number and updates this index appropriately. The process |
| | 13 | is modelled after the PEP process used in the python community. Each |
| | 14 | document has a number that never changes and the history of document is |
| | 15 | maintained in subversion [#svn]. |
