From techtonik at gmail.com  Fri Apr  1 00:34:12 2011
From: techtonik at gmail.com (anatoly techtonik)
Date: Fri, 1 Apr 2011 01:34:12 +0300
Subject: [Tracker-discuss] folded form
In-Reply-To: <4D94F3D4.2060208@v.loewis.de>
References: <20110330000725.3A356140209@kimball.webabinitio.net>
	<19858.31322.721096.355136@montanaro.dyndns.org>
	<4D94F3D4.2060208@v.loewis.de>
Message-ID: <AANLkTim4jgFnaPUmq1OJje4EKh_WSOrcsNYDsu1cAZV2@mail.gmail.com>

On Fri, Apr 1, 2011 at 12:36 AM, "Martin v. L?wis" <martin at v.loewis.de> wrote:
>> Sounds like a GSoC project to me...
>
> I doubt that. Any form of folding would require users to click more to
> access the hidden controls, to which they have strongly objected.
>
> So the lesson learned is: don't fold this forms in any form.

I'd object this. Google Code and Trac folding are rather good
compromise between presentation and usability. I am sure that a GSoC
student with good design skills is able get more candy out of pydotorg
rusks.

--
anatoly t.

From metatracker at psf.upfronthosting.co.za  Tue Apr  5 11:30:04 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Tue, 05 Apr 2011 09:30:04 +0000
Subject: [Tracker-discuss] [issue378] Merge OpenID login feature upstream
In-Reply-To: <1299181785.42.0.0532278744857.issue378@psf.upfronthosting.co.za>
Message-ID: <1301995804.33.0.799077391714.issue378@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

I can do this, but it is licensed under Academic Free License, version 3 
http://svn.python.org/projects/tracker/instances/python-dev/lib/openid2rp.py

So there is nothing I can do unless you can persuade Martin to exchange the license to MIT for some credits in Roundup project.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue378>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Apr  5 11:32:08 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Tue, 05 Apr 2011 09:32:08 +0000
Subject: [Tracker-discuss] [issue387] Need OpenID login for this tracker
In-Reply-To: <1301995928.44.0.997339418316.issue387@psf.upfronthosting.co.za>
Message-ID: <1301995928.44.0.997339418316.issue387@psf.upfronthosting.co.za>


New submission from anatoly techtonik <techtonik at gmail.com>:

I tend to forget passwords too fast. Would be nice to get OpenID login here, for this meta-tracker as well.

----------
messages: 1955
nosy: techtonik
priority: wish
status: unread
title: Need OpenID login for this tracker

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue387>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Apr  5 11:32:31 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Tue, 05 Apr 2011 09:32:31 +0000
Subject: [Tracker-discuss] [issue378] Merge OpenID login feature upstream
In-Reply-To: <1299181785.42.0.0532278744857.issue378@psf.upfronthosting.co.za>
Message-ID: <1301995951.63.0.587429023554.issue378@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

openid2rp is a separate package. It doesn't need to be incorporated into roundup.

----------
nosy: +loewis

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue378>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Apr  5 11:35:27 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Tue, 05 Apr 2011 09:35:27 +0000
Subject: [Tracker-discuss] [issue388] Code highlighting blocks in messages
In-Reply-To: <1301996127.65.0.760501812227.issue388@psf.upfronthosting.co.za>
Message-ID: <1301996127.65.0.760501812227.issue388@psf.upfronthosting.co.za>


New submission from anatoly techtonik <techtonik at gmail.com>:

I wonder what is takes to add support for parsing messages for {{{ }}} code blocks and highlight them?

----------
messages: 1957
nosy: techtonik
priority: feature
status: unread
title: Code highlighting blocks in messages

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue388>
_______________________________________________________

From turnbull at sk.tsukuba.ac.jp  Tue Apr  5 13:19:41 2011
From: turnbull at sk.tsukuba.ac.jp (Stephen J. Turnbull)
Date: Tue, 05 Apr 2011 20:19:41 +0900
Subject: [Tracker-discuss]  [issue378] Merge OpenID login feature upstream
In-Reply-To: <1301995951.63.0.587429023554.issue378@psf.upfronthosting.co.za>
References: <1299181785.42.0.0532278744857.issue378@psf.upfronthosting.co.za>
	<1301995951.63.0.587429023554.issue378@psf.upfronthosting.co.za>
Message-ID: <87lizpq71u.fsf@uwakimon.sk.tsukuba.ac.jp>

Martin v. L?wis writes:
 > 
 > Martin v. L?wis <martin at v.loewis.de> added the comment:
 > 
 > openid2rp is a separate package. It doesn't need to be incorporated into roundup.

I don't see what the problem is, anyway.  The AFL is a permissive,
noncopyleft license, and sublicensable.  That specifically means that
roundup can apply any license it likes to the whole, subject to a one
time change in COPYING.  Something similar was already done for
PageTemplates (actually, that's more than is required for the AFL).

Furthermore, if openid2rp is distributed without change, and not
copied into roundup, absolutely no license obligations are created at
all.  See http://www.rosenlaw.com/OSL3.0-explained.pdf, p. 7.

From metatracker at psf.upfronthosting.co.za  Tue Apr  5 13:14:19 2011
From: metatracker at psf.upfronthosting.co.za (Stephen Turnbull)
Date: Tue, 05 Apr 2011 11:14:19 +0000
Subject: [Tracker-discuss] [issue378] Merge OpenID login feature upstream
In-Reply-To: <1301995951.63.0.587429023554.issue378@psf.upfronthosting.co.za>
Message-ID: <87lizpq71u.fsf@uwakimon.sk.tsukuba.ac.jp>


Stephen Turnbull <stephen at xemacs.org> added the comment:

Martin v. L?wis writes:
 > 
 > Martin v. L?wis <martin at v.loewis.de> added the comment:
 > 
 > openid2rp is a separate package. It doesn't need to be incorporated into roundup.

I don't see what the problem is, anyway.  The AFL is a permissive,
noncopyleft license, and sublicensable.  That specifically means that
roundup can apply any license it likes to the whole, subject to a one
time change in COPYING.  Something similar was already done for
PageTemplates (actually, that's more than is required for the AFL).

Furthermore, if openid2rp is distributed without change, and not
copied into roundup, absolutely no license obligations are created at
all.  See http://www.rosenlaw.com/OSL3.0-explained.pdf, p. 7.

----------
nosy: +stephen

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue378>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Apr  5 14:35:50 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Tue, 05 Apr 2011 12:35:50 +0000
Subject: [Tracker-discuss] [issue378] Merge OpenID login feature upstream
In-Reply-To: <1299181785.42.0.0532278744857.issue378@psf.upfronthosting.co.za>
Message-ID: <1302006950.95.0.541744907523.issue378@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

Actually by "merging upstream" I meant OpenID support out of the box.

As for AFL, the biggest concern that nobody cares about it anymore, it is named redundant and there is still no consensus whatever it is compatible with GPL or not [1]. So I doubt anybody would want this stuff in their codebase.

It is also unclear under which license are current Roundup modifications.

1. http://en.wikipedia.org/wiki/Academic_Free_License

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue378>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Apr  5 20:30:37 2011
From: metatracker at psf.upfronthosting.co.za (Carsten Klein)
Date: Tue, 05 Apr 2011 18:30:37 +0000
Subject: [Tracker-discuss] [issue389] Weird behaviour when logging in using
	the registered email	address and not the login name
In-Reply-To: <1302028237.23.0.248770128189.issue389@psf.upfronthosting.co.za>
Message-ID: <1302028237.23.0.248770128189.issue389@psf.upfronthosting.co.za>


New submission from Carsten Klein <carsten.klein at axn-software.de>:

Today I logged on into the Python issue tracker and suddenly I received duplicate notifications on posting comments to an existing issue.

The nice people over at Python quickly identified the problem for being that I got added to the nosy list twice, once by the login name and a second time by the email address I used when logging in and commenting upon the issue.

Looking at the account details it showed that the login name was changed to the email address instead of the one already registered in the database.

----------
messages: 1960
nosy: carsten.klein
priority: bug
status: unread
title: Weird behaviour when logging in using the registered email address and not the login name

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue389>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Apr  6 02:21:46 2011
From: metatracker at psf.upfronthosting.co.za (Stephen Turnbull)
Date: Wed, 06 Apr 2011 00:21:46 +0000
Subject: [Tracker-discuss] [issue378] Merge OpenID login feature upstream
In-Reply-To: <1302006950.95.0.541744907523.issue378@psf.upfronthosting.co.za>
Message-ID: <87ipusql5t.fsf@uwakimon.sk.tsukuba.ac.jp>


Stephen Turnbull <stephen at xemacs.org> added the comment:

anatoly techtonik writes:

 > As for AFL, the biggest concern that nobody cares about it anymore,
 > it is named redundant and there is still no consensus whatever it
 > is compatible with GPL or not [1].

So what?  It's the license that Martin chose.

The real question is "will the Roundup Cabal accept the contribution
under those terms?"  Have you asked them?

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue378>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Apr  6 09:50:06 2011
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Wed, 06 Apr 2011 07:50:06 +0000
Subject: [Tracker-discuss] [issue388] Code highlighting blocks in messages
In-Reply-To: <1301996127.65.0.760501812227.issue388@psf.upfronthosting.co.za>
Message-ID: <1302076206.92.0.948531681757.issue388@psf.upfronthosting.co.za>


Georg Brandl <g.brandl at gmx.net> added the comment:

I don't think this is useful.  We shouldn't encourage people to put big chunks of code into tracker messages, they should go into attached files instead.  And for small chunks highlighting is not needed.

If our messages were markup-parsed in any other way, it would be natural to offer code blocks -- but we don't have any markup, and everything is monospaced.

----------
nosy: +gbrandl
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue388>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Apr  6 09:51:22 2011
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Wed, 06 Apr 2011 07:51:22 +0000
Subject: [Tracker-discuss] [issue378] Merge OpenID login feature upstream
In-Reply-To: <1299181785.42.0.0532278744857.issue378@psf.upfronthosting.co.za>
Message-ID: <1302076282.87.0.459665942451.issue378@psf.upfronthosting.co.za>


Georg Brandl <g.brandl at gmx.net> added the comment:

The question is rather, are Martin's changes to Roundup itself (NOT openid2rp, which is a separate library) subject to the AFL as well?

----------
nosy: +gbrandl

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue378>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Apr  6 17:43:52 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Wed, 06 Apr 2011 15:43:52 +0000
Subject: [Tracker-discuss] [issue388] Code highlighting blocks in messages
In-Reply-To: <1301996127.65.0.760501812227.issue388@psf.upfronthosting.co.za>
Message-ID: <1302104632.84.0.786934493265.issue388@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

Don't you think that markup processing can greatly improve the quality of information presented in the bug tracker? If code blocks are at least have different background - it will simplify reading a lot.

As for your fears about people posting big chunks of code just to make it highlighted, I never seen any complaint about this in any Trac installation. People are not that dumb to post a 64kB source code inline and if they do this - I doubt that it is because of code highlighting.

So, do you know how to approach this to make code blocks in messages work?

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue388>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Apr  6 17:53:09 2011
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Wed, 06 Apr 2011 15:53:09 +0000
Subject: [Tracker-discuss] [issue388] Code highlighting blocks in messages
In-Reply-To: <1301996127.65.0.760501812227.issue388@psf.upfronthosting.co.za>
Message-ID: <1302105189.75.0.5969787131.issue388@psf.upfronthosting.co.za>


Georg Brandl <g.brandl at gmx.net> added the comment:

> Don't you think that markup processing can greatly improve the quality of
> information presented in the bug tracker? If code blocks are at least have
> different background - it will simplify reading a lot.

No, I don't. You can immediately see what is code and what is text even if
they have the same background.

> As for your fears about people posting big chunks of code just to make it
> highlighted, I never seen any complaint about this in any Trac installation.
> People are not that dumb to post a 64kB source code inline and if they do
> this - I doubt that it is because of code highlighting.

I also never have seen any code in Trac where the highlighting was really
needed.  I'm not against code highlighting in general (it would be strange
for me as the author of Pygments), but here I just don't see the point.

And since it means that you have to introduce a new markup language where
previously there was none, it's just another thing for people to know when
using the tracker.

> So, do you know how to approach this to make code blocks in messages work?

Use the same hook we use for linking to issues, extract the code blocks and
highlight them with Pygments.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue388>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Apr  6 18:17:37 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Wed, 06 Apr 2011 16:17:37 +0000
Subject: [Tracker-discuss] [issue388] Code highlighting blocks in messages
In-Reply-To: <1302105189.75.0.5969787131.issue388@psf.upfronthosting.co.za>
Message-ID: <BANLkTikSQ3uMAoqRwykazOF21iqpFJG5sQ@mail.gmail.com>


anatoly techtonik <techtonik at gmail.com> added the comment:

On Wed, Apr 6, 2011 at 6:53 PM, Georg Brandl
<metatracker at psf.upfronthosting.co.za> wrote:
>
>> Don't you think that markup processing can greatly improve the quality of
>> information presented in the bug tracker? If code blocks are at least have
>> different background - it will simplify reading a lot.
>
> No, I don't. You can immediately see what is code and what is text even if
> they have the same background.

That's why we need more people to reach a consensus.

> I also never have seen any code in Trac where the highlighting was really
> needed. ?I'm not against code highlighting in general (it would be strange
> for me as the author of Pygments), but here I just don't see the point.

So, it is just useless for you, but you won't object if anybody will
do this. Am I right?

> And since it means that you have to introduce a new markup language where
> previously there was none, it's just another thing for people to know when
> using the tracker.

I'm just introducing a {{{ }}} code block. Well, bullet points is a
good addition for choices and summaries in discussions, but it is a
featurecreeping in the scope of this ticket.

>> So, do you know how to approach this to make code blocks in messages work?
>
> Use the same hook we use for linking to issues, extract the code blocks and
> highlight them with Pygments.

Thanks. I hope that's not too hardcore.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue388>
_______________________________________________________

From techtonik at gmail.com  Wed Apr  6 18:19:14 2011
From: techtonik at gmail.com (anatoly techtonik)
Date: Wed, 6 Apr 2011 19:19:14 +0300
Subject: [Tracker-discuss] Development instance
Message-ID: <BANLkTikfi3hj+_LymY0=29rTqrjVWJEDjQ@mail.gmail.com>

Greetings,

In the recent threads about dev.pypi.python.org I thought that it will
be nice to get the same infrastructure for tracker, so people can show
their modifications and let others play with them. What do you think?
--
anatoly t.

From metatracker at psf.upfronthosting.co.za  Wed Apr  6 18:30:17 2011
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Wed, 06 Apr 2011 16:30:17 +0000
Subject: [Tracker-discuss] [issue388] Code highlighting blocks in messages
In-Reply-To: <1301996127.65.0.760501812227.issue388@psf.upfronthosting.co.za>
Message-ID: <1302107417.67.0.297817796784.issue388@psf.upfronthosting.co.za>


Georg Brandl <g.brandl at gmx.net> added the comment:

> That's why we need more people to reach a consensus.

They're free to comment here, of course.

> So, it is just useless for you, but you won't object if anybody will
> do this. Am I right?

In voting terms, I'm -0.

> I'm just introducing a {{{ }}} code block. Well, bullet points is a
> good addition for choices and summaries in discussions, but it is a
> featurecreeping in the scope of this ticket.

That's exactly what I'm talking about.  How do you tell users that they
can use {{{ }}} blocks?  Also, do you just want to highlight Python, or
do you want to introduce a syntax to select the source language as well?

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue388>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Apr  6 18:39:00 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Wed, 06 Apr 2011 16:39:00 +0000
Subject: [Tracker-discuss] [issue388] Code highlighting blocks in messages
In-Reply-To: <1301996127.65.0.760501812227.issue388@psf.upfronthosting.co.za>
Message-ID: <1302107940.29.0.157731409284.issue388@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

I don't think this is worth the effort.  Code chunks in messages don't appear too often, and they are usually small enough that highlight will bring little benefit.  Implementing it is not entirely trivial, and adds another dependency on the tracker.  Also if you want to support syntax highlight you might want to do it for diffs and C code too and that gets even more complicated.
I'm therefore closing this.  If someone comes up with a patch it might be considered.

----------
nosy: +ezio.melotti
status: chatting -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue388>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Apr  6 21:49:18 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Wed, 06 Apr 2011 19:49:18 +0000
Subject: [Tracker-discuss] [issue388] Code highlighting blocks in messages
In-Reply-To: <1302107417.67.0.297817796784.issue388@psf.upfronthosting.co.za>
Message-ID: <4D9CC3BD.7080605@v.loewis.de>


Martin v. L?wis <martin at v.loewis.de> added the comment:

>> So, it is just useless for you, but you won't object if anybody will
>> do this. Am I right?
> 
> In voting terms, I'm -0.

So am I: -0.

----------
nosy: +loewis
status: resolved -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue388>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Apr  7 15:18:05 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?b?SmVzw7pzIENlYSBBdmnDs24=?=)
Date: Thu, 07 Apr 2011 13:18:05 +0000
Subject: [Tracker-discuss] [issue390] NOSY can't be changed when an username
	has an space on it	/ usernames with spaces!
In-Reply-To: <1302182285.95.0.686747374527.issue390@psf.upfronthosting.co.za>
Message-ID: <1302182285.95.0.686747374527.issue390@psf.upfronthosting.co.za>


New submission from Jes?s Cea Avi?n <jcea at jcea.es>:

Maybe the actual issue is that the tracker accepts usernames with spaces.

See http://bugs.python.org/msg133214

----------
messages: 1970
nosy: jcea
priority: bug
status: unread
title: NOSY can't be changed when an username has an space on it / usernames with spaces!

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue390>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Apr  7 16:13:38 2011
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Thu, 07 Apr 2011 14:13:38 +0000
Subject: [Tracker-discuss] [issue388] Code highlighting blocks in messages
In-Reply-To: <1301996127.65.0.760501812227.issue388@psf.upfronthosting.co.za>
Message-ID: <1302185618.91.0.988339999755.issue388@psf.upfronthosting.co.za>


R David Murray <rdmurray at bitdance.com> added the comment:

I think I'm about -0.5, for the reasons that Ezio cited.

----------
nosy: +r.david.murray
status: resolved -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue388>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Apr  7 23:40:00 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Thu, 07 Apr 2011 21:40:00 +0000
Subject: [Tracker-discuss] [issue390] NOSY can't be changed when an username
	has an space on it	/ usernames with spaces!
In-Reply-To: <1302182285.95.0.686747374527.issue390@psf.upfronthosting.co.za>
Message-ID: <1302212400.15.0.661053322228.issue390@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

I fail to see the problem. I could edit the nosy list just fine.

----------
nosy: +loewis
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue390>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Apr  8 03:25:52 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?b?SmVzw7pzIENlYSBBdmnDs24=?=)
Date: Fri, 08 Apr 2011 01:25:52 +0000
Subject: [Tracker-discuss] [issue390] NOSY can't be changed when an username
	has an space on it	/ usernames with spaces!
In-Reply-To: <1302182285.95.0.686747374527.issue390@psf.upfronthosting.co.za>
Message-ID: <1302225952.53.0.445151402707.issue390@psf.upfronthosting.co.za>


Jes?s Cea Avi?n <jcea at jcea.es> added the comment:

OK. Reproductible case:

1. I went to http://bugs.python.org/issue6715

2. I deleted my self from the nosy list.

3. Commit.

4. Go to http://bugs.python.org/issue6715 again.

5. Add myself to the NOSY list using the "+" button.

6. Commit

I get this error message: "property nosy: 'ChristopheSimonis' is not a user.".

Note that there is no spaces in the username reported in the error.

7. Go again http://bugs.python.org/issue6715

8. Add myself to the nosy list using the "+" button.

9. Before committing, I check the altered NOSY list. The javascript launched when pressed "+" actually deleted the space in "Christophe Simonis".

10. Add the space back, by hand.

11. Commit.

Success.

So the issue is the javascript. Seems it should delete spaces only a) before and after the text and b) before and after a comma until hitting a non space char.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue390>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Apr  8 03:29:25 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Fri, 08 Apr 2011 01:29:25 +0000
Subject: [Tracker-discuss] [issue390] NOSY can't be changed when an username
	has an space on it	/ usernames with spaces!
In-Reply-To: <1302182285.95.0.686747374527.issue390@psf.upfronthosting.co.za>
Message-ID: <1302226165.92.0.72265122543.issue390@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

I'll look at it.

----------
assignedto:  -> ezio.melotti
nosy: +ezio.melotti

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue390>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Apr  8 03:42:54 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Fri, 08 Apr 2011 01:42:54 +0000
Subject: [Tracker-discuss] [issue390] NOSY can't be changed when an username
	has an space on it	/ usernames with spaces!
In-Reply-To: <1302182285.95.0.686747374527.issue390@psf.upfronthosting.co.za>
Message-ID: <1302226974.39.0.913811080474.issue390@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Should be fixed in r88811, thanks for the report.

----------
status: chatting -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue390>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Apr  8 04:54:04 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Fri, 08 Apr 2011 02:54:04 +0000
Subject: [Tracker-discuss] [issue385] Forms are too wide
In-Reply-To: <1301432554.71.0.932571596008.issue385@psf.upfronthosting.co.za>
Message-ID: <1302231244.41.0.364295511261.issue385@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

I removed some unnecessary whitespace around the menu in r88812 so the situation now should be better.  The minimal width is given by the cols="72" and size="50" attributes in the comment field and in the input fields.  This could be changed via CSS somehow (it's not trivial to get the right min/max-width right on all the browsers though), but if this is good enough I won't touch the fields.

----------
assignedto:  -> ezio.melotti
status: unread -> testing

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue385>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Apr  8 05:06:48 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?b?SmVzw7pzIENlYSBBdmnDs24=?=)
Date: Fri, 08 Apr 2011 03:06:48 +0000
Subject: [Tracker-discuss] [issue390] NOSY can't be changed when an username
	has an space on it	/ usernames with spaces!
In-Reply-To: <1302182285.95.0.686747374527.issue390@psf.upfronthosting.co.za>
Message-ID: <1302232008.01.0.302578520285.issue390@psf.upfronthosting.co.za>


Jes?s Cea Avi?n <jcea at jcea.es> added the comment:

Enzo, your fix is

-    var nosy_text = nosy.value.replace(/\s+/g, '');
+    var nosy_text = nosy.value.replace(/,\s+/g, ',');

I don't think it is complete. You can have spaces before the comma, or at the begining/end of the nosy.

Maybe the easiest way would be to forget about regex and simply do something like

nosy_text = ",".join([i.strip() for i in nosy_text.split(",")])

----------
status: resolved -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue390>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Apr  8 14:37:37 2011
From: metatracker at psf.upfronthosting.co.za (Antoine Pitrou)
Date: Fri, 08 Apr 2011 12:37:37 +0000
Subject: [Tracker-discuss] [issue385] Forms are too wide
In-Reply-To: <1301432554.71.0.932571596008.issue385@psf.upfronthosting.co.za>
Message-ID: <1302266257.87.0.0840385249818.issue385@psf.upfronthosting.co.za>


Antoine Pitrou <pitrou at free.fr> added the comment:

Hmm, I don't see any difference. Did you put the changes online?

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue385>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Apr  8 20:52:08 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Fri, 08 Apr 2011 18:52:08 +0000
Subject: [Tracker-discuss] [issue385] Forms are too wide
In-Reply-To: <1301432554.71.0.932571596008.issue385@psf.upfronthosting.co.za>
Message-ID: <1302288728.75.0.951311621518.issue385@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

The change was put online on or before 15:56 UTC today.

----------
nosy: +loewis

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue385>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Apr  8 21:02:44 2011
From: metatracker at psf.upfronthosting.co.za (Antoine Pitrou)
Date: Fri, 08 Apr 2011 19:02:44 +0000
Subject: [Tracker-discuss] [issue385] Forms are too wide
In-Reply-To: <1301432554.71.0.932571596008.issue385@psf.upfronthosting.co.za>
Message-ID: <1302289364.07.0.776671786726.issue385@psf.upfronthosting.co.za>


Antoine Pitrou <pitrou at free.fr> added the comment:

Thank you, this is better now. The nosy list is still longish, though. I agree it's tough to get right across browsers.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue385>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sat Apr  9 21:04:33 2011
From: metatracker at psf.upfronthosting.co.za (Steffen Daode Nurpmeso)
Date: Sat, 09 Apr 2011 19:04:33 +0000
Subject: [Tracker-discuss] [issue391] Rietveld Code Review Tool can't handle
	well-known controls
In-Reply-To: <1302375873.9.0.391279709951.issue391@psf.upfronthosting.co.za>
Message-ID: <1302375873.9.0.391279709951.issue391@psf.upfronthosting.co.za>


New submission from Steffen Daode Nurpmeso <sdaoden at gmail.com>:

The file http://bugs.python.org/file21593/11650.termios.diff
cannot be parsed, i guess it's due to ^D, ^Z, ^\ and ^C being
embedded as ASCII control characters.
Maybe this is a feature, though.
Then someone should close this.
Nice weekend all of you.

----------
messages: 1981
nosy: sdaoden
priority: bug
status: unread
title: Rietveld Code Review Tool can't handle well-known controls

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue391>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Apr 12 14:28:45 2011
From: metatracker at psf.upfronthosting.co.za (Steffen Daode Nurpmeso)
Date: Tue, 12 Apr 2011 12:28:45 +0000
Subject: [Tracker-discuss] [issue391] Rietveld Code Review Tool can't handle
	well-known controls
In-Reply-To: <1302375873.9.0.391279709951.issue391@psf.upfronthosting.co.za>
Message-ID: <1302611325.92.0.236472909827.issue391@psf.upfronthosting.co.za>


Steffen Daode Nurpmeso <sdaoden at gmail.com> added the comment:

Only the side-by-side diff fails:

    http://bugs.python.org/review/11650/diff/2373/5575

The failure message ("Can't parse the patch") is meaningless.

----------
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue391>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Apr 13 17:51:44 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Wed, 13 Apr 2011 15:51:44 +0000
Subject: [Tracker-discuss] [issue373] Add 'module' field to tracker
In-Reply-To: <1296578034.58.0.494679196594.issue373@psf.upfronthosting.co.za>
Message-ID: <1302709904.16.0.343777950509.issue373@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

>From the wiki page about desired features:

When I want to find all bugs related to one module or package, I have to use the plain text search, which could give false positives and leave out valid results. For some packages I can use a component, e.g. Distutils, but not for all. I suggest a new field that would allow selecting what module(s)/package(s) a bug apply to. This would provide reliable and discoverable URIs for people who want to monitor particular modules or packages. [me]

This has been suggested and rejected a number of times on python-dev. --RDM

This information is not useful. Can you list the arguments? -- techtonik

No, but it would be great if you would search the archives and post links to the threads here. --RDM

I tried with no luck. It would be useful to find the threads for future reference, but your memory is enough for me to withdraw my feature request. ?merwok

Found this: http://psf.upfronthosting.co.za/roundup/meta/issue78 ?merwok

Nice catch. But that's not python-dev requests RDM is referring to. -techtonik

----------
nosy: +eric.araujo

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue373>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Apr 13 17:53:40 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Wed, 13 Apr 2011 15:53:40 +0000
Subject: [Tracker-discuss] [issue381] default mime-type for attachments
	should be text/plain
In-Reply-To: <1300916251.18.0.103274029072.issue381@psf.upfronthosting.co.za>
Message-ID: <1302710020.96.0.312365116197.issue381@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

A possible refinement: default content type should be text/plain, unless there is a NUL byte in the file.

----------
nosy: +eric.araujo
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue381>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Apr 13 17:57:12 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Wed, 13 Apr 2011 15:57:12 +0000
Subject: [Tracker-discuss] [issue267] Make the 'remove' buttons less annoying
In-Reply-To: <1239158834.9.0.636756137699.issue267@psf.upfronthosting.co.za>
Message-ID: <1302710232.73.0.901013959124.issue267@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

I have been telling contributors to clean up the list of files on some bugs.  Having the remove buttons on the main bug page or on message pages works equally well, I think (message pages can be opened in news tabs easily), so +1 on moving the buttons, as long as both the creator of the file and developers can remove (and maybe restore) them.

----------
nosy: +eric.araujo

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue267>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Apr 13 17:58:36 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Wed, 13 Apr 2011 15:58:36 +0000
Subject: [Tracker-discuss] [issue298] realname search should be case
	insensitive
In-Reply-To: <1253148331.7.0.788282669865.issue298@psf.upfronthosting.co.za>
Message-ID: <1302710316.57.0.42259625341.issue298@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

I use a Python application which has a case-insensitive search which is buggy with non-ASCII characters, so don?t make the same mistake :)

----------
nosy: +eric.araujo

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue298>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Apr 13 18:02:32 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Wed, 13 Apr 2011 16:02:32 +0000
Subject: [Tracker-discuss] [issue155] Add to Python Bug Sys RSS Feeds for
	Bug Reports, with Filters
In-Reply-To: <1189687013.8.0.983775873845.issue155@psf.upfronthosting.co.za>
Message-ID: <1302710552.17.0.375555738599.issue155@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

FWIW, Atom is a better choice than the various RSS formats.
http://www.intertwingly.net/wiki/pie/Rss20AndAtom10Compared
http://diveintomark.org/archives/2004/02/04/incompatible-rss

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue155>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Apr 13 18:04:36 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Wed, 13 Apr 2011 16:04:36 +0000
Subject: [Tracker-discuss] [issue291] force closed issues to have a
	resolution
In-Reply-To: <1246311618.39.0.313946202453.issue291@psf.upfronthosting.co.za>
Message-ID: <1302710676.65.0.405331336722.issue291@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Does Roundup support a concept of dependencies between field, or would this have to be added in an ad-hoc fashion?  For example, another useful modification would be to move from ?patch needed? to ?patch review? when a patch is added.

----------
nosy: +eric.araujo

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue291>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Apr 13 18:07:05 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Wed, 13 Apr 2011 16:07:05 +0000
Subject: [Tracker-discuss] [issue312] Add a 'go to the last message' link
In-Reply-To: <1263565390.97.0.608174776201.issue312@psf.upfronthosting.co.za>
Message-ID: <1302710825.11.0.195699407277.issue312@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

In general, duplicating browser UI in HTML (like those ?go to top? links) is a mistake IMO.  The End key (and similar controls) works.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue312>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Apr 13 18:28:46 2011
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Wed, 13 Apr 2011 16:28:46 +0000
Subject: [Tracker-discuss] [issue291] force closed issues to have a
	resolution
In-Reply-To: <1246311618.39.0.313946202453.issue291@psf.upfronthosting.co.za>
Message-ID: <1302712126.74.0.746539675604.issue291@psf.upfronthosting.co.za>


R David Murray <rdmurray at bitdance.com> added the comment:

It would have to be added, but it is not ad-hoc, it is completely programmable.  Python code can be hooked in before or after the field value changes are finalized, and implement whatever dependencies we want.  This is how autonosy and email notifications work, for example.

vis the "patch review" change, though, note that a patch-like thing being attached to an issue does not always mean it is time for a patch review.  The fact that it is most of the time might be reason enough to do it, though.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue291>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Apr 13 18:32:46 2011
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Wed, 13 Apr 2011 16:32:46 +0000
Subject: [Tracker-discuss] [issue312] Add a 'go to the last message' link
In-Reply-To: <1263565390.97.0.608174776201.issue312@psf.upfronthosting.co.za>
Message-ID: <1302712366.08.0.6899270667.issue312@psf.upfronthosting.co.za>


R David Murray <rdmurray at bitdance.com> added the comment:

That would be true of the 'end' button took you to the last message.  But it doesn't, it takes you to the end of the history list.

A better solution would be fold the history list by default, I think.  Or alternatively to interleave it with the messages, but I'd have to see how that looks to know if I liked it.  (That's how RT works by default, though, and I do find it useful in RT.)

----------
nosy: +r.david.murray

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue312>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Apr 13 20:28:51 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Wed, 13 Apr 2011 18:28:51 +0000
Subject: [Tracker-discuss] [issue381] default mime-type for attachments
	should be text/plain
In-Reply-To: <1300916251.18.0.103274029072.issue381@psf.upfronthosting.co.za>
Message-ID: <1302719331.92.0.107926981432.issue381@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

I'd use a more strict rule: it should decode as UTF-8, and should only include the standard whitespace control characters.

----------
nosy: +loewis

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue381>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Apr 13 20:36:35 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Wed, 13 Apr 2011 18:36:35 +0000
Subject: [Tracker-discuss] [issue291] force closed issues to have a
	resolution
In-Reply-To: <1246311618.39.0.313946202453.issue291@psf.upfronthosting.co.za>
Message-ID: <1302719795.75.0.641642998346.issue291@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

detector/patches.py is the automatically adds the patches keyword; it could easily make other changes also.

----------
nosy: +loewis

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue291>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Apr 13 22:37:03 2011
From: metatracker at psf.upfronthosting.co.za (Antoine Pitrou)
Date: Wed, 13 Apr 2011 20:37:03 +0000
Subject: [Tracker-discuss] [issue381] default mime-type for attachments
	should be text/plain
In-Reply-To: <1302719331.92.0.107926981432.issue381@psf.upfronthosting.co.za>
Message-ID: <1302727020.3600.3.camel@localhost.localdomain>


Antoine Pitrou <pitrou at free.fr> added the comment:

> I'd use a more strict rule: it should decode as UTF-8, and should only
> include the standard whitespace control characters.

I think this discussion of heuristics distracts us from the original
(simple) request: that files that don't belong to a recognized file type
get tagged as text/plain rather than application/octet-stream.
This would go a long way towards making day-to-day use of the tracker
more pleasant, and is probably much simpler than deciding on a
content-guessing heuristic.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue381>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Apr 13 23:00:16 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Wed, 13 Apr 2011 21:00:16 +0000
Subject: [Tracker-discuss] [issue381] default mime-type for attachments
	should be text/plain
In-Reply-To: <1300916251.18.0.103274029072.issue381@psf.upfronthosting.co.za>
Message-ID: <1302728416.79.0.275399252402.issue381@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

I disagree that the original simple request should be granted. I'd rather err on the safe side. So it's either a safe heuristics, or no change.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue381>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Apr 13 23:02:40 2011
From: metatracker at psf.upfronthosting.co.za (Antoine Pitrou)
Date: Wed, 13 Apr 2011 21:02:40 +0000
Subject: [Tracker-discuss] [issue381] default mime-type for attachments
	should be text/plain
In-Reply-To: <1300916251.18.0.103274029072.issue381@psf.upfronthosting.co.za>
Message-ID: <1302728560.94.0.00525211269603.issue381@psf.upfronthosting.co.za>


Antoine Pitrou <pitrou at free.fr> added the comment:

> I disagree that the original simple request should be granted.

Why?

> I'd rather err on the safe side.?

What is the security issue? text/plain can't execute arbitrary code in your browser.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue381>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Apr 13 23:08:06 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Wed, 13 Apr 2011 21:08:06 +0000
Subject: [Tracker-discuss] [issue381] default mime-type for attachments
	should be text/plain
In-Reply-To: <1302728560.94.0.00525211269603.issue381@psf.upfronthosting.co.za>
Message-ID: <4DA610B0.8020004@v.loewis.de>


Martin v. L?wis <martin at v.loewis.de> added the comment:

> What is the security issue? text/plain can't execute arbitrary code in your browser.

Depending on the browser, it could trigger "funny" control sequences
(in particular in a text browser running in a terminal). I believe that
text/plain *can* run arbitrary code.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue381>
_______________________________________________________

From martin at v.loewis.de  Wed Apr 13 23:08:00 2011
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Wed, 13 Apr 2011 23:08:00 +0200
Subject: [Tracker-discuss] [issue381] default mime-type for attachments
 should be text/plain
In-Reply-To: <1302728560.94.0.00525211269603.issue381@psf.upfronthosting.co.za>
References: <1302728560.94.0.00525211269603.issue381@psf.upfronthosting.co.za>
Message-ID: <4DA610B0.8020004@v.loewis.de>

> What is the security issue? text/plain can't execute arbitrary code in your browser.

Depending on the browser, it could trigger "funny" control sequences
(in particular in a text browser running in a terminal). I believe that
text/plain *can* run arbitrary code.

From metatracker at psf.upfronthosting.co.za  Wed Apr 13 23:16:01 2011
From: metatracker at psf.upfronthosting.co.za (Antoine Pitrou)
Date: Wed, 13 Apr 2011 21:16:01 +0000
Subject: [Tracker-discuss] [issue381] default mime-type for attachments
	should be text/plain
In-Reply-To: <4DA610B0.8020004@v.loewis.de>
Message-ID: <1302729359.3600.6.camel@localhost.localdomain>


Antoine Pitrou <pitrou at free.fr> added the comment:

> > What is the security issue? text/plain can't execute arbitrary code in your browser.
> 
> Depending on the browser, it could trigger "funny" control sequences
> (in particular in a text browser running in a terminal). I believe that
> text/plain *can* run arbitrary code.

I don't think that's a serious concern. Anyone wanting to use the bug
tracker's Web UI in a text-mode browser has probably given up long ago.

Also, if a text-mode Web browser renders control sequences without
escaping them, I'd say the browser has a security problem, not the Web
site.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue381>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Apr 13 23:19:41 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Wed, 13 Apr 2011 21:19:41 +0000
Subject: [Tracker-discuss] [issue381] default mime-type for attachments
	should be text/plain
In-Reply-To: <1302729359.3600.6.camel@localhost.localdomain>
Message-ID: <4DA61368.50701@v.loewis.de>


Martin v. L?wis <martin at v.loewis.de> added the comment:

> I don't think that's a serious concern. Anyone wanting to use the bug
> tracker's Web UI in a text-mode browser has probably given up long ago.

Please don't argue - I just won't change my position on that. Text files
shouldn't render as moji-bake, period. Please also trust me that doing
any of the proposed heuristics is nearly as simple as implementing your
"simple" approach.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue381>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Apr 13 23:24:51 2011
From: metatracker at psf.upfronthosting.co.za (Antoine Pitrou)
Date: Wed, 13 Apr 2011 21:24:51 +0000
Subject: [Tracker-discuss] [issue381] default mime-type for attachments
	should be text/plain
In-Reply-To: <1300916251.18.0.103274029072.issue381@psf.upfronthosting.co.za>
Message-ID: <1302729891.16.0.547468592988.issue381@psf.upfronthosting.co.za>


Antoine Pitrou <pitrou at free.fr> added the comment:

Ok, good luck.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue381>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Apr 14 00:10:28 2011
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Wed, 13 Apr 2011 22:10:28 +0000
Subject: [Tracker-discuss] [issue381] default mime-type for attachments
	should be text/plain
In-Reply-To: <1300916251.18.0.103274029072.issue381@psf.upfronthosting.co.za>
Message-ID: <1302732628.24.0.0418620903499.issue381@psf.upfronthosting.co.za>


R David Murray <rdmurray at bitdance.com> added the comment:

The roundup UI is actually quite usable from a (good) text mode browser.  It's not exactly compact, but it *works* just fine.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue381>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Apr 14 00:44:52 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Wed, 13 Apr 2011 22:44:52 +0000
Subject: [Tracker-discuss] [issue381] default mime-type for attachments
	should be text/plain
In-Reply-To: <1300916251.18.0.103274029072.issue381@psf.upfronthosting.co.za>
Message-ID: <1302734692.96.0.403446335796.issue381@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

+1 for Antoine. I hate to download patches to my PC just to be able to view them. Considering that we are speaking about default mime type, .zip archives and other extensions will be unaffected, so impact is minimal.

Martin, I do not understand your concerns about text mode browser security. You should not use browsers that control your system using binary characters from text/plain web pages. It puts all Python infrastructure at risk.

----------
nosy: +techtonik

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue381>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Apr 14 00:54:55 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Wed, 13 Apr 2011 22:54:55 +0000
Subject: [Tracker-discuss] [issue381] default mime-type for attachments
	should be text/plain
In-Reply-To: <1302734692.96.0.403446335796.issue381@psf.upfronthosting.co.za>
Message-ID: <4DA629B8.20004@v.loewis.de>


Martin v. L?wis <martin at v.loewis.de> added the comment:

> Martin, I do not understand your concerns about text mode browser security. 

anatoly, I do not understand your concerns about the solution proposed
by eric and me.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue381>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Apr 14 01:09:49 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Wed, 13 Apr 2011 23:09:49 +0000
Subject: [Tracker-discuss] [issue373] Add 'module' field to tracker
In-Reply-To: <1296671291.26.0.0258128953305.issue373@psf.upfronthosting.co.za>
Message-ID: <BANLkTikRijtEBOoKtr4TqC+kwe6Z900wRg@mail.gmail.com>


anatoly techtonik <techtonik at gmail.com> added the comment:

On Wed, Feb 2, 2011 at 8:28 PM, Ezio Melotti
<metatracker at psf.upfronthosting.co.za> wrote:
>
> Even if knowing the module(s) related to the issue is useful, there are a number of problems that should be considered:
> * there are hundreds of modules;

How many exactly? I doubt there is more than hundred.
https://bugzilla.gnome.org/ handles it pretty well.

> * there's no easy way to display so many options;

If the tracker suxx - change the tracker. It should help development -
not constrain it.

> * several modules can be related to the issue;

Make them tags.

> * there are different modules depending on the Python version;
> * there are different names for the same modules depending on the Python version;

Use both until subset of Python versions is not selected. If you need
to store both names - use module description format -
http://code.google.com/p/pydotorg/issues/detail?id=8

> * the list of modules must be updated when modules are added/removed/renamed;

Store module mapping in repository and throw warning during build
stage when files added or removed.

> * a new field adds clutter to the UI and more work for the submitters and triagers;

Split reporting in two steps like in Gnome or Eclipse Bugzillas. The
first step can also force search for similar items - like in
Launchpad.

> * searching for a specific module won't include the issues if the field is not set correctly (i.e. old issues and issues that haven't be triaged), the normal search will;

All issues should undergo triaging process. Opened old issues can be
retriaged. Closed could be left RIP. If you want to find them - use
module name in normal search - it will still work.

> * there's no patch ready to implement (or attempt to implement) this feature;
>
> Another option is looking automatically at the attached patches, figure out what files they affect, and make this information available.
> This won't require extra work for submitters and triagers and no new fields are needed in the issue page (only a field in the search page).

That's included in the proposal by the link above. But mind you that
issues without patches may never get any, because module maintainers
are unaware that there are issues for them. Modules should have their
own bug Atom feed.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue373>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Apr 14 01:13:36 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Wed, 13 Apr 2011 23:13:36 +0000
Subject: [Tracker-discuss] [issue381] default mime-type for attachments
	should be text/plain
In-Reply-To: <1300916251.18.0.103274029072.issue381@psf.upfronthosting.co.za>
Message-ID: <1302736416.35.0.393857264028.issue381@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

Heuristics adds additional maintenance burden and complicates code. Default mime type is not a hack and a simple solution everybody could find and revert in case it causes problem. There is a lot of hacks handling patches already.

If I made my concerns clear for you, could you make the same for me, please?

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue381>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Apr 14 04:28:36 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Thu, 14 Apr 2011 02:28:36 +0000
Subject: [Tracker-discuss] [issue312] Add a 'go to the last message' link
In-Reply-To: <1263565390.97.0.608174776201.issue312@psf.upfronthosting.co.za>
Message-ID: <1302748116.51.0.452355412001.issue312@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Folding the history is actually what I was planning to do. Interleaving some of the history is useful too, but I'll have to see about that.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue312>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Apr 14 08:32:50 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Thu, 14 Apr 2011 06:32:50 +0000
Subject: [Tracker-discuss] [issue381] default mime-type for attachments
	should be text/plain
In-Reply-To: <1302736416.35.0.393857264028.issue381@psf.upfronthosting.co.za>
Message-ID: <4DA69510.70607@v.loewis.de>


Martin v. L?wis <martin at v.loewis.de> added the comment:

> Heuristics adds additional maintenance burden and complicates code.

Please leave that concern to the people who are *actually*
maintaining the tracker.

> Default mime type is not a hack

It's worse than a hack - it doesn't actually work. It's
not roundup who currently fills in application/octet-stream
as the mime type by default - the web browser will already
supply the mime type, in all cases. So if text/plain was
the default mime type, the default would never be used.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue381>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Apr 14 08:52:36 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Thu, 14 Apr 2011 06:52:36 +0000
Subject: [Tracker-discuss] [issue381] default mime-type for attachments
	should be text/plain
In-Reply-To: <1300916251.18.0.103274029072.issue381@psf.upfronthosting.co.za>
Message-ID: <1302763956.64.0.0856244051465.issue381@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

FWIW Roundup has some code to set the default content-type (and even to guess it when it's not provided) in roundup-src/roundup/cgi/form_parser.py:456.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue381>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Apr 14 12:52:05 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Thu, 14 Apr 2011 10:52:05 +0000
Subject: [Tracker-discuss] [issue381] default mime-type for attachments
	should be text/plain
In-Reply-To: <4DA69510.70607@v.loewis.de>
Message-ID: <BANLkTi=K_JDF4PO4+9ZjphzgjAOSdGAqzQ@mail.gmail.com>


anatoly techtonik <techtonik at gmail.com> added the comment:

Good. I assume that security of text mode browsers is not the concern
anymore. So right now the question is - how to setup default mime-type
for attachment, if mime-type is not assigned by Roundup or web-server.

As I don't have access to server, can anybody describe the
configurations for attachments in Roundup in general and in b.p.o
instance in particular (wiki link is ok):
1. Are attachments served as static resources?
2. Can Roundup serve static resources itself?
3. What kind of control does Roundup have over HTTP headers for static
resources?
4. When request arrives at Roundup, is mime-type already set by the
web server in request?

msg:checkpoint

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue381>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Apr 14 12:54:16 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Thu, 14 Apr 2011 10:54:16 +0000
Subject: [Tracker-discuss] [issue392] source linking for meta-tracker
In-Reply-To: <1302778456.3.0.238032301869.issue392@psf.upfronthosting.co.za>
Message-ID: <1302778456.3.0.238032301869.issue392@psf.upfronthosting.co.za>


New submission from anatoly techtonik <techtonik at gmail.com>:

It would be extremely handy to have a linkifier for pydotorg tracker sources in this tracker. e.g. http://psf.upfronthosting.co.za/roundup/meta/msg2008

----------
messages: 2010
nosy: techtonik
priority: feature
status: unread
title: source linking for meta-tracker

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue392>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Apr 14 21:34:11 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Thu, 14 Apr 2011 19:34:11 +0000
Subject: [Tracker-discuss] [issue381] default mime-type for attachments
	should be text/plain
In-Reply-To: <1300916251.18.0.103274029072.issue381@psf.upfronthosting.co.za>
Message-ID: <1302809651.16.0.274057285608.issue381@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

This is now fixed as of r88814.

----------
status: chatting -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue381>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Apr 14 23:31:16 2011
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Thu, 14 Apr 2011 21:31:16 +0000
Subject: [Tracker-discuss] [issue381] default mime-type for attachments
	should be text/plain
In-Reply-To: <1300916251.18.0.103274029072.issue381@psf.upfronthosting.co.za>
Message-ID: <1302816676.04.0.224696941553.issue381@psf.upfronthosting.co.za>


R David Murray <rdmurray at bitdance.com> added the comment:

Thank you, Martin.  That has been an annoying issue for a long time.

----------
status: resolved -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue381>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sun Apr 17 15:52:04 2011
From: metatracker at psf.upfronthosting.co.za (Stephen Turnbull)
Date: Sun, 17 Apr 2011 13:52:04 +0000
Subject: [Tracker-discuss] [issue393] Security policy should be visible on
	top page of tracker, maybe every page
In-Reply-To: <1303048324.83.0.514918059654.issue393@psf.upfronthosting.co.za>
Message-ID: <1303048324.83.0.514918059654.issue393@psf.upfronthosting.co.za>


New submission from Stephen Turnbull <stephen at xemacs.org>:

Python's documentation should make it clear at the most important entry points that the appropriate place to report possible security issues is security at python.org, not the tracker.  In particular, the tracker's top page (the one you get from http://bugs.python.org/) should make that clear.
See the News/Security Advisories on Python's main pages and Brian Curtin's 2011-04-14 post for reasonable descriptions of the de facto policy.

The Tracker documentation probably should be updated with this as well.

It might be a good idea to have a way for triagers to suppress display of security issues by classifying them as security (eg, via priority, keyword, or possibly even resolution).

Xref thread starting at http://mail.python.org/pipermail/python-dev/2011-April/110722.html.

----------
messages: 2013
nosy: stephen
priority: bug
status: unread
title: Security policy should be visible on top page of tracker, maybe every page

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue393>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Mon Apr 18 17:48:21 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Mon, 18 Apr 2011 15:48:21 +0000
Subject: [Tracker-discuss] [issue393] Security policy should be visible on
	top page of tracker, maybe every page
In-Reply-To: <1303048324.83.0.514918059654.issue393@psf.upfronthosting.co.za>
Message-ID: <1303141701.05.0.21935430316.issue393@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Closing with an ?invalid? resolution would certainly be appropriate.

----------
nosy: +eric.araujo, ezio.melotti
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue393>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Mon Apr 18 18:32:18 2011
From: metatracker at psf.upfronthosting.co.za (Stephen Turnbull)
Date: Mon, 18 Apr 2011 16:32:18 +0000
Subject: [Tracker-discuss] [issue393] Security policy should be visible on
	top page of tracker, maybe every page
In-Reply-To: <1303048324.83.0.514918059654.issue393@psf.upfronthosting.co.za>
Message-ID: <1303144338.88.0.182787063543.issue393@psf.upfronthosting.co.za>


Stephen Turnbull <stephen at xemacs.org> added the comment:

That would help, and is available now.

However, a search of closed issues with "security" or "exploit" or "overrun" somewhere in their text would bring most of them up.

----------
status: chatting -> unread

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue393>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Mon Apr 18 21:46:49 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Mon, 18 Apr 2011 19:46:49 +0000
Subject: [Tracker-discuss] [issue393] Security policy should be visible on
	top page of tracker, maybe every page
In-Reply-To: <1303048324.83.0.514918059654.issue393@psf.upfronthosting.co.za>
Message-ID: <1303156009.78.0.589617913214.issue393@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

If some member of security at python.org could speak up: that would be appreciated. It certainly possible to implement any hiding/deletion/obfuscation that is desired. However, I'd like to hear some "official" statement as to what policy the tracker should follow exactly.

----------
nosy: +loewis
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue393>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Mon Apr 18 21:52:30 2011
From: metatracker at psf.upfronthosting.co.za (Ned Deily)
Date: Mon, 18 Apr 2011 19:52:30 +0000
Subject: [Tracker-discuss] [issue394] Better integration with Rietveld code
	review tool
In-Reply-To: <1303156350.85.0.792534425783.issue394@psf.upfronthosting.co.za>
Message-ID: <1303156350.85.0.792534425783.issue394@psf.upfronthosting.co.za>


New submission from Ned Deily <nad at acm.org>:

While there may be a review button link automatically created to a Rietveld code review instance for a submitted patch, there is no other indication (as far as I can tell) that of any activity on the Rietveld side including the submission of any comments there.  That seems to mean that if you are looking at an issue in the tracker, you must now periodically go to the Rietveld page to see if there is any activity there (assuming you are not on the review CC list and that the CC list is working properly).  That is far from ideal.  Many people don't need or want to be added to the nosy list or review CC list just to keep track of updates, for example, if they are monitoring activity via the mailing list archives or via something like gmane.org.  There should be some indication on the normal bug issue page that there is activity on the Rietveld side, perhaps by having Rietveld comment commits generating a message in the tracker.

----------
messages: 2017
nosy: ned.deily
priority: feature
status: unread
title: Better integration with Rietveld code review tool

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue394>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Mon Apr 18 22:02:58 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Mon, 18 Apr 2011 20:02:58 +0000
Subject: [Tracker-discuss] [issue393] Security policy should be visible on
	top page of tracker, maybe every page
In-Reply-To: <1303048324.83.0.514918059654.issue393@psf.upfronthosting.co.za>
Message-ID: <1303156978.18.0.337569961466.issue393@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Some warning message could be shown when type:"security" is selected, but if security issues are not supposed to go through the tracker maybe that type shouldn't exist in the first place.
A fixed message in the issue creation page might be OK too, as long as it is not too invasive.  Adding some instructions to the devguide is definitly OK.

BTW, a more effective and already available way to "hide" those messages is to mark them as spam -- but that's just an ugly workaround.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue393>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Mon Apr 18 22:16:48 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Mon, 18 Apr 2011 20:16:48 +0000
Subject: [Tracker-discuss] [issue393] Security policy should be visible on
	top page of tracker, maybe every page
In-Reply-To: <1303048324.83.0.514918059654.issue393@psf.upfronthosting.co.za>
Message-ID: <1303157808.03.0.917948365128.issue393@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Another alternative is to add security at python.org to the nosy automatically when a "security" issue is created (this can be done anyway) and make the issue visible only to a limited group of person (e.g. core developers and the OP).

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue393>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Mon Apr 18 22:20:48 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Mon, 18 Apr 2011 20:20:48 +0000
Subject: [Tracker-discuss] [issue393] Security policy should be visible on
	top page of tracker, maybe every page
In-Reply-To: <1303048324.83.0.514918059654.issue393@psf.upfronthosting.co.za>
Message-ID: <1303158048.09.0.752854650744.issue393@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

Because of all these options I'd like some of the security team to state how they actually want it. There is no point in changing something proactively that is then still undesired.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue393>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Apr 19 14:28:50 2011
From: metatracker at psf.upfronthosting.co.za (Steffen Daode Nurpmeso)
Date: Tue, 19 Apr 2011 12:28:50 +0000
Subject: [Tracker-discuss] [issue395] My mails can change the title (nothing
	else)
In-Reply-To: <1303216130.53.0.812232423265.issue395@psf.upfronthosting.co.za>
Message-ID: <1303216130.53.0.812232423265.issue395@psf.upfronthosting.co.za>


New submission from Steffen Daode Nurpmeso <sdaoden at gmail.com>:

When i reply to a message which has been posted before a title change,
the title will be reverted to it's original value.
On the other hand i can't use the '[x=y]' notation which Roundup seems
to support according to it's docs somewhere, forgotten where.
I do believe this is because i'm not a committer, i.e. missing rights.
I think this role of mine should be adhered for the title too.
(Even better: reverting should not happen at all.)

----------
messages: 2021
nosy: sdaoden
priority: feature
status: unread
title: My mails can change the title (nothing else)

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue395>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Apr 21 17:20:31 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Thu, 21 Apr 2011 15:20:31 +0000
Subject: [Tracker-discuss] [issue312] Add a 'go to the last message' link
In-Reply-To: <1263565390.97.0.608174776201.issue312@psf.upfronthosting.co.za>
Message-ID: <1303399231.54.0.140425913641.issue312@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

> That would be true of the 'end' button took you to the last message.  But it
> doesn't, it takes you to the end of the history list.

In most bug reports, that?s not far from the end of the message list, or one PageUp keystroke away.  But I acknowledge that there are bugs with pathologically long history (or file lists *cough*regex*cough* *wink*).

> A better solution would be fold the history list by default, I think.

I?m wondering: if it wouldn?t hurt to hide it, doesn?t that mean it?s useless?

> Or alternatively to interleave it with the messages, but I'd have to see how
> that looks to know if I liked it.  (That's how RT works by default, though,
> and I do find it useful in RT.)

Oh please yes.  Having the list of files separated makes sense, but having a list of messages and a list of actions does not IMO.  I use other bug trackers with only one list and it?s in my experience much nicer to use.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue312>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Apr 21 18:10:48 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Thu, 21 Apr 2011 16:10:48 +0000
Subject: [Tracker-discuss] [issue312] Add a 'go to the last message' link
In-Reply-To: <1263565390.97.0.608174776201.issue312@psf.upfronthosting.co.za>
Message-ID: <1303402248.26.0.113190064764.issue312@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

> I?m wondering: if it wouldn?t hurt to hide it, doesn?t that mean it?s useless?

It mostly is, but currently there are cases where it's useful (e.g. link to superseders, see things that got deleted, changes in the title, etc.).
Some of things could be fixed in other places though, but folding it would be a good compromise.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue312>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Apr 21 18:18:59 2011
From: metatracker at psf.upfronthosting.co.za (Stephen Turnbull)
Date: Thu, 21 Apr 2011 16:18:59 +0000
Subject: [Tracker-discuss] [issue312] Add a 'go to the last message' link
In-Reply-To: <1303399231.54.0.140425913641.issue312@psf.upfronthosting.co.za>
Message-ID: <87liz3bmiq.fsf@uwakimon.sk.tsukuba.ac.jp>


Stephen Turnbull <stephen at xemacs.org> added the comment:

?ric Araujo writes:

 > Oh please yes.  Having the list of files separated makes sense, but having a list of messages and a list of actions does not IMO.  I use other bug trackers with only one list and it?s in my experience much nicer to use.

But be a little picky about filtering out "noise" actions.  On the
MacPorts Trac you occasionally see a full screen (about 20 entries
for me) of nothing but "CC me!" messages.  (These are the equivalent
of adding to nosy in Roundup.)  At the very least, changes to nosy
should not be interleaved with the messages.  There may be other
uninteresting actions though I can't think of any offhand.

----------
nosy: +stephen

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue312>
_______________________________________________________

From stephen at xemacs.org  Thu Apr 21 18:24:29 2011
From: stephen at xemacs.org (Stephen J. Turnbull)
Date: Fri, 22 Apr 2011 01:24:29 +0900
Subject: [Tracker-discuss] [issue312] Add a 'go to the last message' link
In-Reply-To: <1303399231.54.0.140425913641.issue312@psf.upfronthosting.co.za>
References: <1263565390.97.0.608174776201.issue312@psf.upfronthosting.co.za>
	<1303399231.54.0.140425913641.issue312@psf.upfronthosting.co.za>
Message-ID: <87liz3bmiq.fsf@uwakimon.sk.tsukuba.ac.jp>

?ric Araujo writes:

 > Oh please yes.  Having the list of files separated makes sense, but having a list of messages and a list of actions does not IMO.  I use other bug trackers with only one list and it?s in my experience much nicer to use.

But be a little picky about filtering out "noise" actions.  On the
MacPorts Trac you occasionally see a full screen (about 20 entries
for me) of nothing but "CC me!" messages.  (These are the equivalent
of adding to nosy in Roundup.)  At the very least, changes to nosy
should not be interleaved with the messages.  There may be other
uninteresting actions though I can't think of any offhand.

From metatracker at psf.upfronthosting.co.za  Thu Apr 21 18:42:56 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Thu, 21 Apr 2011 16:42:56 +0000
Subject: [Tracker-discuss] [issue373] Add 'module' field to tracker
In-Reply-To: <1296578034.58.0.494679196594.issue373@psf.upfronthosting.co.za>
Message-ID: <1303404176.57.0.752141245417.issue373@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

>> Even if knowing the module(s) related to the issue is useful, there are a
>> number of problems that should be considered:
>> * there are hundreds of modules;
> How many exactly? I doubt there is more than hundred.

More than two hundreds.

>> * several modules can be related to the issue;
> Make them tags.

What are tags?

>> * the list of modules must be updated when modules are added/removed/renamed;
> Store module mapping in repository and throw warning during build
> stage when files added or removed.

Or maybe use the mapping in lib2to3.fixes.fix_imports (not sure the Python used for our Roundup is recent enough.)

>> * a new field adds clutter to the UI and more work for the submitters and triagers;
> Split reporting in two steps like in Gnome or Eclipse Bugzillas.

Interesting idea.

>> * searching for a specific module won't include the issues if the field is not set
>> correctly (i.e. old issues and issues that haven't be triaged), the normal search will;
> All issues should undergo triaging process. Opened old issues can be
> retriaged. Closed could be left RIP. If you want to find them - use
> module name in normal search - it will still work.

?Should? is nice.  How do you propose to implement it concretely?  It could possible to add a special ?untriaged? state used in queries, but I?m not sure this would help; given enough volunteers with enough free time, bug triaging happens quite effectively.  The weekly email also helps find unanswered reports.

>> Another option is looking automatically at the attached patches, figure out
>> what files they affect, and make this information available.

Sounds good.  I?m sure difflib can do that.

> But mind you that issues without patches may never get any, because module
> maintainers are unaware that there are issues for them.

There are triagers who use the experts list (in the devguide) to add maintainers to nosy.

----------
nosy: +r.david.murray

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue373>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Apr 21 18:46:14 2011
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Thu, 21 Apr 2011 16:46:14 +0000
Subject: [Tracker-discuss] [issue312] Add a 'go to the last message' link
In-Reply-To: <1263565390.97.0.608174776201.issue312@psf.upfronthosting.co.za>
Message-ID: <1303404374.18.0.855136972663.issue312@psf.upfronthosting.co.za>


R David Murray <rdmurray at bitdance.com> added the comment:

I disagree that the actions are "mostly useless", or even that the 'nosy' change information is noise.  While I don't refer to the action list often, I do refer to it regularly to answer some question about actions taken on the issue.  And I'd guess that about half the time I do I'm checking to see when someone got added as nosy and whether they did it themselves or if someone else added them (and if so, I sometimes care about who did the add).

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue312>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Apr 21 18:57:35 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Thu, 21 Apr 2011 16:57:35 +0000
Subject: [Tracker-discuss] [issue312] Add a 'go to the last message' link
In-Reply-To: <1263565390.97.0.608174776201.issue312@psf.upfronthosting.co.za>
Message-ID: <1303405055.81.0.548874174693.issue312@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

"mostly useless" means that in most of the cases you don't care about them and if you do it's just about a specific action.
I'd leave nosy changes out from the interleaved history for example, and also changes to most of the other fields.
One thing that should definitely be interleaved are the files that get added, because often the messages refer to "the attached patch" and there might be several patches attached to the issue.
So IMHO it's better to avoid having too much noise between the messages and leave the detailed history collapsed at the bottom -- if someone needs something specific he can then go there and look.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue312>
_______________________________________________________

From stephen at xemacs.org  Thu Apr 21 19:12:14 2011
From: stephen at xemacs.org (Stephen J. Turnbull)
Date: Fri, 22 Apr 2011 02:12:14 +0900
Subject: [Tracker-discuss] [issue312] Add a 'go to the last message' link
In-Reply-To: <1303404374.18.0.855136972663.issue312@psf.upfronthosting.co.za>
References: <1263565390.97.0.608174776201.issue312@psf.upfronthosting.co.za>
	<1303404374.18.0.855136972663.issue312@psf.upfronthosting.co.za>
Message-ID: <87ipu7bkb5.fsf@uwakimon.sk.tsukuba.ac.jp>

R David Murray writes:

 > I disagree that the actions are "mostly useless",

Did somebody actually write that?  I didn't.

 > or even that the 'nosy' change information is noise.  While I don't
 > refer to the action list often, I do refer to it regularly to
 > answer some question about actions taken on the issue.  And I'd
 > guess that about half the time I do I'm checking to see when
 > someone got added as nosy and whether they did it themselves or if
 > someone else added them (and if so, I sometimes care about who did
 > the add).

I was incautious in my phrasing.  By "filter out" I meant to imply
"into a list at the bottom".  If you are checking explicitly, ISTM
it's more convenient to have a compact list at the bottom of the page
to check, rather than looking for the action interleaved with all the
messages.  But when interlined, most of the time "nosy += me" really
is just noise, and when you get 20 in a row, it's quite annoying.


From metatracker at psf.upfronthosting.co.za  Thu Apr 21 19:06:39 2011
From: metatracker at psf.upfronthosting.co.za (Stephen Turnbull)
Date: Thu, 21 Apr 2011 17:06:39 +0000
Subject: [Tracker-discuss] [issue312] Add a 'go to the last message' link
In-Reply-To: <1303404374.18.0.855136972663.issue312@psf.upfronthosting.co.za>
Message-ID: <87ipu7bkb5.fsf@uwakimon.sk.tsukuba.ac.jp>


Stephen Turnbull <stephen at xemacs.org> added the comment:

R David Murray writes:

 > I disagree that the actions are "mostly useless",

Did somebody actually write that?  I didn't.

 > or even that the 'nosy' change information is noise.  While I don't
 > refer to the action list often, I do refer to it regularly to
 > answer some question about actions taken on the issue.  And I'd
 > guess that about half the time I do I'm checking to see when
 > someone got added as nosy and whether they did it themselves or if
 > someone else added them (and if so, I sometimes care about who did
 > the add).

I was incautious in my phrasing.  By "filter out" I meant to imply
"into a list at the bottom".  If you are checking explicitly, ISTM
it's more convenient to have a compact list at the bottom of the page
to check, rather than looking for the action interleaved with all the
messages.  But when interlined, most of the time "nosy += me" really
is just noise, and when you get 20 in a row, it's quite annoying.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue312>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Apr 21 19:12:32 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Thu, 21 Apr 2011 17:12:32 +0000
Subject: [Tracker-discuss] [issue312] Add a 'go to the last message' link
In-Reply-To: <87liz3bmiq.fsf@uwakimon.sk.tsukuba.ac.jp>
Message-ID: <BANLkTi=yvbstAnDRN_JHSVjq9Xs2cbp2Kw@mail.gmail.com>


anatoly techtonik <techtonik at gmail.com> added the comment:

On Thu, Apr 21, 2011 at 7:18 PM, Stephen Turnbull
<metatracker at psf.upfronthosting.co.za> wrote:
>
> ?ric Araujo writes:
>
> ?> Oh please yes. ?Having the list of files separated makes sense, but having a list of messages and a list of actions does not IMO. ?I use other bug trackers with only one list and it?s in my experience much nicer to use.

What else besides Trac do you mean?

> At the very least, changes to nosy
> should not be interleaved with the messages.

If noisy change takes one line between messages, it won't hurt too
much even for 20 noizees.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue312>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Apr 21 19:14:57 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Thu, 21 Apr 2011 17:14:57 +0000
Subject: [Tracker-discuss] [issue312] Add a 'go to the last message' link
In-Reply-To: <1263565390.97.0.608174776201.issue312@psf.upfronthosting.co.za>
Message-ID: <1303406097.05.0.833460162373.issue312@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

If you're going to relocate the list of actions based on action type, please add `duplicate issue` actions beneath attached files.

(don't you find the title of this issue rather offtopic?)

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue312>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Apr 21 20:18:25 2011
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Thu, 21 Apr 2011 18:18:25 +0000
Subject: [Tracker-discuss] [issue373] Add 'module' field to tracker
In-Reply-To: <1296578034.58.0.494679196594.issue373@psf.upfronthosting.co.za>
Message-ID: <1303409905.24.0.815244409589.issue373@psf.upfronthosting.co.za>


R David Murray <rdmurray at bitdance.com> added the comment:

Please no two step process.  Also, I've never encountered a bug tracker-autosearch that worked worth a darn.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue373>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Apr 21 20:22:02 2011
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Thu, 21 Apr 2011 18:22:02 +0000
Subject: [Tracker-discuss] [issue312] Add a 'go to the last message' link
In-Reply-To: <1263565390.97.0.608174776201.issue312@psf.upfronthosting.co.za>
Message-ID: <1303410122.1.0.0541554933657.issue312@psf.upfronthosting.co.za>


R David Murray <rdmurray at bitdance.com> added the comment:

As long as the information is accessible, I don't really care where it is.  I thought you were advocating getting rid of the nosy update information altogether.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue312>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Apr 21 23:05:27 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Thu, 21 Apr 2011 21:05:27 +0000
Subject: [Tracker-discuss] [issue373] Add 'module' field to tracker
In-Reply-To: <1303404176.57.0.752141245417.issue373@psf.upfronthosting.co.za>
Message-ID: <BANLkTimvi68TpxUx4zWsABzETVi3Q9ZBYw@mail.gmail.com>


anatoly techtonik <techtonik at gmail.com> added the comment:

On Thu, Apr 21, 2011 at 7:42 PM, ?ric Araujo
<metatracker at psf.upfronthosting.co.za> wrote:
>
>>> Even if knowing the module(s) related to the issue is useful, there are a
>>> number of problems that should be considered:
>>> * there are hundreds of modules;
>> How many exactly? I doubt there is more than hundred.
> More than two hundreds.

How many exactly?

>>> * several modules can be related to the issue;
>> Make them tags.
> What are tags?

Issue labels. Like GMail labels or labels in Google Code tracker. In
Google Code you can label the same issue as documentation issue and as
module issue, for example.

>>> * the list of modules must be updated when modules are added/removed/renamed;
>> Store module mapping in repository and throw warning during build
>> stage when files added or removed.
> Or maybe use the mapping in lib2to3.fixes.fix_imports (not sure the Python used for our Roundup is recent enough.)

As a quick hack, yes. But lib2to3 is underdocumented and can break at
any moment. Ideally lib2to3 should fetch information from branches of
versions it tries to convert.

>>> * a new field adds clutter to the UI and more work for the submitters and triagers;
>> Split reporting in two steps like in Gnome or Eclipse Bugzillas.
> Interesting idea.

We may need to leave an option for RDM to go directly to the second
page as he finds that the Roundup search suxx (and I totally agree).
However, if search scope is limited by module, the results will still
be useful.

>>> * searching for a specific module won't include the issues if the field is not set
>>> correctly (i.e. old issues and issues that haven't be triaged), the normal search will;
>> All issues should undergo triaging process. Opened old issues can be
>> retriaged. Closed could be left RIP. If you want to find them - use
>> module name in normal search - it will still work.
>
> ?Should? is nice. ?How do you propose to implement it concretely? ?It could possible to add a special ?untriaged? state used in queries, but I?m not sure this would help; given enough volunteers with enough free time, bug triaging happens quite effectively. ?The weekly email also helps find unanswered reports.

In Google Code all issue have 'New' status by default. Triaged are
usually 'Accepted' or 'Acknowledged'. In Bugzilla new issues are
'unconfirmed'. In SCons we use 'untriaged' flag. Of course, triaging
is about priorities and without module maintainers, roadmaps and
release plans the process can be a bit pointless. So, if somebody
answers to b.p.o report, does that mean that the report is triaged?
What is the result of triage on b.p.o?

>>> Another option is looking automatically at the attached patches, figure out
>>> what files they affect, and make this information available.
> Sounds good. ?I?m sure difflib can do that.

Difflib can't parse patches - it produces diffs only, but you can
download python-patch from Google Code. SVN version has a nice
diffstat capability.

>> But mind you that issues without patches may never get any, because module
>> maintainers are unaware that there are issues for them.
>
> There are triagers who use the experts list (in the devguide) to add maintainers to nosy.

You still don't allow new people to opt-in to help with module
maintenance, testing or patching.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue373>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Apr 22 15:56:38 2011
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Fri, 22 Apr 2011 13:56:38 +0000
Subject: [Tracker-discuss] [issue373] Add 'module' field to tracker
In-Reply-To: <1296578034.58.0.494679196594.issue373@psf.upfronthosting.co.za>
Message-ID: <1303480598.63.0.810222761966.issue373@psf.upfronthosting.co.za>


R David Murray <rdmurray at bitdance.com> added the comment:

Actually I think roundup search works very well, except for the case sensitivity on username searches.  The UI could use some help, but personally I won't be satisified with it until I get around to writing a command line interface for it :)  But that is off topic.

In our tracker, an untriaged issue has stage 'no selection'.

We can already label an issue with multiple components.

Having a way for non-commiters to indicate to everyone (but especially triagers) that they are interested in helping with a given module would be a nice feature.  Someone has to figure out how to implement it though, and I think any movement on this issue is going to have to start with a concrete UI design.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue373>
_______________________________________________________

From stephen at xemacs.org  Fri Apr 22 17:11:39 2011
From: stephen at xemacs.org (Stephen J. Turnbull)
Date: Sat, 23 Apr 2011 00:11:39 +0900
Subject: [Tracker-discuss] [issue373] Add 'module' field to tracker
In-Reply-To: <1303480598.63.0.810222761966.issue373@psf.upfronthosting.co.za>
References: <1296578034.58.0.494679196594.issue373@psf.upfronthosting.co.za>
	<1303480598.63.0.810222761966.issue373@psf.upfronthosting.co.za>
Message-ID: <87ei4ub9sk.fsf@uwakimon.sk.tsukuba.ac.jp>

R David Murray writes:

 > Having a way for non-commiters to indicate to everyone

In XEmacs's Roundup we allow any user to assign themselves an
"assignable" Role (which is misnamed "Developer").  All this does is
add them to the list that pops up for "Assigned-To" (there is also an
assign-to-me option there which allows anybody to assign an issue to
themselves, whether they have the Developer Role or not).

This was trivial.  A couple lines to create the Role in schema.py, and
a couple lines in the issue template to filter in Reviewers and
Developers in the Assign-To menu.

 > (but especially triagers) that they are interested in helping with
 > a given module would be a nice feature.

Limiting a user's offer to a given module would be more effort to
implement, but shouldn't be too hard.  Probably the code would be very
similar to the auto-nosy that some maintainers have for modules they
maintain.



From metatracker at psf.upfronthosting.co.za  Fri Apr 22 17:06:05 2011
From: metatracker at psf.upfronthosting.co.za (Stephen Turnbull)
Date: Fri, 22 Apr 2011 15:06:05 +0000
Subject: [Tracker-discuss] [issue373] Add 'module' field to tracker
In-Reply-To: <1303480598.63.0.810222761966.issue373@psf.upfronthosting.co.za>
Message-ID: <87ei4ub9sk.fsf@uwakimon.sk.tsukuba.ac.jp>


Stephen Turnbull <stephen at xemacs.org> added the comment:

R David Murray writes:

 > Having a way for non-commiters to indicate to everyone

In XEmacs's Roundup we allow any user to assign themselves an
"assignable" Role (which is misnamed "Developer").  All this does is
add them to the list that pops up for "Assigned-To" (there is also an
assign-to-me option there which allows anybody to assign an issue to
themselves, whether they have the Developer Role or not).

This was trivial.  A couple lines to create the Role in schema.py, and
a couple lines in the issue template to filter in Reviewers and
Developers in the Assign-To menu.

 > (but especially triagers) that they are interested in helping with
 > a given module would be a nice feature.

Limiting a user's offer to a given module would be more effort to
implement, but shouldn't be too hard.  Probably the code would be very
similar to the auto-nosy that some maintainers have for modules they
maintain.

----------
nosy: +stephen

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue373>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Apr 22 18:29:49 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 22 Apr 2011 16:29:49 +0000
Subject: [Tracker-discuss] [issue312] Add a 'go to the last message' link
In-Reply-To: <1263565390.97.0.608174776201.issue312@psf.upfronthosting.co.za>
Message-ID: <1303489789.21.0.237511018372.issue312@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

[Stephen]
>> I disagree that the actions are "mostly useless",
> Did somebody actually write that?  I didn't.
It is I who wondered about it.

[Ezio]
> One thing that should definitely be interleaved are the files that get added,
> because often the messages refer to "the attached patch" and there might be
> several patches attached to the issue.
Exactly.  I?d be very happy if this was changed and the rest of the actions list left alone.

anatoly: debbugs and codingteam, for instance.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue312>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Apr 22 23:04:10 2011
From: metatracker at psf.upfronthosting.co.za (Philip Jenvey)
Date: Fri, 22 Apr 2011 21:04:10 +0000
Subject: [Tracker-discuss] [issue396] Grant jython-dev user dev access on
	bugs.jython.org
In-Reply-To: <1303506250.16.0.899227765775.issue396@psf.upfronthosting.co.za>
Message-ID: <1303506250.16.0.899227765775.issue396@psf.upfronthosting.co.za>


New submission from Philip Jenvey <pjenvey at underboss.org>:

I've created the jython-dev user on bugs.jython.org as our 'Roundup Robot', it will be the account that updates tickets from the mercurial repo post commit hook.

This account needs a higher access so it can close out tickets. Please grant it enough access to do this (as if it were a jython committer).

http://bugs.jython.org/user814

Thanks

----------
messages: 2037
nosy: pjenvey
priority: feature
status: unread
title: Grant jython-dev user dev access on bugs.jython.org

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue396>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Apr 26 15:40:28 2011
From: metatracker at psf.upfronthosting.co.za (Antoine Pitrou)
Date: Tue, 26 Apr 2011 13:40:28 +0000
Subject: [Tracker-discuss] [issue381] default mime-type for attachments
	should be text/plain
In-Reply-To: <1300916251.18.0.103274029072.issue381@psf.upfronthosting.co.za>
Message-ID: <1303825228.45.0.0201230581262.issue381@psf.upfronthosting.co.za>


Antoine Pitrou <pitrou at free.fr> added the comment:

There's a file there which seems to have fallen between the cracks:
http://bugs.python.org/file21782

----------
status: resolved -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue381>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Apr 26 22:23:53 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Tue, 26 Apr 2011 20:23:53 +0000
Subject: [Tracker-discuss] [issue381] default mime-type for attachments
	should be text/plain
In-Reply-To: <1300916251.18.0.103274029072.issue381@psf.upfronthosting.co.za>
Message-ID: <1303849433.03.0.319166258657.issue381@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

That file was deliberately not marked text/plain: it has funny control characters in it.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue381>
_______________________________________________________