Location: pro!vision GmbH, Berlin (Charlottenburg), Germany
Date: September 5th, 2019
|Sling 12 themes|
Where does the current CI experience fall short? Implement quick wins and design more long-term changes if needed
Challenge: Building non-committer PRs with Jenkins is no longer allowed (). Is switching to TravisCI or Cloudbees an option?
Docker Engine on build hosts for integration tests (possible?)
|Committer CLI||Discuss and potentially demo the committer CLI. Polish/implement new features.||1h|
|Minimal Sling instances||Break Apache Sling into features, based on the Sling feature model, and propose different types of Sling applications - e.g. rendering instances with custom code, content authoring instances, etc.||1h|
State of the Sling feature model
Quickly skim through the list of Sling Modules and make a deliberate decision about deprecating them. Also quickly discuss how to tag/reference them in https://sling.apache.org/downloads.cgi and in https://sling.apache.org/repolist.html and on Github (e.g. https://github.com/apache/sling-org-apache-sling-hc-annotations) categories.
Later note: Github tagging is solved with .asf.yaml features for git repositories .