6 a.m.
Hi guys,
OIDF has agreed to host the OIDC libraries that I helped Google build.
They also understand that they must fund the maintenance of the libraries.
To make it more concrete they want the Python packages (which are the only one that are
done) to be moved to the
OIDF GitHub site within the next couple of weeks.
This means that the cryptojwt, oidcmsg, oidcservice and oidcrp repos will be moved away
from IdentityPython.
I people don’t disagree I’d like to keep the OP side repo oidcendpoint and oidc-op (not
there yet) at IdentityPython.
And of course all the repos that has to do with OIDC identity federations.
— 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)
4:53 p.m.
On 2018-06-08 08:00, Roland Hedberg wrote:
Hi guys,
OIDF has agreed to host the OIDC libraries that I helped Google build.
They also understand that they must fund the maintenance of the libraries.
To make it more concrete they want the Python packages (which are the
only one that are done) to be moved to the
OIDF GitHub site within the next couple of weeks.
This means that the cryptojwt, oidcmsg, oidcservice and oidcrp repos
will be moved away from IdentityPython.
I people don’t disagree I’d like to keep the OP side repo oidcendpoint
and oidc-op (not there yet) at IdentityPython.
And of course all the repos that has to do with OIDC identity federations.
Several questions spring to mind... for instance:
- What governance is the OIDF putting in place?
- Is IdentityPython ok depending/relying on what the OIDF delivers?
- Does this mean IdentityPython have to roll our own OIDC-stack now?
- We have a process for moving stuff into IdentityPython but no
process for moving stuff out - what if IdentityPython wants to keep
(a fork of) the OIDF stack?
These questions are probably best treated like the starting point of
a dialogue with the OIDF.
Cheers Leif
6:08 p.m.
8 juni 2018 kl. 18:53 skrev Leif Johansson <leifj
at sunet.se>:
On 2018-06-08 08:00, Roland Hedberg wrote:
All good questions and I agree with Leif we should have a discussion about this with the
OIDF.
-- Roland
"Education is the path from cocky ignorance to miserable uncertainty.” - Mark Twain
Hi guys,
OIDF has agreed to host the OIDC libraries that I helped Google build.
They also understand that they must fund the maintenance of the libraries.
To make it more concrete they want the Python packages (which are the
only one that are done) to be moved to the
OIDF GitHub site within the next couple of weeks.
This means that the cryptojwt, oidcmsg, oidcservice and oidcrp repos
will be moved away from IdentityPython.
I people don’t disagree I’d like to keep the OP side repo oidcendpoint
and oidc-op (not there yet) at IdentityPython.
And of course all the repos that has to do with OIDC identity federations.
Several questions spring to mind... for instance:
- What governance is the OIDF putting in place?
- Is IdentityPython ok depending/relying on what the OIDF delivers?
- Does this mean IdentityPython have to roll our own OIDC-stack now?
- We have a process for moving stuff into IdentityPython but no
process for moving stuff out - what if IdentityPython wants to keep
(a fork of) the OIDF stack?
These questions are probably best treated like the starting point of
a dialogue with the OIDF.
6:19 p.m.
My 2c
8 juni 2018 kl. 18:53 skrev Leif Johansson <leifj
at sunet.se>:
On 2018-06-08 08:00, Roland Hedberg wrote:
Absolutely no idea.
Hi guys,
OIDF has agreed to host the OIDC libraries that I helped Google build.
They also understand that they must fund the maintenance of the libraries.
To make it more concrete they want the Python packages (which are the
only one that are done) to be moved to the
OIDF GitHub site within the next couple of weeks.
This means that the cryptojwt, oidcmsg, oidcservice and oidcrp repos
will be moved away from IdentityPython.
I people don’t disagree I’d like to keep the OP side repo oidcendpoint
and oidc-op (not there yet) at IdentityPython.
And of course all the repos that has to do with OIDC identity federations.
Several questions spring to mind... for instance:
- What governance is the OIDF putting in place? - Is IdentityPython ok depending/relying on what the
OIDF delivers?
Don’t know. I would, be since I would expect most of the contributers to
come out of the IdentityPython crowed and it looks like I
will have the job as chief maintainer. So, if you trust me to look after
your needs … :-)
- Does this mean IdentityPython have to roll our own
OIDC-stack now?
I really hope not. We don’t need one more.
- We have a process for moving stuff into
IdentityPython but no
process for moving stuff out - what if IdentityPython wants to keep
(a fork of) the OIDF stack?
Depends on whether IdentityPython has needs that are not covered by what
is happening with the OIDF copy. I don’t forsee any such needs right now.
These questions are probably best treated like the
starting point of
a dialogue with the OIDF.
Cheers Leif
_______________________________________________
Idpy-discuss mailing list
Idpy-discuss at lists.sunet.se
https://lists.sunet.se/listinfo/idpy-discuss
-- Roland
"Education is the path from cocky ignorance to miserable uncertainty.” - Mark Twain
6:22 p.m.
Skickat från min iPhone
Agreed
The idpy community should have a say tho...
8 juni 2018 kl. 19:19 skrev Roland Hedberg <roland
at catalogix.se>:
My 2c
I trust you. I do not trust Don. See governance question.
8 juni 2018 kl. 18:53 skrev Leif Johansson
<leifj at sunet.se>:
On 2018-06-08 08:00, Roland Hedberg wrote:
Absolutely no idea.
Hi guys,
OIDF has agreed to host the OIDC libraries that I helped Google build.
They also understand that they must fund the maintenance of the libraries.
To make it more concrete they want the Python packages (which are the
only one that are done) to be moved to the
OIDF GitHub site within the next couple of weeks.
This means that the cryptojwt, oidcmsg, oidcservice and oidcrp repos
will be moved away from IdentityPython.
I people don’t disagree I’d like to keep the OP side repo oidcendpoint
and oidc-op (not there yet) at IdentityPython.
And of course all the repos that has to do with OIDC identity federations.
Several questions spring to mind... for instance:
- What governance is the OIDF putting in place? - Is IdentityPython ok depending/relying on what
the OIDF delivers?
Don’t know. I would, be since I would expect most of the contributers to
come out of the IdentityPython crowed and it looks like I
will have the job as chief maintainer. So, if you trust me to look after
your needs … :-) - Does this mean IdentityPython have to roll our
own OIDC-stack now?
I really hope not. We don’t need one more.
- We have a
process for moving stuff into IdentityPython but no
process for moving stuff out - what if IdentityPython wants to keep
(a fork of) the OIDF stack?
Depends on whether IdentityPython has needs that are not covered by what
is happening with the OIDF copy. I don’t forsee any such needs right now. These questions are probably best treated like
the starting point of
a dialogue with the OIDF.
Cheers Leif
_______________________________________________
Idpy-discuss mailing list
Idpy-discuss at lists.sunet.se
https://lists.sunet.se/listinfo/idpy-discuss
-- Roland
"Education is the path from cocky ignorance to miserable uncertainty.” - Mark Twain
2581
days inactive
2581
days old
4 comments
2 participants
participants (2)
-
leifj＠sunet.se -
roland＠catalogix.se