On Friday 30 September 2016 10:11:28 Carsten Ziegeler wrote: > Stefan Seifert wrote > > > discussed at the Sling Committer Round Table @ adaptTo() 2016 > > > > before taking steps like migration sling svn to git we should check if we > > have modules that are no longer relevant and maintained, and moving them > > to the "attic" (perhaps creating a new one for this). > > > > esp. in contrib there is a good deal of modules not touched for years and > > perhaps no longer relevant. > I think there are some points to add: > - moving to the attic does not mean that this is bad code or something > like that > - if we move something to the attic it does not mean that we can't move > it out again. > > Based on that I would be rather aggressive on moving things to attic. > > I had a brief look at some parts in contrib, started with scripting. > From those I think we can move the following to the attic > > - freemarker
+ freemarker FreeMarker is a very well known templating language and was donated to the ASF last year (still in incubator). I did made some updates and added some ITs recently and hope to get Sling Models useable soon. Doing a first release afterwards. > - groovy + groovy I did a release in January and already some updates for the next version. > - jsp-taglib-atom > - jst > - python > - ruby > - scala > - velocity > - xproc > > In the JCR folder: > > - compiler > - jackrabbit-client > - js > - ocm > - prefs > > I'm not sure about contrib/s3 - but I think no one really touched that > stuff for a long time, so I would move it to the attic as well. > > I didn't look into the other folders yet. I don't have a strong opinion on that, but not moving anything to attic and creating separate repos for each module would allow other developers to easily fork modules and keep them alive or revive them. Regards, O. > Regards > > Carsten
