Skip site navigation (1) Skip section navigation (2)

Re: [pgsql-www] Collaboration Tool Proposal

From: Shridhar Daithankar <shridhar(at)frodo(dot)hserus(dot)net>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [pgsql-www] Collaboration Tool Proposal
Date: 2004-02-27 14:51:27
Message-ID: 200402272021.27882.shridhar@frodo.hserus.net (view raw or flat)
Thread:
Lists: pgsql-advocacypgsql-hackerspgsql-hackers-win32pgsql-www
On Friday 27 February 2004 19:59, Andrew Dunstan wrote:
> I believe it should not be hard to do a one-time bulk registration of
> everyone on the lists, if that was desired.

I agree. If possible we could also run postgresql registration system where we 
can track general usage of postgresql on various fronts, for the information 
people are willing to put their name on. It could be a massive advocacy 
ammo..

> Signal to Noise. It's not at all clear to me why a bug tracking system
> should have a worse signal to noise ratio than a mailing list with
> similar access rules, especially since we also provide the facility to
> log bugs through a web form directly off the postgresql.org home page.
> But even if it does, that can be managed by good triage. That should
> improve the ratio for all but those doing the triage. Personally, I'd be
> surprised if it took one knowledgable person more than 30 minutes a day
> to weed out the garbage (sorry for the mixed metaphor), and if the load
> was spread across several people it would be just a few minutes a day
> for any one of them, at a significant saving to everyone else.

Look at KDE bugzilla. They first make you search and then file the bug. I have 
seen duplicates dropping from several thousands to few hundreds. Simple but 
effective step. For sure postgresql will hardly receive that kind of bug 
flurry.

They put a direct report a bug in KDE2.0. Click on a menu item and it send a 
bug report. As a result they had massive duplicates. Now the menu item give 
you a URL to click on, then you go and search etc. Very nice system.

> Email interface: it should not be beyond the wit of man to provide some
> level of email interface to any reasonable bug tracking system. Whether
> or not it is worth doing depends on the demand. Two obvious places for
> it would be 1) to allow initial logging of a bug via email, and 2)
> periodically run query 'foo' and email me the results. Getting a once a
> day digest of new bug reports might be quite nice in fact.

Logging bugs via email is a bad idea because you can not enforce the fields. 
Would you like somebody filing a bug via mail and leaving postgresql version 
out?

Let people use webforms. It is nice enough IMHO..

 Shridhar

In response to

pgsql-www by date

Next:From: Greg StarkDate: 2004-02-27 14:57:24
Subject: Re: [pgsql-www] Collaboration Tool Proposal
Previous:From: Andrew DunstanDate: 2004-02-27 14:29:24
Subject: Re: [HACKERS] Collaboration Tool Proposal

pgsql-advocacy by date

Next:From: Greg StarkDate: 2004-02-27 14:57:24
Subject: Re: [pgsql-www] Collaboration Tool Proposal
Previous:From: Andrew DunstanDate: 2004-02-27 14:29:24
Subject: Re: [HACKERS] Collaboration Tool Proposal

pgsql-hackers by date

Next:From: Karl DeBisschopDate: 2004-02-27 14:51:36
Subject: Re: [pgsql-www] Collaboration Tool Proposal
Previous:From: Chris GamacheDate: 2004-02-27 14:38:51
Subject: Re: Any Gentoo users interested in a slotted PostgreSQL

pgsql-hackers-win32 by date

Next:From: Greg StarkDate: 2004-02-27 14:57:24
Subject: Re: [pgsql-www] Collaboration Tool Proposal
Previous:From: Andrew DunstanDate: 2004-02-27 14:29:24
Subject: Re: [HACKERS] Collaboration Tool Proposal

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group