Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 221E6189E834 for ; Tue, 10 Apr 2012 04:47:09 -0300 (ADT) Received: from exprod7og102.obsmtp.com ([64.18.2.157]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SHVn7-000541-Ek for pgsql-docs@postgresql.org; Tue, 10 Apr 2012 07:47:08 +0000 Received: from mail-lpp01m010-f48.google.com ([209.85.215.48]) (using TLSv1) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP ID DSNKT4Pla9TE7/ctA/nMUAfNmCtBUbexaa1R@postini.com; Tue, 10 Apr 2012 00:47:05 PDT Received: by lagu2 with SMTP id u2so3612829lag.7 for ; Tue, 10 Apr 2012 00:46:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=QJw8Sg8pRYguErarfJsa2HvBrWVwwrsQLt/9L3VSYIw=; b=ZMpEPxonNZFiCm5hit6tMIj15TYzjxJ7QrkXngne1x1VwAyvccOAwGX3jMn64iNHEt mA1fiimQLQ9nB3CXz/TKpV/aNDvaW1hPk/fh4j3tUqSUDcBtPW4TX9EaMYXeoD6zOAm5 Ap3xgugP5JKvEmF9mz2lQ2QFfM5nRVxRsdIVVCqs9IDEZ+wRcpsYmrSWdGASRRrOSVmI 7B/PtJ5Qkv3Ox58VeIVyuVHSM8JklX6zDcCyr4UA6MuKkO4gSYAAwLuBhnON2Lf0Xo5j DGPMqZFYoiIy+gmsx+plJ/ebqVIbt+DbrdjkArdcUmtdsM+vRQQURMiYPKydnHFKS+4s UkTg== Received: by 10.112.49.5 with SMTP id q5mr870818lbn.7.1334044009834; Tue, 10 Apr 2012 00:46:49 -0700 (PDT) Received: from [192.168.1.101] (dsl-hkibrasgw2-ff6cc300-200.dhcp.inet.fi. [88.195.108.200]) by mx.google.com with ESMTPS id w10sm24583189lbe.14.2012.04.10.00.46.48 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 10 Apr 2012 00:46:48 -0700 (PDT) Message-ID: <4F83E566.1010304@enterprisedb.com> Date: Tue, 10 Apr 2012 10:46:46 +0300 From: Heikki Linnakangas User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.3) Gecko/20120324 Icedove/10.0.3 MIME-Version: 1.0 To: Magnus Hagander CC: Dave Page , Thom Brown , pgsql-docs Subject: Re: Discouraging new projects from pgFoundry References: <4F83D627.2030809@enterprisedb.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQlzsKN8+vgFyS1W2oa4b59z5vwIqbkQnet9QlVtMPxN/DTHX6m13GT73N8nmGFXnSfwS3jh X-Pg-Spam-Score: -4.2 (----) X-Archive-Number: 201204/25 X-Sequence-Number: 7279 On 10.04.2012 10:17, Magnus Hagander wrote: > On Tue, Apr 10, 2012 at 08:41, Heikki Linnakangas > wrote: >> I've been thinking of migrating pldebugger out of pgfoundry, converting it >> to git, and modernizing it by packaging as an extension. What should I do? I >> can host the git repository at github or git.postgresql.org, but what's the >> best place to get a website, a wiki, and a mailing list these days? >> sourceforge? > > If you need mailinglists, I think that's pretty much where you have to > go. github will give you everything except a mailinglist, and I > believe the same holds for bitbucket. I don't know of anybody other > than sourceforge that actually provide mailinglists. Hmm, pldebugger is quite intimately related to pgAdmin, as that's the GUI that uses the pldebugger API, so on second thought it's probably best to just have all pldebugger-related discussions on the pgadmin mailing list. In fact, there's currently no mailing list for pldebugger anyway, so the volume isn't very high :-). Then github can provide everything else. Actually, I'm not sure if pldebugger needs a separate website either, could just create a subpage on the pgadmin website. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com