Top-level package names, UX questions

[Martin Albisetti]

On Mon, Mar 16, 2015 at 3:22 PM, Gustavo Niemeyer
<gustavo.niemeyer at canonical.com> wrote:
> I wasn't part of the original conversation, but it sounds like this would be
> equivalent to having a single global namespace, except we are allowed to
> override anybody else's names at will, which is unfriendly. In other words,
> when we add a package X, we put any existing applications previously named X
> in trouble.
>
> Whatever scheme we choose, at the end people should be able to pick an
> identifier without being concerned about future unintended conflicts.

Agreed, we shouldn't force you to understand the consequences of you
picking a name. That, I think, is one of the main drivers for
developer-keyed names. There's no collisions.

The main subject here is how to implement the promotion from
developer-keyed to top-level, which is a manual recognition that you
are the best person to care for that particular piece of software with
that name.


-- 
Martin