On Thu, 14 Oct 2010 09:55:51 +0200, Zygmunt Krynicki
wrote:
> If we work together we might do that. Don't worry about external
> dependencies yet. If it works we'll worry about solving that problem.
Well, we can work in parallel on that. I don't want to have code queued
up which we ask IS to dep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
W dniu 13.10.2010 19:52, James Westby pisze:
> On Wed, 13 Oct 2010 12:35:54 -0300, Guilherme Salgado
> wrote:
>> I think we can use existing libraries (python-oauth and
>> lazr.authentication) and follow the examples of Canonical django
>> projects t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
W dniu 14.10.2010 04:19, Michael Hudson pisze:
> It has to be said, I'm not sure the aesthetic appeal of oauth outweigh
> these costs. It smells a bit overengineered.
Alternatives?
>> 1) We need to allow users to authenticate before we allow them to
[ Apologies to anyone receiving this again, but I have had problems with
mail delivery and wanted to make sure that everyone got this ]
On Wed, 13 Oct 2010 12:35:54 -0300, Guilherme Salgado
wrote:
> I think we can use existing libraries (python-oauth and
> lazr.authentication) and follow the exa
On Tue, 12 Oct 2010 20:36:26 +0200, Zygmunt Krynicki
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi.
>
> As you know we've been trying to deliver an authenticated interface for
> the dashboard for quite some time now without success. Recently we've
> decided to add oauth suppor
On Tue, 2010-10-12 at 20:36 +0200, Zygmunt Krynicki wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi.
>
> As you know we've been trying to deliver an authenticated interface for
> the dashboard for quite some time now without success. Recently we've
> decided to add oauth support t
