You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Oliver Lietz <ap...@oliverlietz.de> on 2018/06/20 17:41:10 UTC

Upcoming Scripting releases – contrib

hi,

I'm planning to release Scripting FreeMarker, Groovy and Thymeleaf shortly and 
"move them out of contrib" – any concerns?

Do we need a contrib status at all now activity is much more visible due to 
GitHub? IMHO there are some more modules where "contrib" status doesn't make 
sense, e.g. Security, Rewriter, Commons HTML and Pipes.

Regards,
O.


Re: Upcoming Scripting releases – contrib

Posted by Eugen Stan <ie...@netdava.com>.
Woot Woot!

On 20.06.2018 20:41, Oliver Lietz wrote:
> hi,
>
> I'm planning to release Scripting FreeMarker, Groovy and Thymeleaf shortly and 
> "move them out of contrib" – any concerns?
>
> Do we need a contrib status at all now activity is much more visible due to 
> GitHub? IMHO there are some more modules where "contrib" status doesn't make 
> sense, e.g. Security, Rewriter, Commons HTML and Pipes.
>
> Regards,
> O.
>



Re: Upcoming Scripting releases – contrib

Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi Jason,

On Thu, Jun 21, 2018 at 2:53 PM Jason E Bailey <je...@apache.org> wrote:
> ...I've been thinking about this in relation to the downloads section. I believe it would be helpful to
> partition the downloads into sections that help describe their roles....

Agreed, and I think these partitions should be based on
https://issues.apache.org/jira/browse/SLING-7684 badges, which is why
I suggested earlier creating our own badges for static things like
contrib, core etc. and put them under sling.apache.org/res/badges so
we have long-term stable URLs for them that we can analyze in scripts.

The badges can then also be used at http://sling.apache.org/repolist.html

-Bertrand

Re: Upcoming Scripting releases – contrib

Posted by Jason E Bailey <je...@apache.org>.
I've been thinking about this in relation to the downloads section. I believe it would be helpful to partition the downloads into sections that help describe their roles.

Some ideas being -

Core - being modules that make Sling what it is and must be installed

Integrations - Not core, but would make Sling work in different environments, this would contain various resource providers, datasource provider, security providers, etc.

Add-ons /Features - Not something everyone needs, and really doesn't fit into the REST framework model, but people have found them useful, maybe a re-branding of contrib?


- Jason

On Thu, Jun 21, 2018, at 3:00 AM, Bertrand Delacretaz wrote:
> Hi,
> 
> On Wed, Jun 20, 2018 at 7:41 PM Oliver Lietz <ap...@oliverlietz.de> wrote:
> > ...Do we need a contrib status at all now activity is much more visible due to
> > GitHub?...
> 
> I think we do - "contrib" is our way to say "this module is not
> considered core and might stop being maintained without notice".
> 
> I think we should use badges for such classifications, as per
> https://issues.apache.org/jira/browse/SLING-7684
> 
> -Bertrand

Re: Upcoming Scripting releases – contrib

Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi,

On Wed, Jun 20, 2018 at 7:41 PM Oliver Lietz <ap...@oliverlietz.de> wrote:
> ...Do we need a contrib status at all now activity is much more visible due to
> GitHub?...

I think we do - "contrib" is our way to say "this module is not
considered core and might stop being maintained without notice".

I think we should use badges for such classifications, as per
https://issues.apache.org/jira/browse/SLING-7684

-Bertrand