HowToGetInvolved: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(Adding GNU Radio Calendar link to page.) |
||
Line 7: | Line 7: | ||
* Find small bugs and fix them, or help fix known bugs posted to our [https://github.com/gnuradio/gnuradio/issues Github Issues page]. | * Find small bugs and fix them, or help fix known bugs posted to our [https://github.com/gnuradio/gnuradio/issues Github Issues page]. | ||
* Test [https://github.com/gnuradio/gnuradio/pulls Pull Requests] people have submitted, and provide feedback/input. | * Test [https://github.com/gnuradio/gnuradio/pulls Pull Requests] people have submitted, and provide feedback/input. | ||
* We have a [[Calendar]] containing monthly developer calls and other events | |||
== Coding and debugging == | == Coding and debugging == |
Revision as of 23:52, 11 January 2021
- Chat with us on our Matrix Server (or using our IRC Bridge)
- Participate on the mailing list
- 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 and fix them, or help fix known bugs posted to our Github Issues page.
- Test Pull Requests people have submitted, and provide feedback/input.
- We have a Calendar containing monthly developer calls and other events
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