Attendees 9 January
Heather, Ivan, Rainer, Scott, Roland, Einar, Ioannis, John, Johan,
Rainer, Leif, Benn
Action item:
- Heather to get links to the mailing lists for the different components
on the website
- Ivan to post a proposal to the idpy-discuss mailing list for
adding/removing projects from idpy
- Leif and Ioannis to work on slack channel ownership
- Heather to send Benn a list of people to add to the BlueJeans invitation
Agenda bash
1. Project introduction
- Policy stuff: How do we communicate? Where should issues be reported?
* idpy-discuss for general discussion; will send meeting information
to this list
* the other technical components also have their own lists (e.g.,
satosa-dev)
*
o pysaml
o pyoidc library is in a bit of a special place as Roland works
for Google on this library in the different languages. Roland
would like to retire the current pyoidc, which has implications
for other idpy projects like Satosa, that will need to be
updated to point to the newer libraries. Google will be at the
heart of maintaining the newer libraries going forward.
* Suggest consolidating slack spaces - Ioannis
- The community: Who is using our projects? How we communicate with
these entities? How can they get involved? What are their concerns?
- The competition: We offer a product, but there are other tools
that can satisfy one's requirements. What are we doing differently and why.
2. Project governance (Leif, Heather)
* Google has an opinion on governance. The problem is they want idpy
to handle all three libraries, not just the python library. This is
still under discussion. One suggestion is the OIF.
*
o Heather to talk to Adam Dawes @ Google to discuss what they
would like to see, what kind of stability do they need to find
an organization
* Everything will be in an open source license
* Who owns idpy? Who holds the copyright? What country is this based in?
* Currently looking at NLNet / Commons Conservancy and others as
possible hosts for the project, a neutral third party
* One possibility is to standardizing on the architecture (API spec),
but not the language
*
o Roland to discuss with OIF so we can have a cross-language API
for pyoidc
o This is independent of idpy governance
3. Project technical details
- Project goals and roadmap(s)
* the different projects have their own architects; there is no
overarching architect for idpy
*
o Discuss the dependencies in Vienna (1-2 hours)
o Are there missing parts/additions we could incorporate/develop?
This will come out of the discussion in Vienna as well
4. Review GitHub (does it have all the projects it's supposed to?) -
https://github.com/IdentityPython
* It does not have everything; will aim for moving things after Vienna
* What is the consensus process for accepting new work into idpy?
*
o Proposal: someone other than the project maintainer proposes a
project to the list; we collect +1s and aim for rough consensus
o
+ taking something in means we are responsible for maintaining it
+ removing things from idpy means that no components we use
are impacted (this will take longer than taking things in)
+ Ivan to draft a proposal for the process and post to to the list
5. TIIME planning (Rainer, Heather)
Proto agenda:
* any open pull requests (see Rainer’s PR)
* release policies (will we have a regular release cadence?)
* refactoring (e.g., logging in Satosa)
* coding guidelines
* other items to be added as we build agenda on site
* Note that each project may need dedicated time
6. Administrivia
- call schedule and platform for 2018- future call
7. AOB
Agenda for next call: Brainstorm on requirements or goals for
documentation, versioning and release cycles, common coding guidelines
The number of registration is zero, because I failed to define a ticket for the event :-^(.
I have seen registrations from Heather, Roland and Scott for other tracks, so there is no need for you to act. Everybody who plans to join else please register.
https://tiimeworkshop.eu/
Thanks,
Rainer
Hello all,
The process of setting up a call fell off the radar, but hopefully the
poll results for a decent time slot for a regular, biweekly call still
works for most.
The proposal is to have a a biweekly call starting Tuesday, December 5 @
15:00 GMT+1. This will give us four calls (five if we really want to
meet on January 2) between now and TIIME.
DRAFT AGENDA (Please add your topics to the thread)
* Introductions
* Planning for the TIIME workshop (what do you want to get out of it?)
* Project governance status
* Current coding priorities
Does anyone have a particular preference for video conference tools? We
could use Google Hangouts, Skype, or someone could volunteer something
(Lifecloud?)
Dear all,
I am pleased to announce that Heather Flanagan [1] has been funded by
the National Institute of Health's National Institute of Allergies and
Infectious Diseases (NIH NIAID) to act as the project manager for the
Identity Python project. This represents a major step for the project
and will enable us to move forward more quickly and will also help us
establish the Identity Python governance and organizational structure
needed for long-term sustainability of the project.
[1] https://www.linkedin.com/in/hlflanagan/
Cheers Leif
Folks,
I'm thinking it might be a good idea to have a dev meeting
soon to discuss progress and some of the recent development
efforts that have been very active recently.
Who would be interested in (and able to) come to Stockholm
for a (say) 2 day workshop sometime in the Oct-Nov-Dec
time frame (when Sweden really shines as a warm and sunny
place you really want to travel to) ?
Cheers Leif
On 2017-09-30 21:23, Whalen, Christopher (NIH/NIAID) [C] wrote:
> We might be able to do something at our site in Uganda in collaboration with RENU (local NREN) if you want equatorial.
hmm... whats the weather like in Uganda in December?
Skickat från min iPhone
> 29 sep. 2017 kl. 19:18 skrev Rainer Hoerbe <rainer at hoerbe.at>:
>
> I would join.
>
> BTW, I have been considering to offer a day for workshops and dev-meetings with TIIME 2018 in Vienna. There will be no REFEDS and EduGAIN meeting colocated with TIIME. Therefore Tuesday, 6. February would be available with the 2 open space days following Wed/Thu. Let me know what you think.
I think we should consider that too but I was hoping for something sooner...
>
> - Rainer
>
>
>> Am 29.09.2017 um 17:08 schrieb Leif Johansson <leifj at sunet.se>:
>>
>>
>> Folks,
>>
>> I'm thinking it might be a good idea to have a dev meeting
>> soon to discuss progress and some of the recent development
>> efforts that have been very active recently.
>>
>> Who would be interested in (and able to) come to Stockholm
>> for a (say) 2 day workshop sometime in the Oct-Nov-Dec
>> time frame (when Sweden really shines as a warm and sunny
>> place you really want to travel to) ?
>>
>> Cheers Leif
>> _______________________________________________
>> Satosa-dev mailing list
>> Satosa-dev at lists.sunet.se
>> https://lists.sunet.se/listinfo/satosa-dev
>
Hi!
This is a message to test the list but also to correct an error (I think) on the idpy.org
website.
Among the projects pyJWT is mentioned, I think it should be pyJWKEST.
— Roland
