[Container-tools] Metadata unrelated to containers

[Tomas Radej]

Hi, all.

There's something that I'd like to discuss for potential inclusion in 
the Nulecule spec: development-related metadata not specifying container 
setup or running. Examples (non exhaustive):

* The app's documentation is written in Sphinx.
   * Makefile for the doc is in a particular location
* The app's source is written in Python
   * Optionally specify where the file with deps is located

This sort of metadata is extremely useful for DevAssistant because it's 
a clear indication that certain generic assistant scripts can be used on 
this app. For example, if the documentation is written in Sphinx, 
DevAssistant can pretty easily invoke the makefile or compile the 
documentation to HTML itself. With the knowledge that the app is written 
in Python, it could e. g. scan the source files for missing dependencies 
and add them to requirements.txt (and possibly to the container's config 
file).

The question is if you consider this kind of information useful enough 
outside DevAssistant that it would justify adding (a category for) it to 
the spec (optional, of course). If not, we'll simply add it to the 
metadata:devassistant mapping and be done with it.

Ideas?

Thanks, Tomas Radej a.k.a. Sheldon