forked from bitcoin/bips
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update the BIP Process #2
Open
murchandamus
wants to merge
116
commits into
master
Choose a base branch
from
2024-05-update-process
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 103 commits
Commits
Show all changes
116 commits
Select commit
Hold shift + click to select a range
bbf7c51
Create first outline
murchandamus d1d49e9
Add an initial abstract
murchandamus 0bd8036
Start filling in Workflow
murchandamus 4643b16
Use "champion" for BIP Author
murchandamus 74e691d
Revisit Abstract and What is a BIP?
murchandamus e600c49
Deliberate significance of BIPs
murchandamus 3f990ed
Rework draft stage of BIP workflow, add BIP-0002 to bottom of document
murchandamus 97744be
Require proof of work before number assignment
murchandamus 9426c2e
Describe Proposed and Withdrawn
murchandamus 613f1ff
Clarify Proposed, describe Withdrawn, and retain Transferring Ownership
murchandamus 59c9f12
Retain description of BIP Types
murchandamus 0214659
Minor improvements to process description
murchandamus 4ba4e47
Describe optional FINAL/ACTIVE status
murchandamus f076ade
Start tracking changes compared to BIP 2
murchandamus ba40daa
Drop "changes to environment and tools" from process examples
murchandamus affea61
State that adoption tracking is out of scope
murchandamus f23cf9d
Inherit initial BIP Editors section from BIP-2
murchandamus 556e2d4
Move BIP Types to top, reiterate adoption
murchandamus 598848b
Update responsibilities of BIP editors
murchandamus 96df5fe
Define scope of the BIPs repository
murchandamus ca32adb
Add image for Status transitions
murchandamus 5017847
Add second variant for transition diagram
murchandamus ddfe787
Add Revisions as an optional topic
murchandamus 88e68c0
Note that Proposed overloads with Proposal
murchandamus 2ffcb8d
Track open issues
murchandamus 851858c
Inherit formatting spec from BIP-2 as a start
murchandamus 10e23f5
Reword BIP section descriptions
murchandamus 7ce39f9
Reword preamble instructions
murchandamus 896b4ec
Rename Author header to Champions header
murchandamus 3916387
Test whether footnotes via ref work
murchandamus 5d50bb1
Update preamble header descriptions
murchandamus 2d2d4f1
Drop Discussions-To header
murchandamus 0296846
Drop Comments, Comments-URI, and Comments-Summary
murchandamus 13b64e3
Swap order of Specification and Workflow
murchandamus 4a4b640
Mark Open questions as todo
murchandamus 33ed167
BIPs do not become rejected due to inactivity
murchandamus 02c9717
Move changes to the bottom for easier access
murchandamus afb5b9c
Update Licensing instructions
murchandamus 56ebea0
Add open question about change log
murchandamus 0446c5f
Mention inacceptability of OPL in rationale
murchandamus 7727100
Discourage 'Other Implementations' sections
murchandamus 3ae7a3b
Combine Status Field description and workflow (WIP)
murchandamus 5b0f797
Incorporate Status Field section into Workflow
murchandamus 8168178
Match transition graph to status field values
murchandamus c30ec6a
Rename Proposed to Nominated
murchandamus b67dda6
Expand acceptable changes of Nominated BIP
murchandamus e90f180
Pascal-case the Status field values
murchandamus a677b0d
Collect Rationale in one section
murchandamus b09ca95
Remove outdated graphics
murchandamus 7d2b81a
Fix minor optical issues and broken links
murchandamus a6b5e65
Clarify that feedback must be actionable
murchandamus 7f90aa5
Update Changes to BIP 2 section
murchandamus 99646f1
Add linebreaks to footnotes
murchandamus f2b1a6c
Add link to incident report example
murchandamus 6ad4172
Update Preamble description
murchandamus a676839
Describe Change Log section
murchandamus d6780d7
Address minor issues from review
murchandamus 4b63d36
Update terminology for status update
murchandamus 374ab86
Return BSD licenses to acceptable
murchandamus 8194030
Use Author instead of Champion
murchandamus d198deb
Replace Nominated with Preliminary
murchandamus e4b4c7c
Replace Post-History header with Discussion
murchandamus e4a59ab
Small improvements
murchandamus d3d0e7e
Harmonize references to other BIPs
murchandamus d5a3e91
Strike open points
murchandamus 564c38d
Match short and long description of Created Header
murchandamus df1e84a
Improve description of interactions with Abandoned
murchandamus 57d8c08
Update Comparison to BIP 2
murchandamus f5e5414
Add Backwards Compatibility section
murchandamus 41cd06a
Make Process BIPs living documents
murchandamus dea58f3
Elaborate on scope of repository (H/T RFC 2223)
murchandamus 452c05c
Replace Standards Track with Specification type
murchandamus b35e02f
Minor update to Significance of BIPs
murchandamus ac95ca2
Improve Abstract
murchandamus 0caa8aa
Addressing feedback WIP
murchandamus 6b184dc
Address several small feedback items
murchandamus eea8df8
Drop astroturfing footnote
murchandamus f667bf0
Add Motivation
murchandamus 8458dfd
Add footnote recommending to stick to basic Markdown features
murchandamus 9e804df
Require only Preamble, Abstract, and Copyright
murchandamus e07f38e
Drop footnotes
murchandamus 94cebfd
Amend Preamble, raise title limit to 50 characters
murchandamus fd423a8
Rewrite the Discussion header description
murchandamus 3504b74
Amend scope 'aim to support'
murchandamus 4ba4899
Update description of License identifiers
murchandamus 1da9d40
Update README to match updated process
murchandamus 3c47a01
Touch up Status and Ownership
murchandamus 85c4fe5
Update Changes to BIP 2
murchandamus e987582
Use BSD-2-Clause to adhere to license of BIP 2
murchandamus 1a648aa
Add Rationale for new BIPs over new versions
murchandamus 36e716f
Add examples for out-of-scope topics
murchandamus 27e174c
Fix typos and minor details from readthrough
murchandamus a4c8b23
Invert recommendation to split proposals
murchandamus b10f117
Reword incomplete specification
murchandamus c41b2ee
Warn against breaking changes in implemented BIPs
murchandamus 311b3d0
Require settled BIP before Active
murchandamus e158b95
Strengthen recommendation for discussion on ML
murchandamus 201ffd2
Use absolute link to BIP 352
murchandamus c1e27bb
Add Revision header to Preamble
murchandamus b795d91
Fix Discussion example link
murchandamus 2cb5a90
Recast status field values
murchandamus 2f1cd93
Address Larry’s feedback in README
murchandamus e2378f3
Adopt small improvements from Review
murchandamus d226be7
Avoid the term draft
murchandamus f2c1afb
Revert to Draft for the first state
murchandamus 52304cd
Revert "Ready" to "Proposed"
murchandamus 78b6b44
Reconsider uses of words that matched statuses
murchandamus cf2e14f
Defer changes to README until Proposal is adopted
murchandamus 81a2310
Address minor review concerns
murchandamus b54223d
Capitalize bitcoin only in proper nouns
murchandamus 7650ff3
Address Larry’s feedback comments
murchandamus 4f99f38
Update status diagram to match Statuses
murchandamus 3bdc703
Adopt remaining comments from Larry’s review
murchandamus 5113902
Improve Process BIP description
murchandamus 7a359f7
Drop phrase about off-list correspondence
murchandamus 985f976
Adopt suggestion to Scope section
murchandamus File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps drop "and cannot be agreed upon" and instead something like
"The exceptions are when a proposal is contentious or appears controversial, in which case BIP editors may prefer to opt for prudence or the more conservative path."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that this improves the phrasing, but it also leaves the outcome completely open. I would prefer if the guidance established some sort of expectation toward an outcome.
Thinking more about it, the appropriate time to adapt the README to match this proposal would probably be when this proposal is adopted by the community, rather when it is merged to the repository, so I am deferring the changes to the README to that time and have separated them into another PR #3.