Hi, I volunteered to provide a list of modules, which are not touched for quite some time; the thought is that that these modules are also less used, and there is a very low (potentially no) interest in maintaining them anymore. If we have such modules, we should consider to move them into the attic, and officially deprecate them. Right now we have 300+ git repositories in github, and my gut feeling is that the current focus is quite narrow on a few dozens of module, and that we many modules which are not in active maintenance yet (that means, that PRs by dependabot are not checked, etc.).
I found a wiki page [1] plus an accompanying ticket SLING-6264 [2] from 2016, in which we already had that discussion, but I think it's time to repeat it. To compile such a list as a starting point for the discussion, I just checked all maven modules for the latest commit in the src/ folder (ignoring all POM updates and any CI/CD settings and badges) and sorted them by their year, just listing the ones which have the last commit before 2020. I used the command [3] to achieve it (works on Linux). The list of modules, in which the latest commit into src/ has been made before 2018 (that means no code change in the last 5 years): ./org-apache-sling-commons-cache-ehcache,Date: 2012 ./org-apache-sling-commons-cache-impl,Date: 2012 ./org-apache-sling-commons-cache-portal,Date: 2012 ./adapter-annotations,Date: 2013 ./org-apache-sling-commons-cache-container-test,Date: 2013 ./org-apache-sling-launchpad-test-fragment,Date: 2013 ./org-apache-sling-auth-xing-api,Date: 2014 ./org-apache-sling-extensions-classloader-leak-detector,Date: 2014 ./org-apache-sling-junit-performance,Date: 2014 ./launchpad-standalone-archetype,Date: 2015 ./launchpad-webapp-archetype,Date: 2015 ./maven-launchpad-plugin,Date: 2015 ./org-apache-sling-hc-junit-bridge,Date: 2015 ./org-apache-sling-jcr-repository-it-resource-versioning,Date: 2015 ./org-apache-sling-launchpad-installer,Date: 2015 ./org-apache-sling-nosql-couchbase-client,Date: 2015 ./org-apache-sling-nosql-launchpad,Date: 2015 ./org-apache-sling-resourceaccesssecurity-it,Date: 2015 ./org-apache-sling-scripting-xproc,Date: 2015 ./org-apache-sling-testing-logging-mock,Date: 2015 ./servlet-archetype,Date: 2015 ./launchpad-debian,Date: 2016 ./org-apache-sling-bnd-models,Date: 2016 ./org-apache-sling-hapi-samplecontent,Date: 2016 ./org-apache-sling-jcr-js-nodetypes,Date: 2016 ./org-apache-sling-nosql-couchbase-resourceprovider,Date: 2016 ./org-apache-sling-nosql-generic,Date: 2016 ./org-apache-sling-nosql-mongodb-resourceprovider,Date: 2016 ./org-apache-sling-resource-editor,Date: 2016 ./org-apache-sling-testing-hamcrest,Date: 2016 ./org-apache-sling-cassandra,Date: 2017 ./org-apache-sling-extensions-webconsolebranding,Date: 2017 ./org-apache-sling-hapi-client,Date: 2017 ./org-apache-sling-hapi,Date: 2017 ./org-apache-sling-hc-it,Date: 2017 ./org-apache-sling-hc-samples,Date: 2017 ./org-apache-sling-installer-factory-model,Date: 2017 ./org-apache-sling-junit-remote,Date: 2017 ./org-apache-sling-launchpad-api,Date: 2017 ./org-apache-sling-launchpad-contrib-testing,Date: 2017 ./org-apache-sling-paxexam-util,Date: 2017 ./org-apache-sling-tail,Date: 2017 ./org-apache-sling-testing-email,Date: 2017 ./taglib-archetype,Date: 2017 Looking at those, a few might be referenced from other sling modules, but many are standalone, and I am not sure if anyone is still using them (xing-auth anyone?) I understand that the mailing list is not necessarily the right place to discuss if an individual module should or should not be moved into an attic. So I will create a page in cwiki (or what's the system we should use today?) and will create a table (just like [1]) and there we can annotate each bundle if it's needed by a different Sling module (which is either actively used/developed or in active maintenance), or if someone is volunteering to maintain it. [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65873121 [2] https://issues.apache.org/jira/browse/SLING-6264 [3] it can probably be done better, but worked for me: find ./* -maxdepth 0 -type d | while read a; do (cd $a; test -d src && echo -n "$a," && git log --date=format:%Y -1 -- src -- | grep Date); done | grep 201 | sort -t ' ' -k 2 -n -- Cheers, Jörg Hoh, https://cqdump.joerghoh.de
