This document provides an overview of the various documents and links that are part of this project's general information:
- Community Roles and Processes
- Project Team
- Mailing Lists
- Issue Tracking
- Source Repository
- Continuous Integration
- Project License
- Documentation Repository
These are the mailing lists that 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.
|Sling Users List||Subscribe||Unsubscribe||users at sling.apache.org||lists.apache.org||www.mail-archive.com MarkMail Nabble|
|Sling Developers List||Subscribe||Unsubscribe||dev at sling.apache.org||lists.apache.org||www.mail-archive.com MarkMail Nabble|
|Sling Source Control List||Subscribe||Unsubscribe||lists.apache.org||www.mail-archive.com MarkMail|
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.
A number of Sling modules that are not being developed further have been moved to the Sling Attic in the svn repository that we used until late 2017.
Now that the Sling codebase is split in multiple Git repositories, we'll probably keep such modules in place but mark them as being retired. We haven't had such a case since the move to Git, we will clarify once that happens.
Sling builds run automatically on the ASF's Jenkins instance, triggered by commits.
We maintain multiple build jobs, typically one or two per module. These are grouped into two views:
- Sling, which holds all Sling-related jobs
- Sling-Dashboard, which holds all Sling jobs needing attention, such as failed jobs.
More documentation regarding the Jenkins setup is available as wiki links from the views mentioned above.
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.
- Locally check out the git repository.
- Edit the documentation, don't commit.
- From the command line
git diff > site.patch.
- Navigate to the Jira issue tracker.
- Create an account and/or login.
- Create a ticket, enter a description and choose Documentation for Components.
- Select the ticket, click more, select attach files and attach your Git patch.
Additionally there is a Github hosted Apache Sling Site Project Mirror which can be used to submit changes as well.
- Navigate to the Apache Sling Site Project Mirror.
- Create an account and/or login.
- Edit the documentation using the edit icon Fork this project and edit this file.
- Once all changes are done click New pull request.
- Select base fork:apache/sling-site base:master as the project to push to