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.
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.
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. :man_shrugging:
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.
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.
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
No conflicts as of last run.
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?
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.
I’d also say to keep the empty file in the repo
Pushed to just empty the file.