Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <44b57a610805071233i7cc8f39bvb49094c385ae8b2@mail.gmail.com>
Date: Wed, 7 May 2008 15:33:38 -0400
From: "Les Hazlewood" <les@hazlewood.com>
Sender: les.hazlewood@anjinllc.com
To: general@incubator.apache.org
Subject: Re: JSecurity Champion Recruitment
In-Reply-To: <f2e8eedf0805071202s5deea16s3f618644fcc5ae44@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <44b57a610805071155n1f1afb3dk6b5285fe671083bd@mail.gmail.com>
	 <f2e8eedf0805071202s5deea16s3f618644fcc5ae44@mail.gmail.com>

Hi James,

Thanks for the feedback.  Simplicity and ease-of-understanding are
paramount factors when we discuss architectural/implementation
approaches.

On Wed, May 7, 2008 at 3:02 PM, James Carman <james@carmanconsulting.com> wrote:
> I like the idea of JSecurity.  I myself have found Acegi to be
>  somewhat difficult to understand.  I like how simple the JSecurity API
>  is.  I'd be interested in seeing this become a podling.  I don't know
>  if I'm qualified enough to be a "champion" for the project, though.
>
>
>
>  On Wed, May 7, 2008 at 2:55 PM, Les Hazlewood <les@hazlewood.com> wrote:
>  > Hello all,
>  >
>  >  I've been a lurker for a while, attempting to get an overall feel for
>  >  the incubator process, and this is my first foray into (hopefully)
>  >  making things a reality for our project, JSecurity.
>  >
>  >  JSecurity (http://www.jsecurity.org/) is a "powerful and flexible
>  >  open-source Java security framework that cleanly handles
>  >  authentication, authorization, enterprise session management and
>  >  cryptography."
>  >
>  >  Our mission is to "provide the most robust and comprehensive Java
>  >  security framework available while also being very easy to understand
>  >  and extremely simple to use."
>  >
>  >  The JSecurity development team has discussed at length about what it
>  >  means to become an Apache project and what it would mean for our team
>  >  and the future direction of the project.  After having read the
>  >  incubator processes and policies at length, we are now prepared to
>  >  engage with the ASF.  This is our formal attempt at recruiting a
>  >  Champion in the hopes of acquiring guidance into the proposal phase,
>  >  understanding the ASF in more detail and maybe eventually becoming a
>  >  podling.
>  >
>  >  Mission Statement & project origins: http://www.jsecurity.org/about
>  >  High level features overview: http://www.jsecurity.org/features
>  >  Community support - forums, mailing lists, jira:
>  >  http://www.jsecurity.org/support
>  >
>  >  JSecurity is Apache 2.0 licensed.
>  >
>  >  Thank you for any feedback and recommendations.  We look forward to
>  >  your responses.
>  >
>  >  Best regards,
>  >
>  >  Les Hazlewood
>  >  JSecurity lead & project founder
>  >
>  >  ---------------------------------------------------------------------
>  >  To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>  >  For additional commands, e-mail: general-help@incubator.apache.org
>  >
>  >
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>  For additional commands, e-mail: general-help@incubator.apache.org
>
>

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