LLVM Bugzilla is read-only and represents the historical archive of all LLVM issues filled before November 26, 2021. Use github to submit LLVM bugs

Bug 43778 - Obtaining commit access for new developers
Summary: Obtaining commit access for new developers
Status: RESOLVED FIXED
Alias: None
Product: Documentation
Classification: Unclassified
Component: General docs (show other bugs)
Version: trunk
Hardware: PC Linux
: P normal
Assignee: Unassigned LLVM Bugs
URL:
Keywords:
Depends on:
Blocks: github
  Show dependency tree
 
Reported: 2019-10-23 12:14 PDT by Mark de Wever
Modified: 2019-11-07 12:58 PST (History)
5 users (show)

See Also:
Fixed By Commit(s):

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mark de Wever 2019-10-23 12:14:47 PDT 
I noticed this page [1] hasn't been updated for the GitHub migration.


[1] http://llvm.org/docs/DeveloperPolicy.html#obtaining-commit-access
Comment 1 emaste 2019-10-23 12:43:01 PDT 
Or for existing committers who failed to add themselves to github-usernames.txt in time.
Comment 2 Mark de Wever 2019-10-26 04:15:02 PDT 
If you had access before you should contact Tom [1]:

"Also, if you were an SVN committer and you still need commit access, please
email me off list with your svn and github IDs, and I'll get you added."

[1] http://lists.llvm.org/pipermail/llvm-dev/2019-October/136155.html
Comment 3 Eli Friedman 2019-10-30 11:42:22 PDT 
https://github.com/llvm/llvm-project/blob/master/llvm/docs/DeveloperPolicy.rst is already updated.  The website sync is currently broken, though, so nobody can make any changes to it.
Comment 4 Mark de Wever 2019-10-30 16:15:25 PDT 
(In reply to Eli Friedman from comment #3)
> https://github.com/llvm/llvm-project/blob/master/llvm/docs/DeveloperPolicy.
> rst is already updated.  The website sync is currently broken, though, so
> nobody can make any changes to it.

Thanks for the information!

I'll leave the bug open until the synchronisation is fixed so others can find this information.
Comment 5 Mark de Wever 2019-11-07 12:58:24 PST 
The synchronisation seems to work and the new policy is online.