- Idpy-discuss - lists3.sunet.se

Doodle poll: idpy IPR home and the Commons Conservancy

by hlflanagan＠sphericalcowgroup.com

Hello all, As mentioned on the developers call this morning, I'm setting up a call with Michiel Leenaars at Commons Conservancy to discuss the possibility of working with them as an IPR home for the idpy projects. I've set up a doodle poll (link below). Please fill out the poll by this Friday. I know not everyone will be ready, willing, and/or able to attend the call, so if I don't see your response by this Friday, I'll assume you are willing to catch up via the notes from the call. https://doodle.com/poll/dugz5cadrd9r2q23 Thanks for your time, Heather

7 years, 7 months

1
0
0 0

Notes: idpy developers call, 3 April 2018

by hlflanagan＠sphericalcowgroup.com

Attendees: Jonas, Ivan, Roland, Heather, Rainer 0. Agenda bash 1. pySAML2 PRs - https://github.com/IdentityPython/pysaml2/pulls Ivan spoke with Leif yesterday; may be coming up to Sweden soon for a meeting (and maybe more). Ivan has 493 and 495 assigned; 493 is still being examined. 495 will be resolved soon. Will start looking at 499; Ivan has an idea on how to simplify. When that’s done, it can be merged as well. 498 will be assigned to Ivan; it can be merged, but he has some ideas on how to make it better. 485 and 483 are waiting on Scott to add tests. 468 to the bottom of the list - haven’t looked at those in detail yet. 468 will be rejected. Team is considering adding labels. Ivan will look into what might be appropriate; he has used these in previous repositories. 2. Satosa PRs - https://github.com/IdentityPython/SATOSA/pulls Ivan is currently looking at 137 and 160, and expects to close those tomorrow. They won’t be accepted, but he will take parts of them. When that’s done, he’ll go to 166 (related to issue 165). He has downloaded a Windows virtual machine to try and reproduce. 171 is a fairly big one. 172 can be merge, but waiting on Scott adding some tests. 176 has some fixes, but one of the fixes changes the behavior of Satosa. Ivan would like to go over that with them. Ivan will look at the issues after the PRs. Note that Martin opened an issue in the micro services repository today; will need to review that as well. The question is how to handle the split repo. This has been discussed a bit on the mailing list, but Ivan will ping the list to remind people that input is needed so we can bring this a conclusion. 3. Governance update Heather will be sending a note to committers re: (C)CLA. Expect a set of doodle polls for calls with Commons Conservancy and Apereo so we can discuss their organizations as possible IPR homes for idpy. The call with CC will happen first (Heather hasn't heard back from Apereo yet). 4. AOB pyFF - not sure if Leif has a more permanent workaround for the segfault issue. Also not sure if this has been refactored to be a flask project.

7 years, 7 months

1
0
0 0

Agenda: idpy developers meeting, 3 April 2017

by hlflanagan＠sphericalcowgroup.com

Date: Tuesday, 3 April 2018 Time: 06:00 PT | 09:00 ET | 15:00 GMT https://bluejeans.com/655841213 Agenda: 0. Agenda bash 1. pySAML2 PRs - https://github.com/IdentityPython/pysaml2/pulls 2. Satosa PRs - https://github.com/IdentityPython/SATOSA/pulls 3. Governance update 4. AOB

7 years, 7 months

1
1
0 0

Notes: idpy governance call, 27 March 2017

by hlflanagan＠sphericalcowgroup.com

Attendees: Heather, Scott, Benn, Ivan, Leif https://docs.google.com/spreadsheets/d/1dNR8clA_wKouhwonD8bIiyA5N2wMsorS8Uz… A few notes re: the spreadsheet: * Items in yellow are things we should think about, but may not be blockers in our particular circumstances. * The phrase “more application than integration” applies to the idea that a good home has a process for ensuring projects are sustainable, and that the organization will not just become a dumping ground for random projects. The process of vetting an inbound project (and bringing it into conformance as needed) is generally referred to as incubation. The incubation process is usually fairly complicated, and involves active engagement with the potential home organization. An application process is simpler, and basically consists of a few questions for the potential home's board to consider in deciding whether or not to accept the project. * Organizations may want to have their lawyers look at the application process. Leif: the project has to feel “at home” with the other projects in the IPR home; we can’t be too different from what else is happening in that organization. That makes Apereo perhaps a bit of a stretch. We want to have a home where we can have a certain amount of self-governance. * Apache Foundation has a lot of structure, and each project is reasonably independent but expected to follow Apache Foundation’s rules. Leif: a poor fit because of the focus on what their projects are about (i.e., they don’t have much in the way of identity-related projects). * SPI, SFC - Benn is not seeing a lot of support in SPI or any level of community in SPI or SFC. Heather: if these were the last options available, that would be something we would pursue further, but we have other options so these aren’t worth pursuing * Apereo - Leif is concerned about Apereo’s long term viability, though Benn points out if we own the IPR we can always move the project. * Commons Conservancy - GEANT already has something of an agreement that would make this easier, and NLNet Foundation (the parent organization for CC) has long term viability via their established DNS software (see https://nlnet.nl/project/current.html for list of NLNet Foundation projects) Channeling of funding * some organizations want ability to collect money; Commons Conservancy is not set up to route funds (that’s what they use NLNet Foundation or GEANT for). Apereo is set up for that. * This was by design for Commons Conservancy - indirect IPR protection; it would be pointless to a takeover because the project does not control its funds. If someone sues you for IPR infringement, there is no money to be taken. * There is definitely a possibility of future cash donations (not just the current in-kind funding via FTE that we see today) Action item: * Heather to set up calls with both Apereo and Commons Conservancy to have them talk to us, introduce ourselves, etc. * How do donations work? How do we handle money? How do tax agreements get handled with multiple countries? Given that we’re giving with contributors across national boundaries, where do the CCLAs fall in terms of jurisdiction? What is the international suitability of their CCLA? * Heather to reach out to the code authors to see if they have a hard “no” (which include non-responses) re: signing a CCLA to turn over their code to the project

7 years, 7 months

3
5
0 0

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

by bas.zoetekouw＠surfnet.nl

more details »<https://www.google.com/calendar/event?action=VIEW&eid=NWtrOGRldGlsamQxbW5ld…> idpy developers call (biweekly) When Every 2 weeks from 6am to 7am on Tuesday 24 times Pacific Time Where https://bluejeans.com/655841213 (map<https://www.google.com/url?q=https%3A%2F%2Fbluejeans.com%2F655841213&sa=D&u…>) Calendar discuss at idpy.org Who • hlflanagan at sphericalcowgroup.com - organizer • discuss at idpy.org Going? All events in this series: Yes<https://www.google.com/calendar/event?action=RESPOND&eid=NWtrOGRldGlsamQxbW…> - Maybe<https://www.google.com/calendar/event?action=RESPOND&eid=NWtrOGRldGlsamQxbW…> - No<https://www.google.com/calendar/event?action=RESPOND&eid=NWtrOGRldGlsamQxbW…> more options »<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<https://support.google.com/calendar/answer/37135#forwarding>.

7 years, 8 months

1
0
0 0

Reminder: idpy governance call tomorrow, 27 March 2018

by hlflanagan＠sphericalcowgroup.com

Hello all, This is a reminder that there is a call about idpy governance tomorrow, 27 March @ 16:00 UTC (9am PT | 12noon ET | 18:00 in Sweden). The goal of the call is to settle on an IPR home for idpy; once we've done that, I can start creating the necessary policies and procedures in accordance with the requirements for $IPRHOME. A comparison chart of possible IPR homes is available in a Google doc: https://docs.google.com/spreadsheets/d/1dNR8clA_wKouhwonD8bIiyA5N2wMsorS8Uz… If you have not received an invitation and want to be on the call, please reach out to skoranda at sphericalcowgroup.com and he'll get you added to the BlueJeans meeting invitation. Thanks!

7 years, 8 months

1
0
0 0

Doodle poll: idpy governance call (second attempt)

by hlflanagan＠sphericalcowgroup.com

Hi all, There was no good time for folks with the first attempt at a call to discuss finding an IPR home for idpy. I've put together another doodle poll - hopefully there will be a time that works more easily for mst! https://doodle.com/poll/33gu594nmn4q7p85 If you would, please fill out the poll by Wednesday, 21 March 2018. Thanks! Heather

7 years, 8 months

3
3
0 0

lxml 4.2.0 problems in pyFF

by martin＠surfnet.nl

Hi, We were experiencing severe pyFF restarting problems since our last deployment. It turned out lxml was updated to 4.2.0 which introduced segmentation faults on every metadata refresh. Downgrading to 4.1.1 resolved our problems. As for adopting CMService in idPy: Niels will make an official statement about that. Best regards, Martin

7 years, 8 months

2
1
0 0

idpy call next week CANCELLED (20 March)

by hlflanagan＠sphericalcowgroup.com

Hi all, The list has been quiet, and people with action items related to the PRs still have some work to do. Please take the meeting hour to work on your tests or flesh out your PRs to meet the new templates, and Ivan will do his magic with regards to reviewing and writing code. If you have any questions or discussion topics, please post to the list! -Heather

7 years, 8 months

1
0
0 0

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

by hlflanagan＠sphericalcowgroup.com

This event has been changed. Title: Biweekly idpy Developers call When: Every 2 weeks from 6am to 7am on Tuesday from Tue Feb 20 to Tue Mar 20 Pacific Time (changed) 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, 8 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

Idpy-discuss