Hi,
I've started thinking a bit about the Git migration process. I don't
think we've discussed naming individual Sling modules after being
extracted from SVN.
ASF mandates that we use a pattern of 'TLP-module' for the git
repositories, so the modules must be name sling-${something}.
As for that ${something}, it can be one of
1. artifactId / Bundle-SymbolicName
2. short name ( as currently used in the SVN repo )
I would favour option 2, as I think option 1 has too much redundancy:
sling-org.apache.sling.auth.core
is too verbose compared to
sling-auth-core
Refining option #2, we should remove some commons prefixes, such as:
- bundles
- contrib/bundles
- bundles/extensions
- contrib
- contrib/extensions
- karaf
- tooling/maven
Thoughts?
Robert
