Difference between revisions of "Trackers"
m (Protected "Trackers" ([edit=sysop] (indefinite) [move=sysop] (indefinite))) |
(Updated to ref new trackers.) |
||
| Line 1: | Line 1: | ||
| − | [[TSK]] and [[Autopsy]] use | + | [[TSK]] and [[Autopsy]] use online systems to keep track of bugs and feature requests. Currently, we use two different systems, depending on the age of the project. Older projects use the SourceForge trackers and newer projects use Github Issues. |
| − | + | Both systems allow bugs and feature requests to be created and people can view and comment on them. Once the bug is fixed or a feature request is satisfied, the artifact is "closed". You will need a SourceForge or Github account to edit or create artifacts. | |
| − | + | ||
| − | + | = Sleuth Kit = | |
| + | The Sleuth Kit is organized into two components. Sleuth Kit Core is the volume and file system analysis functionality that has been around for a long time. It uses the trackers at Source Forge: | ||
* [http://sourceforge.net/tracker2/?group_id=55685&atid=477889 Sleuth Kit Bug Tracker] | * [http://sourceforge.net/tracker2/?group_id=55685&atid=477889 Sleuth Kit Bug Tracker] | ||
| − | * [http://sourceforge.net/ | + | * [http://sourceforge.net/tracker2/?group_id=55685&atid=477892 Sleuth Kit Feature Request Tracker] |
| − | + | The newer [[TSK Framework]] uses GitHub for issues. Both feature requests and bugs are tracked here. | |
| − | The feature | + | * [http://github.com/sleuthkit/sleuthkit/issues Sleuth Kit Framework Issues] |
| + | Each module in the framework also has its own issue tracker. Here are a list of some of them: | ||
| + | * TO ADD | ||
| + | |||
| + | = Autopsy = | ||
| + | [[Autopsy 3]] uses GitHub to track issues. Both feature requests and bugs are tracked here. | ||
| + | * [http://github.com/sleuthkit/autopsy/issues Autopsy Issues] | ||
| + | |||
| + | Autopsy 2 was maintained at SourceForge. For legacy reasons, here are the links: | ||
| + | * [http://sourceforge.net/tracker2/?group_id=55687&atid=477897 Autopsy Bug Tracker] | ||
* [http://sourceforge.net/tracker2/?group_id=55687&atid=477900 Autopsy Feature Request Tracker] | * [http://sourceforge.net/tracker2/?group_id=55687&atid=477900 Autopsy Feature Request Tracker] | ||
| − | * [http://sourceforge.net/ | + | |
| + | = mac-robber = | ||
| + | [[mac-robber]] uses SourceForge to track issues and feature requests. | ||
| + | * [http://sourceforge.net/tracker/?group_id=77673&atid=550912 mac-robber Bug Tracker] | ||
* [http://sourceforge.net/tracker/?group_id=77673&atid=550915 mac-robber Feature Request Tracker] | * [http://sourceforge.net/tracker/?group_id=77673&atid=550915 mac-robber Feature Request Tracker] | ||
Revision as of 14:07, 5 June 2012
TSK and Autopsy use online systems to keep track of bugs and feature requests. Currently, we use two different systems, depending on the age of the project. Older projects use the SourceForge trackers and newer projects use Github Issues.
Both systems allow bugs and feature requests to be created and people can view and comment on them. Once the bug is fixed or a feature request is satisfied, the artifact is "closed". You will need a SourceForge or Github account to edit or create artifacts.
Sleuth Kit
The Sleuth Kit is organized into two components. Sleuth Kit Core is the volume and file system analysis functionality that has been around for a long time. It uses the trackers at Source Forge:
The newer TSK Framework uses GitHub for issues. Both feature requests and bugs are tracked here.
Each module in the framework also has its own issue tracker. Here are a list of some of them:
- TO ADD
Autopsy
Autopsy 3 uses GitHub to track issues. Both feature requests and bugs are tracked here.
Autopsy 2 was maintained at SourceForge. For legacy reasons, here are the links:
mac-robber
mac-robber uses SourceForge to track issues and feature requests.
