Re: [Acegisecurity-developer] Captcha

2005-06-25 Thread Marc-Antoine Garrigue
Hi Georges, all, I am a member of the JCaptcha team, and we have planned to release a new JCaptcha-module in order to integrate it with Acegi. We are so honored that you think about it too! Our plan is to provide a standard way to ckeck user humanity, which can be needed in many situations (postin

RE: [Acegisecurity-developer] Captcha

2005-07-03 Thread marc antoine garrigue
: "Ben Alex" <[EMAIL PROTECTED]> To: Sent: Sunday, June 26, 2005 12:37 AM Subject: Re: [Acegisecurity-developer] Captcha > Marc-Antoine Garrigue wrote: > > > Ben Alex told me recently that the API is now stabilized and thus we > > planned to share our code before

RE: [Acegisecurity-developer] Captcha

2005-07-05 Thread marc antoine garrigue
hat > approach with their AJAX framework (well, sort of) and I think it opens it > up to a whole new set of people. I agree. Best regards. MAG > > > > - Original Message - > From: "marc antoine garrigue" <[EMAIL PROTECTED]> > To: > Sent:

RE: [Acegisecurity-developer] Captcha

2005-07-08 Thread marc antoine garrigue
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Ben Alex > Sent: mardi 5 juillet 2005 11:56 > To: acegisecurity-developer@lists.sourceforge.net > Subject: Re: [Acegisecurity-developer] Captcha > > marc antoine garrigue wr

RE: [Acegisecurity-developer] Captcha

2005-07-19 Thread marc antoine garrigue
; Ben Alex > Sent: lundi 11 juillet 2005 03:01 > To: acegisecurity-developer@lists.sourceforge.net > Subject: Re: [Acegisecurity-developer] Captcha > > marc antoine garrigue wrote: > > >Hi all, > >I have some question regarding the development rules: > >-Where

RE: [Acegisecurity-developer] Captcha

2005-07-19 Thread marc antoine garrigue
Done. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Ben Alex > Sent: mardi 19 juillet 2005 13:25 > To: acegisecurity-developer@lists.sourceforge.net > Subject: Re: [Acegisecurity-developer] Captcha > > marc antoi

Re: [Acegisecurity-developer] IMPORTANT: Project management procedures

2005-07-28 Thread Marc-Antoine Garrigue
+1 MAGOn 7/25/05, Ben Alex <[EMAIL PROTECTED]> wrote: Hi everyoneNow that we've got 14 developers with CVS rights, and we've recentlyintroduced JIRA, I wish to propose some project management procedures.These are aimed at making life easier for all of us, and helping the community to understand ou

Re: [Acegisecurity-developer] Anyone experiencing core tests failing?

2005-09-19 Thread Marc-Antoine Garrigue
hp___ Home: http://acegisecurity.sourceforge.netAcegisecurity-developer mailing listAcegisecurity-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer-- Best regards. Marc-Antoine Garrigue

RE: [Acegisecurity-developer] Anyone experiencing core tests failing?

2005-09-20 Thread marc antoine garrigue
test report? Best Regards MAG       From: Marc-Antoine Garrigue [mailto:[EMAIL PROTECTED]] Sent: lundi 19 septembre 2005 10:13 To: acegisecurity-developer@lists.sourceforge.net Subject: Re: [Acegisecurity-developer] Anyone experiencing core tests failing?   Hi, I'll take a lo

Re: [Acegisecurity-developer] Re: CAS configuration

2006-04-19 Thread Marc-Antoine Garrigue
join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmdlnk&kid0944&bid$1720&dat1642 > ___ > Home: http://acegisecurity.org > Acegisecurity-developer mailing list

Re: [Acegisecurity-developer] Releasing 1.0.2

2006-09-07 Thread marc antoine garrigue
Hi all, May I commit the SEC-304 fix code before 1.0.2 release? Best Regards MAG > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Carlos Sanchez > Sent: vendredi 8 septembre 2006 07:36 > To: acegisecurity-developer@lists.sourceforge.net > Subject:

Re: [Acegisecurity-developer] Releasing 1.0.2

2006-09-24 Thread marc antoine garrigue
t > Subject: Re: [Acegisecurity-developer] Releasing 1.0.2 > > marc antoine garrigue wrote: > > > May I commit the SEC-304 fix code before 1.0.2 release? > > This change is in a sensitive area of code. You can commit provided that > it does not change the API or break b