4 dec 2012 kl. 00:02 skrev Ovidiu Sas osas@voipembedded.com:
On Mon, Dec 3, 2012 at 5:44 PM, Daniel-Constantin Mierla miconda@gmail.com wrote:
On 12/3/12 11:36 PM, Ovidiu Sas wrote:
Then we should move all config files from examples into the relevant module directory?
At least a cleanup should be done. The fact is that the examples directory it was not really kept up to date. I noticed that you did an addition quite recently and wanted to discuss, just that the task didn't reach the top of my stack yet, due to traveling.
From my point of view, examples folder is not the right place because is not really visible from documentation, many peoples don't have a clue about it and one has to go to sources tree. So I think it would be better if the example config for some module would be reflected directly in the readme docs - people will use it then, either from README or from the web html docs.
I like the idea of having all the examples into one directory (no need to change directory to see examples from other modules). And it also keeps the module source directory cleaner. But maybe that's just me :)
We need a new "core examples" directory. The problem with the old directory is that it is old and filled with stuff that may or may not be relevant for current users.
Module-related examples should go into the module docs first. There might be cases where there are many modules involved in an example, like with the presence solutions, that we decide to create a shared example.
Daniel - can we create an /etc/examples directory and add current stuff to it for these cases, and then start moving working configurations from /examples to it?
/etc is a directory that usually is included in distributions.
/O