shiro-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lhazlew...@apache.org
Subject svn commit: r733404 - /incubator/jsecurity/board/2009-01.txt
Date Sun, 11 Jan 2009 00:37:16 GMT
Author: lhazlewood
Date: Sat Jan 10 16:37:16 2009
New Revision: 733404

URL: http://svn.apache.org/viewvc?rev=733404&view=rev
Log:
added January 2009 board report

Added:
    incubator/jsecurity/board/2009-01.txt

Added: incubator/jsecurity/board/2009-01.txt
URL: http://svn.apache.org/viewvc/incubator/jsecurity/board/2009-01.txt?rev=733404&view=auto
==============================================================================
--- incubator/jsecurity/board/2009-01.txt (added)
+++ incubator/jsecurity/board/2009-01.txt Sat Jan 10 16:37:16 2009
@@ -0,0 +1,50 @@
+2008-October JSecurity Incubator status report
+
+JSecurity is a powerful and flexible open-source Java security framework
+that cleanly handles authentication, authorization, enterprise session
+management and cryptography.
+
+JSecurity has been incubating since June 2008.
+
+At the end of November, the JSecurity team released a final
+external (non-Apache) release: 0.9.0 final.  All modifications
+after the release were made under the assumption that the next
+release will be an Apache incubating release.
+
+After the November final release, there has been lengthy discussion
+for the month and half following about JSecurity's name and whether
+or not it should be changed to something else.  3 of the 5 project
+mentors for the project voted in favor of changing the name from
+JSecurity to something else, citing concerns of a few external
+(3rd party) products that might cause a name conflict.  Concensus
+was not reached, resulting in the vote.
+
+More recently, the team has debated about how the source tree
+should be configured to allow easy modular builds and to clearly
+delineate the differnece of jsecurity core versus web support and
+3rd party support.  The team came to concensus about an initial
+directory organization and the ant build files were modified to
+reflect the new structure.
+
+Infrastructure migration (noted in our STATUS file) is almost
+complete - all that needs to be done is migration of the jsecurity.org
+website into our incubator snapshot.  A volunteer is currently
+in the process of enabling the existing JSecurity theme in the ASF's
+Confluence export mechanism.
+
+Low-hanging fruit to be cleared hopefully by the next board report is
+all IP clearance:  the Copyright & Licensing and Distribution Rights
+sections of the STATUS file should be able to be completed in their
+entirety.
+
+The biggest exit criteria remaining is Team Collaboration.  Although
+the team is satisfying all collaboration directives and has a good
+community, we need to attract new committers.  Hopefully that will be
+a significant difference in the upcoming months and throughout 2009.
+
+The project team is not considering graduation at this point,
+as the code is not ready for an Apache release. Once IP clearance is
+complete, we'll attempt our first incubator release.
+
+The status is being maintained at
+http://svn.apache.org/repos/asf/incubator/jsecurity/STATUS
\ No newline at end of file



Mime
View raw message