I've got a standing commitment at 1700 EDT / 2100 UTC, but

I believe Dag is proposing 1300 PDT / 1600 EDT / 2000 UTC / 2200 CEST

Does 20:00 UTC work for everyone?

A


On Wed, Jun 18, 2014 at 1:09 PM, Dag Sverre Seljebotn <
d.s.seljeb...@astro.uio.no> wrote:

> Can we do two hours earlier? I'm on CEST (Oslo) and it appears this is
> midnight for me.
>
> I'm basically available rest of today and tomorrow, 08-23 CEST.
>
> Dag Sverre
>
>
> On 06/18/2014 01:44 PM, Volker Braun wrote:
>
>> How about Thursday, then? I'd suggest again 23:00 BST = 15:00 PDT =
>> 22:00 CEDT. That might give the kiwis a chance, too.
>>
>>
>>
>> On Wednesday, June 18, 2014 2:19:08 AM UTC+1, Chris Kees wrote:
>>
>>     I'm mostly available tomorrow (Wednesday) and Thursday pretty much
>>     anytime after 7AM pacific. -Chris
>>
>>
>>     On Tue, Jun 17, 2014 at 4:25 PM, Volker Braun <vbrau...@gmail.com
>>     <javascript:>> wrote:
>>
>>         Since nobody showed up, maybe you can suggest when? Do you have
>>         time during the week?
>>
>>         cc to hashdist list in case somebody hasn't heard of this thread
>>         yet ;-)
>>
>>
>>         On Tuesday, June 17, 2014 5:25:23 PM UTC+1, Volker Braun wrote:
>>
>>             Good idea, whats a good time?
>>
>>             I'll be online today at 23:00 BST UTC = 22:00 UTC = 15:00PDT.
>>
>>             https://plus.google.com/__events/__
>> cff6ldm40v1skgq5eeslmhg4j5g
>>
>>             <https://plus.google.com/events/cff6ldm40v1skgq5eeslmhg4j5g>
>>
>>
>>             On Tuesday, June 17, 2014 4:30:18 PM UTC+1, dagss wrote:
>>
>>                 If you are interested in cooperating perhaps the
>>                 quickest way to move forward is a Google Hangout
>>                 session; I think a lot of this is really about what
>>                 software architecture would fit the package manager of
>>                 Sage, and that all the smaller issues discussed so far
>>                 in the thread is more on the background noise level (as
>>                 they are things easily changed about Hashdist), and it
>>                 may be difficult to kick the discussion to the level we
>>                 need in an email thread.
>>
>>
>>         --
>>         You received this message because you are subscribed to the
>>         Google Groups "hashdist" group.
>>         To unsubscribe from this group and stop receiving emails from
>>         it, send an email to hashdist+u...@googlegroups.com
>> <javascript:>.
>>
>>
>>         For more options, visit https://groups.google.com/d/optout
>>         <https://groups.google.com/d/optout>.
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "hashdist" group.
>> To unsubscribe from this group and stop receiving emails from it, send
>> an email to hashdist+unsubscr...@googlegroups.com
>> <mailto:hashdist+unsubscr...@googlegroups.com>.
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "hashdist" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to hashdist+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to