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 14:40:28 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

The comment on the change is:
Changed to link to correct page

------------------------------------------------------------------------------
+ This page has been renamed to ["JSecurityPropsal"].  Please visit there.  Admins:  you can
delete this page (JsecurityProposal) - I just couldn't find the delete link - LesHazlewood
- This proposal seeks to create a project within the Apache Software
- Foundation to continue the development and advancement of JSecurity 
- technology. It has broad backing from the JSecurity Community. 
  
- Thank you for your consideration.
- 
- 
- ---------------------------------------------------------------------------
- '''JSecurity Proposal'''
- 
- ''Proposal for new project JSecurity''
- 
- ---------------------------------------------------------------------------
- 
- == (0) rationale ==
- 
- ''FILL ME IN''
- 
- == (0.1) criteria ==
- 
- === Meritocracy ===
- 
- The JSecurity project will be meritocractic. 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
- 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,
- we are committed to creating an environment to foster a meritocracy.
- 
- === Community ===
- 
- ''FILL ME IN''
- 
- === Core Developers ===
- 
- ''FILL ME IN''
- 
- === 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.
- 
- ''MAYBE MORE?''
- 
- 
- == (0.2) warning signs ==
- 
- === Orphaned products ===
- 
- ''FILL ME IN''
- 
- === Inexperience with open source ===
- 
- The initial committers have varying degrees of experience with open source
- projects. All have been involved with source code that has been released under
- an open source license, but there is limited experience developing code with an
- open source development process. We do not, however, expect any difficulty in
- executing under normal meritocracy rules.
- 
- === Homogenous developers ===
- 
- ''FILL ME IN''
- 
- === Reliance on salaried developers ===
- 
- ''FILL ME IN''
- 
- === No ties to other Apache products ===
- 
- ''Are there any?''
- 
- There are potential future ties (http server, database backend, etc)
- that will be explored.
- 
- === A fascination with the Apache brand ===
- 
- ''FILL ME IN''
- 
- 
- == (1) scope of the project ==
- 
- 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 ==
- 
- The initial resources would be garnered from:
-     * JSecurity
-       (http://sourceforge.net/projects/jsecurity/) project on sourceforge.net
- 
- 
- ==  (3) identify the ASF resources to be created ==
- 
- === (3.1) mailing list(s) ===
-     * jsec-ppmc (with moderated subscriptions)
-     * jsec-dev
-     * jsec-commits
-     * jsec-user
- 
- 
- === (3.2) Subversion or CVS repositories ===
- 
- JSecurity would like to use a Subversion repository.
- 
- === (3.3) Jira (issue tracking) ===
- 
- Since JSecurity would have its own release cycle, it should have its own JIRA project
-     * Project Name: JSecurity
-     * Project Key: JSEC
- 
- 
- == (4) identify the initial set of committers ==
- 
-     * Alan Cabrera (adc@apache.org) 
- 
- 
- == (5) identify apache sponsoring individual ==
- 
- === Champion ===
-     * Alan D. Cabrera
- 
- === Mentors ===
-     * Paul Fremantle
-     * Alex Karasulu
-     * 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