This document provides an overview of the various documents and links that are part of this project's general information:
The following English-speaking mailing lists have been established for this project. For each list, there is a subscribe, unsubscribe, and an archive link.
The Sling Users List is the preferred way of getting help with Sling. However, you can also Ask a Sling question on StackOverflow if you prefer.
Please subscribe before posting messages to these lists. If you don't, your messages are likely to be delayed, as we need to moderate them, or maybe even become lost in the flow of spam that we get from non-subscribed senders.
|Name||Subscribe||Unsubscribe||Post||ASF Archive||Other Archives|
|Users List||Subscribe||Unsubscribe||users at sling.apache.org||lists.apache.org||www.mail-archive.com|
|Developers List||Subscribe||Unsubscribe||dev at sling.apache.org||lists.apache.org||www.mail-archive.com|
|Commit Events List||Subscribe||Unsubscribe|| ||lists.apache.org||www.mail-archive.com|
This project uses JIRA a J2EE-based, issue tracking and project management application. Issues, bugs, and feature requests should be submitted to the following issue tracking system for this project.
The issue tracker can be found at http://issues.apache.org/jira/browse/SLING
This project uses Git to manage its source code. The source code is hosted on the ASF GitBox setup and replicated to Apache organisation on GitHub. As a developer you may push to either GitBox or GitHub. Note however that for GitHub to work you need to set up your GitHub account with two-factor authentication from the main GitBox page.
To check out the Sling source code, see the instructions from Getting and building Sling.
For additional information see Using Git with Sling.
The source code can be accessed using either the GitHub or GitBox setup.
See Deprecating Sling Modules for how we manage module deprecation.
The Sling Monitor page lists jobs that need attention.
The Sling Folder page lists all jobs.
In any case you wish to customize the jenkins build of a module, just add a
.sling-module.json at the root of your project, with overriden values listed in Jenkins Sling module descriptor.
The documentation website, in fact the very page that you are reading right now, is located at The Apache Sling Site Project. You can contribute without being an official project committer.
git diff > site.patch.
Additionally there is a Github hosted Apache Sling Site Project Mirror which can be used to submit changes as well.