Code contributions are the best way to get formally recognized (in CREDITS.txt, the wiki, release notes, etc). If you've had an intro to programming, I'd encourage you to look through some of the volatility source code (while reading along with the existing documentation on our wiki) and try to become familiar with how things work and what might be necessary to implement new ideas that you may have. You could always test install procedures, verify commands work on various types of memory images, and work on some unfinished documentation, but really that's quite boring and anyone could do it. I'd suggest you challenge yourself and spend your time learning how to do something new. 

MHL