Hi,
I think our current directory is a little bit confusing for new users,
We have several top level dirs (like commons, extensions, osgi, sling)
which do not clearly indicate what they might contain.
I know this is a "hot topic" :) and we could debate for ages about it. I
think we should just try to follow a pragmatic approach and try to limit
the number of dirs and modules.
This first part is about the commons and the osgi dirs. I think
"commons" is a great name and its content is "common stuff" :) which
means it is stuff that is used by Sling but not directly tied to Sling -
it can be used outside of Sling. So we should keep this dir and its
current content.
Actually I think the "osgi" dir is confusing; most of our stuff is about
osgi so what does it contain? An osgi implementation?
I think it currently contains common stuff (bundles) as well, so it
would make sense to merge the contents into the commons dir.
But :) we want to move the console-web to Felix, so let's not move it to
"commons"; the assembly stuff is currently not used, same with the obr.
I think we should move this to a sandbox area.
The log is a common implementation of the LogService and we should move
it to "commons".
And osgi/commons has "common stuff" as well :), so we should move it to
commons/osgi or commons/osgi-util.
So, wrapping up:
a) "commons" is a place for common code/bundles which is not directly
tied to Sling (but used by Sling)
b) We move the stuff from the "osgi" dir to "better places"
c) osgi/assembly -> sandbox
d) osgi/commons -> commons/osgi-util
e) osgi/console-web -> Apache Felix
f) osgi/log -> commons/log
g) osgi/obr -> sandbox
Does this make sense?
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
