[Openid-specs-risc] Bi-weekly call schedule

[Stan Bounev]

I vote for #1 or #3, but not #2. The reason is 10am is the busiest time of the day.

From: Openid-specs-risc <openid-specs-risc-bounces at lists.openid.net> on behalf of Adam Hampton via Openid-specs-risc <openid-specs-risc at lists.openid.net>
Reply-To: Adam Hampton <adam.hampton at sailpoint.com>
Date: Thursday, March 5, 2020 at 7:30 AM
To: ALI Asad <asad.ali at thalesgroup.com>, "Morteza Ansari (moransar)" <moransar at cisco.com>, Rob Otto <robotto at pingidentity.com>, Rich Smith <rich at duo.com>
Cc: Openid-specs-risc <openid-specs-risc at lists.openid.net>
Subject: Re: [Openid-specs-risc] Bi-weekly call schedule

I vote for #2.  3pm west coast, 5pm central is particularly bad for me; I can only make the first 15 or 30 minutes of those calls for the next month but in May that becomes a really bad slot for me.

Adam Hampton
Senior Staff Engineer, SailPoint Labs
adam.hampton at sailpoint.com<mailto:adam.hampton at sailpoint.com>
www.sailpoint.com<http://www.sailpoint.com>

From: Openid-specs-risc <openid-specs-risc-bounces at lists.openid.net> on behalf of ALI Asad via Openid-specs-risc <openid-specs-risc at lists.openid.net>
Reply-To: ALI Asad <asad.ali at thalesgroup.com>
Date: Thursday, March 5, 2020 at 8:29 AM
To: "Morteza Ansari (moransar)" <moransar at cisco.com>, Rob Otto <robotto at pingidentity.com>, Rich Smith <rich at duo.com>
Cc: Openid-specs-risc <openid-specs-risc at lists.openid.net>
Subject: Re: [Openid-specs-risc] Bi-weekly call schedule

Same for me, Option 2 and 3 both work.

Regards,
--- Asad

From: Openid-specs-risc [mailto:openid-specs-risc-bounces at lists.openid.net] On Behalf Of Morteza Ansari (moransar) via Openid-specs-risc
Sent: Thursday, March 05, 2020 1:48 AM
To: Rob Otto <robotto at pingidentity.com>; Rich Smith <rich at duo.com>
Cc: Openid-specs-risc <openid-specs-risc at lists.openid.net>
Subject: Re: [Openid-specs-risc] Bi-weekly call schedule

They equally work for me.

From: Openid-specs-risc <openid-specs-risc-bounces at lists.openid.net<mailto:openid-specs-risc-bounces at lists.openid.net>> on behalf of Rob Otto via Openid-specs-risc <openid-specs-risc at lists.openid.net<mailto:openid-specs-risc at lists.openid.net>>
Reply-To: Rob Otto <robotto at pingidentity.com<mailto:robotto at pingidentity.com>>
Date: Wednesday, March 4, 2020 at 11:16 PM
To: Rich Smith <rich at duo.com<mailto:rich at duo.com>>
Cc: Openid-specs-risc <openid-specs-risc at lists.openid.net<mailto:openid-specs-risc at lists.openid.net>>
Subject: Re: [Openid-specs-risc] Bi-weekly call schedule

Like Rich, I vote for 2 with 3 as a second choice.

On Wed, 4 Mar 2020 at 22:39, Rich Smith via Openid-specs-risc <openid-specs-risc at lists.openid.net<mailto:openid-specs-risc at lists.openid.net>> wrote:
Hi Atul,

I would vote for choice 2), but could get onboard with 3) if there were needs we should accommodate for on the Pacific timezone side of things.

Cheers
Rich



On March 3, 2020 at 8:25:14 PM, Atul Tulshibagwale via Openid-specs-risc (openid-specs-risc at lists.openid.net<mailto:openid-specs-risc at lists.openid.net>) wrote:
Hi all,
We discussed whether the current time is suitable for everyone in the list. There were emails from members from the EMEA region that a 3PM PT time does not work very well for them. On the call today, everyone thought a 10 AM PT time would be more suitable to them (this was the time where the CAEP calls would take place)

So I'd like everyone to vote on one of the following choices:

  1.  Keep the current time (3PM PT), which is mostly NA and APAC friendly
  2.  Change to 10 AM PT, which is mostly NA and EMEA friendly
  3.  Alternate between the two times.
Please vote on this by Tuesday, 3/10, to give enough time for people to adjust their schedule to attend the call in the week of 3/16.

Thanks,


Atul Tulshibagwale

Software Engineer

+14157613123 Mobile

1600 Amphitheatre Parkway, Mountain View, CA 94043<https://www.google.com/maps/search/1600+Amphitheatre+Parkway,+Mountain+View,+CA+94043?entry=gmail&source=g>


[Image removed by sender.]

_______________________________________________
Openid-specs-risc mailing list
Openid-specs-risc at lists.openid.net<mailto:Openid-specs-risc at lists.openid.net>
http://lists.openid.net/mailman/listinfo/openid-specs-risc
_______________________________________________
Openid-specs-risc mailing list
Openid-specs-risc at lists.openid.net<mailto:Openid-specs-risc at lists.openid.net>
http://lists.openid.net/mailman/listinfo/openid-specs-risc
--
Rob Otto
EMEA Field CTO - Ping Identity
+44 777 135 6092

CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited.  If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20200305/5d9dfd9b/attachment-0001.html>