Why Nostr? What is Njump?
2023-06-07 17:40:54
in reply to

gb [ARCHIVE] on Nostr: šŸ“… Original date posted:2015-09-21 šŸ“ Original message:Although the planning for ...

šŸ“… Original date posted:2015-09-21
šŸ“ Original message:Although the planning for this a bit far along now, one consideration I
might add from experience on working with other transglobal IT projects
is the effect of timezones on local mood/alertness/awareness etc. The
guys at 9am pinging on their first coffee in the antipodes will be in a
different mindset than those at 21:00 in Europe, and this is
unavoidable. What is possible is to schedule the meeting every other
week at a time that is better for the "other" half, whoever that might
be. This comes at the cost of not having an exactly same time set every
week.

On Mon, 2015-09-21 at 15:29 +0200, Wladimir J. van der Laan via
bitcoin-dev wrote:
> On Fri, Sep 18, 2015 at 03:07:10AM +0200, Wladimir J. van der Laan wrote:
> > Hello,
> >
> > At Monday's code sprint we had a good idea to schedule a regular developer meeting in #bitcoin-dev.
> >
> > Attendance is of course voluntary, but it may be good to have a time that many people are expected to be present and current issues can be discussed.
> >
> > Any preference for days/times?
> >
> > What about e.g. every week 15:00-16:00 UTC on Thursday?
>
> From Jonasschnelli's doodle ( http://doodle.com/poll/cihug53sa8u4h2in#table ) it appears that Thursday 19:00 UTC - 20:00 UTC is the most popular time.
>
> I think scheduling the meeting in UTC (=Iceland time) makes sense internationally because different locales have different DST or no DST at all, so all in all that makes it more complex. It's true that this can make a convenient time less convenient half of the year, for some people, but I don't think there's a time that works for everyone anyway...
>
> Wladimir
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
Author Public Key
npub1j0cee8lvw7v75c0vfsgfpt5xv8qmr3xzhlwpg9lestngmzwu0u9s6u0kje