Eclipse Committers at EclipseCon Europe: if you see me wandering around, or sitting in a talk or at table, please come and introduce yourself. I’d like to meet you.
Earlier tonight, I tweeted an observation:
The EGit project doesn’t use its name in UI contributions. This helps the project feel like an integral part of the workbench.
— Wayne Beaton (@waynebeaton) October 23, 2012
@waynebeaton CDT has the same policy. If you see ‘CDT’ on any menu item or preference page, it’s a bug.
— Doug Schaefer (@dougschaefer) October 23, 2012
Almost none of the estimated six million users of Eclipse need to know that the Git support provided in their favourite IDE was provided by the EGit project. In fact, most of those users would probably be confused by that knowledge. I like to think that most of them would sort of understand the purpose of an “EGit” perspective, but what they’re really looking for is a means of working with Git repositories. And so it is with CDT. Users of CDT are building C/C++ applications, not CDT applications. EGit and CDT get it right. So do a lot of other projects.
Project names belong in the “About” dialog and installation details. They don’t belong in the menus, views, editors, preferences, etc.
I think that getting this right is important. In many (perhaps most) cases, project names are like code names: they’re important to help a small subset of the community disambiguate providers of functionality. But when I use the software, I’ve noticed that I tend to think of the project-named functionality as being not-so-tightly integrated with the rest of the IDE experience. EGit and CDT on the other hand seem like very natural parts of my Eclipse configuration.
What does it mean to create a new “Woolsey Project”? (note that the Woolsey project doesn’t actually contribute anything like this). Those in the know would understand what it meant, but the broader audience would not. Some brave souls would give the option a try, but most users will just skip over the option and happily build a new “PHP Project” (PDT) or a “Maven Project” (m2eclipse).
It’s in a project’s best interest to avoid the “what the hell is this?” factor in favour of providing the most obvious “I want to do this” sort of option. Ultimately, though, project team members are the ones who best understand their community and what they expect to see when they sit down to use Eclipse.