[sleuthkit-developers] Open Source Forensics Hack-a-thon
Brought to you by:
carrier
From: Brian C. <ca...@sl...> - 2012-03-30 19:06:21
|
We're thinking about hosting an open source forensics hack-a-thon along with the Sleuth Kit and Open Source Digital Forensics Conference (http://www.osdfcon.org/2012). But, we want to know how many engineers we can expect to participate. E-mail hac...@os... if you would be interested (details are below). [side note: reminder that submissions for presentations at the conference are due April 16. You don't need to submit the full presentation, just the abstract and we are interested in presentations from both users and developers] What is a hack-a-thon? A hack-a-thon is when a bunch of developers and non-developers get together to build something in a short amount of time, we're thinking 24 hours. Anyone comes up with an idea for a new feature or tool (i.e. it could be to make modules for the new Sleuth Kit, Autopsy, or other frameworks). Developers pick a team to join (or make their own) and everyone works to build the best solution. The winning teams gets a prize. Some events give out cash, some ipads, etc. We haven't finalized that part yet. We'll provide the food and drinks for the duration. Who is needed? We need non-developers to come up with use cases, ideas, testing, project management, and working on a final presentation. We need developers to come up with use cases and ideas and to write code. Why should you participate? Developers get to learn about new tools and learn about new use cases. Non-developers get to push their ideas for tools that don't exist and get to learn more about the development process. When would it be? After the conference on October 4, 2012. The conference will be on October 3 and tutorials will be held on October 2. What do we want to know? Because the goal of the event is to develop code, having enough developers is crucial to these events and we want to know if we'll have enough. If you would be interested in participating, e-mail hac...@os.... thanks, brian |