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 20:02:15 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

------------------------------------------------------------------------------
   * Authorization (access control) via one or more of said Realms.
   * 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.
+  * POJO-based Enterprise Session Management - access to clustered/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, C#+SOAP etc).
   * Simple SSO (Single Sign-On) support.
   * Simple Cryptography API.
@@ -30, +30 @@

  
  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.
+ Furthermore, 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 ===
  
@@ -38, +38 @@

  
  The JSecurity project will be meritocratic. The project will follow the guidelines
  (http://apache.org/foundation/how-it-works.html#meritocracy) of the Apache
- Software Foundation. In order to achieve this, we plan on proactively recruiting
+ Software Foundation. In order to achieve this, we plan on pro actively recruiting
  individuals in the Community to get involved in the project: specifying work
  that needs to be done, encouraging bug fixes, enhancements, and advancements,
  and engaging in discussion on how the code works and is structured. In the end,
@@ -78, +78 @@

  projects, including Spring (http://www.springframework.org), Hibernate (http://www.hibernate.org),
Grails (http://www.grails.org), and others.  All have been involved with source code that
has been released under
  an open source license using an open source development process to varying degrees. All
current committers are comfortable with normal meritocracy rules, as that is how the development
team informally operates now. We do not in any way expect any difficulty in executing under
normal ASF meritocracy rules.
  
- ==== Homogenous developers ====
+ ==== Homogeneous developers ====
  
  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.
  
@@ -107, +107 @@

  
  ---------------------------------------------------------------------------
  
- == 2. Identify the initial source from which the project is to be populated ==
+ == 2. Initial Population Source ==
  
  The initial resources would be garnered from:
      * JSecurity SourceForge repository
@@ -115, +115 @@

  
  ---------------------------------------------------------------------------
  
- == 3. Identify the ASF resources to be created ==
+ == 3. ASF Resources Needed ==
  
- === 3.1 Mailing list(s) ===
+ === 3.1 Mailing lists ===
   * jsec-ppmc (with moderated subscriptions)
   * jsec-user
   * jsec-dev
   * jsec-scm (scm = Software Configuration Management for SVN commits, automated build notifications,
et. al.)
  
- === 3.2 Subversion or CVS repositories ===
+ === 3.2 Revision Control System ===
  
  JSecurity would like to use a Subversion repository: https://svn.apache.org/repos/asf/incubator/jsecurity
  
- === 3.3 Jira (issue tracking) ===
+ === 3.3 Issue Tracking ===
  
  Since JSecurity would have its own release cycle, it should have its own JIRA project
   * Project Name: JSecurity
@@ -135, +135 @@

  
  ---------------------------------------------------------------------------
  
- == 4. Identify the initial set of committers ==
+ == 4. Initial Comitters ==
   * Alan Cabrera (adc@apache.org)
   * Les Hazlewood
   * Jeremy Haile
@@ -145, +145 @@

  
  ---------------------------------------------------------------------------
  
- == 5. Identify apache sponsoring individual ==
+ == 5. Sponsoring Individual ==
  
  We kindly request the Apache Incubator PMC to be the sponsor for this project.
  

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


Mime
View raw message