Collaboration

We use Codeberg as the central point for development, maintenance and distribution of GNU Guile. There you can open issues for bug reports, propose changes in pull requests and keep track of the project activity. (Bug reports made before 2026 can be seen in the legacy Debbugs database.)

The source files for all the components of the project, including software, web site, documentation, and artwork, are available in Git repositories at Codeberg.

When you report a bug, please try to provide exact directions we can follow to make the bug show itself when we test on our systems. If we can reproduce the bug, it's almost certain we will be able to fix it.

If you have fixed the bug as well, we ask that you:

• Submit the proposed changes as a pull request.
• Please include a ChangeLog-style commit log with your fix.
• Include references to the bug report. Turn the example that triggers the bug into a test case, submitted as part of your patch.
• If the patch changes more than about ten lines of code, we may ask you to assign your copyright to the FSF before it can be applied.

Contribution Policy

Contributions to Guile are subject to the following requirements:

• We do not accept code produced by a large language model (LLM) or based on code produced by such a tool. Thus, if you use LLMs or similar "generative AI" tools and services, we kindly ask you to be transparent about it.
• Contributors agree to the Developer Certificate of Origin (DCO); this agreement is materialized by adding a Signed-off-by Git trailer in commit messages.

See the HACKING file for more information.