HowToGetInvolved: Difference between revisions

From GNU Radio
Jump to navigation Jump to search
(Imported from Redmine)
 
(Add section on Documentation)
 
(20 intermediate revisions by 3 users not shown)
Line 1: Line 1:
= How can I get involved with GNU Radio? =
* Chat with us on our [https://chat.gnuradio.org Matrix Server] (or using our [[Chat|IRC Bridge]])
 
* Participate on the [[MailingLists|mailing list]]
Getting involved doesn't necessarily mean lots of work, just active participation.
 
Of course, if you want to contribute code, that's great!
 
== Easy things you can do ==
 
* 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]].
* Participate on the [[MailingLists|mailing list]] and on [[IRC]], help answer peoples questions
* 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.
* Become a mentor for the Google summer of code
* Become a mentor for the [[GSoC|Google Summer of Code]]
* Find small bugs (e.g. through Coverity) and fix them
* 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.
* We have a [[Calendar]] containing monthly [[DevelopersCalls|developer calls]] and other events


== Coding and debugging ==
== Coding and debugging ==
Line 18: Line 13:
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.
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 ===
=== 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 [http://cgran.org/ CGRAN] .
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 [http://cgran.org/ CGRAN] .
Line 25: Line 20:


* Definitely read the [[Development|contributor guide]]
* Definitely read the [[Development|contributor guide]]
* To figure out what needs doing, a good read is [http://gnuradio.org/redmine/attachments/download/253/01-corgan-contributing-to-gnu-radio.pdf Johnathan's presentation from GRCon 2011]
* Browse through the GitHub issues and PRs within the main [https://github.com/gnuradio/gnuradio git repo]
* Check our [http://jenkins.gnuradio.org/jenkins/job/GNURadio-master/ integration server] and our [https://scan.coverity.com/projects static code analysis], our goal is it to always reduce the number of warnings, FIXMEs and TODOs.
* Write QA code and provide example flowgraphs where they are missing
* Write QA codes where it is missing
 
== Documentation ==
 
Without documentation, the GNU Radio toolkit would be very difficult to learn and use. There are many areas where the documentation can be completed and expanded.
 
=== Block docs ===
 
In GNU Radio, a block is a functional item which processes data. Currently there are more than 480 blocks. The [https://wiki.gnuradio.org/index.php/Category:Block_Docs Block Docs] index has a page for each block, describing it's function and use. Many of the block pages have incomplete information, needing example flowgraphs, links to the source code, and other items.
 
=== Tutorials ===
 
There are many good [[Tutorials]] for beginner level through advanced developers. However, new releases of the GNU Radio code may impact details in the existing tutorials. So the tutorials need review and updating as new software is released. Additional tutorials are also helpful.
 
=== How to get started ===
 
* Although anyone can edit the Wiki, if you are going to do much work on it, you should get a Wiki account. At the top right of any of the wiki pages (including this one), click on "Request account" and fill in the fields. It may take a day or two for a moderator to approve you.
* Learn to use [https://www.mediawiki.org/wiki/MediaWiki MediaWiki] (the markup language for the wiki).
* Choose a block which needs work and update it!

Latest revision as of 17:31, 15 October 2022

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

Documentation

Without documentation, the GNU Radio toolkit would be very difficult to learn and use. There are many areas where the documentation can be completed and expanded.

Block docs

In GNU Radio, a block is a functional item which processes data. Currently there are more than 480 blocks. The Block Docs index has a page for each block, describing it's function and use. Many of the block pages have incomplete information, needing example flowgraphs, links to the source code, and other items.

Tutorials

There are many good Tutorials for beginner level through advanced developers. However, new releases of the GNU Radio code may impact details in the existing tutorials. So the tutorials need review and updating as new software is released. Additional tutorials are also helpful.

How to get started

  • Although anyone can edit the Wiki, if you are going to do much work on it, you should get a Wiki account. At the top right of any of the wiki pages (including this one), click on "Request account" and fill in the fields. It may take a day or two for a moderator to approve you.
  • Learn to use MediaWiki (the markup language for the wiki).
  • Choose a block which needs work and update it!