Thread: Discouraging new projects from pgFoundry

Discouraging new projects from pgFoundry

From
Thom Brown
Date:
Hi,

Here's an extract from our docs: "If you have a PostgreSQL-related
open source project that you would like to have hosted at PgFoundry,
please feel free to create a new project there."

Link: http://www.postgresql.org/docs/9.1/static/external-projects.html

--
Thom

Re: Discouraging new projects from pgFoundry

From
Heikki Linnakangas
Date:
On 09.04.2012 21:23, Thom Brown wrote:
> Hi,
>
> Here's an extract from our docs: "If you have a PostgreSQL-related
> open source project that you would like to have hosted at PgFoundry,
> please feel free to create a new project there."
>
> Link: http://www.postgresql.org/docs/9.1/static/external-projects.html

Yeah, that needs updating. But I'm not sure what to update it to. I also
note that www.pgfoundry.org has no notice that we're planning to pull
the plug on it.

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?

--
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

Re: Discouraging new projects from pgFoundry

From
Magnus Hagander
Date:
On Tue, Apr 10, 2012 at 08:41, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
> On 09.04.2012 21:23, Thom Brown wrote:
>>
>> Hi,
>>
>> Here's an extract from our docs: "If you have a PostgreSQL-related
>> open source project that you would like to have hosted at PgFoundry,
>> please feel free to create a new project there."
>>
>> Link: http://www.postgresql.org/docs/9.1/static/external-projects.html
>
>
> Yeah, that needs updating. But I'm not sure what to update it to. I also
> note that www.pgfoundry.org has no notice that we're planning to pull the
> plug on it.
>
> 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.

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

Re: Discouraging new projects from pgFoundry

From
Heikki Linnakangas
Date:
On 10.04.2012 10:17, Magnus Hagander wrote:
> On Tue, Apr 10, 2012 at 08:41, Heikki Linnakangas
> <heikki.linnakangas@enterprisedb.com>  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

Re: Discouraging new projects from pgFoundry

From
Dave Page
Date:
On Tue, Apr 10, 2012 at 2:41 AM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
> On 09.04.2012 21:23, Thom Brown wrote:
>>
>> Hi,
>>
>> Here's an extract from our docs: "If you have a PostgreSQL-related
>> open source project that you would like to have hosted at PgFoundry,
>> please feel free to create a new project there."
>>
>> Link: http://www.postgresql.org/docs/9.1/static/external-projects.html
>
>
> Yeah, that needs updating. But I'm not sure what to update it to. I also
> note that www.pgfoundry.org has no notice that we're planning to pull the
> plug on it.
>
> 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?

I'll be moving it to git.postgresql.org in the not-to-distant future.

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Re: Discouraging new projects from pgFoundry

From
Tom Lane
Date:
Magnus Hagander <magnus@hagander.net> writes:
> On Tue, Apr 10, 2012 at 08:41, Heikki Linnakangas
> <heikki.linnakangas@enterprisedb.com> 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.

FWIW, I'm thinking of pushing pg_filedump to sourceforge.  But that's
mostly because I already have a sourceforge account, not because it
needs a mailing list ...

            regards, tom lane