Attendees: Shayna, Ivan, Mikael, Matthew, Hannah This meeting was a 2025 kickoff. We discussed ideas, goals and plans for the IdPy project so that we can keep momentum going and make a better experience for deployers, developers, and end users. - Ivan's take: Idpy provides tooling that you can put together in a flexible manner. But only if you know what you're doing! - Not a lot of people are using these tools that are provided because the domain is complex, and the way they are being provided is not optimal. - there could be a push to move from tooling/libraries to running services - configuration is mostly done for you, with minimal changes - this might also convince people to contribute back, as they would not be spending as much time getting things set up - this would include adding more documentation and improving the documentation that is there - this probably needs to be a board level discussion; Leif needs to agree; GEANT and Christos - then get buy-in from the users like Giuseppe, CESNET, and stakeholders - Nikos working on oidc parts, Mikael and Enrique are working on pyff - There are resourcing issues - need a dedicated person for idpy tools to combine tools as a service, and someone to help with UX parts - Alex is working closely with Ivan - looking at SATOSA, pysaml2 - Matthew - are there resources we should be reaching out to ? Ivan: there is a divide between opensource projects and financing. - GÉANT finances many projects/tools/services, including some of the IdPy projects - Who is using SATOSA? Italian government and some agencies, SUNET, GÉANT (Core AI, incubator projects), Italian federation, CESnet (czech) and CERN. Norwegian projects (NORDnet, CSC) - Mikael: It will probably be easier to get testing/ quality assurance help than pure development - There seems to be a lack of a plan - What are the priorities? Can we adopt some sort of project management process? For instance, how do we get single logout incorporated? - The calls are supposed to help with that, but right now there is nothing official to keep a plan in place and keep it moving forward. - The time is the issue. - We can use Github's project functionalities - have planning calls, use Kanban? - We should Increase the cadence of this meeting to weekly instead of bi-weekly - Need to plan for new features/capabilities, protocol changes from the things we us : for example from OIDC /OpendID foundation - Need to address usability - deployer, developer, end-user - the meeting becomes a check-in - what are you working on, what's finished, what's in your way? And also sprint planning / customer delivery, product backlog annual review - We need to formalize that in meeting agenda - 10 minutes backlog grooming (are we working on the right things at the right time?). Then what are you working on? What have we finished? What's blocking progress? Can we connect people? - Do we need to check in with the board? Maybe give the board a monthly report showing our progress. This will drum up further support for the project. - May need to change the meeting time. - Ivan is currently spending 2 days a month on idpy tools - he is hoping to increase this Steps to focus on before next meeting: - We should invite Enrique & Alex to the meeting - also try to find a time to meet on a weekly basis - Ivan can send a message to the board, to discuss transitioning to a different model (running services) - Ivan will work on the next stages of release, incorporating different categories of PRs. - Shayna will look into/ learn about what we can use from the Agile methodology to improve our meetings/project direction - Matthew would like to see documentation be a first priority. Mikael echoed Matthew's frustration with the current state of documentation. Examples of good documentation that help a developer get set up quickly: SQL Alchemy documentation (deploying an ORM); another is the Typer python package for building CLI. We should initially focus on: - pysaml2 documentation - HOW to use classes, functions, constants? - deployment guide for SATOSA