From metatracker at psf.upfronthosting.co.za  Thu Jul  1 01:50:04 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Wed, 30 Jun 2010 23:50:04 +0000
Subject: [Tracker-discuss] [issue251] Allow searching,
	displaying message and nosy counts
In-Reply-To: <1237385124.95.0.505475087652.issue251@psf.upfronthosting.co.za>
Message-ID: <1277941804.64.0.0818653253403.issue251@psf.upfronthosting.co.za>


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

In order to remove unnecessary elements in the UI, I suggest to revert the addition of the nosy count in the issue page, next to the nosy list.
I don't think that knowing the exact number of users in the nosy has any utility.

----------
nosy: +ezio.melotti
status: resolved -> done-cbb

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

From metatracker at psf.upfronthosting.co.za  Thu Jul  1 02:42:48 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Thu, 01 Jul 2010 00:42:48 +0000
Subject: [Tracker-discuss] [issue343] Improve or remove "(list)" from the
	issue item page
In-Reply-To: <1277944968.57.0.434782350772.issue343@psf.upfronthosting.co.za>
Message-ID: <1277944968.57.0.434782350772.issue343@psf.upfronthosting.co.za>


New submission from Ezio Melotti <ezio.melotti at gmail.com>:

Currently there are 3 "(list)" links in the issue page, one for the superseder, one for the dependencies and the last for the nosy list.
The first two just show a list of all the issues, with no way to search for them, and other completely useless.
The third one might be useful but:
  1) it's difficult to use;
  2) the search searches only the Username and not Name and Surname;
  3) the search is case-sensitive;
  4) there's a "phone" field that's completely useless.

This means that if I know the name or surname of the user but these don't appear in the username or they appear with a different casing I won't be able to find them (luckily I can still find them if I know the phone number but not the name).

I suggest to remove the first two and possibly figure out a way to improve the third. A better search might be a good starting point, get rid of the ugly interface would be even better.

----------
assignedto: ezio.melotti
messages: 1707
nosy: amk, ezio.melotti, loewis
priority: wish
status: unread
title: Improve or remove "(list)" from the issue item page

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

From metatracker at psf.upfronthosting.co.za  Thu Jul  1 09:58:18 2010
From: metatracker at psf.upfronthosting.co.za (Philipp Gortan)
Date: Thu, 01 Jul 2010 07:58:18 +0000
Subject: [Tracker-discuss] [issue342] remove "phone" field for users
In-Reply-To: <1277934377.76.0.701119970252.issue342@psf.upfronthosting.co.za>
Message-ID: <1277971098.91.0.10032229501.issue342@psf.upfronthosting.co.za>


Philipp Gortan <mephinet at gmx.net> added the comment:

This might be true for a public tracker, but for in-house trackers in a larger software shop I think having the extension only a click away is a good thing...

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

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

From metatracker at psf.upfronthosting.co.za  Thu Jul  1 10:02:00 2010
From: metatracker at psf.upfronthosting.co.za (techtonik)
Date: Thu, 01 Jul 2010 08:02:00 +0000
Subject: [Tracker-discuss] [issue342] remove "phone" field for users
In-Reply-To: <1277934377.76.0.701119970252.issue342@psf.upfronthosting.co.za>
Message-ID: <1277971320.79.0.48990105255.issue342@psf.upfronthosting.co.za>


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

If it is not required then I won't bother. I'd propose to add a link to Google Talk web chat gadget or IRC applet.

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

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

From metatracker at psf.upfronthosting.co.za  Thu Jul  1 13:14:45 2010
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Thu, 01 Jul 2010 11:14:45 +0000
Subject: [Tracker-discuss] [issue342] remove "phone" field for users
In-Reply-To: <1277934377.76.0.701119970252.issue342@psf.upfronthosting.co.za>
Message-ID: <1277982885.66.0.480444948313.issue342@psf.upfronthosting.co.za>


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

mephinet: we're only talking about the Python tracker here.

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

From metatracker at psf.upfronthosting.co.za  Thu Jul  1 13:28:48 2010
From: metatracker at psf.upfronthosting.co.za (Philipp Gortan)
Date: Thu, 01 Jul 2010 11:28:48 +0000
Subject: [Tracker-discuss] [issue342] remove "phone" field for users
In-Reply-To: <1277934377.76.0.701119970252.issue342@psf.upfronthosting.co.za>
Message-ID: <1277983728.42.0.262728790736.issue342@psf.upfronthosting.co.za>


Philipp Gortan <mephinet at gmx.net> added the comment:

/me is sorry for the confusion!

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

From metatracker at psf.upfronthosting.co.za  Thu Jul  1 22:34:55 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Thu, 01 Jul 2010 20:34:55 +0000
Subject: [Tracker-discuss] [issue343] Improve or remove "(list)" from the
	issue item page
In-Reply-To: <1277944968.57.0.434782350772.issue343@psf.upfronthosting.co.za>
Message-ID: <1278016495.53.0.151499604528.issue343@psf.upfronthosting.co.za>


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

I removed the "(list)" for superseder and dependencies in r82425 (and r82426).

----------
status: unread -> in-progress

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

From metatracker at psf.upfronthosting.co.za  Thu Jul  1 22:35:39 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Thu, 01 Jul 2010 20:35:39 +0000
Subject: [Tracker-discuss] [issue251] Allow searching,
	displaying message and nosy counts
In-Reply-To: <1237385124.95.0.505475087652.issue251@psf.upfronthosting.co.za>
Message-ID: <1278016539.46.0.770446403438.issue251@psf.upfronthosting.co.za>


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

I removed the nosy count in r82427.

----------
status: done-cbb -> resolved

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

From metatracker at psf.upfronthosting.co.za  Thu Jul  1 22:48:57 2010
From: metatracker at psf.upfronthosting.co.za (techtonik)
Date: Thu, 01 Jul 2010 20:48:57 +0000
Subject: [Tracker-discuss] [issue343] Improve or remove "(list)" from the
	issue item page
In-Reply-To: <1277944968.57.0.434782350772.issue343@psf.upfronthosting.co.za>
Message-ID: <1278017337.79.0.599071373373.issue343@psf.upfronthosting.co.za>


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

Without tracker admin/superuser privileges these (list) fields were not visible at all, so it didn't worth the hassle. Removing issue lookup instead of fixing its search interface looks like a way to skip an annoying problem - not to fix it.

Good solution would be to provide unified search interface for lists and submit it upstream. If you don't like (list) annotations eating web page space - it is possible to invoke lookup when you just click the field.

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

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

From metatracker at psf.upfronthosting.co.za  Thu Jul  1 22:54:11 2010
From: metatracker at psf.upfronthosting.co.za (techtonik)
Date: Thu, 01 Jul 2010 20:54:11 +0000
Subject: [Tracker-discuss] [issue251] Allow searching,
	displaying message and nosy counts
In-Reply-To: <1237385124.95.0.505475087652.issue251@psf.upfronthosting.co.za>
Message-ID: <1278017651.51.0.0400451436035.issue251@psf.upfronthosting.co.za>


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

Nosy counts have utility. As we don't have any stars to mark interesting issues, the nosy count is the only indicator how important issue is to community.

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

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

From metatracker at psf.upfronthosting.co.za  Fri Jul  2 00:22:50 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Thu, 01 Jul 2010 22:22:50 +0000
Subject: [Tracker-discuss] [issue251] Allow searching,
	displaying message and nosy counts
In-Reply-To: <1237385124.95.0.505475087652.issue251@psf.upfronthosting.co.za>
Message-ID: <1278022969.96.0.642051550711.issue251@psf.upfronthosting.co.za>


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

I just removed the count from the user interface in the issue item page.

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

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

From metatracker at psf.upfronthosting.co.za  Fri Jul  2 00:57:30 2010
From: metatracker at psf.upfronthosting.co.za (techtonik)
Date: Thu, 01 Jul 2010 22:57:30 +0000
Subject: [Tracker-discuss] [issue251] Allow searching,
	displaying message and nosy counts
In-Reply-To: <1237385124.95.0.505475087652.issue251@psf.upfronthosting.co.za>
Message-ID: <1278025050.73.0.2348021228.issue251@psf.upfronthosting.co.za>


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

-0.5 on this

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

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

From metatracker at psf.upfronthosting.co.za  Fri Jul  2 00:59:05 2010
From: metatracker at psf.upfronthosting.co.za (techtonik)
Date: Thu, 01 Jul 2010 22:59:05 +0000
Subject: [Tracker-discuss] [issue251] Allow searching,
	displaying message and nosy counts
In-Reply-To: <1237385124.95.0.505475087652.issue251@psf.upfronthosting.co.za>
Message-ID: <1278025145.02.0.248469011123.issue251@psf.upfronthosting.co.za>


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

closing as you're +1 on this and I do not have any desire or time to revert

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

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

From metatracker at psf.upfronthosting.co.za  Sun Jul  4 04:26:24 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sun, 04 Jul 2010 02:26:24 +0000
Subject: [Tracker-discuss] [issue254] Roundup treats <URL> badly
In-Reply-To: <1238038227.04.0.719265951876.issue254@psf.upfronthosting.co.za>
Message-ID: <1278210384.92.0.211878470733.issue254@psf.upfronthosting.co.za>


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

I fixed the ')' in r82525, using some heuristic to determine if the ')' is part of the URL or not (if you want to try breaking it you are welcome).
Regarding the '>' I think it might depend on the version of Roundup used for this tracker and the Jython one. Is it the same version that we use for python-dev?
In recent versions of Roundup the regex for matching URLs has been improved.

----------
nosy: +amk

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

From techtonik at gmail.com  Sun Jul  4 08:09:02 2010
From: techtonik at gmail.com (anatoly techtonik)
Date: Sun, 4 Jul 2010 09:09:02 +0300
Subject: [Tracker-discuss] Fwd: [issue9106] remove numbers from 3-.. level
	entries in docs toc
In-Reply-To: <1278208021.31.0.576528515018.issue9106@psf.upfronthosting.co.za>
References: <1277749704.58.0.992065909356.issue9106@psf.upfronthosting.co.za>
	<1278208021.31.0.576528515018.issue9106@psf.upfronthosting.co.za>
Message-ID: <AANLkTikqLbYstViJeE0NrZz9V88yDyEyrIo0YRmR6bPk@mail.gmail.com>

Need "invalid tracker" category.
-- 
anatoly t.




---------- Forwarded message ----------
From: Terry J. Reedy <report at bugs.python.org>
Date: Sun, Jul 4, 2010 at 4:47 AM
Subject: [issue9106] remove numbers from 3-.. level entries in docs toc
To: techtonik at gmail.com



Terry J. Reedy <tjreedy at udel.edu> added the comment:

'Invalid' because invalid for this tracker and moved to sphinx tracker
(there is no option for 'wrong tracker').

On Windows help-format docs, there are no numbers on the left. There
are in the chapter TOC in the chapter pages. I would have to see an
alternative before I would say yes to changing that.

I do wish the page/section for each module had a section toc with
links so I could see what subsections there are and jump without
scrolling. I gather that would be a sphinx tracker issue too.

----------
nosy: +tjreedy
resolution: ?-> invalid

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue9106>
_______________________________________

From metatracker at psf.upfronthosting.co.za  Sun Jul  4 08:29:13 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sun, 04 Jul 2010 06:29:13 +0000
Subject: [Tracker-discuss] [issue284] Better summary reports
In-Reply-To: <1241911709.97.0.816502801538.issue284@psf.upfronthosting.co.za>
Message-ID: <1278224953.02.0.309864034395.issue284@psf.upfronthosting.co.za>


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

I started working on this issue and tried to further improve roundup-summary.
It seems to me that the code could be simplified quite a lot if we removed the HTML reporting (o anyway part of it, since IMHO there are quite a lot of "YAGNI" features). Given that we don't use it and it's anyway quite ugly, can I remove it?

----------
assignedto:  -> ezio.melotti
nosy: +amk, ezio.melotti, loewis
status: unread -> chatting

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

From techtonik at gmail.com  Sun Jul  4 08:40:22 2010
From: techtonik at gmail.com (anatoly techtonik)
Date: Sun, 4 Jul 2010 09:40:22 +0300
Subject: [Tracker-discuss] [issue284] Better summary reports
In-Reply-To: <1278224953.02.0.309864034395.issue284@psf.upfronthosting.co.za>
References: <1241911709.97.0.816502801538.issue284@psf.upfronthosting.co.za>
	<1278224953.02.0.309864034395.issue284@psf.upfronthosting.co.za>
Message-ID: <AANLkTimkpvIwEI9q8u4BmZPBO_gxMbaN0lkqGLPTYAuL@mail.gmail.com>

I don't use it, but properly formatted HTML notifications are looking
better (i.e. Google Calendar). You can use proportional fonts and
tables to align elements and insert short action links instead of full
URLs.
-- 
anatoly t.



On Sun, Jul 4, 2010 at 9:29 AM, Ezio Melotti
<metatracker at psf.upfronthosting.co.za> wrote:
>
> Ezio Melotti <ezio.melotti at gmail.com> added the comment:
>
> I started working on this issue and tried to further improve roundup-summary.
> It seems to me that the code could be simplified quite a lot if we removed the HTML reporting (o anyway part of it, since IMHO there are quite a lot of "YAGNI" features). Given that we don't use it and it's anyway quite ugly, can I remove it?
>
> ----------
> assignedto: ?-> ezio.melotti
> nosy: +amk, ezio.melotti, loewis
> status: unread -> chatting
>
> _______________________________________________________
> PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
> <http://psf.upfronthosting.co.za/roundup/meta/issue284>
> _______________________________________________________
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>

From metatracker at psf.upfronthosting.co.za  Sun Jul  4 08:40:24 2010
From: metatracker at psf.upfronthosting.co.za (techtonik)
Date: Sun, 04 Jul 2010 06:40:24 +0000
Subject: [Tracker-discuss] [issue284] Better summary reports
In-Reply-To: <1278224953.02.0.309864034395.issue284@psf.upfronthosting.co.za>
Message-ID: <AANLkTimkpvIwEI9q8u4BmZPBO_gxMbaN0lkqGLPTYAuL@mail.gmail.com>


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

I don't use it, but properly formatted HTML notifications are looking
better (i.e. Google Calendar). You can use proportional fonts and
tables to align elements and insert short action links instead of full
URLs.
-- 
anatoly t.

On Sun, Jul 4, 2010 at 9:29 AM, Ezio Melotti
<metatracker at psf.upfronthosting.co.za> wrote:
>
> Ezio Melotti <ezio.melotti at gmail.com> added the comment:
>
> I started working on this issue and tried to further improve roundup-summary.
> It seems to me that the code could be simplified quite a lot if we removed the HTML reporting (o anyway part of it, since IMHO there are quite a lot of "YAGNI" features). Given that we don't use it and it's anyway quite ugly, can I remove it?
>
> ----------
> assignedto: ?-> ezio.melotti
> nosy: +amk, ezio.melotti, loewis
> status: unread -> chatting
>
> _______________________________________________________
> PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
> <http://psf.upfronthosting.co.za/roundup/meta/issue284>
> _______________________________________________________
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>

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

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

From metatracker at psf.upfronthosting.co.za  Sun Jul  4 08:59:57 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sun, 04 Jul 2010 06:59:57 +0000
Subject: [Tracker-discuss] [issue284] Better summary reports
In-Reply-To: <1241911709.97.0.816502801538.issue284@psf.upfronthosting.co.za>
Message-ID: <1278226797.68.0.778503659525.issue284@psf.upfronthosting.co.za>


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

AFAIK this script is only used to send the weekly reports to python-dev, and these have always been in plain text. Since I don't see any reason to switch to HTML and I think that most of the python-dev users prefer plain text anyway, I suggest to remove it to make the script easier to understand and more maintainable.

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

From georg at python.org  Sun Jul  4 09:05:40 2010
From: georg at python.org (Georg Brandl)
Date: Sun, 04 Jul 2010 09:05:40 +0200
Subject: [Tracker-discuss] Fwd: [issue9106] remove numbers from 3-..
 level entries in docs toc
In-Reply-To: <AANLkTikqLbYstViJeE0NrZz9V88yDyEyrIo0YRmR6bPk@mail.gmail.com>
References: <1277749704.58.0.992065909356.issue9106@psf.upfronthosting.co.za>	<1278208021.31.0.576528515018.issue9106@psf.upfronthosting.co.za>
	<AANLkTikqLbYstViJeE0NrZz9V88yDyEyrIo0YRmR6bPk@mail.gmail.com>
Message-ID: <4C3032C4.9090501@python.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 04.07.2010 08:09, schrieb anatoly techtonik:
> Need "invalid tracker" category.

I think "invalid" covers this well enough.

Georg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)

iEYEARECAAYFAkwwMsEACgkQN9GcIYhpnLC9XQCfc099NYpZQaBqokdbNlSz+p2n
HHYAn2txl7Es4IQW2ZRoCR0rq89RwK8x
=vGxe
-----END PGP SIGNATURE-----

From metatracker at psf.upfronthosting.co.za  Sun Jul  4 20:46:18 2010
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Sun, 04 Jul 2010 18:46:18 +0000
Subject: [Tracker-discuss] [issue284] Better summary reports
In-Reply-To: <1241911709.97.0.816502801538.issue284@psf.upfronthosting.co.za>
Message-ID: <1278269178.65.0.753630633347.issue284@psf.upfronthosting.co.za>


Brett C. <brett at python.org> added the comment:

Python-dev would hate to get HTML emails, so that it is not a possibility.

----------
nosy: +brett.cannon

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

From metatracker at psf.upfronthosting.co.za  Sun Jul  4 21:01:20 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sun, 04 Jul 2010 19:01:20 +0000
Subject: [Tracker-discuss] [issue284] Better summary reports
In-Reply-To: <1241911709.97.0.816502801538.issue284@psf.upfronthosting.co.za>
Message-ID: <1278270080.75.0.101413642507.issue284@psf.upfronthosting.co.za>


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

That's what I thought. It might still be useful to have HTML reports on some page on the site, but I don't know if anyone cares about having it and/or doing it.
Anyway I think I can preserver the HTML output after some refactoring.

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

From metatracker at psf.upfronthosting.co.za  Sun Jul  4 22:22:57 2010
From: metatracker at psf.upfronthosting.co.za (techtonik)
Date: Sun, 04 Jul 2010 20:22:57 +0000
Subject: [Tracker-discuss] [issue284] Better summary reports
In-Reply-To: <1241911709.97.0.816502801538.issue284@psf.upfronthosting.co.za>
Message-ID: <1278274977.67.0.499604177823.issue284@psf.upfronthosting.co.za>


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

If the script can be reused l8r for running personal notifications - that would be awesome.

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

From techtonik at gmail.com  Sun Jul  4 22:38:10 2010
From: techtonik at gmail.com (anatoly techtonik)
Date: Sun, 4 Jul 2010 23:38:10 +0300
Subject: [Tracker-discuss] Preserve search line
Message-ID: <AANLkTimNJPiPZluU2q9nkPjprE_TVVdqwziZ-qCl_fEW@mail.gmail.com>

Eric, as you are seem to be deep in Roundup code for the moment - can
you please fix the search box to preserve query when results page is
loaded. Somebody already changed default behavior of search box to
return both open and closed issues, so this must be somewhere near.

Thank you.
-- 
anatoly t.

From ezio.melotti at gmail.com  Mon Jul  5 04:37:29 2010
From: ezio.melotti at gmail.com (Ezio Melotti)
Date: Mon, 05 Jul 2010 05:37:29 +0300
Subject: [Tracker-discuss] Preserve search line
In-Reply-To: <AANLkTimNJPiPZluU2q9nkPjprE_TVVdqwziZ-qCl_fEW@mail.gmail.com>
References: <AANLkTimNJPiPZluU2q9nkPjprE_TVVdqwziZ-qCl_fEW@mail.gmail.com>
Message-ID: <4C314569.8000303@gmail.com>

On 04/07/2010 23.38, anatoly techtonik wrote:
> Eric, as you are seem to be deep in Roundup code for the moment - can
> you please fix the search box to preserve query when results page is
> loaded. Somebody already changed default behavior of search box to
> return both open and closed issues, so this must be somewhere near.
>
> Thank you.
>    
Fixed in r82568.

From techtonik at gmail.com  Mon Jul  5 08:41:01 2010
From: techtonik at gmail.com (anatoly techtonik)
Date: Mon, 5 Jul 2010 09:41:01 +0300
Subject: [Tracker-discuss] Preserve search line
In-Reply-To: <4C314569.8000303@gmail.com>
References: <AANLkTimNJPiPZluU2q9nkPjprE_TVVdqwziZ-qCl_fEW@mail.gmail.com>
	<4C314569.8000303@gmail.com>
Message-ID: <AANLkTilhdBDWKvUzeGAA3HSgHaH6ICY1oHbtktxzcOfv@mail.gmail.com>

On Mon, Jul 5, 2010 at 5:37 AM, Ezio Melotti <ezio.melotti at gmail.com> wrote:
>>
>> Eric, as you are seem to be deep in Roundup code for the moment - can
>> you please fix the search box to preserve query when results page is
>> loaded. Somebody already changed default behavior of search box to
>> return both open and closed issues, so this must be somewhere near.
>>
>> Thank you.
>>
>
> Fixed in r82568.

Thanks Ezio. Seems like I was constantly confusing you with Eric due
to a minor difference of your names in pixels. Now I know who is who.

By the way, when changes are usually propagated to servers?
How to see which revision tracker is running on?

-- 
anatoly t.

From techtonik at gmail.com  Tue Jul  6 08:57:01 2010
From: techtonik at gmail.com (anatoly techtonik)
Date: Tue, 6 Jul 2010 09:57:01 +0300
Subject: [Tracker-discuss] Fwd: [issue9106] remove numbers from 3-..
	level entries in docs toc
In-Reply-To: <4C3032C4.9090501@python.org>
References: <1277749704.58.0.992065909356.issue9106@psf.upfronthosting.co.za>
	<1278208021.31.0.576528515018.issue9106@psf.upfronthosting.co.za>
	<AANLkTikqLbYstViJeE0NrZz9V88yDyEyrIo0YRmR6bPk@mail.gmail.com>
	<4C3032C4.9090501@python.org>
Message-ID: <AANLkTinzFVvOF77RJvx_bKy40_4sH2hklEhgehXON8w1@mail.gmail.com>

With query "Documentation" + "Invalid Tracker" I could find all Sphinx
issues d.p.o is dependent on. Such issues are valid for d.p.o as user
stories. They are just not impossible to fix here.
-- 
anatoly t.



On Sun, Jul 4, 2010 at 10:05 AM, Georg Brandl <georg at python.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Am 04.07.2010 08:09, schrieb anatoly techtonik:
>> Need "invalid tracker" category.
>
> I think "invalid" covers this well enough.
>
> Georg
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.15 (GNU/Linux)
>
> iEYEARECAAYFAkwwMsEACgkQN9GcIYhpnLC9XQCfc099NYpZQaBqokdbNlSz+p2n
> HHYAn2txl7Es4IQW2ZRoCR0rq89RwK8x
> =vGxe
> -----END PGP SIGNATURE-----
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>

From breamoreboy at yahoo.co.uk  Tue Jul  6 17:06:22 2010
From: breamoreboy at yahoo.co.uk (Mark Lawrence)
Date: Tue, 6 Jul 2010 08:06:22 -0700 (PDT)
Subject: [Tracker-discuss] reassigning issues from georg.brandl to
	docs@python
Message-ID: <495997.18712.qm@web23306.mail.ird.yahoo.com>

Hi all,

In a private email R. David Murray pointed out to me that any documentation issues can be reassigned from Georg to docs at python.  I've run a search and found 133 of these.  Is there a way to automatically reassign these, or could someone write a bit of code to do this?  Failing that, I'll take on the grunt bit and manually reassign them myself.

Kindest regards.

Mark Lawrence.



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20100706/ed040aca/attachment.html>

From brett at python.org  Tue Jul  6 22:34:11 2010
From: brett at python.org (Brett Cannon)
Date: Tue, 6 Jul 2010 13:34:11 -0700
Subject: [Tracker-discuss] reassigning issues from georg.brandl to
	docs@python
In-Reply-To: <495997.18712.qm@web23306.mail.ird.yahoo.com>
References: <495997.18712.qm@web23306.mail.ird.yahoo.com>
Message-ID: <AANLkTikPafGDTxZgeXM_TwMkrwNrNPFRtEgAAMZ-8_Ov@mail.gmail.com>

On Tue, Jul 6, 2010 at 08:06, Mark Lawrence <breamoreboy at yahoo.co.uk> wrote:
> Hi all,
>
> In a private email R. David Murray pointed out to me that any documentation
> issues can be reassigned from Georg to docs at python.? I've run a search and
> found 133 of these.? Is there a way to automatically reassign these, or
> could someone write a bit of code to do this?

Georg asked to have them automatically assigned to him, so unassigning
blindly would not be good.

>? Failing that, I'll take on
> the grunt bit and manually reassign them myself.

Just make sure that they should be re-assigned, but otherwise have at it!

From breamoreboy at yahoo.co.uk  Tue Jul  6 23:22:00 2010
From: breamoreboy at yahoo.co.uk (Mark Lawrence)
Date: Tue, 6 Jul 2010 21:22:00 +0000 (GMT)
Subject: [Tracker-discuss] reassigning issues from georg.brandl to
	docs@python
In-Reply-To: <AANLkTikPafGDTxZgeXM_TwMkrwNrNPFRtEgAAMZ-8_Ov@mail.gmail.com>
References: <495997.18712.qm@web23306.mail.ird.yahoo.com>
	<AANLkTikPafGDTxZgeXM_TwMkrwNrNPFRtEgAAMZ-8_Ov@mail.gmail.com>
Message-ID: <37516.63342.qm@web23301.mail.ird.yahoo.com>

Brett,

thanks for your response.

To quote from David's original email to me.

"
3) Up until recently, georg.brandl was auto-assigned all doc bugs.
Now the auto-assign is to docs at python, which is a mailing list for all
people interested in working on the Python docs.  So if you come across
a 
doc bug that is still set to georg, you can change it to docs at python.
"


Are you and David talking at cross purposes?  If yes how do we go forward?  If no the query in my email stands.

Kindest regards.

Mark




________________________________
From: Brett Cannon <brett at python.org>
To: Mark Lawrence <breamoreboy at yahoo.co.uk>
Cc: tracker-discuss at python.org
Sent: Tue, 6 July, 2010 21:34:11
Subject: Re: [Tracker-discuss] reassigning issues from georg.brandl to  docs at python

On Tue, Jul 6, 2010 at 08:06, Mark Lawrence <breamoreboy at yahoo.co.uk> wrote:
> Hi all,
>
> In a private email R. David Murray pointed out to me that any documentation
> issues can be reassigned from Georg to docs at python.  I've run a search and
> found 133 of these.  Is there a way to automatically reassign these, or
> could someone write a bit of code to do this?

Georg asked to have them automatically assigned to him, so unassigning
blindly would not be good.

>  Failing that, I'll take on
> the grunt bit and manually reassign them myself.

Just make sure that they should be re-assigned, but otherwise have at it!



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20100706/dea98bc9/attachment.html>

From brett at python.org  Tue Jul  6 23:24:43 2010
From: brett at python.org (Brett Cannon)
Date: Tue, 6 Jul 2010 14:24:43 -0700
Subject: [Tracker-discuss] reassigning issues from georg.brandl to
	docs@python
In-Reply-To: <37516.63342.qm@web23301.mail.ird.yahoo.com>
References: <495997.18712.qm@web23306.mail.ird.yahoo.com>
	<AANLkTikPafGDTxZgeXM_TwMkrwNrNPFRtEgAAMZ-8_Ov@mail.gmail.com> 
	<37516.63342.qm@web23301.mail.ird.yahoo.com>
Message-ID: <AANLkTikQ58LxPyyHiYL1oNmz15hiytbQuJ3Q2oQMcLF4@mail.gmail.com>

On Tue, Jul 6, 2010 at 14:22, Mark Lawrence <breamoreboy at yahoo.co.uk> wrote:
> Brett,
>
> thanks for your response.
>
> To quote from David's original email to me.
>
> "
> 3) Up until recently, georg.brandl was auto-assigned all doc bugs.
> Now the auto-assign is to docs at python, which is a mailing list for all
> people interested in working on the Python docs.? So if you come across
> a doc bug that is still set to georg, you can change it to docs at python.
> "
>
> Are you and David talking at cross purposes?? If yes how do we go forward?
> If no the query in my email stands.

David's right. As for doing it automatically, there might be some SQL
query that could be run to do the re-assignment, but I'm not sure.

-Brett

>
> Kindest regards.
>
> Mark
>
> ________________________________
> From: Brett Cannon <brett at python.org>
> To: Mark Lawrence <breamoreboy at yahoo.co.uk>
> Cc: tracker-discuss at python.org
> Sent: Tue, 6 July, 2010 21:34:11
> Subject: Re: [Tracker-discuss] reassigning issues from georg.brandl to
> docs at python
>
> On Tue, Jul 6, 2010 at 08:06, Mark Lawrence <breamoreboy at yahoo.co.uk> wrote:
>> Hi all,
>>
>> In a private email R. David Murray pointed out to me that any
>> documentation
>> issues can be reassigned from Georg to docs at python.? I've run a search and
>> found 133 of these.? Is there a way to automatically reassign these, or
>> could someone write a bit of code to do this?
>
> Georg asked to have them automatically assigned to him, so unassigning
> blindly would not be good.
>
>>? Failing that, I'll take on
>> the grunt bit and manually reassign them myself.
>
> Just make sure that they should be re-assigned, but otherwise have at it!
>
>

From martin at v.loewis.de  Tue Jul  6 23:54:10 2010
From: martin at v.loewis.de (=?UTF-8?B?Ik1hcnRpbiB2LiBMw7Z3aXMi?=)
Date: Tue, 06 Jul 2010 23:54:10 +0200
Subject: [Tracker-discuss] reassigning issues from georg.brandl
	to	docs@python
In-Reply-To: <AANLkTikQ58LxPyyHiYL1oNmz15hiytbQuJ3Q2oQMcLF4@mail.gmail.com>
References: <495997.18712.qm@web23306.mail.ird.yahoo.com>	<AANLkTikPafGDTxZgeXM_TwMkrwNrNPFRtEgAAMZ-8_Ov@mail.gmail.com>
	<37516.63342.qm@web23301.mail.ird.yahoo.com>
	<AANLkTikQ58LxPyyHiYL1oNmz15hiytbQuJ3Q2oQMcLF4@mail.gmail.com>
Message-ID: <4C33A602.8090000@v.loewis.de>

>> Are you and David talking at cross purposes?  If yes how do we go forward?
>> If no the query in my email stands.
> 
> David's right. As for doing it automatically, there might be some SQL
> query that could be run to do the re-assignment, but I'm not sure.

It's certainly possible to do this automatically. If this is desired,
somebody in charge please submit a request to the meta tracker.

I'd rather use roundup API instead of SQL as this will journal changes.

Regards,
Martin

From georg at python.org  Wed Jul  7 00:48:03 2010
From: georg at python.org (Georg Brandl)
Date: Wed, 07 Jul 2010 00:48:03 +0200
Subject: [Tracker-discuss] reassigning issues from
	georg.brandl	to	docs@python
In-Reply-To: <4C33A602.8090000@v.loewis.de>
References: <495997.18712.qm@web23306.mail.ird.yahoo.com>	<AANLkTikPafGDTxZgeXM_TwMkrwNrNPFRtEgAAMZ-8_Ov@mail.gmail.com>	<37516.63342.qm@web23301.mail.ird.yahoo.com>	<AANLkTikQ58LxPyyHiYL1oNmz15hiytbQuJ3Q2oQMcLF4@mail.gmail.com>
	<4C33A602.8090000@v.loewis.de>
Message-ID: <4C33B2A3.1020804@python.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 06.07.2010 23:54, schrieb "Martin v. L?wis":
>>> Are you and David talking at cross purposes?  If yes how do we go forward?
>>> If no the query in my email stands.
>> 
>> David's right. As for doing it automatically, there might be some SQL
>> query that could be run to do the re-assignment, but I'm not sure.
> 
> It's certainly possible to do this automatically. If this is desired,
> somebody in charge please submit a request to the meta tracker.
> 
> I'd rather use roundup API instead of SQL as this will journal changes.

I wouldn't mind this change, however please make sure that only Documentation
category issues are transferred.

cheers,
Georg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)

iEYEARECAAYFAkwzsqMACgkQN9GcIYhpnLAbugCcDNtpJiaEvcNdgRyC150guQV6
hpMAoKH8cjrh76JSh32Y2eehnQzbULeO
=gYE7
-----END PGP SIGNATURE-----

From metatracker at psf.upfronthosting.co.za  Wed Jul  7 09:36:35 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Wed, 07 Jul 2010 07:36:35 +0000
Subject: [Tracker-discuss] [issue266] Buttons to add/remove self from nosy
	list, assign issue to self
In-Reply-To: <1239149532.95.0.77008083815.issue266@psf.upfronthosting.co.za>
Message-ID: <1278488195.81.0.549821303816.issue266@psf.upfronthosting.co.za>


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

I did some minor tweaking in r82362 and r82412. This can be closed now.

----------
status: in-progress -> resolved

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

From metatracker at psf.upfronthosting.co.za  Sat Jul 10 01:38:12 2010
From: metatracker at psf.upfronthosting.co.za (Daniel Stutzbach)
Date: Fri, 09 Jul 2010 23:38:12 +0000
Subject: [Tracker-discuss] [issue344] "Message has been classified as spam"
In-Reply-To: <1278718692.94.0.69626475263.issue344@psf.upfronthosting.co.za>
Message-ID: <1278718692.94.0.69626475263.issue344@psf.upfronthosting.co.za>


New submission from Daniel Stutzbach <daniel at stutzbachenterprises.com>:

I'm not sure if this is the correct place to report this or not.  If not, I'd appreciate it a pointer to a more appropriate place.

One of my messages on bugs.python.org has been incorrectly marked as spam.

http://bugs.python.org/issue9141#msg109265

Could I please get it unmarked as spam?  Also, I do not see why the classifier would decide that the message looks like spam.  It might be worth looking in to.

Is there a way to check if any of my other messages have been marked as spam?  Since I have a confirmed email address with the tracker, it'd be nice to get a notification when this happens.

----------
messages: 1727
nosy: stutzbach
priority: bug
status: unread
title: "Message has been classified as spam"

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

From metatracker at psf.upfronthosting.co.za  Sat Jul 10 06:24:26 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sat, 10 Jul 2010 04:24:26 +0000
Subject: [Tracker-discuss] [issue344] "Message has been classified as spam"
In-Reply-To: <1278718692.94.0.69626475263.issue344@psf.upfronthosting.co.za>
Message-ID: <4C37F5F3.5060508@v.loewis.de>


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

> Could I please get it unmarked as spam?

Mark Dickinson has done that.

> Also, I do not see why the classifier would decide that the message looks like spam.  
> It might be worth looking in to.

It sometimes misclassifies short messages, primarily because there is so
little spam in the tracker. Your specific messages was classified as
follows:

Word  	Probability  	Times in ham  	Times in spam
*H* 	0.04 	- 	-
*S* 	0.74 	- 	-
contrast 	0.16 	2 	0
skip:c 10 	0.39 	179 	6
authorage:18 	0.62 	20 	1
with 	0.66 	82 	7
skip:p 10 	0.66 	12 	1
you 	0.66 	90 	8
can 	0.68 	43 	4
object 	0.72 	9 	1
calling 	0.77 	7 	1
skip:u 20 	0.83 	10 	2
your 	0.91 	22 	10

> Is there a way to check if any of my other messages have been marked as spam? 

I have checked; there were none.

> Since I have a confirmed email address with the tracker, it'd be nice to get a notification when this happens.

That would be difficult to implement.

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

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

From martin at v.loewis.de  Sat Jul 10 06:24:19 2010
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Sat, 10 Jul 2010 06:24:19 +0200
Subject: [Tracker-discuss] [issue344] "Message has been classified as
 spam"
In-Reply-To: <1278718692.94.0.69626475263.issue344@psf.upfronthosting.co.za>
References: <1278718692.94.0.69626475263.issue344@psf.upfronthosting.co.za>
Message-ID: <4C37F5F3.5060508@v.loewis.de>

> Could I please get it unmarked as spam?

Mark Dickinson has done that.

> Also, I do not see why the classifier would decide that the message looks like spam.  
> It might be worth looking in to.

It sometimes misclassifies short messages, primarily because there is so
little spam in the tracker. Your specific messages was classified as
follows:

Word  	Probability  	Times in ham  	Times in spam
*H* 	0.04 	- 	-
*S* 	0.74 	- 	-
contrast 	0.16 	2 	0
skip:c 10 	0.39 	179 	6
authorage:18 	0.62 	20 	1
with 	0.66 	82 	7
skip:p 10 	0.66 	12 	1
you 	0.66 	90 	8
can 	0.68 	43 	4
object 	0.72 	9 	1
calling 	0.77 	7 	1
skip:u 20 	0.83 	10 	2
your 	0.91 	22 	10

> Is there a way to check if any of my other messages have been marked as spam? 

I have checked; there were none.

> Since I have a confirmed email address with the tracker, it'd be nice to get a notification when this happens.

That would be difficult to implement.

From metatracker at psf.upfronthosting.co.za  Mon Jul 12 22:38:47 2010
From: metatracker at psf.upfronthosting.co.za (rocky)
Date: Mon, 12 Jul 2010 20:38:47 +0000
Subject: [Tracker-discuss] [issue345] sys.call_tracing isn't mentioned in
	online python docs
In-Reply-To: <1278967127.64.0.647000006367.issue345@psf.upfronthosting.co.za>
Message-ID: <1278967127.64.0.647000006367.issue345@psf.upfronthosting.co.za>


New submission from rocky <rocky at gnu.org>:

sys.call_tracing doesn't appear in Python documents and I think it should. For a start, one could use the docstring from sysmodule.c: 

  call_tracing(func, args) -> object

  Call func(*args), while tracing is enabled.  The tracing state is saved, and restored afterwards.  This is intended to be called from a
debugger from a checkpoint, to recursively debug some other code.

Thanks.

----------
messages: 1729
nosy: rocky
priority: feature
status: unread
title: sys.call_tracing isn't mentioned in online python docs

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

From metatracker at psf.upfronthosting.co.za  Mon Jul 12 23:20:25 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Mon, 12 Jul 2010 21:20:25 +0000
Subject: [Tracker-discuss] [issue345] sys.call_tracing isn't mentioned in
	online python docs
In-Reply-To: <1278967127.64.0.647000006367.issue345@psf.upfronthosting.co.za>
Message-ID: <1278969625.8.0.389341065271.issue345@psf.upfronthosting.co.za>


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

I think you want to report that to bugs.python.org
This tracker is for bugs of the bug tracker itself (hence ?meta-tracker?).
Thank you.

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

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

From metatracker at psf.upfronthosting.co.za  Mon Jul 12 23:27:28 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Mon, 12 Jul 2010 21:27:28 +0000
Subject: [Tracker-discuss] [issue253] Remove outdated keywords
In-Reply-To: <1237513464.32.0.072891570662.issue253@psf.upfronthosting.co.za>
Message-ID: <1278970048.78.0.286386260068.issue253@psf.upfronthosting.co.za>


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

?after moratorium? will most probably go. ?gsoc? has been asked for by Tarek, to tag issues to be done during a GSoC (one in progress, or ideas for a future one).

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

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

From metatracker at psf.upfronthosting.co.za  Mon Jul 12 23:31:18 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Mon, 12 Jul 2010 21:31:18 +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: <1278970278.38.0.751793476915.issue312@psf.upfronthosting.co.za>


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

Feedback on Antoine?s comments:
- On bugs with long discussion, jumping to the end is not enough to get the last bug.
- Would that be JavaScript folding? How would it work for people without JavaScript?
- Agreed on clutter. I personally prefer bug trackers that have only one merged list of messages and actions, preferably with just one line for an action (unlike Trac e.g.)

----------
nosy: +merwok

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

From metatracker at psf.upfronthosting.co.za  Mon Jul 12 23:39:25 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Mon, 12 Jul 2010 21:39:25 +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: <1278970765.23.0.91658485748.issue312@psf.upfronthosting.co.za>


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

I was unclear. In my first point, I meant ?bugs with a long discussion and thus a long actions list?. In the third point, I meant to say that with such a merged list, jumping to the end (with the End key) is always be the best way to go to the last message, except in very rare cases where a message would be followed by a screenful of actions.

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

From metatracker at psf.upfronthosting.co.za  Tue Jul 13 06:50:00 2010
From: metatracker at psf.upfronthosting.co.za (Oti)
Date: Tue, 13 Jul 2010 04:50:00 +0000
Subject: [Tracker-discuss] [issue346] request for permission to edit
	versions in jython bugs
In-Reply-To: <1278996600.65.0.349505701628.issue346@psf.upfronthosting.co.za>
Message-ID: <1278996600.65.0.349505701628.issue346@psf.upfronthosting.co.za>


New submission from Oti <ohumbel at gmail.com>:

Hi,

i am Oti from the Jython developers, and recently built and published the new 2.5.2b1 release.
Now i'd like to be able to add the new version to http://bugs.jython.org/version.
Is it possible to give me the necessary permissions?
My user name is otmarhumbel both here and in jython bugs.

Thanks a lot!
Oti.

----------
messages: 1734
nosy: otmarhumbel
priority: wish
status: unread
title: request for permission to edit versions in jython bugs

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

From metatracker at psf.upfronthosting.co.za  Tue Jul 13 08:12:40 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Tue, 13 Jul 2010 06:12:40 +0000
Subject: [Tracker-discuss] [issue345] sys.call_tracing isn't mentioned in
	online python docs
In-Reply-To: <1278967127.64.0.647000006367.issue345@psf.upfronthosting.co.za>
Message-ID: <1279001560.81.0.80748844309.issue345@psf.upfronthosting.co.za>


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

Reported as http://bugs.python.org/issue9237
Closing.

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

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

From metatracker at psf.upfronthosting.co.za  Tue Jul 13 15:48:14 2010
From: metatracker at psf.upfronthosting.co.za (techtonik)
Date: Tue, 13 Jul 2010 13:48: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: <1279028894.94.0.0706633776935.issue312@psf.upfronthosting.co.za>


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

Much better usability feature would be a personal message filter, so you can hide irrelevant messages.

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

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

From draghuram at gmail.com  Tue Jul 13 16:24:31 2010
From: draghuram at gmail.com (Raghuram Devarakonda)
Date: Tue, 13 Jul 2010 10:24:31 -0400
Subject: [Tracker-discuss] [issue346] request for permission to edit
	versions in jython bugs
In-Reply-To: <1278996600.65.0.349505701628.issue346@psf.upfronthosting.co.za>
References: <1278996600.65.0.349505701628.issue346@psf.upfronthosting.co.za> 
	<1278996600.65.0.349505701628.issue346@psf.upfronthosting.co.za>
Message-ID: <AANLkTinIuiwIx8dxN6fxNWvfgyoy3wxcDj_sumIgit4P@mail.gmail.com>

On Tue, Jul 13, 2010 at 12:50 AM, Oti
<metatracker at psf.upfronthosting.co.za> wrote:
>
> New submission from Oti <ohumbel at gmail.com>:
>
> Hi,
>
> i am Oti from the Jython developers, and recently built and published the new 2.5.2b1 release.
> Now i'd like to be able to add the new version to http://bugs.jython.org/version.
> Is it possible to give me the necessary permissions?
> My user name is otmarhumbel both here and in jython bugs.

I have added "Coordinator" role to your account (in addition to User
and Developer). I am not sure if this is sufficient to be able to edit
versions and other stuff. Please give it a try.

Thanks,
Raghu

From metatracker at psf.upfronthosting.co.za  Tue Jul 13 16:24:54 2010
From: metatracker at psf.upfronthosting.co.za (Raghuram Devarakonda)
Date: Tue, 13 Jul 2010 14:24:54 +0000
Subject: [Tracker-discuss] [issue346] request for permission to edit
	versions in jython bugs
In-Reply-To: <1278996600.65.0.349505701628.issue346@psf.upfronthosting.co.za>
Message-ID: <AANLkTinIuiwIx8dxN6fxNWvfgyoy3wxcDj_sumIgit4P@mail.gmail.com>


Raghuram Devarakonda <draghuram at gmail.com> added the comment:

On Tue, Jul 13, 2010 at 12:50 AM, Oti
<metatracker at psf.upfronthosting.co.za> wrote:
>
> New submission from Oti <ohumbel at gmail.com>:
>
> Hi,
>
> i am Oti from the Jython developers, and recently built and published the new 2.5.2b1 release.
> Now i'd like to be able to add the new version to http://bugs.jython.org/version.
> Is it possible to give me the necessary permissions?
> My user name is otmarhumbel both here and in jython bugs.

I have added "Coordinator" role to your account (in addition to User
and Developer). I am not sure if this is sufficient to be able to edit
versions and other stuff. Please give it a try.

Thanks,
Raghu

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

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

From metatracker at psf.upfronthosting.co.za  Tue Jul 13 16:46:11 2010
From: metatracker at psf.upfronthosting.co.za (Oti)
Date: Tue, 13 Jul 2010 14:46:11 +0000
Subject: [Tracker-discuss] [issue346] request for permission to edit
	versions in jython bugs
In-Reply-To: <1278996600.65.0.349505701628.issue346@psf.upfronthosting.co.za>
Message-ID: <1279032371.47.0.131823872699.issue346@psf.upfronthosting.co.za>


Oti <ohumbel at gmail.com> added the comment:

Yep,
i got the text field and the edit button.
Thanks a lot for adding 2.5.2b1 already!
Oti.

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

From metatracker at psf.upfronthosting.co.za  Tue Jul 20 21:39:32 2010
From: metatracker at psf.upfronthosting.co.za (Mark Lawrence)
Date: Tue, 20 Jul 2010 19:39:32 +0000
Subject: [Tracker-discuss] [issue347] Reassign all doc issues from
	georg.brandl to docs@python
In-Reply-To: <1279654772.31.0.343558345169.issue347@psf.upfronthosting.co.za>
Message-ID: <1279654772.31.0.343558345169.issue347@psf.upfronthosting.co.za>


New submission from Mark Lawrence <breamoreboy at yahoo.co.uk>:

I requested this on tracker-discuss, see e.g. http://mail.python.org/pipermail/tracker-discuss/2010-July/002607.html

----------
messages: 1739
nosy: BreamoreBoy
priority: wish
status: unread
title: Reassign all doc issues from georg.brandl to docs at python

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

From metatracker at psf.upfronthosting.co.za  Sun Jul 25 21:00:45 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sun, 25 Jul 2010 19:00:45 +0000
Subject: [Tracker-discuss] [issue262] Ignore file content in 'All text'
	search
In-Reply-To: <1238989669.77.0.307325287973.issue262@psf.upfronthosting.co.za>
Message-ID: <1280084445.57.0.278838232226.issue262@psf.upfronthosting.co.za>


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

This has been fixed in r82976.

----------
status: testing -> resolved

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

From metatracker at psf.upfronthosting.co.za  Sun Jul 25 21:04:17 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sun, 25 Jul 2010 19:04:17 +0000
Subject: [Tracker-discuss] [issue285] Add issue title to issue links,
	avoid linking to bogus issues
In-Reply-To: <1242322496.14.0.859560166441.issue285@psf.upfronthosting.co.za>
Message-ID: <1280084657.24.0.0806615070072.issue285@psf.upfronthosting.co.za>


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

Fixed in r83129, r83130, r83131, and r83132 (see also http://issues.roundup-tracker.org/issue2550659).

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

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

From metatracker at psf.upfronthosting.co.za  Sun Jul 25 21:07:09 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sun, 25 Jul 2010 19:07:09 +0000
Subject: [Tracker-discuss] [issue280] Save patches as text plain in the meta
	and setuptools	instances
In-Reply-To: <1241296793.03.0.105591612932.issue280@psf.upfronthosting.co.za>
Message-ID: <1280084829.19.0.903281261009.issue280@psf.upfronthosting.co.za>


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

Fixed in r83138.

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

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

From metatracker at psf.upfronthosting.co.za  Mon Jul 26 17:12:37 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Mon, 26 Jul 2010 15:12:37 +0000
Subject: [Tracker-discuss] [issue303] Exception when sending a ticket reply
	via email
In-Reply-To: <1255688821.53.0.717488738607.issue303@psf.upfronthosting.co.za>
Message-ID: <1280157157.88.0.0653930823033.issue303@psf.upfronthosting.co.za>


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

This doesn't seem to be a problem anymore, so I'm closing it.

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

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

From metatracker at psf.upfronthosting.co.za  Mon Jul 26 18:21:44 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Mon, 26 Jul 2010 16:21:44 +0000
Subject: [Tracker-discuss] [issue279] Removing a message sends an empty
	changenote to nosy users
In-Reply-To: <1241281073.6.0.853732988237.issue279@psf.upfronthosting.co.za>
Message-ID: <1280161304.03.0.949823602627.issue279@psf.upfronthosting.co.za>


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

When a file is removed the message reports it correctly, but this doesn't work for messages.
As Daniel mentioned the two solutions are:
 1) just send a message that says that the message has been removed;
 2) don't send any message for removed files/msgs;
Solution 2) would avoid useless mail sent when someone e.g. updates a patch removing the previous version, but OTOH if a message or file is removed by mistake it might pass unnoticed.

There's also a third solution though:
 3) avoid sending messages immediately for files/msgs that gets removed (and for any other "minor" changes, like in the nosy list or in the priority). Once another message is sent to the tracker, a single mail that includes the new message and the other minor changes that happened in the meanwhile (clarifying who is the author of each change) can be send. So if I add a name to the nosy, I delete a file, and then I add a message with a new patch only one mail will be sent.

The problem with this approach is that if someone deletes a file/msg by mistake no one will notice it until another message is sent. This is however a broader and different issue, but if it's accepted it will also fix #279.

----------
assignedto:  -> ezio.melotti
nosy: +amk, ezio.melotti, loewis
status: unread -> in-progress

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

From metatracker at psf.upfronthosting.co.za  Fri Jul 30 07:19:17 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Fri, 30 Jul 2010 05:19:17 +0000
Subject: [Tracker-discuss] [issue284] Better summary reports
In-Reply-To: <1241911709.97.0.816502801538.issue284@psf.upfronthosting.co.za>
Message-ID: <1280467157.57.0.508210023275.issue284@psf.upfronthosting.co.za>


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

Attached there's the new roundup-summary script. The script is 30% shorter (650 loc vs. 920 of the original script) and hopefully easier to maintain and extend.
I preserved most of the original features -- including the HTML reports.
As is, the summary shows the number of open, closed and total issues and the delta with the previous period, e.g.:
Issues stats:
  open      16 ( +2)
  closed     5 ( +0)
  total     21 ( +2)

It then shows the number of open issues with patches and the following tables:
 * Issues opened during the last period
 * Issues closed during the last period
 * Top issues most discussed (the 10 most discussed issues of the last period)
 * Issues waiting for review (issues with patches, "needs review" keyword or "patch review" stage)

If the script is OK I'll commit it and then, after a few tests, it could be used to replace the old one.

----------
status: chatting -> testing

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue284>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: roundup-summary2.py
Type: text/x-python
Size: 24279 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20100730/ec0a0b37/attachment-0001.py>

From metatracker at psf.upfronthosting.co.za  Fri Jul 30 16:19:26 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Fri, 30 Jul 2010 14:19:26 +0000
Subject: [Tracker-discuss] [issue279] Removing a message sends an empty
	changenote to nosy users
In-Reply-To: <1241281073.6.0.853732988237.issue279@psf.upfronthosting.co.za>
Message-ID: <1280499566.85.0.0926195259437.issue279@psf.upfronthosting.co.za>


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

I fixed it sending a message with a link to the message that has been removed in r83280. Now the message is similar to the one sent when a file is removed.

----------
status: in-progress -> done-cbb

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

From metatracker at psf.upfronthosting.co.za  Fri Jul 30 18:15:22 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Fri, 30 Jul 2010 16:15:22 +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: <1280506522.27.0.714576113754.issue298@psf.upfronthosting.co.za>


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

I looked at this but I can't find any easy solution. AFAIU the value is passed as is to the database and the query is probably generated automatically. I couldn't find where exactly this happens but I suspect that making the query case-insensitive would affect all the fields, and it might also need to be special cased for user search if there is a common entry point for all the queries.

----------
nosy: +ezio.melotti

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

From metatracker at psf.upfronthosting.co.za  Fri Jul 30 20:19:25 2010
From: metatracker at psf.upfronthosting.co.za (Oleg)
Date: Fri, 30 Jul 2010 18:19:25 +0000
Subject: [Tracker-discuss] [issue348] Can't login to cheeseshop.python.org -
	error with 'rel'
In-Reply-To: <1280513965.9.0.236514061037.issue348@psf.upfronthosting.co.za>
Message-ID: <1280513965.9.0.236514061037.issue348@psf.upfronthosting.co.za>


New submission from Oleg <phd at phd.pp.ru>:

I tried to claim an OpenID http://phd.pp.ru/ at http://pypi.python.org/pypi?%3Aaction=user_form and got Error: "There's been a problem with your request: 'rel'". What's wrong? At the page http://phd.pp.ru/ there are OpenID version 2 links:

<link rel="openid2.local_id" href="http://phd.pp.ru/">
<link rel="openid2.provider" href="http://phd.pp.ru/cgi-bin/poit.py">

I can login to SourceForge and FreshMeat, e.g. with this ID, the script http://phd.pp.ru/cgi-bin/poit.py works just fine.

----------
messages: 1748
nosy: phd
priority: bug
status: unread
title: Can't login to cheeseshop.python.org - error with 'rel'

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

From metatracker at psf.upfronthosting.co.za  Sat Jul 31 01:45:34 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Fri, 30 Jul 2010 23:45:34 +0000
Subject: [Tracker-discuss] [issue348] Can't login to cheeseshop.python.org -
	error with 'rel'
In-Reply-To: <1280513965.9.0.236514061037.issue348@psf.upfronthosting.co.za>
Message-ID: <1280533534.69.0.115492253975.issue348@psf.upfronthosting.co.za>


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

Thanks for the report. This is now fixed in c5faae00a3eb
The problem was caused by a bogus link element on the page, which has a rev= parameter instead of a rel= parameter.

Please notice that the bug tracker for the Cheese Shop is at SourceForge, not here.

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

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

From metatracker at psf.upfronthosting.co.za  Sat Jul 31 12:33:39 2010
From: metatracker at psf.upfronthosting.co.za (Oleg)
Date: Sat, 31 Jul 2010 10:33:39 +0000
Subject: [Tracker-discuss] [issue348] Can't login to cheeseshop.python.org -
	error with 'rel'
In-Reply-To: <1280513965.9.0.236514061037.issue348@psf.upfronthosting.co.za>
Message-ID: <1280572419.62.0.607698381329.issue348@psf.upfronthosting.co.za>


Oleg <phd at phd.pp.ru> added the comment:

Thank you for the fix, now it works!

There is nothing bogus in the link, <link rev=made> is a widely known way to show the author's email.

I came to the tracker from http://wiki.python.org/moin/TrackerDevelopment where this meta tracker is described as "handling bugs and features requests for the Python Tracker."

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

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

From metatracker at psf.upfronthosting.co.za  Sat Jul 31 12:54:09 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sat, 31 Jul 2010 10:54:09 +0000
Subject: [Tracker-discuss] [issue348] Can't login to cheeseshop.python.org
	-	error with 'rel'
In-Reply-To: <1280572419.62.0.607698381329.issue348@psf.upfronthosting.co.za>
Message-ID: <4C5400CE.6090502@v.loewis.de>


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

> There is nothing bogus in the link, <link rev=made> is a widely known
> way to show the author's email.

Ah, ok.

> I came to the tracker from
> http://wiki.python.org/moin/TrackerDevelopment where this meta
> tracker is described as "handling bugs and features requests for the
> Python Tracker."

Sure. However, your report was not about the Python Tracker
(bugs.python.org), but for the Cheese Shop (pypi.python.org).

----------
title: Can't login to cheeseshop.python.org - error with 'rel' -> Can't login to cheeseshop.python.org -	error with 'rel'

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

From martin at v.loewis.de  Sat Jul 31 12:54:06 2010
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Sat, 31 Jul 2010 12:54:06 +0200
Subject: [Tracker-discuss] [issue348] Can't login to
 cheeseshop.python.org -	error with 'rel'
In-Reply-To: <1280572419.62.0.607698381329.issue348@psf.upfronthosting.co.za>
References: <1280572419.62.0.607698381329.issue348@psf.upfronthosting.co.za>
Message-ID: <4C5400CE.6090502@v.loewis.de>

> There is nothing bogus in the link, <link rev=made> is a widely known
> way to show the author's email.

Ah, ok.

> I came to the tracker from
> http://wiki.python.org/moin/TrackerDevelopment where this meta
> tracker is described as "handling bugs and features requests for the
> Python Tracker."

Sure. However, your report was not about the Python Tracker
(bugs.python.org), but for the Cheese Shop (pypi.python.org).

From metatracker at psf.upfronthosting.co.za  Sat Jul 31 13:05:21 2010
From: metatracker at psf.upfronthosting.co.za (Oleg)
Date: Sat, 31 Jul 2010 11:05:21 +0000
Subject: [Tracker-discuss] [issue348] Can't login to cheeseshop.python.org
	-	error with 'rel'
In-Reply-To: <1280513965.9.0.236514061037.issue348@psf.upfronthosting.co.za>
Message-ID: <1280574321.93.0.526492181618.issue348@psf.upfronthosting.co.za>


Oleg <phd at phd.pp.ru> added the comment:

I see now. Sorry for the confusion. Now I know better. Thank you!

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