On Tuesday 18 September 2018 15:46:09 Bertrand Delacretaz wrote:
> On Tue, Sep 18, 2018 at 3:38 PM Jason E Bailey wrote:
> > ...I'll throw "community" and/or "community supported" into the ring for
> > consideration as well. For those bundles that aren't supported...
> I like it, as a way to indic
On Wednesday 26 September 2018 18:29:47 Carsten Ziegeler wrote:
> For setting up Sling from scratch, I guess it would make sense to share
> my list of bundles; I assembled it roughly a year ago and I didn't
> update it since then. I'll go through this exercise and once I have
> something I'll share
Right, that's what I have. I splitted it up into two, OSGi basics and
then Sling specific on top
Regards
Carsten
Bertrand Delacretaz wrote
> Hi,
>
> On Wed, Sep 26, 2018 at 12:29 PM Carsten Ziegeler
> wrote:
>> For setting up Sling from scratch, I guess it would make sense to share
>> my lis
Hi,
On Wed, Sep 26, 2018 at 12:29 PM Carsten Ziegeler wrote:
> For setting up Sling from scratch, I guess it would make sense to share
> my list of bundles...
If that can be done as a feature file in the Sling starter that might
a good way? Just a "core" feature that represents the minimal setup
For setting up Sling from scratch, I guess it would make sense to share
my list of bundles; I assembled it roughly a year ago and I didn't
update it since then. I'll go through this exercise and once I have
something I'll share it with the larger audience.
Regards
Carsten
Jason E Bailey wrote
On Tue, Sep 25, 2018, at 3:25 PM, Dominik Süß wrote:
> Hi Jason,
>
> What beyond the ‚engine‘ is actually required?
I think that's the entire point that I'm trying to make. I don't actually know,
and if you are coming to the website there really isn't a way for you to know
what is or isn't ne
On Wed, Sep 26, 2018 at 4:56 AM Carsten Ziegeler wrote:
> ...For example if you want to use JCR, then this adds a bunch of new
> bundles to the mix which are required for that scenario..
I agree and I think the provisioning / feature model files can express
this nicely, in the end the question mi
For just running Sling you need roughly 30 bundles, from which 12 or so
are Sling bundles. Some of them are Sling commons one, then you need
things like the resource resolver, the servlets bundles and finally a
resource provider.
But I think the notion of required is not really helpfull here,
espe
Hi Jason,
What beyond the ‚engine‘ is actually required?
And even the engine is not required to use some sling bundles.
Sling follows a service oriented architecture thst is very loosely coupled
and expresses minimal depencies. We shouldn’t try to establish wrong
expectations by naming which is w
I still feel like we are missing an axis. One that groups the various bundles
by functionality.
Maybe: Required, Extension, Optional
Required are the minimal bundles you need, Extensions are alternatives or
specific implementations of Required, and Optional is just that.
- Jason
On Tue, Sep
On Tue, 2018-09-18 at 09:38 -0400, Jason E Bailey wrote:
> +1 for defining what the different words mean. I think that's one of
> the problems in this thread is that different words mean different
> things to different people.
One way to approach this would be to link from all badges to a page on
On Tue, Sep 18, 2018 at 3:38 PM Jason E Bailey wrote:
> ...I'll throw "community" and/or "community supported" into the ring for
> consideration as well. For those bundles that aren't supported...
I like it, as a way to indicate that the PMC expects the community to
take care of those bundles, o
+1 for defining what the different words mean. I think that's one of the
problems in this thread is that different words mean different things to
different people.
One of the words I need clarification on is "supported"
>From my understanding so far, supported means a commitment made by the PM
On Tue, Sep 18, 2018 at 11:37 AM Robert Munteanu wrote:
> ...Maybe 'unsupported' is a more expressive term than 'contrib'?
> (Although it might be scarier)...
It's more precise, I agree, but I would argue that those modules are
not actually unsupported, they are supported, but only on a best
effo
On Tue, 2018-09-18 at 09:26 +0200, Bertrand Delacretaz wrote:
> Hi,
>
> On Thu, Sep 13, 2018 at 6:48 PM Daniel Klco wrote:
> > ...One concern I have with the experimental (or perhaps the
> > definition
> > therein) is that it seems much more bleeding edge than what we
> > currently
> > consider c
Hi,
On Thu, Sep 13, 2018 at 6:48 PM Daniel Klco wrote:
> ...One concern I have with the experimental (or perhaps the definition
> therein) is that it seems much more bleeding edge than what we currently
> consider contrib
I think contrib and experimental refer to different axes.
There's the
I much like this set of definitions. I particularly like the Extensions set
as this could accommodate the large number of modules which are used by
downstream applications, but are not "required" for Sling to run. The only
item I might argue, is that Contrib may be a better fit than Legacy, e.g.
th
My take -
Core - Does this mean it has to be in the starter? Does everything that shows
up in the starter means it's Core? My take on the concept of "Core" is that
these are the minimal set of bundles required for Sling and that every Sling
product should have.
Extensions - ? These are bundl
Hi Daniel,
We had no native English speaker in the room when we came up with
“experimental”. However, I think it denotes exactly the status of a module that
was contributed to Sling but was never made a part of the core. I wouldn’t
necessarily call a contrib module unmaintained, however its usa
One concern I have with the experimental (or perhaps the definition
therein) is that it seems much more bleeding edge than what we currently
consider contrib. Is there some more middle ground here, between "not part
of the "core"" and "use on your own risk, probably not well maintained"?
On Thu, S
- current contrib/deprecated state maintained in [1]
- status explanations pages missing e.g. [2]
- we currently have not process when a module should be marked as deprecated -
here is a proposal:
- export statistics on module usage (downloads) from maven central statistics
- mark modules as
21 matches
Mail list logo
