public inbox for [email protected]  

help / color / mirror / Atom feed

From: Dave Page <[email protected]>
To: Josh Berkus <[email protected]>
Cc: [email protected]
Cc: Bruce Momjian <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Heikki Linnakangas <[email protected]>
Cc: Simon Riggs <[email protected]>
Subject: Re: Feature freeze progress report
Date: Tue, 01 May 2007 18:21:55 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>

Josh,

Josh Berkus wrote:
> Is there a reason why the system needs to be primarily based on e-mail?  I was 
> thinking that the patch manager would be entirely a web tool, with people 
> submitting and modifying a patch directly through a web interface.  This 
> would be lots easier to build than an e-mail based system, and also far more 
> useful from a monitoring standpoint.  I've worked with e-mail based systems 
> like RT and OTRS, and frankly they're extremely high-maintenance and suffer a 
> large amount of "lost" information.

The reason for basing the system on email is simply that it minimises 
the changes required in the community process. If it were entirely web 
based, we'd have to change the way we all work to discuss patches in a 
forum style, rather than a list style. I have a sneaking suspicion that 
at least one of our most valued contributors might object to that.

As long as the patch were initially submitted through the web interface 
so that it got assigned an ID, we could automatically track the initial, 
and followup threads on any of the lists as long as the ID is retained 
in the subject line.

> We could also build a number of other things into the web tool, like a "You 
> are submitting this patch under BSD" disclaimer and pointers to the Developer 
> FAQ and other relevant documents.
> 

Oh for sure. We could even do silly stuff like try to automatically 
determine if the patch is in diff -c format ;-)

Regards, Dave

view thread (98+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Feature freeze progress report
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox