Create a community collection of configuration and identifiers

[ITAYC0HEN]

I think it is a good idea to have a community-driven collection of Identifiers and Configurations for Karta. When such a collection get bigger, it will increase the chances that the configuration you are looking for was already created by a community member.

I think that such a solution can be achieved in several ways:

1. Encourage users to push their configs and identifier scripts to Karta/configs and Karta/src/libs
2. Create a new repository to store configs and libs, and use it as a submodule from inside Karta
3. Create an external repository (similar to FLIRTDB) to store the configs and identifiers.

[chkp-eyalit]

Sounds like a good idea. I was hoping that calling researchers to collaborate on this, both in conferences and in twitter, will be enough. But thus far we received 0 commits / pull requests with added configurations / identifiers.

The point in presenting this plugin in conferences was exactly this, to get community collaboration to build a massive collection of identifiers / configurations. Sadly, I already tried the first option, and options 2 and 3 would only make sense once people start submitting new things, otherwise the ROI would be negative.

[ITAYC0HEN]

For (1) this can be a step in the doc. Just after compiling the config and identifier. Something like "Please consider to submit the config you created to the community collection of configurations and fingerprints."

Having a repository that aims to collect all the configurations feels more welcoming to me than pushing new configuration to the main repository

[chkp-eyalit]

For some reason readthedocs fails when I try to build the new documentation. Hopefully it will get fixed in the next few days so the new docs will include this new update.

[chkp-eyalit]

Fixed the docs in #40, now readthedocs is updated to reflect the call to share with us the added support / configs.

[gitmesam]

On the one hand, thank you very much for such a great plugin. What this plugin does - I've been doing it by hand for the last 15 years. And on the other hand, you "revealed" one of my professional secrets. Now, the art of reverse engineering - will no longer be so respected, because the threshold of entry - will be significantly reduced. Perhaps some things are better never to be made public at all.