One of the core reasons why we decided to release Bela last year is to build a community around it. A big part of that is for people to build great projects using Bela, but we also hope that the community will pitch in to help us improve and expand the capabilities of the board.
With the contribution of the community, fixes, improvements and support for new languages can come much quicker than it would with our efforts alone.
If you want to improve the Bela documentation, explaining how you achieved something not yet documented or fixing and tidying up, then you can do that on the wiki, which you can edit as long as you have a github account.
If you have a project to share, use the "Show and tell" tag here on the forum, or get in touch with us if you want to author a full-length post on the blog.
You do not need to be a gearhead to help Bela grow: if you can spare some time to test the bleeding edge features and fixes as they come out, you'll help us make the development faster. If you have some time to contribute by testing new features, then make yourself known!
If you are a developer and want to contribute, add features, port Bela to other programming languages or audio environments, fix bugs, then let's talk about it. Create a new thread and we'll be on it.
All skills are welcomed, from kernel hackers to project management to DSP and everything in between.
Note: ideally I would say "Just subscribe to this (or that) tag on the forum to be notified when something happens for testers or developers", but that features is not available on Flarum (our forum engine) yet, which is why I only say "make yourself known".