Re: [cross-project-issues-dev] Feature user-readable name

[David M Williams <david_williams@xxxxxxxxxx>]

This is a good point. Thanks for calling
our attention to it. 

But ... isn't it a bit late to be making
this sort of change? 
Or, are you just getting us started
on the next release? 

If you are advocating a change now,
then I'll note that it does not seem to me to be of "stop ship"
magnitude (after all, it's only "user confusion" :) 
but more important, I suspect that there
might be some adopters that have gone through some translations, which
might include these feature names? 
Also, it might make some screen captures
incorrect, where they are used in documentation. 

I'm not sure we have Ganymede rules,
per se, about these specifics, but ... in general, the Ganymede UI Freeze
date has long come and gone. 

So, I just wanted to be explicit about
these complications and extenuating factors ... not that I am telling other
projects what to do or that they have to follow the rules :) 

If on the other hand, you are just getting
us started on the next release, then definitely welcome comment ... never
too early ... I hope you'll be giving us lots of advice on how to create
"features" that are meaningful!

From:	Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>
To:	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date:	06/12/2008 02:40 PM
Subject:	[cross-project-issues-dev] Feature user-readable name

---

To feature maintainers:

Since p2 now allows users to search features per name (see attached image),
you may want to verify that the user readable name given to your feature
allows for its easy discovery. What I have seen working is the presence
of your project acronym (e.g. GEF), or some typical keywords describing
your domain (e.g. Ruby, Web, etc.)). 

What is particularly bad is when the acronym ends up revealing something
that is not what you want. For example, typing GMF has the unfortunate
result of revealing the "Third party components for GMF" instead
of revealing the real thing to install which may cause the user some confusion.

PaScaL

(See attached file: filter.jpg)_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Attachment: filter.jpg
Description: JPEG image