Skip to content
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

Define BIP Steward Process and set Temporary Editor #1113

Closed
wants to merge 2 commits into from

Conversation

JaimeCaring
Copy link

On JaimeCaring/OpenBIPs#2 I received feedback that a new repo was "nuclear".

Up-streaming the OpenBIPs process here. See the linked issue for motivation.

I'm happy for a non-nym editor to replace me championing this process, but I don't think anyone deserves the political and reputational loss for this necessary action.

@michaelfolkson
Copy link
Contributor

NACK. This seems to be being discussed on the mailing list by some of the proposed "stewards" and I don't see any reason why it won't be resolved in the usual way without getting 23 people involved. Thanks for trying to move this along but I don't think it is needed personally.

@ghost
Copy link

ghost commented Apr 28, 2021

NACK everything mentioned in this PR

@JeremyRubin
Copy link
Contributor

Concept ACK -- I don't think this is required right now, but it does seem like a decent enough path longer term for governing the BIP process... people might prefer ad hoc process, but I'm a frequent citationer of https://www.jofreeman.com/joreen/tyranny.htm, so I think defined processes end up being less corrupt and more robust than undefined.

curious what bip editor @luke-jr and editor-to-be @kallewoof think about standardizing something similar?

Copy link
Member

@maflcko maflcko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NACK. Please stop electing random people as "Stewards" even when they explicitly asked you not to do this: JaimeCaring/OpenBIPs#2 (comment)

Edit: Didn't realize the bip here was written before the comment above

* @jonatack Jon Atack
* @kallewoof kallewoof
* @laanwj W. J. van der Laan
* @MarcoFalke MarcoFalke
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NACK. Please stop spamming this repository and the list of people here. I am not aware that anyone in this list consents to being included here. In fact there are several that wished to be taken off the list. I can't speak for others, but I certainly don't want to be involved in this and I don't want to further my responsibilities in Bitcoin apart from quality assurance where I voluntarily provide my feedback.

@maflcko
Copy link
Member

maflcko commented May 10, 2021

I think this can be closed?

@michaelfolkson
Copy link
Contributor

I think this can be closed?

Agree that this should be closed. It is a massive proposed change to BIP processes and clearly has strong opposition from many including a number of the proposed "stewards". Those "stewards" should have given their consent prior to be included. It appears none of them were aware that they were being put forward until the PR was opened. Other than perhaps @JeremyRubin I don't see anyone else supporting it.

@luke-jr luke-jr closed this May 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants