December 2018 - Idpy-board - lists3.sunet.se

Doodle Poll: idpy Board call for January 2019

by hlflanagan＠sphericalcowgroup.com

Hola a todos! It's time for our favorite activity: meeting scheduling! https://doodle.com/poll/q43ttxvy497w9a4f If we can make progress on the CLA discussion on the list, that will help make the call itself more efficient. I'll send out a note shortly with further information regarding the number of committers, etc, to help inform the discussion. Thanks, Heather

5 years, 3 months

2
3
0 0

Attending TIIME?

by hlflanagan＠sphericalcowgroup.com

Hola a todos! How many of you are planning to attend the TIIME meeting in Vienna (https://tiimeworkshop.eu/)? Would it be worth adding a governance session at the close of the idpy developers meeting on Monday, 11 February (at the end so that people who might not otherwise be in Vienna could dial in)? -Heather

5 years, 3 months

4
3
0 0

To CLA or Not to CLA

by hlflanagan＠sphericalcowgroup.com

Hola a todos! At this point, I think we've come full circle on the question of whether or not to require a CLA for code committers. Just to get all the information in one place, let me recap/summarize: Arguments in favor: 1. CLAs can be stronger legal protection in case of IPR related issues. 2. Commons Conservancy (our probable home for IPR) recommends a CLA (and has a template we can use for one). Arguments opposed: 1. GitHub Terms of Service are considered by some (both within and independent of idpy) to be more than adequate, particularly after the February 2017 ToS update. 2. Getting a CLA from some committers will be impossible either due to an inability to contact them OR impediments with their employers. 3. Requiring a CLA will (possibly) discourage some committers from continuing participation in the project. 4. Code will likely have to be redone in order to work around third-party code that comes from developers who cannot/will not sign an CLA. A few additional details * There are 108 code committers who have submitted code to an idpy repository BEFORE the Feb 2017 GitHub ToS. This number hasn't significantly changed since then. * In April 2018, I sent email to these individuals letting them know that a CLA might be required at some point. If I missed anything, please chime in. If you have any other questions at all that you need answered before you can vote on this ([Yes|No] to requiring a CLA) please let me know. I'd like to have a final vote on this during our January call. -Heather

5 years, 4 months

1
0
0 0

Very Informal Notes: idpy Board call, 12 December 2018

by hlflanagan＠sphericalcowgroup.com

Attending: Heather, Chris, Leif Regrets: Christos, Roland, Mike, Ivan 0. Agenda bash Given the level of attendance, we’ll likely reuse this agenda for our next call. Heather to send out a doodle poll to find a time in January. 1. IPR - GÉANT and IPR (What is the relationship between IPR and the GEANT project? The default clause in the consortium agreement is that GEANT holds the IPR on behalf of the consortium. Need to see how that would play out if that means handing the IPR over to a third party. Action item for Christos to follow up on.) From Christos: Regarding the IPR, I have discussed this in GÉANT. Unfortunately I cannot provide a final response yet. The topic is in the hands of the GÉANT Execs at the moment. I am nagging them to get it resolved as soon as possible. - Draft Note Well (see email sent 11 December 2018) From Christos: Regarding the draft note, it looks fine to me. Point 3 looks like a very high level code of conduct. [It] is good that we something like this. - Next steps? 2. Review the criteria for bring in new projects to idpy (Practical use case: evolution of pyFF) - https://github.com/IdentityPython/IdentityPython.github.io/wiki/Adding-and-… From Christos: Regarding the criteria for bringing new project to idpy, I do not see mentioning anywhere that the software has to be open source. Are all open source licenses OK? and what about the topic of IPR? 3. TIIME? - idpy Developers meeting @ TIIME, Monday, 11 February 2018 4. AOB Offering a junior developer- Chris has a junior developer who will start on January 15 assigned to work exclusively on idpy project. Discuss tagging releases to make this more acceptable for people who are looking for mature products

5 years, 4 months

3
3
0 0

Agenda: idpy Board call, 12 December 2018

by hlflanagan＠sphericalcowgroup.com

BlueJeans link: https://bluejeans.com/840642655 Date/Time: Wednesday, 12 December 2018 @ 19:00 UTC Agenda 0. Agenda bash 1. IPR - GÉANT and IPR (What is the relationship between IPR and the GEANT project? The default clause in the consortium agreement is that GEANT holds the IPR on behalf of the consortium. Need to see how that would play out if that means handing the IPR over to a third party. Action item for Christos to follow up on.) - Draft Note Well (see email sent 11 December 2018) - Next steps? 2. Review the criteria for bring in new projects to idpy (Practical use case: evolution of pyFF) - https://github.com/IdentityPython/IdentityPython.github.io/wiki/Adding-and-… 3. TIIME? - idpy Developers meeting @ TIIME, Monday, 11 February 2018 4. AOB

5 years, 4 months

1
0
0 0

DRAFT: idpy Note Well

by hlflanagan＠sphericalcowgroup.com

To discuss on our call tomorrow... ---- DRAFT Identity Python Note Well This is a reminder of Identity Python policies in effect on various topics such as patents or other IPR. * By participating (e.g., submitting code, attending in conference calls or meetings, posting to project mailing lists) in Identity Python projects, you agree to follow Identity Python processes and policies as defined in the Identity Python governance pages and in the GitHub Terms of Service. * If you are aware that any code component or idea within an Identity Python project is covered by patents or patent applications that are owned or controlled by you or your sponsor, you must disclose that fact, or not participate in the discussion. * As a participant or attendee, you agree to work respectfully with other participants; please contact the Identity Python board (board at idpy.org) if you have any questions or concerns about this.

5 years, 4 months

1
0
0 0

2024

2023

2022

2021

2020

2019

2018

Idpy-board December 2018