Can I suggest that either Paho or the IoT WG get new call-in numbers. I think that might be the easiest way to ensure we don’t interrupt each other calls. However, I do agree we should try not to overlap.
Ian
From: paho-dev-bounces@xxxxxxxxxxx [mailto:paho-dev-bounces@xxxxxxxxxxx] On Behalf Of Nicholas O'Leary
Sent: April-03-14 8:37 AM
To: General development discussions for paho project
Subject: Re: [paho-dev] Weekly call clash with project leads call
Hi Benjamin,
I think a shared calendar would be very helpful.
The paho calls are bi-weekly at 1:30pm BST (as almost all participants are in the UK) (8:30am ET). So you are right - any week that either our call or the lead call gets shifted by a week, the overlap will occur.
On 3 April 2014 11:26, Benjamin Cabé <benjamin@xxxxxxxxxxx> wrote:
Maybe the problem is we exceptionally shifted our bi-weekly to this week.
What’s the usual schedule for the Paho calls? For IoT WG we do bi-weekly, at 9am ET.
Would that make sense to put together a shared Google Calendar for all the IoT projects + WG?
Andy/Dave/Ben...
not sure if the timezone changes caused the clash, but this week our hour long paho call was interrupted half-way through by the project leads call on the same number.
Do we need to move one of them to avoid a clash in the future? (and I thought we had our own number?)
_______________________________________________ paho-dev mailing list paho-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/paho-dev
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/paho-dev
