[doc] documentation of code review tools

[kuhnel]

Summary

Different LLVM projects on GitHub use different code review tools. This patch updates our developer policy to document which review tool is used where. This is based on the discussion in https://github.com/llvm/llvm-iwg/issues/21

Note: We're not changing which tool is used, we only document the current state.

Authored-by: @agerbes , I posting this on her behalf.

[kuhnel]

ping @reames

[kuhnel]

2nd iteration of the patch

Changes:

• added a bit of boilerplate text
• changed the links to be simpler to read
• removed the project that haven't been updated in a long time or are not performing code reviews

[xgupta]

They are listed in random order, listing them according to their activity would be better.

llvm/docs/DeveloperPolicy.rst

141

142

153

153

better if we have one review tool to contribute, only phabricator would be the right place for llvm-www.

155

mlir-npcomp renamed to torch-mlir.

[reames]

llvm/docs/DeveloperPolicy.rst

131

I request a minor reframing here. Please describe phabricator as the default, and list the github pull requests as the exception to the general policy.

I'd also leave out any where there's been a mix of both. We should bias those towards phabricator unless that particular community desires otherwise. (i.e. contributes their own follow up to list themselves as PRs)

146

Order wise, either alphabetical or popularity. I'd prefer alphabetical.

[kuhnel]

Thx @reames and @xgupta for your review! I hopefully addressed all of them.

Sorry for the slow response rate. I'd actually like to wrap this up rather sonner than later.

llvm/docs/DeveloperPolicy.rst

146

Using alphabetical as it's easier to do and maintain.

[xgupta]

LGTM, Thanks!

[kuhnel]

ping @reames

[xgupta]

This looks good to me.

llvm/docs/DeveloperPolicy.rst

 
 Code Reviews
 ------------
 
 LLVM has a code-review policy. Code review is one way to increase the quality of
 software. Please see :doc:`CodeReview` for more information on LLVM's code-review
 process.
 
+The default tool for code reviews is
+`Phabricator <https://reviews.llvm.org/>`_. However there are also repositories
+that are using GitHub Pull Requests for code reviews. 
+
+**Repositories using Phabricator:**
+
+* `llvm-project <https://github.com/llvm/llvm-project>`_ aka. LLVM Monorepo
+* `llvm-test-suite <https://github.com/llvm/llvm-test-suite>`_  
+* `llvm-www <https://github.com/llvm/llvm-www>`_  
+* `llvm-zorg <https://github.com/llvm/llvm-zorg/>`_
+* `LNT <https://github.com/llvm/llvm-lnt>`_ 
+
+
+**Repositories using Github Pull Requests:**
+
+* `circt <https://github.com/llvm/circt>`_
+* `circt-www <https://github.com/llvm/circt-www>`_
+* `clangd-www <https://github.com/llvm/clangd-www>`_
+* `llvm-blog-www <https://github.com/llvm/llvm-blog-www>`_
+* `llvm-foundation-www <https://github.com/llvm/llvm-foundation-www>`_
+* `llvm-iwg <https://github.com/llvm/llvm-iwg>`_
+* `llvm-test-suite <https://github.com/llvm/llvm-test-suite>`_
+* `llvm-www-pubs <https://github.com/llvm/llvm-www-pubs>`_
+* `mlir-www <https://github.com/llvm/mlir-www>`_
+* `torch-mlir <https://github.com/llvm/torch-mlir>`_
+* `www-releases <https://github.com/llvm/www-releases>`_
+
+
 .. _code owners:
 
 Code Owners
 -----------
 
 The LLVM Project relies on two features of its process to maintain rapid
 development in addition to the high quality of its source base: the combination
 of code review plus post-commit review for trusted maintainers.  Having both is