"Marketing" data in official metaregistry

[tadasant]

Pre-submission Checklist

• I have verified that this discussion would not be more appropriate as an issue in a specific repository
• I have searched existing discussions to avoid duplicates

Discussion Topic

@sandy081 brought up suggestions to include displayName and icon into the API.

I am inclined to say we should keep these out of scope for the following reasons:

• They are non-critical pieces of data (hence me calling it "marketing" data), and minimizing surface area / complexity / maintenance burden is important for our design
• They increase surface area for spam and/or security problems (e.g. icon URLs)
• They are not actually that useful to end-clients, because a concept like displayName is hard to standardize; we wouldn't want to end up with keyword-stuffed Amazon.com-like product listings. The best clients will transform these names or not use them in order to optimize UX for their end-users
• Other package registries don't optimize for this either (for example, there is no displayName on npm)

Suggestions for clients and/or server metadata middlelayer services work around this gap in data:

• Fetch icons from the source_code reference (e.g. from the associated GitHub user or org's profile picture)
• Create a displayName by just stripping the reverse-DNS namespace from name and Title-ize the casing as-desired