Re: [Vol-dev] Contribution
1 Mar
2013
1 Mar
'13
11:15 a.m.
Joel,
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
On Tue, Feb 26, 2013 at 5:05 PM, Joel Anderson <joelr.anders(a)gmail.com>wrote:
Hello Volatility Devs,
I'm currently a student in a Digital Forensics class. We have used your
wonderful tool to do memory dumps. We now have a project to contribute to
an open source project. I was wondering if there was anything that I could
contribute to the Volatility project. My strong point isn't in programming,
but I have had an introduction to it. I don't know if there's any
documentation you'd like to have updated, or whatever. I look forward to a
response.
Warm Regards,
*Joel Anderson*
Brigham Young University - April 2014
Masters of Information Systems Management
(208) 570-7253
_______________________________________________
Vol-dev mailing list
Vol-dev(a)volatilityfoundation.org
http://lists.volatilityfoundation.org/mailman/listinfo/vol-dev
Attachments:
- attachment.html (text/html — 2.3 KB)