It's a nice interface, would be interesting to give potential users an impression before they compile it on their own.

![Screenshot_2019-07-04 OpenWrt - oui(4)](https://user-images.githubusercontent.com/16000931/60661188-bf48ad80-9e59-11e9-8520-cefcd043c

Can you write a little technical documentation, or maybe a schema explaining how it works, what are software used for ?

Fix statement condition on "Install custom OpenWISP 2 Python packages" task in pip.yml:

TASK [openwisp.openwisp2 : Install custom OpenWISP 2 Python packages] **********
[DEPRECATION WARNING]: evaluating 'openwisp2_python_packages' as a bare 
variable, this behaviour will go away and you might need to add |bool to the 
expression in the future. Also see CONDITIONAL_BARE_VARS configur

Reserved for Google Code-In 2020.

Depends on openwisp/openwisp-utils#98.

Use the decorators mentioned in the issue linked above to silence the output of noisy tests.

I just noticed the template tags featue (#34) is not mentioned in the README.

It would be appropiate to mention the config option in the beginning of the README as well as dedicate a brief section to explain how it works.

Reserved for Google Code-In 2020.

Depends on openwisp/openwisp-utils#98.

Use the decorators mentioned in the issue linked above to silence the output of noisy tests.

The Extension Registry is just a stub.

Two things must be done asap:

• add existing extensions
• define how to register extensions

building "testing" or "unstable" libremesh via chef is using 18-06-1 (or master) openwrt. but some package-repos are still with 17.06-brunch. please change!

see f.i. https://chef.libremesh.org/download/lime/unstable/ar71xx/generic/tl-wdr3600-v1/eebcbf571383e0e//buildlog-5fcf314cbc5f146.txt

IMAGE_HASH=5fcf314cbc5f146
BIN_DIR=/tmp/tmp_lyvy_kb
J=4
REPOS=src/gz openwrt_core http://downloads.o