9:06 p.m.
Hello all,
It's not zoom, but it's enough to get us started for next week. Here is
your BlueJeans invitation to join the idpy developers call next week on
Tuesday, 19 December @ 6am PT | 9am ET | 3pm CET.
DRAFT Agenda:
0. Agenda bash
1. Project governance (Leif, Heather)
2. Review GitHub (does it have all the projects it's supposed to?) -
https://github.com/IdentityPython
3. TIIME planning (Rainer, Heather)
4. AOB
Agenda is flexible, so please let me know if you have something you'd
like added.
-Heather
12:26 p.m.
Hi everyone,
On 15 December 2017 at 23:06, Heather Flanagan
<hlflanagan at sphericalcowgroup.com> wrote:
Hello all,
It's not zoom, but it's enough to get us started for next week. Here is
your BlueJeans invitation to join the idpy developers call next week on
Tuesday, 19 December @ 6am PT | 9am ET | 3pm CET.
DRAFT Agenda:
0. Agenda bash
1. Project governance (Leif, Heather)
2. Review GitHub (does it have all the projects it's supposed to?) -
https://github.com/IdentityPython
3. TIIME planning (Rainer, Heather)
4. AOB
Agenda is flexible, so please let me know if you have something you'd
like added.
I have not been involved with the discussion around creating idpy, so
I would add introductory items like these:
- What is the goal of the project?
- What are the intermediate goals (roadmap)?
and then the following:
- Are there missing parts/additions we could incorporate/develop? (and
then place them on the roadmap)
- Policy stuff: How do we communicate? Where should issues be
reported? etc (and make those public so others know)
- 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.
Ofcourse not everything can be covered in a single session. Lets
pick-up what you feel is more important.
-Heather
_______________________________________________
Satosa-dev mailing list
Satosa-dev at lists.sunet.se
https://lists.sunet.se/listinfo/satosa-dev
Cheers,
--
Ivan c00kiemon5ter Kanakarakis >:3
10:12 p.m.
New subject: Updated agenda: idpy developers call, 19 December 2017
On 12/16/17 4:26 AM, Ivan Kanakarakis wrote:
Hi everyone,
On 15 December 2017 at 23:06, Heather Flanagan
<hlflanagan at sphericalcowgroup.com> wrote:
Excellent list!
Updated Agenda:
0. Agenda bash
1. Project introduction
- Policy stuff: How do we communicate? Where should issues be reported?
- 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)
3. Project technical details
- Project goals and roadmap(s)
- Are there missing parts/additions we could incorporate/develop?
4. Review GitHub (does it have all the projects it's supposed to?) -
https://github.com/IdentityPython
5. TIIME planning (Rainer, Heather)
6. Administrivia
- call schedule and platform for 2018
- idpy-discuss vs satosa-dev lists
7. AOB
Hello all,
It's not zoom, but it's enough to get us started for next week. Here is
your BlueJeans invitation to join the idpy developers call next week on
Tuesday, 19 December @ 6am PT | 9am ET | 3pm CET.
DRAFT Agenda:
0. Agenda bash
1. Project governance (Leif, Heather)
2. Review GitHub (does it have all the projects it's supposed to?) -
https://github.com/IdentityPython
3. TIIME planning (Rainer, Heather)
4. AOB
Agenda is flexible, so please let me know if you have something you'd
like added.
I have not been involved with the discussion around creating idpy, so
I would add introductory items like these:
- What is the goal of the project?
- What are the intermediate goals (roadmap)?
and then the following:
- Are there missing parts/additions we could incorporate/develop? (and
then place them on the roadmap)
- Policy stuff: How do we communicate? Where should issues be
reported? etc (and make those public so others know)
- 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.
Ofcourse not everything can be covered in a single session. Lets
pick-up what you feel is more important.
2:14 p.m.
New subject: Call rescheduled: idpy developers call, 19 December 2017
Hello all,
Well, that rather didn't work. Ivan, Rainer, Johan, and Scott win gold
stars for making it to the call, but we needed a few more people (Leif,
Roland, Niels) to have the kickoff call be effective.
The call is now rescheduled to this same time slot on 9 January 2018.
We'll aim for weekly calls at least in January, since some discussion is
necessary to make best use of our time at TIIME. We can discuss ongoing
call schedules later.
The agenda will remain the same for 9 January. Talk to you then!
Updated Agenda:
0. Agenda bash
1. Project introduction
- Policy stuff: How do we communicate? Where should issues be reported?
- 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)
3. Project technical details
- Project goals and roadmap(s)
- Are there missing parts/additions we could incorporate/develop?
4. Review GitHub (does it have all the projects it's supposed to?) -
https://github.com/IdentityPython
5. TIIME planning (Rainer, Heather)
6. Administrivia
- call schedule and platform for 2018
- idpy-discuss vs satosa-dev lists
7. AOB
1:48 p.m.
New subject: Call rescheduled: idpy developers call, 19 December 2017
On 19 Dec 2017, at 15:14, Heather Flanagan
<hlflanagan at sphericalcowgroup.com> wrote:
Hello all,
Well, that rather didn't work. Ivan, Rainer, Johan, and Scott win gold
stars for making it to the call, but we needed a few more people (Leif,
Roland, Niels) to have the kickoff call be effective.
The call is now rescheduled to this same time slot on 9 January 2018.
We'll aim for weekly calls at least in January, since some discussion is
necessary to make best use of our time at TIIME. We can discuss ongoing
call schedules later.
The agenda will remain the same for 9 January. Talk to you then!
BlueJeans/Zoom/.. ??
Could you send out an invite with the relevant meeting information ?
Updated
Agenda:
0. Agenda bash
1. Project introduction
- Policy stuff: How do we communicate? Where should issues be reported?
- 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)
3. Project technical details
- Project goals and roadmap(s)
- Are there missing parts/additions we could incorporate/develop?
4. Review GitHub (does it have all the projects it's supposed to?) -
https://github.com/IdentityPython
5. TIIME planning (Rainer, Heather)
6. Administrivia
- call schedule and platform for 2018
- idpy-discuss vs satosa-dev lists
7. AOB
_______________________________________________
Satosa-dev mailing list
Satosa-dev at lists.sunet.se
https://lists.sunet.se/listinfo/satosa-dev
3:29 p.m.
New subject: Call rescheduled: idpy developers call, 19 December 2017
On 12/22/17 5:48 AM, Roland Hedberg wrote:
BlueJeans/Zoom/.. ??
Could you send out an invite with the relevant meeting information ?
Hi Roland,
That was sent out on 15 December. A copy of the .ics file is attached.
-hf
3:31 p.m.
New subject: Call rescheduled: idpy developers call, 19 December 2017
Hi Heather,
On 22 Dec 2017, at 16:29, Heather Flanagan
<hlflanagan at sphericalcowgroup.com> wrote:
On 12/22/17 5:48 AM, Roland Hedberg wrote:
Right, but then there was some discussions about using Zoom instead of Bluejeans.
Didn’t that go anywhere ?
— Roland
BlueJeans/Zoom/.. ??
Could you send out an invite with the relevant meeting information ?
That was sent out on 15 December. A copy of the .ics file is attached.
3:33 p.m.
New subject: Call rescheduled: idpy developers call, 19 December 2017
On 12/22/17 7:31 AM, Roland Hedberg wrote:
Hi Heather,
No - I was able to get a BlueJeans space; a private request for a zoom
space didn't go anywhere. The BlueJeans info is in the invite. We can
always change to something else later.
-Heather
On 22 Dec 2017, at 16:29, Heather Flanagan
<hlflanagan at sphericalcowgroup.com> wrote:
On 12/22/17 5:48 AM, Roland Hedberg wrote:
Right, but then there was
some discussions about using Zoom instead of Bluejeans.
Didn’t that go anywhere ?
— BlueJeans/Zoom/.. ??
Could you send out an invite with the relevant meeting information ?
That was sent
out on 15 December. A copy of the .ics file is attached.
3:34 p.m.
New subject: Call rescheduled: idpy developers call, 19 December 2017
OK, thanks !
On 22 Dec 2017, at 16:33, Heather Flanagan
<hlflanagan at sphericalcowgroup.com> wrote:
On 12/22/17 7:31 AM, Roland Hedberg wrote:
Hi Heather,
No - I was able to get a BlueJeans space; a private request for a zoom
space didn't go anywhere. The BlueJeans info is in the invite. We can
always change to something else later.
-Heather On 22 Dec 2017, at 16:29, Heather Flanagan
<hlflanagan at sphericalcowgroup.com> wrote:
On 12/22/17 5:48 AM, Roland Hedberg wrote:
Right, but then there was
some discussions about using Zoom instead of Bluejeans.
Didn’t that go anywhere ?
— BlueJeans/Zoom/.. ??
Could you send out an invite with the relevant meeting information ?
That was sent
out on 15 December. A copy of the .ics file is attached.
2339
days inactive
2346
days old
8 comments
3 participants
participants (3)
-
hlflanagan＠sphericalcowgroup.com -
ivan.kanak＠gmail.com -
roland＠sunet.se