Bug 3272

At the moment, we have a wiki page to index publicly available layers:

http://www.openembedded.org/wiki/LayerIndex

It would be useful to have a proper database-backed web interface for managing the list of these - we could record more information about each one (such as maintainer information) as well as gathering information from the layers themselves, potentially allowing searching for individual recipes or other information based on the layer content.

The basic implementation would at minimum need to provide the following:

* List of all layers in short form, similar to what the wiki page does at the moment (without needing to log in)
* Login and user registration system
* New layer registration interface with an approval system (i.e. new layers would need to be approved by one of a group of other authorised users)
* Email notification of changes (simplest case, just email a single address and we can use a mailing list; otherwise we could allow users to choose whether or not to recieve notifications)
* Search function
* A backend script to be run on a scheduled basis to clone/fetch each layer and gather information from each one, at minimum:
 * Recipe file names
 * Last commit date

Ideally this would be implemented using Python-based framework such as Django or Flask, then the backend script can access the metadata or otherwise make use of bitbake code and it will be more easily maintainable by people familiar with our build system.