An analysis of MooseTask hierarchy

here are some notes we wrote when browsing the MooseTask

- It would be good to rename MooseTask should be renamed because it has nothing to do in Moose.t 

- MooseTask and MooseOperator should be in the same package: Moose-Core since MooseOperator has nothing to do with Smalltalk.

- the hierarchy of MooseCompositeImporterTask is really dealing only with Smalltalk importing logic.

so we should rename it:

SmalltalkCompositeExtractorTask or at least SmalltalkCompositeImporterTaskcolle

- MooseImportClassesTask should be renamed SmalltalkImportClassesTask

since it only create entity extracted from Smalltalk. 

( Importer vs extractor

I would like to keep the term importer to the action of populating a model and the action to extract model from source code.

In java, c3 we have extractor and in Moose importers and extractors)

- Nobody is referencing PackageDescription?

- Now our problem is that we would like to run tasks when a 

     a Smalltalk model is extracted and imported