[Python-Dev] Issues with process and discussions (Re: Issues with Py3.1's new ipaddr)

[Alexander Belopolsky]

Alternatively, one could create a python-dev profile on roundup and
encourage people to add python-dev to the nosy list when discussion
needs to be broaden. This way replies to all will be posted in both
places.  Once discussion gets too specialized, someone can remove
python-dev from the "nosies." No new code is required to set this up
as far as I can tell.

On Thu, Jun 4, 2009 at 11:08 AM, C. Titus Brown <ctb at msu.edu> wrote:
> On Thu, Jun 04, 2009 at 11:03:22AM -0400, Alexander Belopolsky wrote:
> -> On Thu, Jun 4, 2009 at 6:20 AM, Paul Moore <p.f.moore at gmail.com> wrote:
> -> ...
> -> > I could still argue that there are downsides (need to take action to
> -> > set myself as nosy on an issue, possibly setting up a new mail filter,
> -> > housekeeping cruft, the fact that people don't quote in the same way
> -> > on tracker items) that make tracker discussions less attractive to me,
> -> > but it's very personal things.
> ->
> -> How hard would it be to set up a bot that will subscribe to python-dev
> -> and archive messages that have [issueXXXX] in the subject under
> -> appropriate roundup ticket?  This way if discussion started on
> -> roundup, it would only take adding python-dev in CC to bring it to the
> -> larger python-dev audience and adding issue number to the python-dev
> -> thread subject will be all it takes to archive new messages on
> -> roundup.  This would not solve a problem of linking threads that start
> -> on python-dev before a ticket is opened, but with some proper
> -> conventions this problem can be solved as well.
>
> In my experience this kind automated stuff is too fragile to work
> reliably & specifically over time, which is what we would want -- "fire
> and forget".
>
> Is there a good python-dev archive search mechanism (other than to
> google "python-dev <term>" ;) out there?  Wouldn't that help?
>
> cheers,
> --titus
> --
> C. Titus Brown, ctb at msu.edu
>