Re: Patch Nagging
- From: Elijah Newren <newren gmail com>
- To: Gnome Bugsquad <gnome-bugsquad gnome org>, Sebastien Bacher <seb128 debian org>, evolution-hackers lists ximian com
- Cc:
- Subject: Re: Patch Nagging
- Date: Wed, 11 May 2005 21:08:14 -0600
I think I should have sent this to evolution-hackers as well
considering the recent request they made about automated emails of
patches, so I'm resending so they can respond as well...
On 5/11/05, Elijah Newren <newren gmail com> wrote:
> What do others think of having
> http://bugzilla.gnome.org/reports/patch-nag.cgi
> replace
> http://bugzilla.gnome.org/reports/patch-report.cgi
> ?
>
> I believe this provides more information and makes it much easier to
> get straight to the patches so that they can be marked as reviewed
> (You don't have to click on a link which takes you to patch-status.cgi
> which redirects you to buglist.cgi, where you have to click on another
> link for the bug you want, where you have to scroll down to the patch
> that you want to edit. My version has a link to editing each
> individual patch on the first page so that there is only one level of
> nesting). Making the change means that people with bookmarks get a
> new improved version immediately; not replacing means
> yet-another-patch-report. :-)
>
> (Note also that I've already cheated and made patch-status.cgi point
> to patch-nag.cgi -- limiting to a product or even a component sure
> speeds the query up).
>
> Other questions:
> 1) Is there anything that should be added/removed/modified with the
> patch-nag.cgi page? (Sebastien suggested modifying attachment.cgi by
> adding an action=review option that looks like action=view but
> provides a link to the attachment box of show_bug.cgi; the idea being
> that patch-nag.cgi would then link to action=review instead of
> action=edit for the patches)
>
> 2) I would like to periodically email maintainers a condensed form of
> what's on the patch-nag.cgi page, and then provide them with a link to
> the patch-nag/patch-report page. How often should such an email be
> sent, and what should its contents be? (My current idea is something
> like "You have xx unreviewed patches in product blablabla; click on
> <link to patch-nag/patch-report> for more info, but note that the
> following new patches have been added to this list in the last
> <day/week/whatever>: <basic info about new patches>" This idea would
> require some additional work to get patch ages, but not a whole lot)
>
> Thanks,
> Elijah
>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]