One of the aspects of Kit that strikes me as most valuable is the precept of namespacing your projects and code.

However, without a central control over who owns what namespace, there is potential for conflicts. And these can't be handled so easily as a path alias or an IRC nick. Without a central registry of names to examine, it's not even easy to identify whether you've managed to choose a unique string at the start of a project.

In the Preservation world, URI's have become popular as namespaces because the internet registry guarantees unique ownership of every domain.

At least as a guideline, Kit should suggest unique namespaces come from a registered domain name (examplecom) or a D.O username.

Folks without a domain to claim that don't want to use there username are probably hosting code on a public server, in which case it should be that server's responsibility to care about namespace collisions. (I.e., featureserversorg)

Limiting it to D.O would be better, but I don't want to suggest people start creating accounts just to claim externally hosted module namespaces.