Hi Timo, thanks, that is very useful! I was playing with the idea of developing it for using in small deployments and embedded devices, but couldn't find any time for it ... To get the code in the repository, there are some things that need to be sorted out: - code reviewing - from my point of view it looks ok, only readme (and associated docbook files) is missing, but since the module is not exporting parameters/functions to config, that should be straightforward to do, basically a short description about the purpose of the module - the new module must have a maintainer for one year. This is to ensure the others can ask questions to somebody in case of troubles and get to know the module properly to be maintained commonly afterwards if the initial maintainer is no longer active. Are you willing to become the maintainer? If yes, we will grant you developer access so you can handle the module directly in the git repository - I will send you another email in this case. If you don't, then maybe another developer volunteers for it Depending on whether you want to maintain the module or not, we should get your new module first in a private branch or project's tracker so other developers can look at it if they want. Cheers, Daniel On 4/4/11 11:49 AM, Timo Teräs wrote: ... -- Daniel-Constantin Mierla http://www.asipto.com