9:33 p.m.
Hi all,
Obviously we'll do a fair bit of agenda building on site, but this list
should give us a sense of what we need to cover and how much time we
have. Does anyone have topics they would like to add, or want to propose
a more precisely defined schedule in advance?
-----
Logistics:
Monday, 5 February 2018, Room E, 13:00-17:30
Tuesday, 6 February 2018, Room E, 09:00-12:30, 13:30-16:00 (if needed)
Topics to cover:
* Technical harmonization: project may need dedicated time, and we
need to decide which projects fall under the idpy umbrella,
including discussions on who is the tech lead for each, what the
project maturity levels are, where we need to target refactoring of code
*
o pyOP
o pyOIDC
o OICcli
o OICmsg
o pyJWKEST
o Satosa
o pySAML
o pyff
* governance
* any open pull requests
5 February 2018
13:00-14:00 - Introduction, agenda building
14:00-17:00 - open
17:00-17:30 - review action items from the day
6 February 2018 (maybe have the open time be split between each project?)
09:00-10:00 - Governance
10:00-10:30 - agenda building
10:30-12:30 - open
13:30-15:30 - open
15:30-16:00 - review action items from the day
12:05 a.m.
Hi all,
Unfortunately I cannot join the meeting on Feb 5. I have however a major
interest in SaToSa and pyFF. Would it be possible to put these on the
agenda for Feb 6?
Also, it seems to me Technical harmonization, Governance and Open pull
requests seems to me to be project specific, as these depend on where
the project is coming from and where it currently stands. Does it make
sense to treat these topics on a per project basis?
Best,
Niels
On 16-01-18 20:33, Heather Flanagan wrote:
Hi all,
Obviously we'll do a fair bit of agenda building on site, but this
list should give us a sense of what we need to cover and how much time
we have. Does anyone have topics they would like to add, or want to
propose a more precisely defined schedule in advance?
-----
Logistics:
Monday, 5 February 2018, Room E, 13:00-17:30
Tuesday, 6 February 2018, Room E, 09:00-12:30, 13:30-16:00 (if needed)
Topics to cover:
* Technical harmonization: project may need dedicated time, and we
need to decide which projects fall under the idpy umbrella,
including discussions on who is the tech lead for each, what the
project maturity levels are, where we need to target refactoring
of code
*
o pyOP
o pyOIDC
o OICcli
o OICmsg
o pyJWKEST
o Satosa
o pySAML
o pyff
* governance
* any open pull requests
5 February 2018
13:00-14:00 - Introduction, agenda building
14:00-17:00 - open
17:00-17:30 - review action items from the day
6 February 2018 (maybe have the open time be split between each project?)
09:00-10:00 - Governance
10:00-10:30 - agenda building
10:30-12:30 - open
13:30-15:30 - open
15:30-16:00 - review action items from the day
_______________________________________________
Idpy-discuss mailing list
Idpy-discuss at lists.sunet.se
https://lists.sunet.se/listinfo/idpy-discuss
--
Niels van Dijk Technical Product Manager Trust & Security
Mob: +31 651347657 | Skype: cdr-80 | PGP Key ID: 0xDE7BB2F5
SURFnet BV | PO.Box 19035 | NL-3501 DA Utrecht | The Netherlands
www.surfnet.nl www.openconext.org
12:09 a.m.
On 1/16/18 2:05 PM, Niels van Dijk wrote:
Hi all,
Unfortunately I cannot join the meeting on Feb 5. I have however a
major interest in SaToSa and pyFF. Would it be possible to put these
on the agenda for Feb 6?
Probably.
Also, it seems to me Technical harmonization,
Governance and Open pull
requests seems to me to be project specific, as these depend on where
the project is coming from and where it currently stands. Does it make
sense to treat these topics on a per project basis?
Open pull requests, definitely per project. Technical harmonization and
governance, probably not, since we're looking at this as an Identity
Python-wide thing. For technical harmonization, we're not saying "change
all the things right now" but if we can start offering guidance on the
coding styles, for instance, then future evolution can have this stuff
align more cleanly. Similarly, for governance, we're looking at this
from an idpy level, not just a component level.
-Heather
Best,
Niels
On 16-01-18 20:33, Heather Flanagan wrote:
Hi all,
Obviously we'll do a fair bit of agenda building on site, but this
list should give us a sense of what we need to cover and how much
time we have. Does anyone have topics they would like to add, or want
to propose a more precisely defined schedule in advance?
-----
Logistics:
Monday, 5 February 2018, Room E, 13:00-17:30
Tuesday, 6 February 2018, Room E, 09:00-12:30, 13:30-16:00 (if needed)
Topics to cover:
* Technical harmonization: project may need dedicated time, and we
need to decide which projects fall under the idpy umbrella,
including discussions on who is the tech lead for each, what the
project maturity levels are, where we need to target refactoring
of code
*
o pyOP
o pyOIDC
o OICcli
o OICmsg
o pyJWKEST
o Satosa
o pySAML
o pyff
* governance
* any open pull requests
5 February 2018
13:00-14:00 - Introduction, agenda building
14:00-17:00 - open
17:00-17:30 - review action items from the day
6 February 2018 (maybe have the open time be split between each
project?)
09:00-10:00 - Governance
10:00-10:30 - agenda building
10:30-12:30 - open
13:30-15:30 - open
15:30-16:00 - review action items from the day
_______________________________________________
Idpy-discuss mailing list
Idpy-discuss at lists.sunet.se
https://lists.sunet.se/listinfo/idpy-discuss
--
Niels van Dijk Technical Product Manager Trust & Security
Mob: +31 651347657 | Skype: cdr-80 | PGP Key ID: 0xDE7BB2F5
SURFnet BV | PO.Box 19035 | NL-3501 DA Utrecht | The Netherlands
www.surfnet.nl www.openconext.org
2531
days inactive
2531
days old
2 comments
2 participants
participants (2)
-
hlflanagan＠sphericalcowgroup.com -
niels.vandijk＠surfnet.nl