(Semi) open licenci...
 
Notifications
Clear all

(Semi) open licencing LE build computer forensics framework

1 Posts
1 Users
0 Likes
258 Views
(@capibara)
Posts: 2
New Member
Topic starter
 

The law enforcement agency that I work for has over the last few years build a modulare scalable and fault tolerant framework/architecture for computer forensics.
Now the time has come that the project is nearing its completion, and needs to be transfered into a support only stage.
Given that it was build by a R&D section that does not have support as one of its core tasks, mention has been made to sell
the architecture to a commercial party.
Given the open nature of the design of the computer forensics architecture we build, I am trying to gather some arguments and/or alternatives to this that
would allow the architecture to retain its open nature while still cost efficiently transfering an effective and sufficiently reactive support to an external party.
Management currently views the architecture mainly as an internal product, and thus I also could use some examples of (forensic) tools build by law enforcement that were released to a broader public in a way that actualy beneffited the agency that build the product. I tried to make the argument that releasing it either as completely open source, or as a law enforcement only
variant op open source licencing would result in modules getting build and made available by other LEAs that would use our architecture, but withour real live examples of such, I dont have much of an argument.
If anyone could give me some help in writing my report sugesting either open source release or LEA only open release if possible combined with transfer of support to external parties, that would be a great help.

 
Posted : 17/04/2006 4:32 pm
Share: