Developers Wanted:

SCons is actively looking for contributors. You can contribute to the code of SCons itself, the documentation, the examples/ cookbook, and more. If you're interested, we'd love to hear from you at scons-dev@scons.org.

What it takes to contribute to SCons:

There is a complete and evolving set of Developer's Guidelines that go into reasonable detail about how we're guaranteeing that SCons continues to be an exceptionally stable and reliable tool for building software. Here are two key points:

  • We write a lot of automated tests to test thoroughly test SCons. Lines of test code currently outnumber lines of code in SCons itself by about 3:1.
  • SCons uses GitHub to manage receiving patches via Pull Requests from the community

Guidelines:

Please take a look at the current guidelines before deciding to hop on board.

GitHub:

SCons' git is hosted on GitHub.

The master branch contains current development.

Occasionally long-term development is carried out on a branch. Anyone may clone the main repository from GitHub.

Latest API documentation

A set of HTML pages documenting the internal APIs of the latest SCons release. These are generated by sphinx from the SCons source code and docstrings.

The API docs are an internal resource, helpful for developing SCons. The distinction between "public API", which comes with consistency guarantees, and "internal API", which does not, is not necessarily clear from these docs; the public API is what appears in the manpage.

There's also kind of an intermediate API: methods which might need to be tapped into by developers writing components to work with SCons, like new tools, builders, scanners, etc.

The docstrings for internal classes and methods aren't really written consistently, or to a consistent style, and improvements here, even piecemeal, would be a nice addition to the project.

How to reach the community

Please reach out to the community via mailing list, IRC channel, or Discord server before doing any of these: