anchor.diff:  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.
  +code reviewers are expected to suggest proper channels for contributors to discuss their contributions.
   
   * 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,
  
positive.code: 
  Pull requests review in Jenkins is not just about reviewing code and accepting them if the code is OK.
  Core maintainers are expected to ensure feasibility and compatibility of changes,
  to maintain good quality of the codebase and documentation,
  and to ensure there is a consensus between contributors.
  
  ==== Verifying Feasibility
  
  Reviewers are expected to look at changes critically from a "product management" point of view.
  It's not just about the code, but also whether the change makes sense in a global / holistic way, considering existing popular plugins and the way users experience Jenkins overall.
  Also, not every change needs to be merged into the core.
  Many features would be better introduced as plugins which have separate release cycles and allow delivering changes faster.
  We want to extend the Jenkins core and incorporate widely used functionality and extension points there,
  but we try to keep the core as minimal as possible in terms of dependencies.
  
  
negative.code: === Ladder
  
  * **Contributors**. Anyone can participate.
    There is no precondition except having a GitHub account, just submit pull requests or comment on existing ones!
  * **Core Pull Request Reviewers** can be nominated by contributors in the link:https://groups.google.com/d/forum/jenkinsci-dev[developer mailing list]. 
  Self-nomination is fine.
  The Decision is made by a consensus in the mailing list or via voting at the link:https://www.jenkins.io/project/governance-meeting/[governance meeting].
  * **Core Maintainers** - same process as for Core PR reviewers.
    All nominees must also sign an link:https://github.com/jenkinsci/infra-cla/[Individual Contributor License Agreement] before getting permission in GitHub repositories.
  * **Release Team Members** are assigned by the Jenkins Release officer
  
  == Pull request review process
  