Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 88D7A650E8A for ; Wed, 2 Jul 2008 09:20:52 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 30127-04 for ; Wed, 2 Jul 2008 09:20:47 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from gauss.credativ.com (gauss.credativ.com [212.112.227.254]) by postgresql.org (Postfix) with ESMTP id 00685650E9F for ; Wed, 2 Jul 2008 09:20:51 -0300 (ADT) Received: from hawking.credativ.lan (exit.credativ.com [87.139.82.80]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gauss.credativ.com (Postfix) with ESMTP id D04B87753D for ; Wed, 2 Jul 2008 14:20:50 +0200 (CEST) From: Peter Eisentraut To: pgsql-www@postgresql.org Subject: gitadmin tracker? Date: Wed, 2 Jul 2008 14:20:50 +0200 User-Agent: KMail/1.9.9 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807021420.50388.peter_e@gmx.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200807/3 X-Sequence-Number: 15433 Folks, I'm a little overwhelmed with all the requests for action on the Git service. We need to organize this better. How about setting up a "gitadmin" project on pgfoundry and putting all sorts of requests and complaints in the tracker there. We could also have an announcement mailing list or things like that if there is demand. Or does someone have a better idea on how to manage these things?