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 <[email protected]> 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
