You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by GitBox <gi...@apache.org> on 2021/12/16 19:56:09 UTC

[GitHub] [trafficcontrol] zrhoffman commented on a change in pull request #6425: adds note to blueprint regarding lazy consensus option

zrhoffman commented on a change in pull request #6425:
URL: https://github.com/apache/trafficcontrol/pull/6425#discussion_r770880006



##########
File path: CONTRIBUTING.md
##########
@@ -68,7 +68,7 @@ list with a short description of your feature plus a link to the blueprint PR.
 1. Wait for feedback to be applied to your blueprint PR. Because it's a PR,
 line-specific feedback can be given.
 1. Just like any PR, once all the concerns have been addressed, the blueprint is
-merged into the blueprints directory (if accepted) or closed (if rejected).
+merged into the blueprints directory (if accepted) or closed (if rejected). Note: Blueprint authors have the option of invoking [lazy consensus](https://community.apache.org/committers/lazyConsensus.html) to facilitate the merge of the blueprint if community feedback is not being provided or feedback has stalled. To invoke lazy consensus, please make the community aware via an email to the [dev@trafficcontrol.apache.org](mailto:dev@trafficcontrol.apache.org) mailing list that you intend to invoke lazy consensus after X hours with no feedback.

Review comment:
       Maybe mention that lazy consensus cannot be invoked once any feedback is left.




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org