From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1My6Zf-00029u-F4 for garchives@archives.gentoo.org; Wed, 14 Oct 2009 16:19:39 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A2144E0904; Wed, 14 Oct 2009 16:19:38 +0000 (UTC) Received: from a1iwww1.kph.uni-mainz.de (a1iwww1.kph.uni-mainz.de [134.93.134.1]) by pigeon.gentoo.org (Postfix) with ESMTP id 49692E0904 for ; Wed, 14 Oct 2009 16:19:38 +0000 (UTC) Received: from a1i15.kph.uni-mainz.de (a1i15.kph.uni-mainz.de [134.93.134.92]) by a1iwww1.kph.uni-mainz.de (8.14.0/8.13.4) with ESMTP id n9EGJXHW015584; Wed, 14 Oct 2009 18:19:33 +0200 Received: from a1i15.kph.uni-mainz.de (localhost [127.0.0.1]) by a1i15.kph.uni-mainz.de (8.14.3/8.14.2) with ESMTP id n9EGJXiR012635; Wed, 14 Oct 2009 18:19:33 +0200 Received: (from ulm@localhost) by a1i15.kph.uni-mainz.de (8.14.3/8.14.3/Submit) id n9EGJXJk012632; Wed, 14 Oct 2009 18:19:33 +0200 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-council@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <19157.64021.783358.246684@a1i15.kph.uni-mainz.de> Date: Wed, 14 Oct 2009 18:19:33 +0200 To: Denis Dupeyron Cc: gentoo-council@lists.gentoo.org Subject: Re: [gentoo-council] Date of next council meeting In-Reply-To: <7c612fc60910140910n405bd8fdna818136f0109c4e2@mail.gmail.com> References: <19157.60956.807706.113326@a1i15.kph.uni-mainz.de> <7c612fc60910140910n405bd8fdna818136f0109c4e2@mail.gmail.com> X-Mailer: VM 8.0.12 under 23.1.1 (x86_64-pc-linux-gnu) From: Ulrich Mueller X-Archives-Salt: 7cba7658-169d-482e-9c0f-d45a16111ef9 X-Archives-Hash: 1b05a5cdfe2e3a97bd9478dbee3d6390 >>>>> On Wed, 14 Oct 2009, Denis Dupeyron wrote: > Keeping the meeting times in sync with universal time doesn't make > much sense as we all have schedules that are tied to our local > times, most of them being in sync most of the time. So far, it was always bound to UTC. But I have no preference. So if the majority of council members prefers 19 UTC (starting with next meeting and until some time in March), then we can shift it. Ulrich