Contribution¶
Note
This section is under developmement right now.
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:
These guidelines are mostly suggestions, not hard-set rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
Code of Conduct¶
This project and everyone participating are governed by the same code of conduct.
Note
Check out https://forum.beagleboard.org/faq as a starting place for our code of conduct.
By participating, you are expected to uphold this code. Please report unacceptable behavior to contact one of our administrators or moderators on https://forum.beagleboard.org/about.
Frequently Asked Questions¶
Please refer to the technical and contribution frequently asked questions pages before posting any of your own questions. Please feel encouraged to ask follow-up questions if any of the answers are not clear enough.
What should I know before I get started?¶
The more you know about Linux and contributing to upstream projects, the better, but this knowledge isn’t strictly required. Simply reading about contributing to Linux and upstream projects can help build your vocabulary in a meaningful way to help out. Learn about the skills required for Linux contributions in the Upstream Kernel Contributions section.
The most useful thing to know is how to ask smart questions. Read about this in the Getting support section. If you ask smart questions on the issue trackers and forum, you’ll be doing a lot to help us improve the designs and documentation.
How can I contribute?¶
The most obvious way to contribute is using the git.beagleboard.org Gitlab server to report bugs, suggest enhancements and providing merge requests, also called pull requests, the provide fixes to software, hardware designs and documentation.
This documentation has a number of todo items where help is needed that can be searched in the source.
Todo
add cape compatibility details
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/beaglebone/ai-64/ch04.rst, line 100.)
Todo
This section needs more work and references to greater detail. Other boot modes are possible. Software to support USB and serial boot modes is not provided by beagleboard.org._Please contact TI for support of this feature.
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/beaglebone/ai-64/ch05.rst, line 225.)
Todo
IMX219 CSI sensor connection with BeagleBone® AI-64 for Edge AI
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/beaglebone/ai-64/edge_ai_apps/getting_started.rst, line 82.)
Todo
BeagleBone® AI-64 wallpaper upon boot
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/beaglebone/ai-64/edge_ai_apps/getting_started.rst, line 187.)
Todo
Microsoft Visual Studio Code for connecting to BeagleBone® AI-64 for Edge AI via SSH
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/beaglebone/ai-64/edge_ai_apps/getting_started.rst, line 252.)
Todo
Make all figure references actual references
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/beaglebone/black/ch07.rst, line 1163.)
Todo
move accessory links to a single common document for all boards.
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/beaglebone/black/ch07.rst, line 1184.)
Todo
We should include all support information in docs.beagleboard.org now and leave eLinux to others, freeing it as much as possible
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/beaglebone/black/ch07.rst, line 1194.)
Todo
We are going to work on a unified accessories page for all the boards and it should replace this.
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/beaglebone/blue/accessories.rst, line 6.)
Todo
Image with what’s inside the box and a better description.
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/beagleconnect/freedom/02-quick-start.rst, line 14.)
Todo
Describe how to screw on the antenna.
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/beagleconnect/freedom/02-quick-start.rst, line 22.)
Todo
Describe how to get a serial connection.
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/beagleconnect/freedom/02-quick-start.rst, line 30.)
Todo
Describe how to get an IEEE802.15.4g connection from BeaglePlay.
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/beagleconnect/freedom/02-quick-start.rst, line 37.)
Todo
Describe how to get to a local console and websockets console.
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/beagleconnect/freedom/02-quick-start.rst, line 48.)
Todo
provide images demonstrating Jupyter Notebook visualization
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/beagleconnect/index.rst, line 76.)
Todo
think a bit more about this section with some feedback from Cathy.
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/beagleconnect/index.rst, line 95.)
Todo
describe how to know it is working
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/beagleplay/demos-and-tutorials/zephyr-cc1352-development.rst, line 39.)
Todo
A big part of what is missing here is to put your BeaglePlay on the Internet such that we can download things in later steps. That has been initially brushed over.
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/beagleplay/demos-and-tutorials/zephyr-cc1352-development.rst, line 50.)
Todo
Describe how to handle the serial connection
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/beagleplay/demos-and-tutorials/zephyr-cc1352-development.rst, line 378.)
Todo
figure out if BONE-SPI0_0 and BONE-SPI0_1 can be loaded at the same time
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/capes/cape-interface-spec.rst, line 504.)
Todo
We need a udev rule to make sure the ADC shows up at /dev/bone/adc! There’s nothing for sure that IIO devices will show up in the same place.
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/capes/cape-interface-spec.rst, line 669.)
Todo
I think we can also create symlinks for each channel based on which device is there, such that we can do /dev/bone/adc/Px_y
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/capes/cape-interface-spec.rst, line 671.)
Todo
I believe a multiplexing IIO driver is the future solution
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/capes/cape-interface-spec.rst, line 673.)
Todo
This doesn’t include any abstraction yet.
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/capes/cape-interface-spec.rst, line 946.)
Todo
For each of the pins with a GPIO, there should be a symlink that comes from the names
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/capes/cape-interface-spec.rst, line 1324.)
Todo
The steps used to verify all of these configurations is to be documented here. It will serve to document what has been tested, how to reproduce the configurations, and how to verify each major triannual release. All faults will be documented in the issue tracker.
(The original entry is located in /builds/docs/docs.beagleboard.io/boards/capes/cape-interface-spec.rst, line 1369.)
Todo
Describe where and how to report issues on git.beagleboard.org
(The original entry is located in /builds/docs/docs.beagleboard.io/intro/contribution/index.rst, line 76.)
Todo
Describe how to introduct ideas on forum.beagleboard.org and git.beagleboard.org
(The original entry is located in /builds/docs/docs.beagleboard.io/intro/contribution/index.rst, line 82.)
Todo
Describe how to introduct ideas on forum.beagleboard.org and git.beagleboard.org
(The original entry is located in /builds/docs/docs.beagleboard.io/intro/contribution/index.rst, line 88.)
Todo
Why “device” drivers?
(The original entry is located in /builds/docs/docs.beagleboard.io/intro/contribution/linux-upstream.rst, line 148.)
Todo
Why do we need drivers?
(The original entry is located in /builds/docs/docs.beagleboard.io/intro/contribution/linux-upstream.rst, line 152.)
Todo
What do drivers look like?
(The original entry is located in /builds/docs/docs.beagleboard.io/intro/contribution/linux-upstream.rst, line 156.)
Reporting bugs¶
Todo
Describe where and how to report issues on git.beagleboard.org
Suggesting enhancements¶
Todo
Describe how to introduct ideas on forum.beagleboard.org and git.beagleboard.org
Submitting merge requests¶
Todo
Describe how to introduct ideas on forum.beagleboard.org and git.beagleboard.org