Project Information

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

Mailing Lists¶

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.

Issue Tracking¶

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

Source Repository¶

This project uses Subversion to manage its source code. Instructions on Subversion use can be found at http://svnbook.red-bean.com/.

Web Access¶

The following is a link to the online source repository.

http://svn.apache.org/viewvc/sling/trunk

Anonymous access¶

The source can be checked out anonymously from SVN with this command:

$ svn checkout http://svn.apache.org/repos/asf/sling/trunk sling

Developer access¶

Everyone can access the Subversion repository via HTTPS, but Committers must checkout the Subversion repository via HTTPS.

$ svn checkout https://svn.apache.org/repos/asf/sling/trunk sling

To commit changes to the repository, execute the following command to commit your changes (svn will prompt you for your password)

$ svn commit --username your-username -m "A message"

Access from behind a firewall¶

For those users who are stuck behind a corporate firewall which is blocking http access to the Subversion repository, you can try to access it via the developer connection:

$ svn checkout https://svn.apache.org/repos/asf/sling/trunk sling

Access through a proxy¶

The Subversion client can go through a proxy, if you configure it to do so. First, edit your "servers" configuration file to indicate which proxy to use. The files location depends on your operating system. On Linux or Unix it is located in the directory "~/.subversion". On Windows it is in "%APPDATA%\Subversion". (Try "echo %APPDATA%", note this is a hidden directory.)

There are comments in the file explaining what to do. If you don't have that file, get the latest Subversion client and run any command; this will cause the configuration directory and template files to be created.

Example : Edit the 'servers' file and add something like :

[global]
http-proxy-host = your.proxy.name
http-proxy-port = 3128

Continuous Integration¶

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.

Documentation Repository¶

The documentation website, in fact the very page that you are reading right now, is located at The ASF Content Management System’s Sling project. You can contribute without being an official project committer.

Save your changes as an SVN patch:¶

1. Log in as username anonymous and leave the password blank.
2. Click Get sling Working Copy to check out a local branch through the browser.
3. Navigate to a document and click edit.
4. Edit the page in the online markdown editor.
5. Uncheck Quick Mail.
6. Click submit.
7. Click Diff, then Download Diff and save the SVN patch to your computer.

Submit your changes:¶

1. Navigate to the Jira issue tracker.
2. Create an account and/or login.
3. Create a ticket, enter a description and choose Documentation for Components.
4. Select the ticket, click more, select attach files and attach your SVN patch.

Further resources:¶

1. Read the ASF CMS reference for non-committers.
2. Watch a video tutorial by Rob Weir for anonymous users.