Better integration of community signatures

[botherder]

At the moment, community signatures are stored in a separate repository. I'm starting to grow the feeling that people are not paying much attention to the documentation section that deals with them.
I imagine that a lot of people are missing out on the presence of the signatures and the existence of the utils/community.py script.

We should brainstorm on what could be possible ways to foster the creation of community signatures and improving the integration so that it becomes ideally seamless to the users.

[KillerInstinct]

Perhaps add a git-check to see if we match the latest commit for the community modules, throw it in lib/cuckoo/core/startup.py

Could make this configurable, similarly to the "check for updates" toggle.

[botherder]

That could be a good idea.

[jbremer]

In development mode the community stuff is also required to fetch the latest monitoring binaries etc (i.e., to be able to analyze any sample at all).
We could leverage this to have people also download the latest signatures etc, but instead of having people do it manually, I think a flag to automatically update would be neat.
Thoughts?

[jbremer]

Anyone up for implementing the Community version check feature?