Module: kamailio
Branch: master
Commit: 9eeab4396d8ec57781244ab80c4a96539d7338ec
URL: https://github.com/kamailio/kamailio/commit/9eeab4396d8ec57781244ab80c4a965…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2023-11-28T10:20:41+01:00
jansson: docs updated for jansson_get_field()
---
Modified: src/modules/jansson/doc/jansson_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/9eeab4396d8ec57781244ab80c4a965…
Patch: https://github.com/kamailio/kamailio/commit/9eeab4396d8ec57781244ab80c4a965…
---
diff --git a/src/modules/jansson/doc/jansson_admin.xml b/src/modules/jansson/doc/jansson_admin.xml
index debc9cc5a19..daa5e9ea51e 100644
--- a/src/modules/jansson/doc/jansson_admin.xml
+++ b/src/modules/jansson/doc/jansson_admin.xml
@@ -56,10 +56,16 @@
<title>Functions</title>
<section id="jansson.f.jansson_get">
<title>
- <function moreinfo="none">jansson_get(key/path, src, dst)</function>
+ <function moreinfo="none">jansson_get(path, src, dst)</function>
</title>
<para>
- Copy the value at the location 'path' from the json object 'src' and store it in pvar 'dst'.
+ Copy the value at the location 'path' from the json object 'src'
+ and store it in variable 'dst'. The path can also be a simple field name
+ (a key), if it does not include any path separator. To retrieve the
+ value of a field that includes path separators in the name, use
+ jansson_get_field().
+ </para>
+ <para>
The 'src' can be a static string or a dynamic string with variables.
</para>
<para>
@@ -71,7 +77,7 @@
</para>
<para>
The function can put a string, integer, null, or new json string into destination.
- If the key/path can't be found in the JSON data structure, the pvar is not changed.
+ If the path can't be found in the JSON data structure, the pvar is not changed.
If it had a previous
value, that value remains unchanged.
</para>
@@ -280,22 +286,27 @@ jansson_xencode("a", "$var(js)");
</section>
<section id="jansson.f.jansson_get_field">
<title>
- <function moreinfo="none">jansson_get_field(src, field_name, dst)</function>
+ <function moreinfo="none">jansson_get_field(field_name, src, dst)</function>
</title>
<para>
- Copy field 'field_name' from json object 'src' and store it in pvar 'dst'.
+ Copy the value of the field 'field_name' from json object 'src'
+ and store it in pvar 'dst'. The field name is not evaluated as JSON
+ path, therefore it has a different behaviour than jansson_get() and
+ can be used when the field name contains path delimiters.
</para>
<para>
- <emphasis>This function is deprecated</emphasis> but kept for backwards compatibility.
- Right now it is just a wrapper around <function>jansson_get</function>, and its
- functionality is the same.
+ Note that till version 5.7.x, this function was similar to jansson_get(),
+ after that its behaviour changed to work as described above. Also,
+ the order of parameters changed.
</para>
<example>
<title><function>jansson_get_field</function> usage</title>
<programlisting format="linespecific">
...
-jansson_get_field("{'foo':'bar'}", "foo", "$var(foo)");
+jansson_get_field("foo", "{'foo':'bar'}", "$var(foo)");
xlog("foo is $var(foo)");
+jansson_get_field("foo.foz", "{'foo.foz':'bar.buz'}", "$var(foofoz)");
+xlog("foo.foz is $var(foofoz)");
...
</programlisting>
</example>
Hello,
during the Kamailio Development Meeting that took place in Dusseldorf
earlier this month, one topic was related to administrative tasks
related to project development and management, how to
simplify/automatize such tasks.
To reduce the work load on volunteering contributors, GitHub Actions
were already used for various tasks related to project development and
management (e.g., automatic builds on commits and pull requests to
detect compile errors or code formatting mistakes).
In Dusseldorf another task was configured to be managed with GitHub
Actions, respectively the check of open issues and pull requests to
evaluate the interest of submitters, developers and community users to
pursue them. If there is no activity on an issue (potential bug or
feature request) or a pull request, after 6 weeks it is marked with the
label `stale`. After two more weeks of no activity, the issue or the
pull request is marked with the label `expired` and closed. Note that
any comment postpones the expire timeline, being considered that there
is interest in pursuing the issue or the pull request.
Requests for features were already treated in this way: if nobody
commits to implement it, it can be closed after one month, but it needed
manual work and many were still kept open. Potential bug reports that
become very old are hard to tackle if the source code changes or new
major releases are out, they might even not be valid anymore.
Anyhow, this automatic operations can be reverted if there is still
interest in pursuing the specific issues or pull requests. A registered
developer can remove labels and reopen a closed issue or pull request.
The non-registered-developer contributors have to make a comment that
includes the token `/notstale` to remove the label `stale` or includes
the token `/notexpired` to reopen a closed item.
This new kind of automatic task management might add a little
inconvenience because one has to restate the interest from time to time
for those items that could not be addressed. However, considering that
Kamailio is an open source collaborative project, in order to be fair
for those that volunteer to spend time and resources for development of
Kamailio, also the users/submitters have to stay engaged, not just
report and forget about.
The process to automatize tasks related to Kamailio development and
administration is work in progress. Everything can be adjusted based on
feedback (e.g., time lines), feel free to suggest improvements or new
solutions to make things easier for everyone within the project ecosystem.
Cheers,
Daniel
--
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training -- asipto.com
Module: kamailio
Branch: master
Commit: 4840ea7536610d07ad6fda76da60ded04dfeabc7
URL: https://github.com/kamailio/kamailio/commit/4840ea7536610d07ad6fda76da60ded…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2023-11-27T19:23:36+01:00
.github/CONTRIBUTING.md: section for issue and pr automatic management
---
Modified: .github/CONTRIBUTING.md
---
Diff: https://github.com/kamailio/kamailio/commit/4840ea7536610d07ad6fda76da60ded…
Patch: https://github.com/kamailio/kamailio/commit/4840ea7536610d07ad6fda76da60ded…
---
diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
index 2c5d46842b8..e01dd82c3ce 100644
--- a/.github/CONTRIBUTING.md
+++ b/.github/CONTRIBUTING.md
@@ -20,6 +20,7 @@ changes to this document in a pull request.
* [Commit Message Examples](#commit-message-examples)
* [See Also](#see-also)
* [Reporting Issues](#reporting-issues)
+ * [Issue And PR Automatic Management](#issue-and-pr-automatic-management)
* [License](#license)
* [License Of New Code Contributions](#license-of-new-code-contributions)
* [Further Assistance](#further-assistance)
@@ -251,6 +252,32 @@ Note: replace any sensitive information in the content you add to the issue
(e.g., passwords in modparams can be replaced with xyz, each IP address can be
replaced with tokens like a.b.c.d, f.g.h.j).
+## Issue And PR Automatic Management ##
+
+This section presents details about the automatic management of potential bug
+reports and requests for new features using github actions.
+
+Kamailio is an open source collaborative project, in order to be fair for those
+that volunteer to spend time and resources for development of Kamailio, the users
+have to stay engaged, not just report and forget about.
+
+To reduce the work load on volunteering contributors, GitHub Actions are used
+for various tasks related to project development and management (e.g., automatic
+builds on commits and pull requests to detect compile errors or code formatting
+mistakes).
+
+One task managed with GitHub Actions is related to the check of open
+issues and pull requests to evaluate the interest of submitter, developers and
+community users. If there is no activity on an issue (potential bug or feature
+request) or a pull request, after 6 weeks it is marked with the label `stale`.
+After two more weeks of no activity, the issue or the pull request is marked
+with the label `expired` and closed.
+
+A registered developer can remove labels and reopen a closed issue or pull
+request. The other contributors have to make a comment that includes the token
+`/notstale` to remove the label `stale` or includes the token `/notexpired` to
+reopen a closed item.
+
## License ##
Kamailio Main License: *GPLv2*.
Module: kamailio
Branch: master
Commit: 96300556ea4787f6f99926dcc7305ec6e4e3df75
URL: https://github.com/kamailio/kamailio/commit/96300556ea4787f6f99926dcc7305ec…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2023-11-27T17:11:53+01:00
.github/ISSUE_TEMPLATE: notes about expiration of items and how to reopen
---
Modified: .github/ISSUE_TEMPLATE/bug_report.md
Modified: .github/ISSUE_TEMPLATE/feature_request.md
---
Diff: https://github.com/kamailio/kamailio/commit/96300556ea4787f6f99926dcc7305ec…
Patch: https://github.com/kamailio/kamailio/commit/96300556ea4787f6f99926dcc7305ec…
---
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
index e657ee1a979..01b1672bbb7 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.md
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -17,6 +17,15 @@ If you have questions about developing extensions to Kamailio or its existing C
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
+Note that an issue report may be closed automatically after about 2 months
+if there is no interest from developers or community users on pursuing it, being
+considered expired. In such case, it can be reopened by writing a comment that includes
+the token `/notexpired`. About two weeks before considered expired, the issue is
+marked with the label `stale`, trying to notify the submitter and everyone else
+that might be interested in it. To remove the label `stale`, write a comment that
+includes the token `/notstale`. Also, any comment postpone the `expire` timeline,
+being considered that there is interest in pursuing the issue.
+
If there is no content to be filled in a section, the entire section can be removed.
You can delete the comments from the template sections when filling.
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
index 2c21427e600..6206cee95c7 100644
--- a/.github/ISSUE_TEMPLATE/feature_request.md
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -21,6 +21,15 @@ If you submit a feature request (or enhancement) add the description of what you
If there is no content to be filled in a section, the entire section can be removed.
+Note that a feature request may be closed automatically after about 2 months
+if there is no interest from developers or community users to implement it, being
+considered expired. In such case can be reopened by writing a comment that includes
+the token `/notexpired`. About two weeks before considered expired, the item is
+marked with the label `stale`, trying to notify the submitter and everyone else
+that might be interested in it. To remove the label `stale`, write a comment that
+includes the token `/notstale`. Also, any comment postpone the `expire` timeline,
+being considered that there is interest in the proposed feature request.
+
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment).
Module: kamailio
Branch: master
Commit: 5a65791e3959439a699d746ce8e63d438e8db0a5
URL: https://github.com/kamailio/kamailio/commit/5a65791e3959439a699d746ce8e63d4…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2023-11-27T14:17:09+01:00
modules: readme files regenerated - topoh ... [skip ci]
---
Modified: src/modules/topoh/README
---
Diff: https://github.com/kamailio/kamailio/commit/5a65791e3959439a699d746ce8e63d4…
Patch: https://github.com/kamailio/kamailio/commit/5a65791e3959439a699d746ce8e63d4…
---
diff --git a/src/modules/topoh/README b/src/modules/topoh/README
index f1a761bf8f9..0217b90d30f 100644
--- a/src/modules/topoh/README
+++ b/src/modules/topoh/README
@@ -162,12 +162,12 @@ modparam("topoh", "mask_key", "some secret here")
IP address to be used in masked headers to build valid SIP URIs. Can be
any IP address, even a private-space or non-existing IP address (e.g.,
192.168.1.1, 127.0.0.2), including the SIP server address, but must not
- be an address potentially used by clients. If not set, the advertised
- IP of the incoming or outgoing socket is used. If there is no
- advertised IP, the IP of the socket is used. It is not used at all for
- SIP routing.
+ be an address potentially used by clients. If set to empty string, the
+ advertised IP of the incoming or outgoing socket is used when
+ specified, otherwise the IP of the socket is used. Note that the value
+ is actually not used at all for SIP routing.
- Default value is empty.
+ Default value is "127.0.0.8".
Example 1.2. Set mask_ip parameter
...