anchor.diff:  
   toc::[]
   
  -Jenkins core is a central component of the project which serves millions of users, and it is critical to maintain it in a good shape.
  -We want to ensure quality of the integrated changes and continuity of the project,
  +Jenkins core is a central component of the project which serves millions of users, and it is critical to maintaining it in a good shape.
  +We want to ensure the quality of the integrated changes and continuity of the project,
   and hence the Jenkins core pull request review and merge process is more sophisticated than for the majority of plugins.
   
   == Scope of the document
  
positive.code: Pull requests often become a venue to discuss feasibility, underlying technical decisions and design.
  We are fine with that as well.
  If there is no consensus about the feasibility and implementation,
  code reviewers are expected to suggest proper channels for contributors to discuss their contribution.
  
  * A discussion in the link:https://groups.google.com/d/forum/jenkinsci-dev[Jenkins Developer Mailing List] is the default way to go
  * If no consensus can be reached on the mailing list,
  
negative.code: Special permissions are not required to take this role or to contribute.
  Anyone is welcome to start contributing (see the <<issue-triage,triage guidelines below>>).
  
  **Core Pull Request Reviewers** is a team for contributors who are willing to regularly review Jenkins pull requests and eventually become Jenkins core maintainers.
  They get https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization[Triage permissions] so that they can manage pull requests, request reviews and prepare changelog drafts in the pull request description.
  Their main responsibility is to triage and review the incoming pull requests
  and to guide newcomer contributors who are not familiar with the project's processes.
  