From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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:19:23 |
Message-ID: | 603c8f070905262019r66ad3d60y3452c4fe16c62d34@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-www |
On Tue, May 26, 2009 at 9:39 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> 3. The integration with the community login system is currently rather
>> poor. The problem is that we can't count on patch submitters to have
>> a community login, and even if they do we can't count on the person
>> adding the patch to the system to know what it is. We could of course
>> require patch submitters to have a community login and to add their
>> patches themselves, but I'm not really that keen on raising the bar
>> for submitting a patch even to that modest extent.
>
>> I'm open to
>> suggestions on how to improve this situation, though, because it's
>> definitely not ideal, and precludes things that reasonable people
>> might want to do, like "contact the guy who submitted this patch",
>> "contact the authors of all patches waiting for review", and similar.
>
> 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?
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2009-05-27 03:21:06 | Re: commitfest management webapp |
Previous Message | Alvaro Herrera | 2009-05-27 02:53:00 | Re: commitfest management webapp |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2009-05-27 03:21:06 | Re: commitfest management webapp |
Previous Message | Alvaro Herrera | 2009-05-27 02:53:00 | Re: commitfest management webapp |