This is placeholder for contributor guidelines.

1. Golden rule: Please do "git log"/"git log -p" and follow the same approach with your changes. Some specifics:
2. One changed module/package per commit.
3. Every commit message starts with "<module>: "
4. Each module's setup.py is autogenerated from metadata.txt by make_metadata.py script, so please make changes to metadata.txt, run make_metadata.py and then commit both metadata.txt and setup.py.
5. Name something test_*.py only if it's a real unittest (which will checks results itself and will fail if there's error). Otherwise if human should check test results, name it example_*.py

When porting a module from CPython or other 3rd-party source:

1. Do some research to find suitable source. CPython 3.3 stdlib should still be considered as a base version to take modules from, as more recent versions has some modules bloated, which isn't really good direction for MicroPython. (But again, try to look at different versions and sources beyond CPython (e.g. PyPy) to find the best.)
2. Start with committing 3rd-party source as-is, clearly stating in commit message from where it was taken (exact version, preferrably with URL to tarball, or VCS revision, preferrably with URL to it).
3. Follow up with your changes as a next commit.
4. When making your changes, the criteria should be minimizing size of a diff. Change as few lines as possible, within lines, don't change more chars than needed. Prefer commenting out to removal of lines. Don't fix typos, formatting, etc. - if you want them to be fixed, submit patches directly to upstream.
5. Prefer taking (and porting) tests from CPython rather than duplicating effort and making your own.