incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "JSecurityProposal" by LesHazlewood
Date Thu, 15 May 2008 17:42:03 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The following page has been changed by LesHazlewood:
http://wiki.apache.org/incubator/JSecurityProposal

------------------------------------------------------------------------------
  
  == Proposal ==
  
- This proposal seeks to create an Apache Software Foundation top-level 
- project to continue the development and advancement of the JSecurity
- open-source framework. It has broad backing from the JSecurity Community.
+ This proposal seeks to create a top-level Apache Software Foundation project to continue
the development and advancement of the JSecurity
+ open-source framework. It has broad backing from the JSecurity Community and unanimous backing
from the current development team.
+ 
  We thank you for your consideration. 
  
  Key Features & Goals:
@@ -24, +24 @@

   * Simple SSO (Single Sign-On) support.
   * Simple Cryptography API.
  
- == (0) rationale ==
+ == (0) Rationale ==
  
  The current JSecurity community (http://www.jsecurity.org) fosters a positive environment
of contribution, feedback and supporting fellow members.  Although already an open-source
project for the last 3+ years, the project as of late has grown quite substantially over the
last six months especially, and it is our desire to see JSecurity be adopted by the Apache
Software Foundation to continue these efforts.  We feel the ASF community will enable the
JSecurity project to reach higher adoption rates with better community support beyond what
we are able to accomplish ourselves.  
  
  Futhermore, a significant number of Apache projects today could find much benefit in JSecurity,
as there is not currently anything in the ASF that addresses its feature set as single unified
project.  We feel that helping other Apache projects would create a symbiotic relationship
beneficial to the existing JSecurity community as well as the ASF.
  
- == (0.1) criteria ==
+ == (0.1) Criteria ==
  
  === Meritocracy ===
  
@@ -59, +59 @@

  ''MAYBE MORE?''
  
  
- == (0.2) warning signs ==
+ == (0.2) Warning Signs ==
  
  === Orphaned products ===
  
@@ -73, +73 @@

  
  === Homogenous developers ===
  
- All 5 current JSecurity committers works for different companies, with no overlap.  They
live in different parts of the world, mostly in the United States and Europe.
+ All 5 current JSecurity committers works for different companies, with no overlap.  They
live in different parts of the world, in the United States and Europe.
  
  === Reliance on salaried developers ===
  
@@ -81, +81 @@

  
  === No ties to other Apache products ===
  
- ''Are there any?''
+ Currently JSecurity has a required dependency on Apache Commons Logging, with an optional
dependency on Apache Commons BeanUtils Core.
  
+ There are many potential future ties for projects that could find utility in JSecurity.
 Apache Tomcat might find utility in its Realm implementation support for multiple back-end
datasources.  There has already been mention on interest by the Apache Directory TripleSec
team in supporting LDAP integration as well as dynamic security support for users, roles,
permissions, et. al.  Any Apache project that uses or performs log-ins, access control, time-based
Session access, or cryptography would find JSecurity beneficial.
- There are potential future ties (http server, database backend, etc)
- that will be explored.
  
  === A fascination with the Apache brand ===
  

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message