Also remember that we have to move all methods that read/write fonts and image out of graphics;
otherwise it depends on a bunch of packages (system, files, ...).
Note that graphics was focused on BitBlt graphics.
But this is only one possible backend (Pharo is developing alternate ones).
Though, the font scanning is independent of BitBlt (well, there is one specialized subclass for rendering on BitBlt).
Thus, in term of modularity these two things could be split eventually (BitBltGraphics depending on Text scanning).
Pharo has grouped text things together (both description and scanning). Don't know if it is a good idea though...
Anyway, I find those classification really limited.
As emphasized thru the discussions there is more than one classification possible.
For example, you might want to see Array both in Collections and Kernel.
Those classifications are like file system: they do not match our need/brain.
We want something that can be queried like a database.
So sometimes, I wonder if we shouldn't have class/methods belonging to several packages.
The class/method would be removed only when all it's parent packages have been removed.