How a project is named is a choice of the author. Nobody gets to demand how someone should name their projects.
Now how project is actually named is not a issue if it is properly handled on pharo side, which in some places is, in some places isn't.
For instance, there's a gazillion UI frameworks out there and, most of the time, the name used for them is one of a famous painter.
We have Magritte, which is a meta-data description framework, not UI framework. :)
How many Pharo *users* (not regular contributors!) know what those tools/frameworks/packages do ???
Probably not many, because they never encounter them, nor care about whether they exist or not.
A very quick look at what's in Pharo 7 shows the following names : Iceberg, Ombu, Calypso, Flashback, Nautilus, Renraku, Zodiac, Shift, Zinc, Hermes, Beacon, Cargo, Hermes, Opal, Shoreline, Epicea, Balloon, BlueInk, Commander, Fuel, Glamorous, Glamour, Gofer, Hiedra, Metacello, Moose, Ring, Rubric, Shout, Spec, etc...
Calypso + Nautilus: as a user you don't get to encounter the names, there's only "System Browser"
Did you know that there are other code browsers you can install? (e.g. Code Panels, Alt Browser, ...)
Iceberg: as someone pointed out, this would be nice to have a "(Git) Versionner" or whatever entry instead
Metacello: npm => "Package manager 1", pip => "Package manager 2", ...
Ombu/Epicea: you access it via "Code Changes", names are hidden from the user
Flashback, Renraku, Hermes, Opal, Shoreline, BlueInk, Hiedra, Ring, Rubric, Shout, Glamorous, Glamour: not something a regular user ever encounters directly, and if they need to, the unique name helps a lot in finding information/docs about it
Moose: are you serious? should Pharo be called "Programming Language 28301" too?
Commander: Commander is a library to implement commands. You literally cannot have a more descriptive name and yet you still complain.
Spec: ... maybe we can rename
�� * Morphic "UI 1"
�� * Baloon "UI -1"
�� * Spec "UI 2"
�� * Rubric "UI 3"
�� * Tx "UI A"
�� * Bloc "UI ��"
�� * Athens "UI��
��"
�� * Cairo "UI����"
�� * Sparta "UI�����"
and then try to find any information about anything.
Was it really that hard to replace the old workspace with Workspace2 or WhateverWorkspace ?�� Or even better : get rid of the old Workspace and replace it with Playground while retaining the name "Workspace" ???
Well I could claim that "Workspace" is a very confusing name, because it is not actually workspace, just a trivial Text Box. If anything, Playground is a much more fitting name.
Or somethings as simple as Regex, the regex package from Bykov.
��
Which variant of regular expressions though?
Unless we *clearly* publicize/describe what those names are, there's no way in a thousand years you could tell that BlueInk is not a package dealing with fonts (that was my first guess) !
I fully agree with this, and as I've mentioned (here, or maybe in another thread), this has improved greatly with move to GitHub, as people finally started to care about describing their projects. But the transition takes time. Btw BlueInk is a "pretty printer", so the name isn't really misleading once you know what it is. But being "clever" with names is sure way to get it misinterpreted. (E.g. "grafoscopio" which has nothing to do with graphs or visualizations, as it is text/nodes/code snippets organization tool.)
(For the record I tend to name projects with the most boring name I can come up with (tonel-migration, IconFactory, file-dialog, xml-magritte-generator, uml-xmi, ...), but it only works if there's only one such thing... if there are competing projects, than sharing the name doesn't help anyone.)
Peter