It’s obvious that we need to define the boundaries of IdentityPython.
Earlier there was a discussion about whether the Java & JavaScript Google/OIDF RP
libraries
would be maintained by IdentityPython since they have a clear connection to the Python
Google/OIDF RP package.
I got the impression then that most people where for having them.
So, what’s reason enough to not care about the python in IdentityPython.
On 15 Oct 2018, at 18:36, Leif Johansson <leifj at
sunet.se> wrote:
The pyFF project which is part of IdentityPython has been working with
RA21 to produce a PoC discovery service (as some of you already know).
At a meeting in Orlando yesterday it was decided to push forward with
a production-scale pilot. To this end it becomes necessary to separate
the frontend (i.e "webby") parts of the pyFF discovery service from
the pyFF codebase.
Although pyFF is mainly python the discovery parts were always mostly
javascript and other frontend technologies and so do not obviously
fit within IdentityPython as a project.
However I would like to make the yet-to-be-named frontend parts of
pyFF into an IdentityPython project and put this question to the board
to discuss.
Cheers Leif
PS Yes Mike we know about accountchooser and openyolo but our
requirements have pushed us in a different direction DS
_______________________________________________
Idpy-board mailing list
Idpy-board at lists.sunet.se
https://lists.sunet.se/listinfo/idpy-board
— Roland
The higher up you go, the more mistakes you are allowed. Right at the top, if you make
enough of them, it's considered to be your style.
-Fred Astaire, dancer, actor, singer, musician, and choreographer (10 May 1899-1987)