Folks,

I was looking at migrating mSQL-interface to pgFoundry, but I'm not sure
there's any reason to do so. It was never finished, doesn't build, and
it's not like I run across mSQL databases in the field. Does anyone?

Shall we just kill it?

Also, "tips" is an apache log converter for which the source code
appears to be completely missing (?). So barring objections, that one
will get the ol' missle from space too.


--Josh



---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Josh Berkus wrote:
> Folks,
>
> I was looking at migrating mSQL-interface to pgFoundry, but I'm not sure
> there's any reason to do so. It was never finished, doesn't build, and
> it's not like I run across mSQL databases in the field. Does anyone?
>
> Shall we just kill it?
>
> Also, "tips" is an apache log converter for which the source code
> appears to be completely missing (?). So barring objections, that one
> will get the ol' missle from space too.

Ka-boom!

--
Bruce Momjian bruce@momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

All,

At the request of Dave Page, here's the semi-final list after looking at
the code:

To be killed:
adddepends
tips
mSQL-interface

To be migrated to pgFoundry:
dbmirror (need owner)
dbase (owner?)
fulltextindex (owner?)
mac (LER)
userlock (Merlin)

--Josh Berkus

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

On Monday 10 July 2006 17:06, Josh Berkus wrote:
> All,
>
> At the request of Dave Page, here's the semi-final list after looking at
> the code:
>
> To be killed:
> adddepends
> tips
> mSQL-interface
>

To be honest I don't know why people are against throwing the code on
pgfoundry with a hefty readme saying that the code is unmaintained and what
it's build status is on various versions. This may not seem too useful, but
if someone were to need this code, or we ever hope to get someone to update
it and/or maintain it, thier not going to find it in the contrib modules in
some small corner of the the ftp archive, but they might have a chance of
finding it on pgfoundry.

--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

On Mon, 10 Jul 2006, Josh Berkus wrote:

> To be migrated to pgFoundry:
> dbmirror (need owner)

I'll volunteer for this if no one else steps forward. I'm not planning on
making any significant chances to dbmirror at this point stage but I can
look after for the pgfoundry project.


> dbase (owner?)
> fulltextindex (owner?)
> mac (LER)
> userlock (Merlin)
>
> --Josh Berkus
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Robert,

> To be honest I don't know why people are against throwing the code on
> pgfoundry with a hefty readme saying that the code is unmaintained and what
> it's build status is on various versions

.... because we don't want to litter pgFoundry with dead, broken projects
which nobody uses and which confuse users and crowd the namespace.
Quality > quantity.

In a year nobody has spoken up for those specific projects. Who's
going to maintain them? Who's going to use them?

--Josh Berkus




---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Robert,

> Given the current number of projects that have no code / files / anything
> associated with them on pgfoundry/gborg right now, this argument rings a
> little hollow.

If you're so keen to add to the problem, you can have my spot as
pgfoundry admin.

Otherwise, the rule that the pgfoundry admins agreed on is that if a
project had no code and no activity in 6 months we would contact the
owner, and if no response kill it. That we've been lagging behind on
this is a manpower issue (and to some degree a technical issue with GForge).

> People do get pointed at adddepends even today... certainly no one will do
> anything with these projects if you nuke them, but I like giving people
> options... your call though.
>

I've already added adddepends to pgFoundry (as "Old PG Upgrade"), since
people spoke up for it. I will assign one of them as admin of the
project (not sure who yet).

However, in the last year nobody has spoken up for the other three, not
even you.

--Josh

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

On Tuesday 11 July 2006 12:55, Josh Berkus wrote:
> Robert,
>
> > To be honest I don't know why people are against throwing the code on
> > pgfoundry with a hefty readme saying that the code is unmaintained and
> > what it's build status is on various versions
>
> ... because we don't want to litter pgFoundry with dead, broken projects
> which nobody uses and which confuse users and crowd the namespace.
> Quality > quantity.
>

Given the current number of projects that have no code / files / anything
associated with them on pgfoundry/gborg right now, this argument rings a
little hollow.

> In a year nobody has spoken up for those specific projects. Who's
> going to maintain them? Who's going to use them?
>

People do get pointed at adddepends even today... certainly no one will do
anything with these projects if you nuke them, but I like giving people
options... your call though.

--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

On 7/10/06, Josh Berkus <josh@agliodbs.com> wrote:
> All,
> userlock (Merlin)

Ok, I will update the project description and maintain it. userlock
is a great feature, and I tried contacting the original author to get
him to relicense the project but could never get a hold of him. To be
honest, the current userlock contrib module is just very thin wrappers
over backend functions with little/no actual value. I think the user
lock functality really belongs in the core project somehow.

The other proposed features to userlock, namely enhancement to certain
aspects of how they are handled in the backend were largely taken care
of by tom for postgresql 8.1.

By the way, some time back I started another project on gborg,
postisam, but never received permission from my former employer to
release the code. so if that is still there it can be nuked as well.

merlin

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

On Tuesday 11 July 2006 14:05, Josh Berkus wrote:
> Robert,
>
> > Given the current number of projects that have no code / files / anything
> > associated with them on pgfoundry/gborg right now, this argument rings a
> > little hollow.
>
> If you're so keen to add to the problem, you can have my spot as
> pgfoundry admin.
>

No need to fly off the handle there Josh.

> Otherwise, the rule that the pgfoundry admins agreed on is that if a
> project had no code and no activity in 6 months we would contact the
> owner, and if no response kill it. That we've been lagging behind on
> this is a manpower issue (and to some degree a technical issue with
> GForge).

No code, or no active code development? Seems there is an important
difference that plays in here... looking a m-SQL it has code and could be a
starting point for someone who was looking for that. I'll grant that tips
doesn't look like much more than an article stub... it should probably be
moved to the new techdocs rather than pgfoundry.

>
> > People do get pointed at adddepends even today... certainly no one will
> > do anything with these projects if you nuke them, but I like giving
> > people options... your call though.
>
> I've already added adddepends to pgFoundry (as "Old PG Upgrade"), since
> people spoke up for it. I will assign one of them as admin of the
> project (not sure who yet).
>
> However, in the last year nobody has spoken up for the other three, not
> even you.
>

Perhaps no one knew they needed to speak up... perhaps people couldn't even
find them in contrib... how many people still ask if we have full text
indexing? contrib isn't exactly the most visible place...

All I am saying is that it couldn't hurt to put the information out there...
we're not hurting for disk space and none of this stuff appears inherently
wrong, just outdated, but it might still prove useful for some people.

--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings