[NTLK] ROM Disassembly online?

[Jake Bordens]

>But what I still really need is someone to tell me what is the most important thing I ought to be doing right now to move Matthias toward the goal of completing his static analysis of the entire ROM!  

I'll take a stab and Matthias can correct me. 

I think his vision is an app that has 2 "databases"-- a "public database" and a "private database."

The public database would contain all the metadata, comments, and annotation about the ROM as entered and developed by those working on the reverse engineering.  The database can be posted to github and updated by anyone.  Crowdsourced if you will.  Any metadata needed to understand, decode, decompile, or disassemble could be held in the public database.

The private database would contain the ROM and derived information from the ROM (disassembly and decompilation).  Perhaps it would have decoded assets such as images, fonts, and sound files eventually as well.  This wouldn't be public, since it is under copyright.

Ideally, with the ROM and the current version of the community "public" database, one would be able to regenerate the private database.   I guess what I'm calling the "private database" is more a cache of decompiled/disassembled code and assets. 

It doesn't necessarily need to be a "database", it could be text files or something more human readable and diff-able, but I'm just using the word as a concept.

Anyhow, that's my interpretation.  We want to be able to collaborate on the public stuff, yet have a way to generate the exact same "private database" without sharing it directly between the developers in the community.