Easiest way to start contributing if you don't have much programming experience

[lynxlynxlynx]

GemRB uses several static analysis tools to help detect new bugs, potential bugs and bad practices.

One of them is Coverity, but it is ran only periodically and current issue count is usually at 0.

Then there is Sonar*, which found a whole other class of issues and suggestions. You can filter out the Confirmed reports to see the ones immediately actionable.

Whichever service and class of problems you choose to work on, please note it here. Some are pointless to address (eg. most of our strlen uses are fine, so that's low priority), especially some related to style or naming. Additionally some are false positives (nothing to fix) and just haven't been marked as such yet.

You are still most welcome to read the contributing guidelines for further ideas and a better grasp on how GemRB is developed.