We would love to have you join the Armbian community! Below summarizes the processes that we follow.
Before reporting an issue, check our backlog of open issues and pull requests to see if someone else has already reported or working on it. If an issues is already open, feel free to add your scenario, or additional information, to the discussion. Or simply "subscribe" to it to be notified when it is updated.
If you find a new issue with the project please let us hear about it! The most important aspect of a bug report is that it includes enough information for us to reproduce it. So, please include as much detail as possible and try to remove the extra stuff that does not really relate to the issue itself. The easier it is for us to reproduce it, the faster it will be fixed!
Please do not include any private/sensitive information in your issue! We are not responsible for your privacy, this is open source software.
Once you have decided to contribute to Armbian by working on an issue, check our backlog of open (or JIRA issues open by the team) looking for any that do not have an "In Progress" label attached to it. Often issues will be assigned to someone, to be worked on at a later time. If you have the time to work on the issue now add yourself as an assignee, and set the "In Progress" label if you are a member of the “Containers” GitHub organization. If you can not set the label, just add a quick comment in the issue asking that the “In Progress” label be set and a member will do so for you.
Please be sure to review the Development Code Review Procedures and Guidelines as well before you begin.
Labels are defined in .github/labels.yml YAML file. They are automatically recreated upon change. Require at least Triage users permission on repository. Request access if you cannot change labels!
Most of labels are self explanoritary but here are short instructions on how to use them:
Automated on PR:
size/small,size/medium,size/largeis determined automatically from the size of the PRdesktop,hardwareandsoftwareis determined automatically depending on location of the changes
Manual on PR:
02050811milestone - determine into which release the PR should gowork in progress- when you are still working onneeds review- when you are done and seeking for attentionready to merge- when you are donehelp needed- when you are desperate and cannot move on
Labeling Issues:
bugwhen it is clear that it is our bug,not our bugif its clearly not ours,duplicateif issue already existsdiscussion, when needed,user errorwhen we know it is a problem on the other sidecan be closedfor stalled issues
This section describes how to start contributing to Armbian.
- Create an Ubuntu 22.04 VM with VirtualBox or any other suitable hypervisor.
- Install Github CLI tool
- Configure git:
git config --global user.email "[email protected]"
git config --global user.name "Your Name"- Generate GPG key
gpg --generate-key- Generate Github login token
- Login to Github (you only have to do the steps above once)
gh auth login --with-token <<< 'your_token'- Fork armbian/build, clone and add remote
gh repo fork armbian/build --clone=true --remote=true- Create branch
cd build
git checkout -b your_branch_name # change branch name for your patch- Compile Armbian (this use case is to change something in the device tree and test the built image)
./compile.sh CREATE_PATCHES="yes"- Full OS image for flashing
- Do not change the kernel configuration
- Choose a board
- Choose a kernel
- Choose a release package base
- Choose image type
- Configuring apt-cacher-ng
- Wait for prompt to make u-boot changes (press Enter after making changes in specified directory)
[ o.k. ] * [l][c] enable-distro-bootcmd.patch
[ warn ] Make your changes in directory: [ /home/yourhome/build/cache/sources/u-boot-odroidxu/odroidxu4-v2017.05 ]
[ warn ] Press <Enter> after you are done [ waiting ]-
Open another terminal or files window
-
In this case I want to add gpio-line-names to the Odroid XU4 device tree when prompted to do so
sudo nano build/cache/sources/linux-odroidxu4/odroid-5.4.y/arch/arm/boot/dts/exynos5420-pinctrl.dtsi
-
Wait for prompt to make kernel changes (press Enter after making changes in specified directory)
[ warn ] Make your changes in this directory: [ /home/yourhome/build/cache/sources/linux-odroidxu4/odroid-5.4.y ] [ warn ] Press <Enter> after you are done [ waiting ]
-
Test the changes you made on your board
- Mine was located in
/home/yourhome/build/output/images/Armbian_21.02.0-trunk_Odroidxu4_focal_current_5.4.83.img
- Mine was located in
-
Rename patch to something meaningful and move to proper location
mv output/patch/kernel-odroidxu4-current.patch patch/kernel/odroidxu4-current/add-gpio-line-names.patch
Next, you can prepare to submit your patch to the Armbian project.
No Pull Request (PR) is too small! Typos, additional comments in the code, new test cases, bug fixes, new features, more documentation, ... everything is welcome!
While bug fixes can first be identified via an "issue", that is not required for things mentioned above. It is fine to just open up a PR with the fix, but make sure you include the same information you would have included in an actual issue - like how to reproduce it.
PRs for new features should include some background on what use cases the new code is trying to address. When possible and when it makes sense, try to break-up larger PRs into smaller parts - it is easier to review smaller code changes. But only if those smaller ones make sense as stand-alone PRs.
You should squash your commits into logical pieces of work that can be reviewed separate from the rest of the PRs. Squashing down to just one commit is ok as well, since in the end the entire PR will be reviewed anyway. If in doubt, squash.
Describe your problem(s). Whether your patch is a one-line bug fix or 5000 lines including a new feature, there must be an underlying problem that motivated you to do this work. Your description should work to convince the reviewer that there is a problem worth fixing and that it makes sense for them to read past the first paragraph. This means providing comprehensive details about the issue, including, but not limited to:
- How the problem presented itself
- How to replicate the problem
- Provide 'dmesg' and/or 'armbianmonitor -u' output showing board used and any console output surrounding the issue
- Why you feel it is important for this issue to be resolved
For general questions and discussion, please use the IRC #armbian, #armbian-devel or #armbian-desktop on Libera.Chat or Discord server. Most IRC and Discord channels are bridged and recorded.
For discussions around issues/bugs and features, you can use the GitHub issues, the PR tracking system or our Jira ticketing system.