[prev in list] [next in list] [prev in thread] [next in thread] 

List:       serdev
Subject:    Re: [sr-dev] [kamailio/kamailio] kamailio KEMI sipt module (Issue #3264)
From:       Daniel-Constantin Mierla <notifications () github ! com>
Date:       2022-10-26 17:21:42
Message-ID: kamailio/kamailio/issues/3264/1292365248 () github ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


There is no task to export old functions to KEMI, it is mainly done based on the \
needs of the developers. I exported most of the functions to the common modules and \
the ones I use. But there are still modules without exports to kemi.

The only exceptional rule is that an export to KEMI of an old function can be \
backported to latest stable branch (obviously if it is not very intrusive by changing \
radically the internals of the module, which should not be the case probably for 99% \
of the functions).

If you want to help exporting sipt to kemi, it will be appreciated, just make a PR \
and it will be reviewed and merged if al ok. Developers will help you along the way \
with comments and suggestions for the PR.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3264#issuecomment-1292365248
You are receiving this because you are subscribed to this thread.

Message ID: <kamailio/kamailio/issues/3264/1292365248@github.com>


[Attachment #5 (text/html)]

<p></p>
<p dir="auto">There is no task to export old functions to KEMI, it is mainly done \
based on the needs of the developers. I exported most of the functions to the common \
modules and the ones I use. But there are still modules without exports to kemi.</p> \
<p dir="auto">The only exceptional rule is that an export to KEMI of an old function \
can be backported to latest stable branch (obviously if it is not very intrusive by \
changing radically the internals of the module, which should not be the case probably \
for 99% of the functions).</p> <p dir="auto">If you want to help exporting sipt to \
kemi, it will be appreciated, just make a PR and it will be reviewed and merged if al \
ok. Developers will help you along the way with comments and suggestions for the \
PR.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br \
/>Reply to this email directly, <a \
href="https://github.com/kamailio/kamailio/issues/3264#issuecomment-1292365248">view \
it on GitHub</a>, or <a \
href="https://github.com/notifications/unsubscribe-auth/ABO7UZI4LDJG5G4DQFMLFGTWFFSCNANCNFSM6AAAAAAREVXT5I">unsubscribe</a>.<br \
/>You are receiving this because you are subscribed to this thread.<img \
src="https://github.com/notifications/beacon/ABO7UZOF4DGKT73IJRV6UOTWFFSCNA5CNFSM6AAAA \
AAREVXT5KWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSNA7W4A.gif" \
height="1" width="1" alt="" /><span style="color: transparent; font-size: 0; display: \
none; visibility: hidden; overflow: hidden; opacity: 0; width: 0; height: 0; \
max-width: 0; max-height: 0; mso-hide: all">Message ID: \
<span>&lt;kamailio/kamailio/issues/3264/1292365248</span><span>@</span><span>github</span><span>.</span><span>com&gt;</span></span></p>
 <script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/kamailio/kamailio/issues/3264#issuecomment-1292365248",
"url": "https://github.com/kamailio/kamailio/issues/3264#issuecomment-1292365248",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>



_______________________________________________
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev


[prev in list] [next in list] [prev in thread] [next in thread]