Registering project names on scala-lang.org

[jvican]

@Blaisorblade

To make package names globally unique on the JVM and prevent accidental collisions, it’s recommended to start package names with (reversed) domain names—so that the DNS system functions as a global top-level registry. People used to actually stick to such rules, especially in Java and in Eclipse—and Eclipse seems big enough that you’d get actual problems otherwise.

Yes, I am familiar with this. What I don’t understand is why Oscar wants to have access to the Scala namespace or a Scala-owned namespace for contributors. Can you elaborate @oscar?

@Blaisorblade

May I ask if this should be an optional Scala Platform benefit, or is this a derailing of the original proposal?

This has been discussed in depth here:

Should the Scala Platform modules use the Scala namespace or a common namespace?

do you want the Scala Platform to use scala.*, not something like scalax.*? My understanding is that the scala namespace is owned by EPFL and platform modules will not be re-rooted. I think it would be a poor idea to do so. Users need to understand what’s part of the core language and what isn’t.

You can read that thread for the context. To answer your question more directly, no @Blaisorblade, the Scala Platform won’t have a common namespace.