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, Sep 13, 2018 at 12:42 PM Stefan Seifert <sseif...@pro-vision.de> wrote: > - 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 deprecated that have both low usage and no committers > willing to actively maintain it > - there is no "attic" any more, so labeling the module as deprecated is > equivalent to attic > - this deprecation check should be done roughly once a year for all > non-deprecated modules > > - the "contrib" flag is difficult to understand what it should mean - we > propose to rename it > - it should be renamed to "experimental" > - modules labeled as experimental (or currently "contrib") must never be > included in the sling starter > - (contrib modules currently includes in starter have to be removed or > "un-contribbed") > - the meaning of "experimental" is: not indented for production use, use > on your own risk, probably not well maintained > > - our sling download page [3] should reflect the deprecated or contrib > status of the modules liste > - this page is the one page users detect most easily, and they should > know when the module is not part of the "core" > > stefan > > [1] https://github.com/apache/sling-aggregator/blob/master/Sling-Repos.csv > [2] > https://github.com/apache/sling-aggregator/blob/master/docs/status/contrib.md > [3] http://sling.apache.org/downloads.cgi > > >
