On Wed, Apr 30, 2008 at 11:24 AM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> Ok, this is part two :) ...
Hmm..just wondering how many episodes we signed up for ;-)
> ... I think the extensions folder is great as well and it should contain
> useful
> extensions new Sling users do not need to worry about. Once they are
> familiar with the core principles of Sling they can have a look at the
> extensions and pick out one or the other...
Ok
> ... The java packages of these bundles do not contain "extension" in their
> name, it's just o.a.s.{bundlepackage} (with possible sub packages).
> We should not use "extensions" in the bundle names either. Distinguishing
> between core and extensions is a little bit arbitrary and we should be able
> to move stuff between core and extensions without having to rename
> everything....
Ok - maybe this info would sit well in a wiki/website page?
> I... think the eventing and the scheduling stuff fall definitly into this
> category, so we should move them....
Ok
> ... The current threads bundle should be moved to commons/threads (including
> package renaming) as it contains a common thread pool implementation which
> is usable outside of Sling...
Ok
> ...This leaves us with removing the "extensions" from the bundle/package
> names
> for the existing stuff....
+1
-Bertrand (offline from tomorrow on, back next monday - looking
forward to what svn update will find ;-)
