Skip to content

Conversation

@fanquake
Copy link
Member

It seems that it's time for our experiment with this file to come to an
end.

See discussion here:
https://github.com/bitcoin/bitcoin/pull/25560/files#r915491743.

@fanquake fanquake added the Docs label Jul 14, 2022
Copy link
Contributor

@kristapsk kristapsk left a comment

Choose a reason for hiding this comment

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

ACK cdbc68c1cd9b8228f8cdee9f61c20639325fb67d. It's kinda CODEOWNERS, don't think Bitcoin Core should have such thing.

@Sjors
Copy link
Member

Sjors commented Jul 14, 2022

No strong preference. I usually look at git blame if I feel the need to nag more reviewers.

@maflcko
Copy link
Member

maflcko commented Jul 14, 2022

Yes, git blame is best if you want to manually find reviewers.

However, this list was made for people to opt-in to bot notifications (as it is explained in the first line of the file), but then some people on the list complained about being notified by a bot. 🤷‍♂️

If there is anyone in this list who prefers those bot notifications, I think we should keep them in this list and remove everyone else.

@maflcko
Copy link
Member

maflcko commented Jul 14, 2022

Currently, the format of the comment looks like this: #25614 (comment)

This may be interesting to people that are not subscribed to the repo, but want to subscribe to changes to a specific file or folder.

My suggestion would be to keep the file and remove all contents for now, then leave the pull open for two weeks before merge. In those two weeks, people can explicitly opt-in by leaving a comment to be (re-)added to the file with the understanding that they will receive some kind of bot notifications. Also, anyone can open a pull request in the future to opt-in.

@DrahtBot
Copy link
Contributor

DrahtBot commented Jul 14, 2022

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Conflicts

No conflicts as of last run.

@DrahtBot DrahtBot mentioned this pull request Jul 14, 2022
@fanquake
Copy link
Member Author

My suggestion would be to keep the file and remove all contents for now, then leave the pull open for two weeks before merge. In those two weeks, people can explicitly opt-in by leaving a comment to be (re-)added to the file with the understanding that they will receive some kind of bot notifications.

Should we wait any longer?

@maflcko
Copy link
Member

maflcko commented Jul 30, 2022

I'd also say to keep the empty file in the repo for another two months to give people a chance to add themselves (opt-in to notifications) if they want.

@fanquake
Copy link
Member Author

I'd also say to keep the empty file in the repo

Pushed to just empty the file.

@maflcko
Copy link
Member

maflcko commented Jul 30, 2022

ACK 4d06fc4 seems best to have devs opt-in to this explicitly by themselves

@maflcko maflcko changed the title doc: remove REVIEWERS doc: empty REVIEWERS file Aug 1, 2022
@maflcko maflcko merged commit ce3b756 into bitcoin:master Aug 1, 2022
@fanquake fanquake deleted the remove_reviewers branch August 1, 2022 10:07
sidhujag pushed a commit to syscoin/syscoin that referenced this pull request Aug 1, 2022
@bitcoin bitcoin locked and limited conversation to collaborators Feb 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants