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:37:23 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

------------------------------------------------------------------------------
  Project Name: JSecurity
  ---------------------------------------------------------------------------
  
- == Proposal ==
+ == Introduction ==
  
  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:
+ === Key Features & Goals ===
  
   * The simplest and easiest to understand Java Security API possible. 
   * Authentication (log-in) across one or more pluggable ''Realms'' (JDBC, LDAP, etc), providing
PAM (Pluggable Authentication Module)  functionality.
@@ -20, +20 @@

   * Dynamic security model support allowing users, roles, and permissions to be changed and
assigned dynamically at runtime.
   * Dynamic Instance-level access control - the ability to secure individual instances (files,
objects, users, etc) at runtime.
   * POJO-based Enterprise Session Management - access to clusterable/distributed/federated
user sessions in web ''or non-web'' environments via the same API.
-  * Heterogeneous client session access - access shared session state across client mediums
(web MVC, Swing, Flash, etc).
+  * Heterogeneous client session access - access shared session state across client mediums
(web MVC, Swing, Flash, C#+SOAP etc).
   * 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 ===
+ ==== Meritocracy ====
  
  The JSecurity project will be meritocratic. The project will follow the guidelines
  (http://apache.org/foundation/how-it-works.html#meritocracy) of the Apache
@@ -44, +44 @@

  and engaging in discussion on how the code works and is structured. In the end,
  we are committed to creating an environment to foster a meritocracy.
  
- === Community ===
+ ==== 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.
  
- === Core Developers ===
+ ==== Core Developers ====
  
  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:
  
@@ -58, +58 @@

   * Peter Ledbrook
   * Allan Ditzel
  
- === Alignment ===
+ ==== 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.
  
@@ -66, +66 @@

  
  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 ==
+ == 0.2 Warning Signs ==
  
  === Orphaned products ===
  
@@ -98, +98 @@

  
  ---------------------------------------------------------------------------
  
- == (1) Project Scope ==
+ == 1. Project Scope ==
  
  The scope of the JSecurity project would be the continued development of JSecurity
  technology core infrastructure software, including the related utilities and tools.
  The development would include adding new features and improving performance, scalability,
quality, and
  extensibility.
  
+ ---------------------------------------------------------------------------
+ 
- == (2) Identify the initial source from which the project is to be populated ==
+ == 2. Identify the initial source from which the project is to be populated ==
  
  The initial resources would be garnered from:
      * JSecurity SourceForge repository
        (http://sourceforge.net/projects/jsecurity/)
  
- ==  (3) Identify the ASF resources to be created ==
+ ---------------------------------------------------------------------------
  
+ == 3. Identify the ASF resources to be created ==
+ 
- === (3.1) Mailing list(s) ===
+ === 3.1 Mailing list(s) ===
      * jsec-ppmc (with moderated subscriptions)
      * jsec-dev
      * jsec-commits
      * jsec-user
  
- === (3.2) Subversion or CVS repositories ===
+ === 3.2 Subversion or CVS repositories ===
  
  JSecurity would like to use a Subversion repository: https://svn.apache.org/repos/asf/incubator/jsecurity
  
- === (3.3) Jira (issue tracking) ===
+ === 3.3 Jira (issue tracking) ===
  
  Since JSecurity would have its own release cycle, it should have its own JIRA project
-     * Project Name: JSecurity
+  * Project Name: JSecurity
-     * Project Key: JSEC
+  * Project Key: JSEC
  
+ ---------------------------------------------------------------------------
  
- == (4) identify the initial set of committers ==
+ == 4. Identify the initial set of committers ==
+  * Alan Cabrera (adc@apache.org)
+  * Les Hazlewood
+  * Jeremy Haile
+  * Tim Veil
+  * Peter Ledbrook
+  * Allan Ditzel  
  
+ ---------------------------------------------------------------------------
-     * Alan Cabrera (adc@apache.org)
-     * Les Hazlewood
-     * Jeremy Haile
-     * Tim Veil
-     * Peter Ledbrook
-     * Allan Ditzel  
  
- == (5) identify apache sponsoring individual ==
+ == 5. Identify apache sponsoring individual ==
  
  We kindly request the Apache Incubator PMC to accept sponsorship for this project.
  
  === Champion ===
-     * Alan D. Cabrera
+  * Alan D. Cabrera
  
  === Mentors ===
+  * Alan D. Cabrera
-     * Paul Fremantle
+  * Paul Fremantle
-     * Alex Karasulu
+  * Alex Karasulu
-     * Emmanuel Lecharny
+  * Emmanuel Lecharny
  

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


Mime
View raw message