- Idpy-discuss - lists3.sunet.se

Invitation: Biweekly idpy Developers call @ Every 2 weeks from 6am to 7am on Tuesday except Tue Mar 6 6am (PST) (discuss@idpy.org)

by hlflanagan＠sphericalcowgroup.com

You have been invited to the following event. Title: Biweekly idpy Developers call When: Every 2 weeks from 6am to 7am on Tuesday except Tue Mar 6 6am Pacific Time Video call: https://plus.google.com/hangouts/_/sphericalcowgroup.com/discuss-hlflana <https://plus.google.com/hangouts/_/sphericalcowgroup.com/discuss-hlflana?hc…> Calendar: discuss at idpy.org Who: * hlflanagan at sphericalcowgroup.com - organizer * discuss at idpy.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=Xzg4cTQ0ZDIyNzEwa2FiO… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account discuss at idpy.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding

7 years, 12 months

1
0
0 0

Agenda and call logistics for today

by hlflanagan＠sphericalcowgroup.com

Hi all, Apologies for the lateness in getting this out. The mailing list software ate the original meeting invitation, which I hadn't realized until late last night. I've sent a revised invitation with the BlueJeans link to the list from my own account; that should make its way through. BlueJeans: https://bluejeans.com/655841213 Agenda 0. Agenda bash 1. Establishing a PR template - https://github.com/blog/2111-issue-and-pull-request-templates 2. Satosa pull requests (no more than 10 minutes each) - https://github.com/IdentityPython/SATOSA - #172 - #137 - #166 - #171 3. pySAML2 - still needs to move to the IdentityPython repository - #483 Enable signature verification for MDQ - #485 Add want_assertions_or_response_signed functionality 4. AOB

7 years, 12 months

2
1
0 0

Invitation: idpy developers call (biweekly) @ Every 2 weeks from 6am to 7am on Tuesday 24 times (PST) (discuss@idpy.org)

by hlflanagan＠sphericalcowgroup.com

You have been invited to the following event. Title: idpy developers call (biweekly) When: Every 2 weeks from 6am to 7am on Tuesday 24 times Pacific Time Where: https://bluejeans.com/655841213 Calendar: discuss at idpy.org Who: * hlflanagan at sphericalcowgroup.com - organizer * discuss at idpy.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=NWtrOGRldGlsamQxbW5ld… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account discuss at idpy.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding

7 years, 12 months

1
0
0 0

Regular calls to review pull requests

by hlflanagan＠sphericalcowgroup.com

Hi all, I'd like to set up regular calls for folks to discuss open pull requests. I'm thinking an hour every other week, with a maximum of 30 minutes on any single pull request. There will have to be a certain amount of scheduling magic to make sure the submitter is on the call to discuss, but that'll be my problem to coordinate. Any objections? Or would folks prefer this to be weekly, at least until we get through the existing backlog of requests? -Heather

8 years

5
11
0 0

Doodle poll: finding a time for a biweekly idpy call

by hlflanagan＠sphericalcowgroup.com

Hi all, As discussed on the list: https://doodle.com/poll/eq62cnivkkkndzaw This would start next week, and go until we don't have anything else to talk about. -Heather

8 years

1
1
0 0

Outcomes of idpy developers meeting, 5-6 February 2018

by hlflanagan＠sphericalcowgroup.com

Accomplishments: 1. Agreed to projects to include in idpy (current list = Satosa, pyff, pySAML, pyXMLsecurity) 2. 1. discussion on the OIDC related ones somewhat dependent on future governance decisions 3. Agreed to a plan for how to work through existing pull requests until such time as we have a dedicated benevolent dictator 4. Reviewed three pull requests for Satosa (174, 171, 161) 5. Discussed prioritization for Satosa/pySAML 6. 1. Clean up Satosa code base, including writing tests 2. 1. fixing logging, error handling 2. more structured documentation on how to import microservices 3. Bigger Satosa refactoring 4. 1. pulling out networking; this will almost certainly have to touch on pySAML and its refactoring Action items: 1. Governance items 2. 1. Heather to create an evaluation matrix for potential IPR home based on criteria proposed by Niels, Benn from previous efforts to look at IPR homes for OpenConext, Cyrus 2. Roland needs to move pySAML to the IdentityPython repository 3. Heather to update idpy.org <http://idpy.org> with GitHub links, other info from the meeting 4. Satosa updates 5. 1. Martin to split pull request 161 2. Heather to make sure Niels and Ivan talk about 171 3. Scott has homework (?) re: 174 Next steps: 1. Governance 2. 1. idpy developers to review IPR home matrix and make decision 2. Community outreach re: governance decisions/recommendations 3. CLA - text and signing 3. Technical architecture 4. 1. Finish evaluating Satosa pull requests 2. Continue to develop additional, better tests 3. pyFF development (currently RA21 focused)

8 years

1
0
0 0

Proposal: Plan B to handle backlog of pull requests

by hlflanagan＠sphericalcowgroup.com

plan B - a process to accept pull requests and do proper releases * No development on the master. * Unit tests must pass before merged into Master. A test may need to be written to validate; a test is always required. * o Measure test coverage with Coverall (?). If the new code (bug fix or RFE) comes in on a place with few tests, then need test needs to be written. If there are a lot of tests, then committer should at least look at the test to see if it is likely to be valid. * Each version has to be tagged with dependencies * Peer review - someone posts to the list, describes how/why and points to a pull request; at least one approver (and the approver has to be someone who is approved to commit code and who isn’t a member of the same organization) * Stable releases should be posted to PyPI

8 years

1
0
0 0

Committers to idpy prospect repos as of 06 feb 2018

by niels.vandijk＠surfnet.nl

Hi all, the following projects are in, or have been voted into the idpy repository. OICRP oiccli oicsrv oicmsg cryptojwt SATOSA fedoicmsg fedoicmsg satosa_microservices fedoicrp fedoiccli pyop pyjwkest satosa-developer Not yet in git pyelevel pysaml pyff Out of these, OICRP oiccli oicsrv oicms, fedoicmsg fedoicrp fedoiccli Only have Roland as a committer The others have multiple commiters, as listed in the attached files. Cheers, Niels -- 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

8 years

2
1
0 0

idpy dev meeting @ TIIME

by hlflanagan＠sphericalcowgroup.com

Hello all, For those of you attending the idpy dev meeting at TIIME, we are up on the fourth floor. Turn left out of the elevator and walk to the end of the hallway. We're going to be flexible with the agenda, as Leif and Roland are stuck in Sweden (airplane issues). We won't see them until tomorrow. -Heather

8 years

1
0
0 0

Notes, idpy dev meeting, 23 January 2018

by hlflanagan＠sphericalcowgroup.com

Attendees: Scott, John, John, Ivan, Roland, Heather Notes: Coding style 1. flake8 and SOLID not mutually exclusive? 2. Any objections we should consider against PEP8/flake8? PEP8 is a start, but need some higher level constraints on things like variable names. Google’s style guide builds on top of PEP8. Perhaps use both? Homework for people to study before TIIME - if you’re not familiar with any of the above, please look them over and be prepared to offer an opinion as to whether using PEP*+flake8 and the Google coding guide should be adopted for idpy projects. Do we want to rely on autogenerated documentation on the code? Any guidance we want to apply? Roland is using Sphinx for some of his projects. Add to discussion at TIIME Incubator program - Ivan’s proposal vs following the model of one of the existing incubators Discuss at TIIME TIIME agenda * separate email AOB Google would like OIDF to host the libraries Roland is working on. Not sure what that means with regards to using GitHub to maintain (since OIDF doesn’t have a GitHub space). Roland would still like the python libraries in idpy. Not sure what Google would think about that (though they probably want everything in one space). What if they were offered a spot on the idpy board? There are many dependencies between them, which means hosting across different orgs would be unreasonably complicated. Next meeting @ TIIME (Cancel next week’s call)

8 years

2
1
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

Idpy-discuss