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 Fri, 16 May 2008 19:26:49 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

------------------------------------------------------------------------------
  
  === Community ===
  
- JSecurity had a small but active community for the first couple of years after inception,
with a significant increase in community members the last 6 months.  There are hundreds of
posts in the forums, some dating back over 2 years old.  Current mailing list activity is
around 100+ messages per month, and growing with the accumulation of new contributors and
users.  It is expected that community growth will only flourish as an ASF adopted project.
+ JSecurity had a small but active community for the first couple of years after inception,
with a significant increase in community members the last 6 months.  There are hundreds of
posts in the forums, some dating back over 2 years old.  Current mailing list activity is
around 100+ messages per month and growing with the accumulation of new contributors and users.
 It is expected that community growth will only flourish as an ASF adopted project.
  
  === Core Developers ===
  
- ''FILL ME IN''
+ All developers who have ever committed to the existing code repository are still active
on the current JSecurity team and will continue to participate.  They are:
+ 
+  * Les Hazlewood
+  * Jeremy Haile
+  * Tim Veil
+  * Peter Ledbrook
+  * Allan Ditzel
  
  === Alignment ===
  
+ JSecurity is aligned well with Apache in terms of technologies and licensing. It fits in
well technologically with other Apache projects, which also focus on clustering, web frameworks,
and Java technolgies.
- JSecurity is aligned well with Apache in terms of technologies and licensing. It fits
- in well technologically with other Apache projects, which also focus on
- clustering, web frameworks, and Java technolgies.
  
- ''MAYBE MORE?''
+ We are sure there are quite a few ASF projects that could find utility in JSecurity.  Apache
Tomcat might wish to enhance or simplify its Realm functionality by using JSecurity's native
support for multiple back-end datasources.  There has also already been mention of interest
by the Apache Directory TripleSec team in using JSecurity to support LDAP integration as well
as enable dynamic runtime support for security users, roles, and permissions.  
  
+ Essentially any Apache project that utilizes log-ins, access control, time-based Session
access (in both web and non web environments), or cryptography would find JSecurity beneficial.
  
  == (0.2) Warning Signs ==
  
@@ -83, +88 @@

  
  === No ties to other Apache products ===
  
- Currently JSecurity has a required dependency on Apache Commons Logging, with an optional
dependency on Apache Commons BeanUtils Core.
+ 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.
+ Also based on the above ''Alignment'' section, JSecurity could very quickly become a part
of many other ASF projects, ensuring a successful future within the ASF.
  
  === A fascination with the Apache brand ===
  
- ''FILL ME IN''
+ JSecurity started outside of the ASF under the LGPL license.  The development team voted
unanimously to switch to the Apache 2.0 license to foster a more open community, provide flexible
options for commercial deployment, and also to be eligible as an ASF project.
  
  ---------------------------------------------------------------------------
  

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


Mime
View raw message