Difference between revisions of "Autopsy Developer's Guide"
(Added Autopsy 3 links) |
|||
Line 16: | Line 16: | ||
= Autopsy 3.0 Design = | = Autopsy 3.0 Design = | ||
Version 3 of Autopsy is a complete rewrite. Find the design docs in this section. | Version 3 of Autopsy is a complete rewrite. Find the design docs in this section. | ||
− | * [[Autopsy 3 Nodes | + | * [[Autopsy 3 Nodes and Data Flow]] |
− | + | ||
* Creating interfaces | * Creating interfaces | ||
** [[Creating a Data Explorer]] | ** [[Creating a Data Explorer]] | ||
** [[Creating a Data Result Viewer]] | ** [[Creating a Data Result Viewer]] | ||
** [[Creating a Data Content Viewer]] | ** [[Creating a Data Content Viewer]] |
Revision as of 12:49, 25 October 2011
This page contains technical information on developing code for Autopsy.
This page is a work in progress and more information will be posted. Here are some starting points.
- The Developer Guidelines define how code and patches can be submitted and incorporated into the distribution.
- The sleuthkit-developers list exists to discuss the development of the tools. Subscribe to ask and answer questions.
- If you want to contribute documentation, then refer to the Support page.
What To Do?
If you are looking for ideas on how you can contribute, then you may want to refer to the feature request and bug trackers. They contain ideas that people have for the tools or bugs that need to be fixed.
Technical Details
The source code is stored in a Subversion repository. You can get the latest source tree by doing a checkout from http://svn.sleuthkit.org/repos/autopsy/. The latest code is in the trunk directory. The branches directory contains branches for minor release versions so that bugs can be fixed there for bug releases. The tags directory contains tags for each release. Note that this repository was created right before the 2.20 release and does not contain the previous CVS history.
More details in this section will be defined...
Autopsy 3.0 Design
Version 3 of Autopsy is a complete rewrite. Find the design docs in this section.