Contribution

Important

First off, thanks for taking the time to think about contributing!

Note

For donations, see BeagleBoard.org - Donate.

The BeagleBoard.org Foundation maintains source for many open source projects.

Example projects suitable for first contributions:

• BeagleBoard project documentation

• Debian image bug repository

• Debian image builder

These guidelines are mostly suggestions, not hard-set rules. Use your best judgment, and feel free to propose changes to this document in a merge request.

Todo

We need some kind of documentation on how the build process runs and how Sphinx is configured. This conf.yml file is just a mystery, with insufficient information on the provided interface.

• Code of Conduct
• Frequently Asked Questions
• What should I know before I get started?
• How can I contribute?
  • Suggesting enhancements
  • Submitting merge requests
  • Site Editing Guide
  • Google Summer of Code (GSoC)
  • Reporting bugs
  • Tackle to-do list
  • Articles on contribution
  • History of contributors
• Google Summer of Code (GSoC)
• Git Usage
  • Relevance
  • Installing git
  • Testing your git installation
  • Creating an OpenBeagle account (optional)
  • Working with the source code
  • Making changes locally
  • Pushing changes to OpenBeagle
  • Merging upstream changes
  • Submitting changes for inclusion in BeagleBoard Docs
  • Evaluating changes
  • Additional Resources
• Documentation Style Guide
• ReStructuredText Cheat Sheet
  • Text formatting
  • Headings
  • Code
  • Links and cross referencing
  • More
• Upstream Kernel Contributions
  • Pre-requisites
  • More Git!
  • C-Programming
  • Cross-arch Development
  • Basics of embedded buses (I2C, UART, SPI, etc.)
  • Device Drivers in Embedded Systems
  • Device Trees
  • Additional Resources
• Building the Documentation
  • Invoking Sphinx
• Contributors