llvm.org GIT mirror llvm / master docs / GettingInvolved.rst

Tree @master (Download .tar.gz)

GettingInvolved.rst @masterview markup · raw · history · blame

Getting Involved

LLVM welcomes contributions of all kinds. To get started, please review the following topics:

An overview on how to contribute to LLVM.
The LLVM project's policy towards developers and their contributions.
A template + tutorial for writing new Sphinx documentation. It is meant to be read in source form.
Describes how to use the Phabricator code review tool hosted on http://reviews.llvm.org/ and its command line interface, Arcanist.
Instructions for properly submitting information about any bugs you run into in the LLVM system.
Describes how bugs are reported, triaged and closed.
Details the LLVM coding standards and provides useful information on writing efficient C++ code.

Development Process

Information about LLVM's development process.

How-to guide and templates for new projects that use the LLVM infrastructure. The templates (directory organization, Makefiles, and test tree) allow the project code to be located outside (or inside) the llvm/ tree, while using LLVM header files and libraries.
Describes the LLVMBuild organization and files used by LLVM to specify component descriptions.
This is a guide to preparing LLVM releases. Most developers can ignore it.
This is a guide to validate a new release, during the release process. Most developers can ignore it.
Instructions for adding new builder to LLVM buildbot master.
Advice on packaging LLVM into a distribution.
:doc:`Release notes for the current release <ReleaseNotes>`
This describes new features, known bugs, and other limitations.

Mailing Lists

If you can't find what you need in these docs, try consulting the mailing lists.

Developer's List (llvm-dev)
This list is for people who want to be included in technical discussions of LLVM. People post to this list when they have questions about writing code for or using the LLVM tools. It is relatively low volume.
Commits Archive (llvm-commits)
This list contains all commit messages that are made when LLVM developers commit code changes to the repository. It also serves as a forum for patch review (i.e. send patches here). It is useful for those who want to stay on the bleeding edge of LLVM development. This list is very high volume.
Bugs & Patches Archive (llvm-bugs)
This list gets emailed every time a bug is opened and closed. It is higher volume than the LLVM-dev list.
Test Results Archive (llvm-testresults)
A message is automatically sent to this list by every active nightly tester when it completes. As such, this list gets email several times each day, making it a high volume list.
LLVM Announcements List (llvm-announce)
This is a low volume list that provides important announcements regarding LLVM. It gets email about once a month.


Users and developers of the LLVM project (including subprojects such as Clang) can be found in #llvm on irc.oftc.net.

This channel has several bots.

  • Buildbot reporters
  • robot - Bugzilla linker. %bug <number>
  • clang-bot - A geordi instance running near-trunk clang instead of gcc.

Meetups and social events

Besides developer meetings and conferences, there are several user groups called LLVM Socials. We greatly encourage you to join one in your city. Or start a new one if there is none:


Community wide proposals

Proposals for massive changes in how the community behaves and how the work flow can be better.

Proposal to adopt a code of conduct on the LLVM social spaces (lists, events, IRC, etc).
Proposal to move from SVN/Git to GitHub.
Design doc for a redesign of the Bugpoint tool.
Proposal to add a libc implementation under the LLVM project.
Proposals for additional benchmarks/programs for llvm's test-suite.
Proposal to change the variable names coding standard.
Proposal to model the process and upgrade the infrastructure of LLVM's Loop Vectorizer.