Attending: Christos, Heather, Roland, Leif, Mike Regrets: Chris, Ivan New Action Items: * Heather to take the action to draft an MoU between Identity Python and OIDF; Mike and Leif will do the first review * Roland will need to remove some of the extraneous forks from the jwtconnect repository so that people cannot contribute to them; will coordinate with Ivan * Heather to take the action to revise the Note Well; will send to the board for feedback then on to the developers lists * Heather to reach out to Scott Koranda re: potential for interns to work on token translation and side tokens * Heather to send out a Doodle poll for the next board call 0. Agenda bash 1. Administrivia - https://github.com/IdentityPython/Governance <https://github.com/IdentityPython/Governance> - OK to sign the statutes? Yes. - OK to formally engage with Commons Conservancy? (Need an update from GEANT first - see below) One caveat - the OIDC libraries (esp. jwtconnect) should not change home from OIDF Perhaps a formal MOU between idpy and the OIDF? In the few instances of overlapping IPR, we have similar and aligned objectives and goals. The MOU itself would say that for a certain set of libraries, the two organizations agree to work towards a shared responsibility for the maintenance of those libraries, but that OIDF would continue to hold the IPR for those libraries where idpy would hold the IPR for the related material (rest of idpy) Heather to take the action to draft that MoU; Mike and Leif will do the first review 2. CLA - GEANT and IPR: Have the green light from GEANT; can continue with the process. At some point we need to go back to the individual contributors (though that does not directly impact GEANT) - Vote (if possible): do we require a CLA for contributions to idpy or do we rely solely on a Note Well? Ivan (absentee), Chris (absentee), Leif, Roland, Christos, Mike (with caveat): vote to not require a CLA Caveat: the items that the items governed by the OIDF (or any other IPR holder) may make a separate decision Suggestion: Add to the Note Well that any contributions to the jwt libraries must sign the CLA with the other IPR holder Roland will need to remove some of the extraneous forks so that people cannot contribute to them; will coordinate with Ivan Heather to take the action to revise the Note Well; will send to the board for feedback then on to the developers lists 3. Developer report - Developers meeting, TIIME workshop, 11 February Very developer-y. Some interesting discussions regarding architecture, code branching, functional programming, etc. Talked about restructuring the Satosa package to have a cleaner plug in architecture. Some interesting work going on with the metadata aggregator; we now have an intern (Hannah) working with Leif on this, working on documenting and some basic scripting to initialize the environment. Very impressive work. myAcademicID project is a project coming along which may have major implications for use for our code, as it is heavily SAML based. This might result in bringing in (hiring) more developers to work on Satosa. 4. Working with interns Ivan: I was taking with Scott on TIIME and he asked me to think of any tasks such a person could overtake. I think to do that I definitely need to know of that person's experience and have a discussion with them. One idea is to have them work on the documentation, user guide and use cases setup, towards the direction we discussed on the TIIME meeting. Note that it takes more time to tutor these interns, so we might not be able to handle more than one intern at a time. Will need more mentors before we can take on more interns. One area of possible mentorship: token translation and side tokens. Scott Koranda and/or Jim Basney could mentor on those topics. Heather to reach out to Scott to discuss. Christos: noted that from the OIDC libraries, there is a gap and perhaps interns could help with some of the work there. Question is, is that work clear enough that an intern could be let loose on it? 5. AOB Next call - late March/early April (topics: anything back from the Commons Conservancy, final approval for Note Well, final approval for MoU; report from the Developers world)