If we do get above 10, then CU has a Zoom[1] account, so I can set up a meeting 
using that. Just let me know.

Tim

[1] https://zoom.us/

________________________________________
From: [email protected] <[email protected]> on 
behalf of Kenneth Hoste <[email protected]>
Sent: Monday, January 11, 2016 3:15 AM
To: EasyBuild
Cc: Todd Gamblin
Subject: Re: [easybuild] conf call to discuss RPATH support

Hi all,

Since we're still below 10 participants and because I've yet to figure
out the problems with using our Skype4Business setup (connecting from a
Linux client seems to be one of them), I've planned the conf call via
Google+ as usual, see
https://plus.google.com/events/cois9e9h81bpk5okmq6q4pa2ksc .

If you're planning to participate, please let us know (preferably by
RSVP'ing in the Google+ event), since seats are limited to 10.


regards,

Kenneth

On 10/01/16 22:02, Kenneth Hoste wrote:
> Hi all,
>
> Everyone who participated in the doodle indicated that tomorrow (Mon
> Jan 11th 2016) 5pm CET works for them, so let's go with that.
>
> I'll look into an alternative to Google+ hangouts for the conf call,
> since that's limited to 10 participants max.
> You should hear back from me well in time before the start of the conf
> call.
>
> If you didn't fill out the doodle and would like to join this conf
> call, please let me know.
>
>
> regards,
>
> Kenneth
>
> On 08/01/16 15:27, Kenneth Hoste wrote:
>> Hi all,
>>
>> After a brief discussion during the EasyBuild conf call earlier this
>> week, it was clear that it is worthwhile to have a dedicated conf
>> call to discuss how we can support RPATH linking in EasyBuild.
>>
>> Please fill out this doodle ASAP if you're interested in joining:
>>
>>     http://doodle.com/poll/ckdvae2pnta46qy8
>>
>> The specified times are CET, and are picked such that Todd (in CC),
>> the lead developer of Spack who has extensive experience with
>> supporting RPATH, can join in comfortably.
>>
>> I would like to pick a time slot by Monday morning (Jan 11th).
>>
>>
>> regards,
>>
>> Kenneth
>

Reply via email to