docs/DeveloperPolicy: Add instructions for requesting GitHub commit access

[xbolva00]

llvm/docs/DeveloperPolicy.rst

415

Needs "cd trunk/" before svn commit, otherwise

~/TMP/tmp-llvm-svn$ svn commit -m " ... "
svn: E155007: '/home/xbolva00/TMP/tmp-llvm-svn' is not a working copy

[tstellar]

Fix svn commit instructions.

[jtony]

I am not able to run the last step successfully. Initially, I thought it's because I used wrong password. So I sent another new password hash to Chris Lattner to update it. He updated the password hash for me. When I used the new password to run svn commit -m "Request commit access for jtony" still failed. Anyway know why? Thanks!

[mehdi_amini]

I think this would be useful to have in?

llvm/docs/DeveloperPolicy.rst

415

ping?

[xbolva00]

llvm/docs/DeveloperPolicy.rst

415

ping what?

[mehdi_amini]

llvm/docs/DeveloperPolicy.rst

415

Nevermind, it seems it has been fixed already. I probably had an old diff I was looking at, since I hit the same issue locally.

[jtony]

In D66840#1702109, @jtony wrote:

I am not able to run the last step successfully. Initially, I thought it's because I used wrong password. So I sent another new password hash to Chris Lattner to update it. He updated the password hash for me. When I used the new password to run svn commit -m "Request commit access for jtony" still failed. Anyway know why? Thanks!

Anyone run into similar issue? What should I do? Thanks!

[jtony]

In D66840#1702109, @jtony wrote:

I am not able to run the last step successfully. Initially, I thought it's because I used wrong password. So I sent another new password hash to Chris Lattner to update it. He updated the password hash for me. When I used the new password to run svn commit -m "Request commit access for jtony" still failed. Anyway know why? Thanks!

Problem solved, by explicitly specify username and password when commiting (not wait until prompt the password enter)

svn commit -m "Request commit access for jtony" --username=jtony --password=$PASSWORD
Sending        github-usernames.txt
Transmitting file data .
Committed revision 375223.

llvm/docs/DeveloperPolicy.rst

 
 In any case, your changes are still subject to `code review`_ (either before or
 after they are committed, depending on the nature of the change).  You are
 encouraged to review other peoples' patches as well, but you aren't required
 to do so.
 
 .. _discuss the change/gather consensus:
 
+Obtaining Commit Access to the GitHub Repository
+------------------------------------------------
+We are currently in the process of migrating the project's source code from SVN
+to a git repository on GitHub.  We are maintaining a file in SVN to map
+SVN usernames to GitHub usernames, so we can automatically grant access to
+existing committers when we complete the migration to GitHub.  In order to
+request commit access, check out the github-usernames.txt file in meta/trunk and
+add a line in the form of $SVN_USERNAME:$GITHUB_USERNAME and commit it.  For
+example:
+
+.. code:: console
+
+  mkdir tmp-llvm-svn
+  cd tmp-llvm-svn
+  svn co https://$[e-mail]/svn/llvm-project/meta/trunk
+  echo "$SVN_USERNAME:$GITHUB_USERNAME" >> trunk/github-usernames.txt
+  cd trunk
+  svn commit -m "Request commit access for $SVN_USERNAME"
+
+
 Making a Major Change
 ---------------------
 
 When a developer begins a major new project with the aim of contributing it back
 to LLVM, they should inform the community with an email to the `llvm-dev
 <http://lists.llvm.org/mailman/listinfo/llvm-dev>`_ email list, to the extent
 possible. The reason for this is to: