On 07/03/07 at 10:48 -0500, Justin Pryzby wrote:
> On Wed, Mar 07, 2007 at 04:09:57PM +0100, Lucas Nussbaum wrote:
> > Hi,
> > 
> > The goal of this mail is to describe a possible new tool in Debian: DDPO by
> > mail, and to start discussing its details and implementation.
> > 
> > == Rationale ==
> > 
> > Many maintainers only maintain a few packages, which are in a very good 
> > state
> > most of the time. But often, such maintainers aren't fully aware of what is
> > happening with their packages. Of course, we could ask maintainers to use 
> > their
> > DDPO page as "start page", but that's not really realistic. :)
> > 
> > == Idea ==
> > 
> > The idea of "DDPO by mail" is to push *useful* information to maintainers
> > by sending them emails on a regular basis (e.g every two weeks).
> 
> I suggested a clientside implementation with comparable intent in
> devscripts #356689.  Present implementation seems somewhat less
> developer-oriented than yours.  I didn't want to list all bugs in ones'
> packages, since for some people this is way to many and just reduces the
> usefulness of other data.  Perhaps it is reasonable though if it is
> included as the last list and configurable.

I think that it's important to make that server-side, so the information
is "pushed" to the developers. With a client-side implementation, most
developers won't use it.

I was never planning to list all bugs, only RC ones (excluding those
with some tags like lenny-ignore). In the future, the script could be
extended to also list stuff like "important bugs with patches opened for
more than two months".

Your script is really interesting. Listing open WNPP bugs and new
upstream releases are good ideas, that should probably be added as well.
But it's probably better to start with something small, figure out all
the details, see how it is received by the other developers, and then
extend it to include more info.
-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED]             GPG: 1024D/023B3F4F |


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to