svn commit: r1015133 - in /websites/staging/directory/trunk/content: ./ fortress/history.html

[bu...@apache.org]

Author: buildbot
Date: Sat Jul  8 15:24:44 2017
New Revision: 1015133

Log:
Staging update by buildbot for directory

Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/fortress/history.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Jul  8 15:24:44 2017
@@ -1 +1 @@
-1800132
+1801298

Modified: websites/staging/directory/trunk/content/fortress/history.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/history.html (original)
+++ websites/staging/directory/trunk/content/fortress/history.html Sat Jul  8 15:24:44 2017
@@ -172,7 +172,7 @@ h2:hover > .headerlink, h3:hover > .head
 <p>In 2009 a small team of developers[1], who are brothers, began work on the <em>Open Access Manager</em> project.  From its onset, the push behind this project was to build a fully functioning access control system that is based on  open standards and wholly open source.  In particular, Role-Based Access Control (ANSI INCITS 359) was a focal point, although that adherence brought with it a need for expanded coverage into other areas like auditing and administration.  After a couple of years of coding in their spare time, the brothers unveiled the project at the 2011 LDAPCon in Heidelberg, and with it a new name - <em>Fortress</em>.  At the same time, it was announced that the OpenLDAP foundation would sponsor the project and it would be released under a BSD-style variant of an Open Source Software license.</p>
 <p>That first release, back in 2011, included just the fortress core and realm components, but development of the web interface (commander) and rest server (enmasse) was already underway.  A few more years saw many more releases and the eventual completion of the commander and enmasse rounding out the entire product line into what's available today.</p>
 <p>Eventually, it was understood that nights and weekends of a few developers isn't enough and so if the fortress concept was to survive, it had to be carried into a larger field.  In 2014 the Fortress project moved from its OpenLDAP foundation home into the ASF as a subproject of the Apache Directory.</p>
-<p>This new home proved worthy as the influx of new talent gained from being associated with the Apache Directory project, along with added exposure from its community has brought with it many gains and improvements.  One day the Fortress project will have to move yet again.  It'll spin off its mentor, Apache Directory, and become a top-level project.  But we're not ready for that just yet...   </p>
+<p>This new home proved worthy as the influx of new talent gained from being associated with the Apache Directory project, along with added exposure from its community has brought with it many gains and improvements.  </p>
 <p>Footnotes:
 [1]. team roster in 2009 consisted of Kelly McKinney (engineering manager), Kevin McKinney (fortress web developer), and Shawn McKinney (fortress core developer).</p>