I\ll be there

On 28 October 2014 11:49, Kenneth Hoste 
<[email protected]<mailto:[email protected]>> wrote:
Hello EasyBuilders,

The next EasyBuild conference call is planned for this afternoon, Tue Oct 28th 
2014 3pm (CET).
More information is available at 
https://github.com/hpcugent/easybuild/wiki/Conference-calls.

To streamline setting up the conference call and inviting the people interested 
in joining, I have created a dedicate private repository on Google+ for the 
conference calls (next to the already available public one), i.e. 
https://plus.google.com/communities/107060659541429449722 .

Please let me know if you're interested in joining the conference calls every 
now and then, so I can invite you to this private community.
See also https://github.com/hpcugent/easybuild/wiki/Conference-calls#practical .

Preliminary topics are:

 * a small report on the JSC workshop last week
 * a lookout to EasyBuild v1.16.0 which will be released in the coming weeks
 * open floor for questions/problems

Suggestions for other topics are welcome.

Please let me know (via mail, IRC, IM) if you're planning to attend this 
conference call.


regards,

Kenneth



--
Dr. Alan O'Cais
Application Support
Juelich Supercomputing Centre
Forschungszentrum Juelich GmbH
52425 Juelich, Germany

Phone: +49 2461 61 5213
Fax: +49 2461 61 6656
E-mail: [email protected]<mailto:[email protected]>
WWW:    http://www.fz-juelich.de/ias/jsc/EN


------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------

Reply via email to