[Serdev] CVS module contrib

[Greger V. Teigre]

I have the following suggestions:
1. All modules in contrib must have an active maintainer with a README file 
that is accurate and complete; inactive modules are removed
2. Makefile is updated to allow compilation and installation of individual 
contrib modules. Default should be NOT to include any contrib modules. All 
contrib modules should show a warning when compiling about the unofficial 
status
3. contrib should be a place for two types of modules:
a) modules in waiting for inclusion among the official modules (awaiting 
testing, qos, etc) and
b) modules contributed, but that are not of enough general interest to be 
included in the official modules tree (or for some reason cannot be 
supported at the level expected for an official module)
4. Modules with core dependencies (AFAIK, TLS is dependent on some 
dictionary changes) can only be included in a branch where these updates 
have been done OR the module has a README file with branch specific 
information on how to patch the core tree before compiling the module.  A 
compile should also generate an extra warning "PATCHING REQUIRED"

So contrib dir will then be a combination of experimental and contributed, 
unofficial modules. I agree that contrib may be confusing, but so is 
experimental...

As for 4, I'm not sure if I think it's a good idea, but I wanted to launch 
it as an idea. We already have a case:TLS
g-)


Cesc Santasusana wrote:
> If TLS was a standalone process running independently ... but it is
> too
> integrated (for me), to place it somewhere else ... but hey, this is
> just my opinion.
> I do not see why it should be separated from the core SER.
> If you are worried that for paying costumers it gets messed up, it
> can be
> place in /tls_free folder, then before compile just needs a soft link
> like:
>> ln -s ser_tls tls
>
> As long as people know about the existence of TLS code for SER and
> know how to find it (a mention in the webpage then would be of first
> order relevance), it is good with me.
>
> my 2 cents ...
>
> Cesc
>
>
> Unclassified
>
>
>>>> Andrei Pelinescu-Onciul <andrei at iptel.org> 06/06/05 02:07PM >>>
> On Jun 06, 2005 at 13:14, Cesc Santasusana
> <cesc.santasusana at nl.thalesgroup..com> wrote:
>> It is a good idea ...
>>
>> One of the first ones could be TLS-free stuff ... i have improved it
>> a little bit more (more configuration options from the script file
>> not used in the first releases) and some fixes to make it compile in
>> openssl v0.9.6 (tested on 0.9.7 and 0.9.6, i have
>> not tried earlier version ... anyway they'd better not be used).
>>
>> Even better would be to include it by default in its original folder
>> ( ...../tls ), but if what it takes to be included and mantaiined
>> somehow other than by hand is
>> to be put in the contrib module ... so be it.
>
> I would suggest to have it separatley in a /ser_tls dir at the same
> level as ser and rtpproxy.
>
> A user would have to check it separately in his sip_router tree and mv
> ser_tls tls. He would need to do this only the first time.
>
>
> Andrei
>
> _______________________________________________
> Serdev mailing list
> serdev at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serdev