On Oct 30, 2015, at 11:11 AM, Robert Schmidt <[email protected]> wrote: > What is the current general schedule? Bi-weekly? > > Maybe we should do one in austin to include people who couldn't make it? > > I'm pretty flexible generally, but making them predictable probably makes > things easier. Biggest problem is time I think to cover a reasonable set of > timezones. > > So lets try to set the next three or so now and talk about making them > predictable
+1 *3 (missed all last 3 sessions because of the same cause - thanks for discussing this!). I have come to believe that latest hours of Wednesdays & Thursdays might work well for most, however a doodle or something alike that is a better source to prove the case. F. > > > On Fri, Oct 30, 2015, 6:48 AM Kenneth Hoste <[email protected]> wrote: > Hi Lumír, > > > On 30/10/15 11:27, Lumír Jasiok wrote: >> Hello everyone, >> >> I would like to discuss possible Easybuild conf calls scheduling >> enhancements. >> >> Right now there is (unconfirmed) list of future conf calls on >> https://github.com/hpcugent/easybuild/wiki/Conference-calls >> >> Problem is, that I need manually create calendar events for conf calls and >> they might be changed in the future. Kenneth is also sending email before >> each conf call, but it’s on the day of the event and this is too late for me. >> >> It would be nice to have some shared (Google?) calendar with conf calls and >> at least one day before reminder. >> >> What do you think? > > I'm very much in favor of this, the way in which conf calls have been planned > / reminded recently is definitely not good enough, I'm happy to admit that. > > The Google+ group for the EB conf calls supports events, we should plan them > way ahead (like, at the end of the conf call, or right after). > > You can probably specify when to send reminders as well. > > > regards, > > Kenneth cheers, Fotis -- echo "sysadmin know better bash than english" | sed s/min/mins/ \ | sed 's/better bash/bash better/' # signal detected in a CERN forum
