Completely agree :)
Or we could use the seaside naming conventions, but I dont have the rationale for one
schema or the other.
http://code.google.com/p/seaside/wiki/PackageNaming

Tentative schema:

Moose-Core
Moose-Tests-Core
Moose-Importer
Moose-Smalltalk-Importer
Moose-Tests-Smalltalk-Importer
Moose-Monticello-Importer
Moose-Finder [-Scripts...]
Moose-Scripts
Moose-Mondrian-Scripts
Famix-Core
Famix-Tests-Core
Famix-Extensions
Famix-Smalltalk [-Extensions]
Famix-Java [-Extensions]
Famix-Cook (ou Moose-Cook?)
Famix-Tests-Cook
Moose-Model-Hismo
Moose-Model-File
Moose-Tests-Model-Hismo
Moose-TestResources-LAN
Moose-TestResources-Reference

Moose-Algorithms-Graph
Moose-Algorithms-FormalConceptAnalysis
Moose-Algorithms-Serialization
Moose-Tests-Algorithms-Graph

I like the proposal of Simon, with the following exceptions:
- Famix-Cook does not (or should not) exist anymore (it is part of Famix-Extensions)
- Moose-Algorithms should be called Moose-Algos

Well ok I just skim through packages to see how to translate them.

I am thinking about the process. So 'Package renaming' refactoring seems to work and
Monticello browser seems 
ok with that at first (it's a surprise, but I didnt commit for now so perhaps there
will be problems)

Only (big) problem I see is that package renaming does not *move* classes to the new
package. So what's the 
point of such a refactoring?

Perhaps it would be a good idea to wait with this refactoring until after the 4.0 release.

Notice a cycle between Moose-ModelTest and Famix-LANTests. Maybe we should merge those
packages 
anyway.

In this spirit, I now removed Moose-MondrianScripts from the ConfigurationOfMoose and
MondrianPaintings from ConfigurationOfMondrian.

We now have only Moose-MondrianPaintings.

I propose the following refactorings:

Moose-LAN -> Moose-TestResources-LAN

Famix-LANTests -> Moose-Tests-SmalltalkImporter-LAN

MooseKGB-TestFamix3 -> MooseKGB-Tests-SmalltalkImporter
Moose-KGB-* -> MooseKGB

Moose-SmalltalkImporter -> Moose-SmalltalkImporter-Core
Moose-SmalltalkImporterTests -> Moose-Tests-SmalltalkImporter-Core

Moose-Test-PackageOne -> Moose-TestResources-Reference-PackageOne
Moose-Test-PackageTwo -> Moose-TestResources-Reference-PackageTwo

Moose-TestResources-PackageBlueprint-P* -> Moose-TestResources-Packages-P*

On second thought, I propose :)


Moose-LAN -> Moose-TestResources-LAN
Famix-LANTests -> Moose-Tests-SmalltalkImporter-LAN
MooseKGB-TestFamix3 -> Moose-Tests-KGB
Moose-KGB-* -> Moose-TestResources-KGB-*
Moose-SmalltalkImporterTests -> Moose-Tests-SmalltalkImporter
Moose-Test-PackageOne -> Moose-TestResources-Reference-PackageOne
Moose-Test-PackageTwo -> Moose-TestResources-Reference-PackageTwo

Moose-ReferenceModel -> Moose-TestResources-Reference-Core

Fixed naming of test packages. Still to do:
Moose-KGB-* -> Moose-TestResources-KGB-*

Done.

Some more todos:
- Rename the two Glamour test packages
- Rename the SmallDude test packages
- Rename DSM packages with the same scheme
- Split Mondrian categories into own packages

I renamed the Glamour and SmallDude packages

Is it finished ?

No:
- DSM was not refactored
- Mondrian was not split into packages

Mondrian is now split into individual packages. Only DSM is left :)

Ok, I will do something like that:

DSM-ModelTest -> Moose-TestResources-Dsm
DSM-Tests-Core -> Moose-Tests-Dsm
DSMCore -> Moose-Dsm
DSMCycleTable -> Moose-CycleTable
DSMExtra -> nothing, this is my experimental software
DSMLayerTable -> merge with DSMExtra

In two weeks, it will be done

We should rename Merlin also

So, after discussing, Merlin is different of Moose

DSM is renamed like that:
DSM-ModelTest -> Moose-TestResources-Dsm
DSM-Tests-Core -> Moose-Tests-Dsm
DSMCore -> Moose-Dsm
DSMCycleTable -> Moose-CycleTable
DSMExtra -> nothing, this is my experimental software
DSMLayerTable -> merge with DSMExtra

I changed ConfigurationOfDSM.