(Redmine issue: #3361)

* Added section for useful links and references.
* Created substitution to create direct link to Git revision page in our project support system.
* Created substitution for easy generation of documentation links.

(Redmine issue: #3361)

This commit represents huge amount of work and introduces new Python-based version of Hawat web user interface for Mentat system. It is built on top of the great Flask framework. Currently it is still work in progress and many features are implemented only as dummy stubs, however the core functionality is almost finished. Following is a list of current key features:

  * Focus on modular architecture using Flask`s blueprint feature.
  * Multi-layered configurability (defaults, multiple file overrides).
  * Plugin system.
  * Internationalization support.
  * Support for multiple authentication systems.

This commit provides working albeit hollow starting point for future web interface development. IT IS NOT READY FOR PRODUCTION USAGE!!!

(Redmine issue: #3734,#3361)

This means that there is one less place to manually increment the version number when deploying new package. There still remains the issue with making the same thing for Grunt configuration. (Redmine issue: #3361,#3387)

(Redmine issue: #3387)

(Redmine issue: #3387)

(Redmine issue: #3387)

(Redmine issue: #3387)

(Redmine issue: #3387)

(Redmine issue: #3387)

Migration, refactoring and code style unification to support latest PyZenKit and Pynspect libraries.

This huge update represents a lot of work on many parts of the system. After major upgrade in PyZenKit and Pynspect libraries it was necessary to bring this project up to date. There were many changes in the code, lot of refactoring and while all this was done, code quality was improved, documentation written and unit tests modified. Many of these changes simply make sure, that the code works with latest versions of both libraries. This commit is supposed to be a single major feature upgrade, after this only smaller commits will follow to polish this huge amount of work.

(Redmine issues: #3374, #1017, #3361, #3387, #3443)

Some documentation source files had to be renamed to enable better integration with automated buildbot system. Documentation for submodules was included into overall project documentation. (Redmine issue: #3361)

Build number from Buildbot system now gets propagated to Grunt and autogenerated documentation. This feature is intended to be used for development (unstable) builds to somehow autoincrement the package version number. For production distributions this will be skipped and developer still has to set the desired version number manually. (Redmine issues: #3361 and #3387)

Version number gets propagated into autogenerated documentation. Buildbot system is responsible for generating appropriate metadata file. (Redmine issues: #3361 and #3387)

Generated documentation now contains information about distribution and revision, from which it was generated. This information is presented on title page a buildbot system provides correct values during build process. This was user can clearly see, which documentation version for which distribution (production, development) he/she is currently browsing. (Redmine issues: #3361 and #3387)

(Redmine issue: #3361)

Project documentation will now be (partly) autogenerated out of the module source code. The environment was prepared and first modules were added into documentation. Guide to generate the documentation locally was added to Redmine project wiki page (Development cheat sheet), so that the documentation is available to developers before it will be published on-line. (Redmine issue: #3361)