Totally agree with you. This certainly clarifies the usage of these modules.

Hm, I think the namespace "Sympa::WWW" would be better. Just my two cents.

I think naming method is matter of preference. The method getting more support would be carried out.

So let's discuss the new namespace on the (developers) mailing list. I also think it is a good idea and it is a good time to this before sympa-7.0 branch starts to take off.

There seems no objection to moving. Rest of issue is how we may move (rename). Before we move to dev list, we would be better to present rationale by each.

My favorite is new top-level namespace WWSympa. By this proposal, directory listing of src/lib will be:

Sympa/
Sympa.pm
WWSympa/
WWSympa.pm

(`Conf.pm will be removed --- hopefully in this year, besides)

Separate namespaces will make separating packages easy:

• Packagers may pick out Sympa* for core package and WWSympa* for web package.
• Developers of new web interace may create new namespace and may work only on Sympa and MojoSympa namespaces.
• I personally have plan of LMTP frontend of Sympa and I may work on LMTPSympa namespace.

etc.

My favourite is to keep all our modules within a single namespace Sympa - this makes more sense to me and doesn't look so ugly like "WWSympa", "LMTPSympa", e.g.

• Sympa::WWW or Sympa::Web
• Sympa::LMTP or Sympa::Mail::LMTP

This doesn't affect the separation of the modules for packaging.

Also, while we are at it, a separate namespace for 3rd party modules would be nice to, e.g. one of these:

• Sympa::Plugin::
• Sympa::Module::
• Sympa::Extension::

Okey, let's continue on dev list.

@dverdin both @racke and i are agree about the namespaces @racke proposed. no one else provided another solution. what's your opinion ?