bitcoin-dev

Adding New BIP Editors

Adding New BIP Editors

Posted on: May 13, 2024 18:33 UTC

Niklas Goegge recently provided an update on the collaborative efforts to revise the Bitcoin Improvement Proposal (BIP) process.

Acknowledging contributions from community discussions and open pull requests in the BIPs repository, he outlined a series of suggestions aimed at enhancing the proposal process. Niklas has begun drafting a new proposal to succeed BIP-2, with the goal of incorporating feedback from these discussions. He is also seeking one or two co-authors to collaborate on this project and welcomes further comments for consideration.

One key area of focus is the role of editors in the BIP process. The consensus suggests minimizing editorial judgment calls, emphasizing formal criteria and editorial qualities over technical evaluation, which should be left to the audience. There's also a debate regarding the classification of BIPs into Standards Track and Informational types, particularly how deviations affecting compatibility dictate classification.

Several points were raised concerning BIP statuses, including the current excessive number of statuses and the ambiguity surrounding their meanings and transition criteria. Recommendations include simplifying statuses to DRAFT, PROPOSED, and WITHDRAWN, with mixed opinions on the necessity of ACTIVE or FINAL statuses. Additionally, there's a suggestion to eliminate the REJECTED status, removing the automatic rejection of proposals over time.

The discussion also touched on format issues within BIPs, noting that sections such as Comments and Comment Summary are often overlooked and don't serve their intended purpose. The need for a backward compatibility section is frequently ignored, and there's a call to remove the "Other Implementations" section from documents. Licensing concerns were also highlighted, with some suggested licenses potentially being unsuitable.

Regarding the scope of the BIP repository, there's a consensus that proposals should meet a certain interest threshold and necessitate standardization, relevant to multiple implementations or a broader audience. Clarifications are sought on the repository's purpose, especially its role in representing community consensus or recommendations. The document underscores a need to refocus on proposals without speculating on acceptance or tracking adoption.

Open questions remain, such as the criteria for BIP relevance to the Bitcoin ecosystem or technology supporting the currency, the interpretation of "keeping with the Bitcoin philosophy," and the method for tracking BIP adoption. Niklas encourages further input on these open questions or alternative suggestions to the summarized points.

For those interested in contributing to this discourse, a thorough review of BIP-2 is recommended to ensure familiarity with the existing guidelines and facilitate a productive dialogue on potential improvements.