- Idpy-board - lists3.sunet.se

Notes: idpy Board call, 7 May 2019

by hlflanagan＠sphericalcowgroup.com

Attendees: Roland, Mike, Heather, Leif, Chris, Christos, Ivan 0) Agenda bash 1) Governance status - Note Well approved 1 May 2019 Heather has sent a copy to the discuss list, and added a link to the idpy.org <http://idpy.org/> website. - MoU with OIDF - status Mike will ping the OIDF people - Commons Conservancy next steps Michiel of CC suggests doing more to make copyright attribution more blatant. Their best practice: https://commonsconservancy.org/faq/licenseinfo/ <https://commonsconservancy.org/faq/licenseinfo/> In general, good to have either ra single file in the root folder of a repository to capture the license and copyright for the whole project (and possibly the exceptions) or have something in each individual file. Right now, we have at least a license file in each repository. Satosa also has a notice file. Our response could be that we’ve considered that approach, but we have the Note Well and the license files now, and consider that enough. Action: Heather to ask CC why they think having a single license file per project is insufficient; if we can avoid adding a header to every single file, that would be nice, esp. given we already have this info in the license file. Action: Heather to post on the idpy.org <http://idpy.org/> website that we are now a project in Commons Conservancy. 2) Development Update (Ivan) Satosa concerns were raised by a member of the community. The board should talk about whether we have sufficient resources for this (and other) idpy projects to make them successful. See Ivan’s response to this particular concern here: https://lists.sunet.se/pipermail/idpy-board/2019-May/000057.html <https://lists.sunet.se/pipermail/idpy-board/2019-May/000057.html> Projects are always open to more volunteers, but there is a bottleneck in terms of having the big architecture picture in order to review and approve code. Suggest we take this back to the developers call about how to resolve. If there is a resource problem, is there a specific ask to the board? Is there a request for more resources? Need clarification. Worth noting that quite a number of PRs have been reviewed and accepted, so work has been happening. Suggest we ask the developers how often a release should happen, and who can help review the code. Developers had come up with a plan for releases and tagging, but need to finish merging open PRs to get to a steady baseline. https://github.com/IdentityPython/IdentityPython.github.io/wiki/Branching-a… <https://github.com/IdentityPython/IdentityPython.github.io/wiki/Branching-a…> If resources are needed, suggest using Hannah temporarily if that would be helpful. Need guidance on what skills are needed to move projects along if we’re going to find more resources. Ivan would appreciate help with documentation (e.g., use cases as collected at TIIME, ready-made docker or vagrant files where we can set up the flows for the use cases). The hardest part is keeping in mind the bigger picture against the changes people propose to the project design. For the developers call: more releases, or more stability? Action: Heather to send out a doodle poll to set up a idpy dev call for a time other than the normal Tuesday 14 May call. If there is a specific request for a particular kind of resource that comes out of the developers meeting, Heather will bring that back to the board. 3) Meeting at TNC19? Full idpy board will meet for drinks/dinner on Sunday evening. Schedule for after speakers reception. Heather to coordinate 4) AOB Regarding the number of projects listed in GitHub, there are three repositories for the federation work, but Roland works in just one. If those three repositories need to be reorganized, that’s up to the lead developer of the project. Just send an email to the list of the changes as an FYI.

7 years, 6 months

1
0
0 0

Fwd: for the IdPy board

by hlflanagan＠sphericalcowgroup.com

> Begin forwarded message: > > From: Ivan Kanakarakis <ivan.kanak at gmail.com> > Subject: Re: for the IdPy board > Date: May 7, 2019 at 8:06:12 AM PDT > To: Heather Flanagan <hlflanagan at sphericalcowgroup.com> > Cc: Scott Koranda <skoranda at gmail.com>, Leif Johansson <leifj at sunet.se> > > Hi everyone, > > > On Tue, 7 May 2019 at 15:07, Heather Flanagan > <hlflanagan at sphericalcowgroup.com> wrote: >> >> Thank you for the feedback, Scott. There is a board meeting later this morning; I will make sure to bring this up then. >> >> Thanks! Heather >> On May 7, 2019, 4:00 AM -0700, Scott Koranda <skoranda at gmail.com>, wrote: >> >> Hi, >> >> It has been almost two years since there was a SATOSA release, and there >> are a number of PRs that have been holding. >> >> Everybody is busy, so I do not know what I expect the board to do, but I >> think the board should at least chat to see if there are any structural >> or other changes that could be made to help SATOSA mature faster. >> >> I really want (need) SATOSA to succeed, so please take this request in >> the positive and forward looking spirit in which I intend it. >> > > The plan is to fix pysaml2#579 and pysaml2#597, then revert SATOSA > bd4303abfc9220dd6b701a23fc522adadbad10b1 and have a new release :) > The reason for this is that I don't want to have those options in > SATOSA and then remove them (a breaking change on an official > release). > > https://github.com/IdentityPython/pysaml2/issues/579 > https://github.com/IdentityPython/pysaml2/pull/597 > https://github.com/IdentityPython/SATOSA/commit/bd4303abfc9220dd6b701a23fc5… > > This needs some work, but I think the hard part is done. I need to > cleanup the modifications I have locally, and make sure the changes > work fine. > > > Cheers, > > -- > Ivan c00kiemon5ter Kanakarakis >:3

7 years, 6 months

1
0
0 0

Fwd: for the IdPy board

by hlflanagan＠sphericalcowgroup.com

Feedback from a community member for us to discuss today. Thanks! Heather ---------- Forwarded message ---------- From: Scott Koranda <skoranda at gmail.com> Date: May 7, 2019, 4:00 AM -0700 To: Heather Flanagan <hlflanagan at sphericalcowgroup.com>, Ivan Kanakarakis <ivan.kanak at gmail.com>, Leif Johansson <leifj at sunet.se> Subject: for the IdPy board > Hi, > > It has been almost two years since there was a SATOSA release, and there > are a number of PRs that have been holding. > > Everybody is busy, so I do not know what I expect the board to do, but I > think the board should at least chat to see if there are any structural > or other changes that could be made to help SATOSA mature faster. > > I really want (need) SATOSA to succeed, so please take this request in > the positive and forward looking spirit in which I intend it. > > Thanks much, > > Scott K

7 years, 6 months

1
0
0 0

Agenda & Reminder: idpy Board call, 7 May 2019

by hlflanagan＠sphericalcowgroup.com

Agenda: 0) Agenda bash 1) Governance status - Note Well approved 1 May 2019 - MoU with OIDF - status? - Commons Conservancy next steps 2) Development Update (Ivan) 3) Meeting at TNC19? 4) AOB ---- BlueJeans info: Meeting URL https://bluejeans.com/471426075?src=join_info Meeting ID 471 426 075 Want to dial in from a phone? Dial one of the following numbers: +1.408.740.7256 (US (San Jose)) +1.408.317.9253 (US (Primary, San Jose)) (see all numbers - https://www.bluejeans.com/premium-numbers) Enter the meeting ID and passcode followed by # Thanks! Heather

7 years, 6 months

1
1
0 0

Results of e-vote on Note Well

by hlflanagan＠sphericalcowgroup.com

Hola a todos! The vote is unanimous in accepting the Note Well. I will send a note to the community list later today. -Heather

7 years, 6 months

1
0
0 0

Doodle Poll: idpy Board meeting, May 2019

by hlflanagan＠sphericalcowgroup.com

And, because doodle polls are SO MUCH FUN… Here’s one to help us find a time for our call in May. As discussed on the call today, I’m avoiding the weeks of May 13 and 20 due to conflicting conferences. https://doodle.com/poll/ivqfuxiwbr8a2yui

7 years, 6 months

1
0
0 0

E-vote: idpy Note Well

by hlflanagan＠sphericalcowgroup.com

Hello all, Below is a poll in order to collect responses re: support for the proposed Note Well text that will serve as the IPR statement for Identity Python contributions (https://github.com/IdentityPython/Governance/blob/master/DRAFT-Note-Well.md <https://github.com/IdentityPython/Governance/blob/master/DRAFT-Note-Well.md>) https://doodle.com/poll/km44afge83d334mz <https://doodle.com/poll/km44afge83d334mz> Please take a moment to record your vote. If you have any questions or concerns, please let me now! -Heather

7 years, 6 months

1
0
0 0

Notes, idpy board call, 19 April 2019

by hlflanagan＠sphericalcowgroup.com

Attendees: Roland, Christos, Mike, Ivan, Heather, Unavailable Leif, Chris Agenda: 0. Agenda bash 1. Administrivia - https://github.com/IdentityPython/Governance <https://github.com/IdentityPython/Governance> Note Well - will turn this into an e-vote Heather has incorporated the changes from Leif and Mike Heather to follow up with Chris to see if he has any specific changes - followed up on IM; he is ok with the text and so will start the e-vote shortly MoU - Mike will send Heather the contact details for the people that need to see the doc. https://docs.google.com/document/d/16T7dsmyUgmeE3A9qtSIEogvUuNMzhT83eFa8Nnq… <https://docs.google.com/document/d/16T7dsmyUgmeE3A9qtSIEogvUuNMzhT83eFa8Nnq…> Incident response https://github.com/IdentityPython/Governance/pull/4 <https://github.com/IdentityPython/Governance/pull/3> Recognition for researchers - Should also add this text to the website; need to modify the text to indicate that we will share their name *with consent* Ivan to update PR; assuming this change, everyone is ok with the addition https://github.com/IdentityPython/Governance/pull/3 <https://github.com/IdentityPython/Governance/pull/3> Storing incident reports - change to say “for the duration of the Identity Python project" Ivan to update the PR; assuming this change, everyone is ok with the addition 2. Commons Conservancy Heather is waiting for the Note Well before following up with the CC 3. Development update Ivan has a long list of things he would like to do. Considering how to make some of this list of changes without breaking existing deployments. Mostly focusing on pySAML2 now, and some things on Satosa. Following that, will look at the UI. Much of that is coming through the angle of eduTEAMS. Another project is now using pySAML2, so we’re seeing some new requests come in from that group. Status of OIDC libraries? Roland has gone through the code, particularly the OP code, to shake out all the obvious bugs. Interested in seeing this incorporated into the Satosa code before TNC19. pyFF update - see idpy-developers list 4. AOB Will aim for a doodle poll for the week of 6 May and May 30-31

7 years, 6 months

1
0
0 0

Agenda: idpy Board call, 19 April 2019

by hlflanagan＠sphericalcowgroup.com

Logistics: Date/time: 19 April 2019 @ 16:00 UTC Meeting URL https://bluejeans.com/686609190?src=join_info Meeting ID 686 609 190 Want to dial in from a phone? Dial one of the following numbers: +1.408.740.7256 (US (San Jose)) +1.408.317.9253 (US (Primary, San Jose)) (see all numbers - https://www.bluejeans.com/premium-numbers) Enter the meeting ID and passcode followed by # Connecting from a room system? Dial: bjn.vc or 199.48.152.152 and enter your meeting ID & passcode Agenda: 0. Agenda bash 1. Administrivia - https://github.com/IdentityPython/Governance <https://github.com/IdentityPython/Governance> * Note Well - vote * MoU 2. Commons Conservancy 3. Development update 4. AOB

7 years, 6 months

1
0
0 0

Final draft: Identity Python Note Well

by hlflanagan＠sphericalcowgroup.com

Hola a todos! An action item from our previous call was to have Leif and Mike do a review of the proposed Note Well text. The revised text is now posted on GitHub and will be posted on the website pending approval by the board. I’ll also remove the word “Draft” at that time. https://github.com/IdentityPython/Governance/blob/master/DRAFT-Note-Well.md Feedback welcome!

7 years, 7 months

1
0
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

Idpy-board