16 Apr
2009
16 Apr
'09
11:02 a.m.
Folks,
I am happy to announce that we finished the migration of SER and Kamailio
modules into a shared git repository and the git repository is now ready for
everyone to use. You can browse the repository here:
http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sip-router;a=summary
There are currently three directories with modules:
* modules: This is the directory that contains modules that have been merged
from both projects.
* modules_k: This is the directory that contains updated Kamailio modules.
* modules_s: This is the directory that contains updated SER modules.
We have reached a significant milestone on our way towards one common
project. It took a tremendous amount of work to get us where we are now and I
would like to take the opportunity to thank all the people from both projects
who made this possible. I will resist the temptation to list names, because
there are too many of them, it's not necessarily only the people who you see
active on the mailing lists. So here is your "thank you" in big friendly
letters:
T H A N K Y O U
There is still a lot of work waiting for us, but it will hopefully be more
exciting and interesting than the migration process itself. There are still
some modules that don't compile, scripts and tools that are missing, and so
on.
But we are on the track and if we keep shoveling coal into the machine, I am
sure the train will get to the "sip-router" station soon, no matter how far
the station may seem now :-).
Jan.
16 Apr
16 Apr
11:34 a.m.
New subject: [SR-Dev] Shared git Repository Ready
Hi Jan,
thanks for your time and work.
Cheers,
Daniel
On 04/16/2009 10:02 AM, Jan Janak wrote:
Folks,
I am happy to announce that we finished the migration of SER and Kamailio
modules into a shared git repository and the git repository is now ready for
everyone to use. You can browse the repository here:
http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sip-router;a=summary
There are currently three directories with modules:
* modules: This is the directory that contains modules that have been merged
from both projects.
* modules_k: This is the directory that contains updated Kamailio modules.
* modules_s: This is the directory that contains updated SER modules.
We have reached a significant milestone on our way towards one common
project. It took a tremendous amount of work to get us where we are now and I
would like to take the opportunity to thank all the people from both projects
who made this possible. I will resist the temptation to list names, because
there are too many of them, it's not necessarily only the people who you see
active on the mailing lists. So here is your "thank you" in big friendly
letters:
T H A N K Y O U
There is still a lot of work waiting for us, but it will hopefully be more
exciting and interesting than the migration process itself. There are still
some modules that don't compile, scripts and tools that are missing, and so
on.
But we are on the track and if we keep shoveling coal into the machine, I am
sure the train will get to the "sip-router" station soon, no matter how far
the station may seem now :-).
--
Daniel-Constantin Mierla
http://www.asipto.com/
12:20 p.m.
New subject: [SR-Dev] Shared git Repository Ready
2009/4/16 Jan Janak <jan(a)iptel.org>rg>:
I am happy to announce that we finished the migration
of SER and Kamailio
modules into a shared git repository and the git repository is now ready for
everyone to use. You can browse the repository here:
http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sip-router;a=summary
There are currently three directories with modules:
* modules: This is the directory that contains modules that have been merged
from both projects.
* modules_k: This is the directory that contains updated Kamailio modules.
* modules_s: This is the directory that contains updated SER modules.
Really thanks for your great effort on it.
Let me some questions:
- Is the aim to merge modules from both projects? or will Kamailio
modules always be in "modules_k"?
- If so, which are the requeriments for a k module to become a "real" sr
module?
- What about module documentation? I still read &kamailio in any
k_module_admin.xml? How to migrate it?
--
Iñaki Baz Castillo
<ibc(a)aliax.net>
12:36 p.m.
New subject: [SR-Dev] Shared git Repository Ready
On 16-04 11:20, Iñaki Baz Castillo wrote:
2009/4/16 Jan Janak <jan(a)iptel.org>rg>:
The aim is to merge them. We will start moving modules that do not have their
counterpart in the other project into modules/ directory. Modules that exist
in both project will be moved into modules/ once we merge the code.
The ultimate goal is to have all modules in a single directory.
I am happy to announce that we finished the
migration of SER and Kamailio
modules into a shared git repository and the git repository is now ready for
everyone to use. You can browse the repository here:
http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sip-router;a=summary
There are currently three directories with modules:
* modules: This is the directory that contains modules that have been merged
from both projects.
* modules_k: This is the directory that contains updated Kamailio modules.
* modules_s: This is the directory that contains updated SER modules.
Really thanks for your great effort on it.
Let me some questions:
- Is the aim to merge modules from both projects? or will Kamailio
modules always be in "modules_k"? - If so, which are the requeriments for a k module to
become a "real" sr module?
If there is no module with the same name in modules_r then it can be moved
right away. If there is a module with the same name then will need to merge
them somehow (which can be a time-consuming process due to changes in the
database schema).
- What about module documentation? I still read
&kamailio in any
k_module_admin.xml? How to migrate it?
This is an open topic. Suggestions are welcome.
Jan.
12:39 p.m.
New subject: [SR-Dev] [Serdev] Shared git Repository Ready
On 16-04 11:36, Jan Janak wrote:
On 16-04 11:20, Iñaki Baz Castillo wrote:
I should have added that this is my understanding of what we want to achieve
long term. If people prefer to keep two sets of modules in separate
directories then this would work too, of course.
Jan.
2009/4/16 Jan Janak <jan(a)iptel.org>rg>:
The aim is to merge them. We will start moving modules that do not have their
counterpart in the other project into modules/ directory. Modules that exist
in both project will be moved into modules/ once we merge the code.
The ultimate goal is to have all modules in a single directory. I am happy to announce that we finished the
migration of SER and Kamailio
modules into a shared git repository and the git repository is now ready for
everyone to use. You can browse the repository here:
http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sip-router;a=summary
There are currently three directories with modules:
* modules: This is the directory that contains modules that have been merged
from both projects.
* modules_k: This is the directory that contains updated Kamailio modules.
* modules_s: This is the directory that contains updated SER modules.
Really thanks for your great effort on it.
Let me some questions:
- Is the aim to merge modules from both projects? or will Kamailio
modules always be in "modules_k"? 
6:28 p.m.
New subject: [SR-Dev] [Kamailio-Devel] Shared git Repository Ready
Jan Janak writes:
There are currently three directories with modules:
* modules: This is the directory that contains modules that have
been merged from both projects.
* modules_k: This is the directory that contains updated Kamailio
modules.
after cloning sip-router, i noticed that modules didn't contain that
many modules. what needs to be done to get more modules, for example
lcr, moved from modules_k to modules?
-- juha
6:46 p.m.
New subject: [SR-Dev] [Kamailio-Devel] Shared git Repository Ready
On 16-04 18:28, Juha Heinanen wrote:
Jan Janak writes:
If there is no module with the same name in modules_s then you can move the
module right away with 'git mv'.
If you know that the corresponding SER module is unmaitained and should be
replaced with its kamailio equivalent then you can delete the module in
modules_s with 'git rm' and move the module from modules_k to modules. That's
the case with lcr, I believe.
In other cases we can move modules from modules_s and modules_k to modules
once we merge them.
Jan.
There are currently three directories with
modules:
* modules: This is the directory that contains modules that have
been merged from both projects.
* modules_k: This is the directory that contains updated Kamailio
modules.
after cloning sip-router, i noticed that modules didn't contain that
many modules. what needs to be done to get more modules, for example
lcr, moved from modules_k to modules?
6:51 p.m.
New subject: [SR-Dev] [Serdev] [Kamailio-Devel] Shared git Repository Ready
On 16-04 17:46, Jan Janak wrote:
On 16-04 18:28, Juha Heinanen wrote:
Just FYI: we considered moving modules that exist only in one project directly
to modules/, but then we realized that it will be better if we import them in
modules_s and modules_k respectively and then move them with 'git mv', because
then it will be recorded in the history of the repository. Also we do not know
which kamailio modules are unmaintained, so it might be better to sort this
out later.
Jan.
Jan Janak writes:
If there is no module with the same name in modules_s then you can move the
module right away with 'git mv'.
If you know that the corresponding SER module is unmaitained and should be
replaced with its kamailio equivalent then you can delete the module in
modules_s with 'git rm' and move the module from modules_k to modules.
That's
the case with lcr, I believe.
In other cases we can move modules from modules_s and modules_k to modules
once we merge them. There are currently three directories with
modules:
* modules: This is the directory that contains modules that have
been merged from both projects.
* modules_k: This is the directory that contains updated Kamailio
modules.
after cloning sip-router, i noticed that modules didn't contain that
many modules. what needs to be done to get more modules, for example
lcr, moved from modules_k to modules?
6:52 p.m.
New subject: [SR-Dev] [Kamailio-Devel] Shared git Repository Ready
Jan Janak writes:
If you know that the corresponding SER module is
unmaitained and should be
replaced with its kamailio equivalent then you can delete the module in
modules_s with 'git rm' and move the module from modules_k to modules.
That's
the case with lcr, I believe.
ok, i'll take a look at ser lcr module to see if there is anything that
would need to be merged.
-- juha
8:05 p.m.
New subject: [SR-Dev] [Kamailio-Devel] Shared git Repository Ready
Jan Janak writes:
If there is no module with the same name in modules_s
then you can move the
module right away with 'git mv'.
If you know that the corresponding SER module is unmaitained and should be
replaced with its kamailio equivalent then you can delete the module in
modules_s with 'git rm' and move the module from modules_k to modules.
That's
the case with lcr, I believe.
i cannot replace s lcr with k lcr. the reason is that k lcr does not
anymore include load_contacts()/next_contacts() functions, because
corresponding functions are in k tm module.
however, modules_k does not anymore contain tm module, because it has
already been merged! that kind of merge should not have been done,
because now sr does not anymore include
t_load_contacts()/t_next_contacts() functions at all!
-- juha
8:14 p.m.
New subject: [SR-Dev] [Kamailio-Devel] Shared git Repository Ready
On 16-04 20:05, Juha Heinanen wrote:
Jan Janak writes:
Then we can add those functions to the shared tm module. I'll look into it.
Jan.
If there is no module with the same name in
modules_s then you can move the
module right away with 'git mv'.
If you know that the corresponding SER module is unmaitained and should be
replaced with its kamailio equivalent then you can delete the module in
modules_s with 'git rm' and move the module from modules_k to modules.
That's
the case with lcr, I believe.
i cannot replace s lcr with k lcr. the reason is that k lcr does not
anymore include load_contacts()/next_contacts() functions, because
corresponding functions are in k tm module.
however, modules_k does not anymore contain tm module, because it has
already been merged! that kind of merge should not have been done,
because now sr does not anymore include
t_load_contacts()/t_next_contacts() functions at all!
5703
days inactive
5703
days old
11 comments
5 participants
participants (5)
-
Daniel-Constantin Mierla -
Henning Westerholt -
Iñaki Baz Castillo -
Jan Janak -
jh＠tutpro.com