We welcome contributions of all forms, including patches to code and documentation, issue reports, or just kind words.
Snek sources are maintained in git and hosted in two places.
-
keithp.com. This is the 'canonical' source location.
-
github. This should exactly mirror the code at keithp.com. I've placed it here to make contributing to Picolibc easier for people familiar with github.
You can create a local copy of the repository with git clone:
$ git clone git://keithp.com/git/picolibc.git
or
$ git clone https://github.com/keith-packard/picolibc.git
Picolibc uses the meson build tool. You'll need to make sure that's installed before you start trying to build the software.
As Picolibc is designed to be used for embedded systems, getting that configured correctly can be a challenge. Learn more about that in the build page.
You can submit patches in a couple of ways:
-
Mail to the picolibc list (see below). This can be tricky as it requires a friendly email system, and you'll have to subscribe to the mailing list before it will let you post anything (sigh). Here's a simple example sending the latest patch in your local repository to the list:
$ git send-email --to [email protected] HEAD^
-
Generate a pull-request in github.
- Fork the picolibc project into your own github account
- Push patches to that repository
- While viewing your repository, click on the 'New pull request' button and follow the instructions there.
We're using the issue tracker on Github for now; if you have issues, please submit them to the Picolibc Issue Tracker
Picolibc has a mailing list, hosted at keithp.com. You can subscribe here. This is a public list, with public archives. Participants are expected to abide by the Picolibc Code of Conduct.
Snek uses the Contributor Covenant, which you'll find in the source tree as CODE_OF_CONDUCT.md. Please help make Snek a kind and welcoming environment by following those rules.