Updates: Status: New Comment #2 on issue 744 by stephane...(a)gmail.com: SmalltalkImporter should be renamed SmalltalkExtractor http://code.google.com/p/moose-technology/issues/detail?id=744 I still maintain this point because it would make the domain cleaner.

Comment #4 on issue 744 by stephane...(a)gmail.com: SmalltalkImporter should be renamed SmalltalkExtractor http://code.google.com/p/moose-technology/issues/detail?id=744 So what does it mean? Should I fork my code, because I wrote the importer as far as I know?

But they are two steps in any languages and you know it. I do not understand your reaction. And the extraction term is only for Smalltalk and nobody cares about Smalltalk because it has no business value so we could have a clear separation for Smalltalk because the importing of Smalltalk is not the same for Java, C# and ….. The SmalltalkImporterTask has nothing to do with the MSEReader or other importingTask. But it brings fuzziness in the domain. Because this is not clear (you know for new people coming in to see ok this is about Smalltalk creation of entity from source code and this is importing from outside). Indeed now there are consequences because if we fork this means that probably all the group here will use another version. Some people suggested to me to fork Moose and I was not in favor but I will keep the option more open now. We will discuss that with the new engineer. Stef