HowToGetInvolved: Difference between revisions
Jump to navigation
Jump to search
(Made the mailing list and Matrix the first thing people read when clicking to here from the Getting Involved tab on our main site) |
|||
| Line 1: | Line 1: | ||
* Participate on the [[MailingLists|mailing list]] and on [https://chat.gnuradio.org Matrix Chat] (or using our [[IRC]] bridge), help answer peoples questions | |||
* Read this wiki and contribute back. Some pages that need constant attention are the [[FAQ]] and the [[Tutorials]]. | * Read this wiki and contribute back. Some pages that need constant attention are the [[FAQ]] and the [[Tutorials]]. | ||
* When you're learning stuff, write a tutorial and put it up here | * When you're learning stuff, write a tutorial and put it up here | ||
* Promote GNU Radio at your workplace, university etc. | * Promote GNU Radio at your workplace, university etc. | ||
Revision as of 14:56, 11 May 2020
- Participate on the mailing list and on Matrix Chat (or using our IRC bridge), help answer peoples questions
- Read this wiki and contribute back. Some pages that need constant attention are the FAQ and the Tutorials.
- When you're learning stuff, write a tutorial and put it up here
- Promote GNU Radio at your workplace, university etc.
- Become a mentor for the Google summer of code
- Find small bugs (e.g. through Coverity) and fix them
Coding and debugging
Of course, the majority of work comes from the people who contribute code. If you want to help here, you can contribute your own code, or help us debug the existing code, take care of bit-rot etc.
Your Own Code
Anything you write using GNU Radio might be of interest! If you've written software, libs or even tutorials, tell us about it on the mailing list, publish the code on the web (e.g. on github) and link it on CGRAN .
GNU Radio Core Code
- Definitely read the contributor guide
- Browse through the GitHub issues and PRs within the main git repo
- Write QA code and provide example flowgraphs where they are missing