How To Get Involved
Getting involved doesn't always require programming or development efforts. There are many ways to get involved depending on your current skill set, interests, and availability.
Contribute code: Whether you have new plugins, patches to existing plugins, or tools you've built on top of The Volatility Framework, we encourage you to share them and give back to the community. Your name will go in the credits file and release documentation. Furthermore, your name stays in the code.
Report bugs: If you encounter an error or unexpected condition, please report it by filling out a bug report in our issue tracker. This may sound insignificant, but if you find a bug, its likely to manifest for other people as well, so helping us identify problems as early as possible is very vaulable.
Create documentation: We always welcome documentation, because too much knowledge can never be a bad thing. If you've found a new tip or trick that your peers can benefit from, write it up! This can be in the form of tutorials, installation guides, or API documentation. We'll link to your page from the community document aggregator.
Publish analysis: Its very likely that you've used Volatility in ways other people would never think about. You've analyzed different malware samples and you've been involved with investigations focusing on unique threat groups. One of the strongest ways you can help other analysts is by example--show them how you combine tools with experience to make a case successful.
Communicate with your peers: Sometimes asking a question is as vaulable as providing an answer. Whether you have Q's or A's, the Vol-Users mailing list or IRC (#volatility on freenode) is a great way to reach thousands of your peers who share the same interests.
Design challenges: There's no doubt - people in our industry love a challenge. Although it takes a good amount of dedication, creating a practical memory analysis challenge can also be very rewarding (for you and the participants). Its also a good way for you to meet similarly-skilled analysts who you can team up with to do great things.
Submit memory samples: If you have memory dumps (clean or infected) and they can be shared publicly, let us know. People are always looking for samples to compare with their own, or to use for verifying plugin support. Its also nice to have access to systems with different configurations (i.e. hardware, software, etc.)
Attend conferences: The Volatility development team organizes an annual conference called Open Memory Forensics Workshop (OMFW). By attending, you'll not only get exposed to the industry's cutting-edge research, but you'll get to meet the team and all attendees in person.
Donate: The Volatility Foundation also welcomes monetary donations. Every size contribution helps in our mission of improving, promoting, and steering the development of Volatility and fighting to protect the rights of open source forensics developers. Thank you!