svn commit: r1633411 - /directory/site/trunk/content/sources.mdtext

[el...@apache.org]

Author: elecharny
Date: Tue Oct 21 16:18:02 2014
New Revision: 1633411

URL: http://svn.apache.org/r1633411
Log:
Updated the page to explain how to work with Fortress source base

Modified:
    directory/site/trunk/content/sources.mdtext

Modified: directory/site/trunk/content/sources.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/sources.mdtext?rev=1633411&r1=1633410&r2=1633411&view=diff
==============================================================================
--- directory/site/trunk/content/sources.mdtext (original)
+++ directory/site/trunk/content/sources.mdtext Tue Oct 21 16:18:02 2014
@@ -18,7 +18,7 @@ Notice: Licensed to the Apache Software 
 
 # Sources
 
-Sources for the Apache Directory projects are currently managed through [Subversion](http://subversion.tigris.org|subversion.tigris.org). For each project you can find a detailed description how to checkout and build the source on the project documentation. This page is just a short overview.
+Sources for the Apache Directory projects are currently managed through [Subversion](http://subversion.tigris.org|subversion.tigris.org), except for Fortress Core which is [git base](https://git-wip-us.apache.org/). For each project you can find a detailed description how to checkout and build the source on the project documentation. This page is just a short overview.
 
 ![Subversion](images/subversion_logo.png)
 
@@ -26,16 +26,25 @@ Sources for the Apache Directory project
 
 If you just want to browse the source code, you can use the [web interface to Subversion](http://svn.apache.org/viewvc/directory). This is current at all times.
 
-## Normal Subversion Access
+## Web access to Git
 
-Anyone can check code out of Subversion. You only need to specify a username and password in order to update the Subversion repository, and only Directory committers have the permissions to do that. We run Subversion over standard HTTPS, so hopefully you won't have problems with intervening firewalls.
+If you just want to browse the source code, you can use the [web interface to Git](https://git-wip-us.apache.org/repos/asf?p=directory-fortress-core.git). This is current at all times.
 
-### Check out from Subversion
+
+## Normal Subversion/Git Access
+
+Anyone can check code out of Subversion. You only need to specify a username and password in order to update the Subversion repository, and only Directory committers have the permissions to do that. We run Subversion and Git over standard HTTPS, so hopefully you won't have problems with intervening firewalls.
+
+### Check out from Subversion or Git
 
 Again, anyone can do this. Use a command like:
 
 	svn checkout http://svn.apache.org/repos/asf/directory/apacheds/trunk-with-dependencies
 
+or for Fortress :
+
+    git clone https://git-wip-us.apache.org/repos/asf/directory-fortress-core.git fortress
+
 to check out the current version of the server, for instance.
 
 The following table displays the URL of each project, and the URL where you can find information about how to build each project.
@@ -48,6 +57,7 @@ The following table displays the URL of 
 | [Apache LDAP API](http://directory.apache.org/api/developer-guide.html) | [http://svn.apache.org/repos/asf/directory/shared/trunk/](http://svn.apache.org/repos/asf/directory/shared/trunk/) |
 | [Apache Mavibot](http://directory.apache.org/mavibot/developer-guide.html) | [http://svn.apache.org/repos/asf/directory/mavibot/trunk/](http://svn.apache.org/repos/asf/directory/mavibot/trunk/) |
 | [Apache eSCIMo](http://directory.apache.org/escimo/developer-guide.html) | [http://svn.apache.org/repos/asf/directory/escimo/trunk/](http://svn.apache.org/repos/asf/directory/escimo/trunk/) |
+| Apache Fortress Core | [https://git-wip-us.apache.org/repos/asf/directory-fortress-core.git](https://git-wip-us.apache.org/repos/asf/directory-fortress-core.git) |
 | Apache Directory Site | [http://svn.apache.org/repos/asf/directory/site/trunk/](http://svn.apache.org/repos/asf/directory/site/trunk/) |
 
 ### Commit Changes to Subversion
@@ -68,6 +78,18 @@ Subversion will prompt you for a passwor
 For committers to be able to commit modification, they should have had checked out the project files using **https** instead of **http**.
 </DIV>
 
+###  Commit changes to Git
+
+Any Directory committer should have a shell account on git-wip-us.apache.org.
+
+You can use a command like this to push your changes to the repository :
+
+    git push
+
+<DIV class="note" markdown="1">
+For committers to be able to commit modification, they should have had checked out the project files using **https** instead of **http**.
+</DIV>
+
 ## Read Only Git Repositories
 
 There are also read only git repositories, which are mirroring the subversion repositories.