On 17/03/18 02:53, Ed Leafe wrote:
On Mar 15, 2018, at 10:31 PM, Gilles Dubreuil wrote:
Any chance we can progress on this one?
I believe there are not enough participants to split the API SIG meeting in 2,
and also more likely because of the same lack of people across the 2 it could
make i
On Mar 15, 2018, at 10:31 PM, Gilles Dubreuil wrote:
>
> Any chance we can progress on this one?
>
> I believe there are not enough participants to split the API SIG meeting in
> 2, and also more likely because of the same lack of people across the 2 it
> could make it pretty inefficient. Ther
Hi,
Any chance we can progress on this one?
I believe there are not enough participants to split the API SIG meeting
in 2, and also more likely because of the same lack of people across the
2 it could make it pretty inefficient. Therefore I think changing the
main meeting time to another migh
Thanks edleafe,
I am interested to attend but it is little early for me(i am in
JST(UTC +9)), any chance we can make it to 23:00 UTC or 0:00 UTC ?
-gmann
On Wed, Dec 13, 2017 at 12:22 AM, Ed Leafe wrote:
> Re-sending this in the hope of getting more responses. If you’re in the APAC
> region
Obviously, I'm interested and I voted.
Thanks,
Gilles
On 13/12/17 02:22, Ed Leafe wrote:
Re-sending this in the hope of getting more responses. If you’re in the APAC
region and interested in contributing to our discussions, please indicate your
preferences on the link below.
That brought u
Re-sending this in the hope of getting more responses. If you’re in the APAC
region and interested in contributing to our discussions, please indicate your
preferences on the link below.
>> That brought up another issue: the current meeting time for the API-SIG is
>> 1600UTC, which is not very
On Dec 7, 2017, at 11:22 AM, Ed Leafe wrote:
> That brought up another issue: the current meeting time for the API-SIG is
> 1600UTC, which is not very convenient for APAC contributors. Gilles is in
> Australia, and so it was the middle of the night for him! As one of the goals
> for the API-SI