[SR-Dev] moving modules

Andrei Pelinescu-Onciul andrei at iptel.org
Mon Apr 20 10:38:55 CEST 2009

Hi *,

Before moving more modules consider the following problem cases:

- same module in k uses mi and in ser rpc => for the near future we
  cannot choose one over the other, because some functionality will be
  lost (e.g. choosing the k module will leave someone wanting a ser like
  config having to use mi for one module).

- a module includes stuff from other modules (e.g. auth_* & auth) =>
  it's probably not safe to replace it with only one version, until the
  modules they depend on are merged.

- even if the module exists only in ser or in k, it might be
  unmaintained or obsolete (in which case we better make another dir,
  something like modules_obsolete or unmaintained and move them there
  until somebody volunteers to take over).

Part of the problem is if we merge everything now or latter. I think
latter is better, unless you want a larger delay (there are just too
many modules/interfaces to merge and too few people knowing enough about
both projects to do it). There are other points we haven't even
discussed yet (like rpc & mi, it doesn't make sense to have 2 management
interfaces in the long run).


More information about the sr-dev mailing list