Re: [newmaint-site] nm.debian.org updates

2014-09-02 Thread Enrico Zini
On Mon, Sep 01, 2014 at 01:32:06PM +0200, Enrico Rossi wrote: nm - login - access with alioth account - back to nm main page with nothing changed (login button still there). I'm not authorized? I'm not suppose to access? I'm not ... something? I think some sort of message/result would be

Re: [newmaint-site] nm.debian.org updates

2014-09-01 Thread Enrico Rossi
Hi Enrico, a quick note, On Sun, Aug 31, 2014 at 09:34:12AM -0700, Enrico Zini wrote: I have done a lot of work on nm.debian.org, mostly refactoring and unit testing, with the goal of finally allowing site logins to anyone with an alioth account. nm - login - access with alioth account -

Re: [newmaint-site] nm.debian.org updates

2014-09-01 Thread Matteo F. Vescovi
Hi! On 2014-09-01 at 13:39 (CEST), Enrico Rossi wrote: nm - login - access with alioth account - back to nm main page with nothing changed (login button still there). Yep, I confirm the same behaviour. HTH. Cheers. -- Matteo F. Vescovi | Debian Maintainer GnuPG KeyID:

Re: [newmaint-site] nm.debian.org updates

2014-09-01 Thread Enrico Zini
On Mon, Sep 01, 2014 at 10:38:23AM -0300, Eriberto wrote: I am trying to advocate Dariusz Dwornikowski now (DD uploading). However, I got 'Server Error (500)'. I hope this help. Thanks for your nice work around NM. I quickly pushed a fix from the airport and I didn't have time to check it:

Re: [newmaint-site] nm.debian.org updates

2014-09-01 Thread Eriberto
Working! Thanks! Eriberto 2014-09-01 13:24 GMT-03:00 Enrico Zini enr...@enricozini.org: I quickly pushed a fix from the airport and I didn't have time to check it: can you please try again? -- To UNSUBSCRIBE, email to debian-newmaint-requ...@lists.debian.org with a subject of unsubscribe.

nm.debian.org updates

2014-08-31 Thread Enrico Zini
Hello, I have done a lot of work on nm.debian.org, mostly refactoring and unit testing, with the goal of finally allowing site logins to anyone with an alioth account. This is a summary of what I have done: - refactored the permission code: computing who-can-do-what-to-whom now happens