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

Re: commitfest management webapp

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, pgsql-www(at)postgresql(dot)org
Subject: Re: commitfest management webapp
Date: 2009-05-27 03:49:14
Message-ID: 26865.1243396154@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-www
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, May 26, 2009 at 9:39 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I don't understand why that bit would be based on community login at
>> all. Wouldn't contacting someone mainly need an email address?

> Yes.  Humor me be elaborating on your thought here?

Um, what's to elaborate?  I'm thinking you should track submitters
and other actors by email address.  A login might be appropriate to
control who can modify the commitfest data, but that should be
seen as a secretarial function, not something that's necessarily
carried out by the patch authors or reviewers themselves.

			regards, tom lane

In response to

pgsql-www by date

Next:From: Stefan KaltenbrunnerDate: 2009-05-27 04:26:58
Subject: Re: commitfest management webapp
Previous:From: Robert HaasDate: 2009-05-27 03:44:30
Subject: Re: [HACKERS] commitfest management webapp

pgsql-hackers by date

Next:From: Stefan KaltenbrunnerDate: 2009-05-27 04:26:58
Subject: Re: commitfest management webapp
Previous:From: ioguixDate: 2009-05-27 03:48:26
Subject: Re: generic options for explain

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