From metatracker at psf.upfronthosting.co.za  Wed Mar  5 18:50:33 2014
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Wed, 05 Mar 2014 17:50:33 +0000
Subject: [Tracker-discuss] [issue352] delete button for queries does not work
In-Reply-To: <1281701983.92.0.554897059954.issue352@psf.upfronthosting.co.za>
Message-ID: <1394041833.28.0.0700143212079.issue352@psf.upfronthosting.co.za>


R David Murray added the comment:

The leave in/out dropdown is a different problem.  I've fixed that one today.

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

From metatracker at psf.upfronthosting.co.za  Wed Mar  5 20:47:59 2014
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Wed, 05 Mar 2014 19:47:59 +0000
Subject: [Tracker-discuss] [issue352] delete button for queries does not work
In-Reply-To: <1281701983.92.0.554897059954.issue352@psf.upfronthosting.co.za>
Message-ID: <1394048879.88.0.513006828727.issue352@psf.upfronthosting.co.za>


R David Murray added the comment:

Also fixed the public yes/no dropdown, which had yet a different bug :(.

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

From metatracker at psf.upfronthosting.co.za  Wed Mar  5 23:19:08 2014
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Wed, 05 Mar 2014 22:19:08 +0000
Subject: [Tracker-discuss] [issue352] delete button for queries does not work
In-Reply-To: <1281701983.92.0.554897059954.issue352@psf.upfronthosting.co.za>
Message-ID: <1394057948.1.0.909382413636.issue352@psf.upfronthosting.co.za>


R David Murray added the comment:

Delete is fixed, at least for most browsers.  There are probably some where the javascript I used won't work.

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

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

From roundup-admin at psf.upfronthosting.co.za  Sat Mar  8 03:02:05 2014
From: roundup-admin at psf.upfronthosting.co.za (Python tracker)
Date: Sat, 08 Mar 2014 02:02:05 +0000
Subject: [Tracker-discuss] Failed issue tracker submission
Message-ID: <20140308020205.E682856915@psf.upfronthosting.co.za>



The node specified by the designator in the subject of your message
("10907797") does not exist.

Subject was: "[issue10907797]"



Mail Gateway Help
=================
Incoming messages are examined for multiple parts:
 . In a multipart/mixed message or part, each subpart is extracted and
   examined. The text/plain subparts are assembled to form the textual
   body of the message, to be stored in the file associated with a "msg"
   class node. Any parts of other types are each stored in separate files
   and given "file" class nodes that are linked to the "msg" node.
 . In a multipart/alternative message or part, we look for a text/plain
   subpart and ignore the other parts.
 . A message/rfc822 is treated similar tomultipart/mixed (except for
   special handling of the first text part) if unpack_rfc822 is set in
   the mailgw config section.

Summary
-------
The "summary" property on message nodes is taken from the first non-quoting
section in the message body. The message body is divided into sections by
blank lines. Sections where the second and all subsequent lines begin with
a ">" or "|" character are considered "quoting sections". The first line of
the first non-quoting section becomes the summary of the message.

Addresses
---------
All of the addresses in the To: and Cc: headers of the incoming message are
looked up among the user nodes, and the corresponding users are placed in
the "recipients" property on the new "msg" node. The address in the From:
header similarly determines the "author" property of the new "msg"
node. The default handling for addresses that don't have corresponding
users is to create new users with no passwords and a username equal to the
address. (The web interface does not permit logins for users with no
passwords.) If we prefer to reject mail from outside sources, we can simply
register an auditor on the "user" class that prevents the creation of user
nodes with no passwords.

Actions
-------
The subject line of the incoming message is examined to determine whether
the message is an attempt to create a new item or to discuss an existing
item. A designator enclosed in square brackets is sought as the first thing
on the subject line (after skipping any "Fwd:" or "Re:" prefixes).

If an item designator (class name and id number) is found there, the newly
created "msg" node is added to the "messages" property for that item, and
any new "file" nodes are added to the "files" property for the item.

If just an item class name is found there, we attempt to create a new item
of that class with its "messages" property initialized to contain the new
"msg" node and its "files" property initialized to contain any new "file"
nodes.

Triggers
--------
Both cases may trigger detectors (in the first case we are calling the
set() method to add the message to the item's spool; in the second case we
are calling the create() method to create a new node). If an auditor raises
an exception, the original message is bounced back to the sender with the
explanatory message given in the exception.
-------------- next part --------------
Return-Path: <tracker-discuss at python.org>
X-Original-To: report at bugs.python.org
Delivered-To: roundup+tracker at psf.upfronthosting.co.za
Received: from mail.python.org (mail.python.org [82.94.164.166])
	by psf.upfronthosting.co.za (Postfix) with ESMTPS id 9E0E1568F4
	for <report at bugs.python.org>; Sat,  8 Mar 2014 03:02:05 +0100 (CET)
Received: from albatross.python.org (localhost [127.0.0.1])
	by mail.python.org (Postfix) with ESMTP id 3fgpq12JjFz7LjZ
	for <report at bugs.python.org>; Sat,  8 Mar 2014 03:02:05 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=python.org; s=200901;
	t=1394244125; bh=AsuNGdJhAHXpqmZa/OGyA2vokEIGEBSFAhrdQU4CQ8k=;
	h=From:To:Subject:Date:From;
	b=huDs+pkheV0oEYgPvHu8ef3a2YS2N8inG8U1rPNQM36Pce1RKYR7A+vHHK6SepGNN
	 SFHCfCSyRVASr6fLstHI3+/oYv4RdQmUsxjPW7hdlqAmZuj+jLJrEICxUvly9QL5kC
	 jHg+HKrC2uB+FyDNBMBAImg4uA8PY01TSaAYaFr0=
Received: from localhost (HELO mail.python.org) (127.0.0.1)
  by albatross.python.org with SMTP; 08 Mar 2014 03:02:05 +0100
Received: from virt-7yvsjn.psf.osuosl.org (unknown [140.211.10.72])
	by mail.python.org (Postfix) with ESMTP
	for <report at bugs.python.org>; Sat,  8 Mar 2014 03:02:04 +0100 (CET)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
From: tracker-discuss at python.org
To: report at bugs.python.org
Subject: [issue10907797]
Message-Id: <3fgpq12JjFz7LjZ at mail.python.org>
Date: Sat,  8 Mar 2014 03:02:05 +0100 (CET)

TmV3IGNoYW5nZXNldCBkODQzYTFjYWJhNzggYnkgUiBEYXZpZCBNdXJyYXkgaW4gYnJhbmNoICdk
ZWZhdWx0JzoKd2hhdHNuZXc6IGNwMjczIGNvZGVjICgjMTA5MDc3OTcpCmh0dHA6Ly9oZy5weXRo
b24ub3JnL2NweXRob24vcmV2L2Q4NDNhMWNhYmE3OAo=

From metatracker at psf.upfronthosting.co.za  Sun Mar  9 00:18:13 2014
From: metatracker at psf.upfronthosting.co.za (Kees)
Date: Sat, 08 Mar 2014 23:18:13 +0000
Subject: [Tracker-discuss] [issue535] Spam entry/entries
Message-ID: <1394320693.24.0.702029853152.issue535@psf.upfronthosting.co.za>


New submission from Kees:

I'm not at all familiar with this list, however in reply to an email to webmaster at python.org I was asked to post the problem here:

Hello,

sorry for the slightly undirected email, but I just noticed (by accident) something which I think is some inappropriate content in the Python bug tracker. For instance, the url http://bugs.python.org/setuptools/file96/wl43.html displays essentially an ad with a link to http://www.wholelifequotes.org/.

----------
messages: 2838
nosy: Kees
priority: wish
status: unread
title: Spam entry/entries

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

From metatracker at psf.upfronthosting.co.za  Sun Mar  9 10:26:55 2014
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Sun, 09 Mar 2014 09:26:55 +0000
Subject: [Tracker-discuss] [issue535] Spam entry/entries
In-Reply-To: <1394320693.24.0.702029853152.issue535@psf.upfronthosting.co.za>
Message-ID: <1394357215.45.0.342886557008.issue535@psf.upfronthosting.co.za>


Georg Brandl added the comment:

It's especially bad that the HTML is displayed as-is.

HTML file attachments should never be served as HTML.

----------
nosy: +gbrandl
priority: wish -> urgent
status: unread -> chatting

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

From metatracker at psf.upfronthosting.co.za  Wed Mar 12 01:40:40 2014
From: metatracker at psf.upfronthosting.co.za (Terry Reedy)
Date: Wed, 12 Mar 2014 00:40:40 +0000
Subject: [Tracker-discuss] [issue536] Search results are sometimes woefully
	incomplete
Message-ID: <1394584840.93.0.707103067555.issue536@psf.upfronthosting.co.za>


New submission from Terry Reedy:

[Firefox, Win 7]  Consider currently open issue http://bugs.python.org/issue18104, opened by me, terry.reedy and with 'human' in the text in multiple places as well as in the title (but hyphenated). Searching All text: human  or Creator: terry.reedy fails to list the issue, whether using Status: open or Status: don't care. I say 'woefully incomplete' because the latter search with 'don't care' returns just 27 issues, while the 'Created by you' link under Summaries returns 207.

For some issues, I initially get [1.. 50 out of mmm] and when I hit [next], I get [51.. 100 out of nnn] where nnn is greater that mmm, sometimes more that twice as great. With 27, there is no [next] button to hit but this might be the same issue.

----------
messages: 2840
nosy: terry.reedy
priority: bug
status: unread
title: Search results are sometimes woefully incomplete

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

From metatracker at psf.upfronthosting.co.za  Wed Mar 12 02:04:42 2014
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Wed, 12 Mar 2014 01:04:42 +0000
Subject: [Tracker-discuss] [issue536] Search results are sometimes woefully
	incomplete
In-Reply-To: <1394584840.93.0.707103067555.issue536@psf.upfronthosting.co.za>
Message-ID: <1394586282.55.0.833541955524.issue536@psf.upfronthosting.co.za>


R David Murray added the comment:

When I search for 'human' in 'all text' leaving all the other fields at their defaults, I get that issue among the 45 results returned.  When I search from the search box, I get 157 results, and 18104 is on the first page of results.

There is a bug in next where it does not do the same search as the search that got you the first page of results.  There's an open issue here for that, but I don't know if anyone has looked in to it yet.

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

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

From techtonik at gmail.com  Wed Mar 12 12:12:47 2014
From: techtonik at gmail.com (anatoly techtonik)
Date: Wed, 12 Mar 2014 14:12:47 +0300
Subject: [Tracker-discuss] [issue536] Search results are sometimes
 woefully incomplete
In-Reply-To: <1394586282.55.0.833541955524.issue536@psf.upfronthosting.co.za>
References: <1394584840.93.0.707103067555.issue536@psf.upfronthosting.co.za>
 <1394586282.55.0.833541955524.issue536@psf.upfronthosting.co.za>
Message-ID: <CAPkN8x+uXb665ygTfuyZGVaiHkf5tQDXNKpuU=yMee-ajOX0GA@mail.gmail.com>

Link to the open issue would help at least this list subscribers to
look into it.

From roundup-admin at psf.upfronthosting.co.za  Mon Mar 17 07:31:05 2014
From: roundup-admin at psf.upfronthosting.co.za (Python tracker)
Date: Mon, 17 Mar 2014 06:31:05 +0000
Subject: [Tracker-discuss] Failed issue tracker submission
Message-ID: <20140317063105.4215056915@psf.upfronthosting.co.za>



The node specified by the designator in the subject of your message
("10907797") does not exist.

Subject was: "[issue10907797]"



Mail Gateway Help
=================
Incoming messages are examined for multiple parts:
 . In a multipart/mixed message or part, each subpart is extracted and
   examined. The text/plain subparts are assembled to form the textual
   body of the message, to be stored in the file associated with a "msg"
   class node. Any parts of other types are each stored in separate files
   and given "file" class nodes that are linked to the "msg" node.
 . In a multipart/alternative message or part, we look for a text/plain
   subpart and ignore the other parts.
 . A message/rfc822 is treated similar tomultipart/mixed (except for
   special handling of the first text part) if unpack_rfc822 is set in
   the mailgw config section.

Summary
-------
The "summary" property on message nodes is taken from the first non-quoting
section in the message body. The message body is divided into sections by
blank lines. Sections where the second and all subsequent lines begin with
a ">" or "|" character are considered "quoting sections". The first line of
the first non-quoting section becomes the summary of the message.

Addresses
---------
All of the addresses in the To: and Cc: headers of the incoming message are
looked up among the user nodes, and the corresponding users are placed in
the "recipients" property on the new "msg" node. The address in the From:
header similarly determines the "author" property of the new "msg"
node. The default handling for addresses that don't have corresponding
users is to create new users with no passwords and a username equal to the
address. (The web interface does not permit logins for users with no
passwords.) If we prefer to reject mail from outside sources, we can simply
register an auditor on the "user" class that prevents the creation of user
nodes with no passwords.

Actions
-------
The subject line of the incoming message is examined to determine whether
the message is an attempt to create a new item or to discuss an existing
item. A designator enclosed in square brackets is sought as the first thing
on the subject line (after skipping any "Fwd:" or "Re:" prefixes).

If an item designator (class name and id number) is found there, the newly
created "msg" node is added to the "messages" property for that item, and
any new "file" nodes are added to the "files" property for the item.

If just an item class name is found there, we attempt to create a new item
of that class with its "messages" property initialized to contain the new
"msg" node and its "files" property initialized to contain any new "file"
nodes.

Triggers
--------
Both cases may trigger detectors (in the first case we are calling the
set() method to add the message to the item's spool; in the second case we
are calling the create() method to create a new node). If an auditor raises
an exception, the original message is bounced back to the sender with the
explanatory message given in the exception.
-------------- next part --------------
Return-Path: <tracker-discuss at python.org>
X-Original-To: report at bugs.python.org
Delivered-To: roundup+tracker at psf.upfronthosting.co.za
Received: from mail.python.org (mail.python.org [82.94.164.166])
	by psf.upfronthosting.co.za (Postfix) with ESMTPS id F1018568E0
	for <report at bugs.python.org>; Mon, 17 Mar 2014 07:31:04 +0100 (CET)
Received: from albatross.python.org (localhost [127.0.0.1])
	by mail.python.org (Postfix) with ESMTP id 3fnSMD4l2qz7LkT
	for <report at bugs.python.org>; Mon, 17 Mar 2014 07:31:04 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=python.org; s=200901;
	t=1395037864; bh=0o/112u6Ds+/6jdFi+YZjcQqtuUdcUFDl77mz5nKB6M=;
	h=From:To:Subject:Date:From;
	b=SpMJOOZfb4t6AMwbdBdk3JVwuJZ6ZLlWl2QJoC9W22kMudmWf0HUdSLqDwsF6dtf4
	 mT9e6Ka0jsybUTw/akey9w36Nh9IrtIAxtwflQb0PsIA6GAuASFgC1grGGVZ09pVod
	 U9GOP1zS9VjJ1NDwoRd2E0A9uUdpGu2phbiiMAtQ=
Received: from localhost (HELO mail.python.org) (127.0.0.1)
  by albatross.python.org with SMTP; 17 Mar 2014 07:31:04 +0100
Received: from virt-7yvsjn.psf.osuosl.org (unknown [140.211.10.72])
	by mail.python.org (Postfix) with ESMTP
	for <report at bugs.python.org>; Mon, 17 Mar 2014 07:31:04 +0100 (CET)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
From: tracker-discuss at python.org
To: report at bugs.python.org
Subject: [issue10907797]
Message-Id: <3fnSMD4l2qz7LkT at mail.python.org>
Date: Mon, 17 Mar 2014 07:31:04 +0100 (CET)

TmV3IGNoYW5nZXNldCBmN2QwOTNhNGViZjYgYnkgUiBEYXZpZCBNdXJyYXkgaW4gYnJhbmNoICcz
LjQnOgp3aGF0c25ldzogY3AyNzMgY29kZWMgKCMxMDkwNzc5NykKaHR0cDovL2hnLnB5dGhvbi5v
cmcvY3B5dGhvbi9yZXYvZjdkMDkzYTRlYmY2Cg==

From metatracker at psf.upfronthosting.co.za  Sat Mar 22 15:17:33 2014
From: metatracker at psf.upfronthosting.co.za (Sorin Sbarnea)
Date: Sat, 22 Mar 2014 14:17:33 +0000
Subject: [Tracker-discuss] [issue537] Proposal to migrate bugs.python.com to
	Jira
Message-ID: <1395497853.57.0.242557705939.issue537@psf.upfronthosting.co.za>


New submission from Sorin Sbarnea:

I?m probably not the first to ask about this and sorry if that?s not the best place to ask or if the subject was discussed and dismissed long time ago (i wasn?t able to find any info online).

I would like to know if it would be any interest on switching from the poor current bug tracker to a much better one, like Atlassian JIRA which is already widely used by so many. 

Probably there is no need to specify the kind of things we would be able to benefit from, like linking bugs to other JIRA systems, accessibility, easy workflows, good statistics and so on.

I am asking this because I do think that a better bug tracker would be of great benefit to Python community and we shouldn?t be victim of not-invented-here syndrome and still be able to recognize and use a better tool even if it?s not made in Python.

I do have extensive experience with JIRA, from user, administrator and developer level.

If you think that the community would be interested about something like this, I would like to invest a signifiant amount of my time on doing this. 

Let me know what you think about it and if you have links to existing discussions please share them.

----------
messages: 2842
nosy: sorin
priority: feature
status: unread
title: Proposal to migrate bugs.python.com to Jira

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

From techtonik at gmail.com  Sun Mar 23 02:09:02 2014
From: techtonik at gmail.com (anatoly techtonik)
Date: Sun, 23 Mar 2014 04:09:02 +0300
Subject: [Tracker-discuss] [issue537] Proposal to migrate
 bugs.python.com to Jira
In-Reply-To: <1395497853.57.0.242557705939.issue537@psf.upfronthosting.co.za>
References: <1395497853.57.0.242557705939.issue537@psf.upfronthosting.co.za>
Message-ID: <CAPkN8xKyxjp-HLXadKNaqJ6=78xfBwC_qgR-QOEeZUfFeTWWJw@mail.gmail.com>

On Sat, Mar 22, 2014 at 5:17 PM, Sorin Sbarnea
<metatracker at psf.upfronthosting.co.za> wrote:
>
> I am asking this because I do think that a better bug tracker would be of great benefit to Python community and we shouldn?t be victim of not-invented-here syndrome and still be able to recognize and use a better tool even if it?s not made in Python.

My version of the main reason why open source projects use open source
software is that it is critical for any open source project not to
fall down into the user only syndrome, where software is not developed
anymore, because its community consists of pure users. People, who
know how to use, but can't learn how things work, modify them and
share this knowledge between each other in a manner that is
challenging and fun for others to try.

> I do have extensive experience with JIRA, from user, administrator and developer level.

"If all you have is a hammer, everything looks like a nail." )

Why not Bugzilla, Trac, Redmine? I am sure there are a lot of people
who are experienced with these. Personally, I am not convinced that
JIRA is superior to those. And also the bus factor of 1 is not
compelling.

> If you think that the community would be interested about something like this, I would like to invest a signifiant amount of my time on doing this.

Well, if you're really a good JIRA hacker and would like to change
JIRA outlook to be more positive, it is real if you will be able to
help people of Qt Project to enable one-click OpenID and Google
account logins, which seems impossible without buying vendor service -
https://bugreports.qt-project.org/browse/QTJIRA-74

I understand that you want to help Python community - not a Qt one,
but there is one project - PySide, which is a QT Project and which is
used by many Python IDEs (and hence very beneficial for Python
community), and lowering contribution barrier for is useful for those
who use Python for GUI works.

> Let me know what you think about it and if you have links to existing discussions please share them.

I have a good experience with both open source and proprietary tracker
solutions. Better tracking practices definitely help development, but
that may not depend on tracker as much as on your ability to convince
rather conservative collective mind about a better practice.

From metatracker at psf.upfronthosting.co.za  Sun Mar 23 03:43:21 2014
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sun, 23 Mar 2014 02:43:21 +0000
Subject: [Tracker-discuss] [issue535] Spam entry/entries
In-Reply-To: <1394320693.24.0.702029853152.issue535@psf.upfronthosting.co.za>
Message-ID: <1395542601.43.0.646474140273.issue535@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

> HTML file attachments should never be served as HTML.

This should be fixed now, but it will affect only new attachments.
The content type of old attachments should be changed (by following the "edit" link) and/or they should be unlinked (together with the spam message/issue.

----------
assignedto:  -> ezio.melotti
nosy: +ezio.melotti, pjenvey
status: chatting -> testing

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

From metatracker at psf.upfronthosting.co.za  Sun Mar 23 09:52:17 2014
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sun, 23 Mar 2014 08:52:17 +0000
Subject: [Tracker-discuss] [issue535] Spam entry/entries
In-Reply-To: <1394320693.24.0.702029853152.issue535@psf.upfronthosting.co.za>
Message-ID: <1395564737.83.0.0694991894779.issue535@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

I have changed the type of all html files in this tracker to text/plain.

I'll also look into turning off the setuptools tracker; I doubt it is active still.

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

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

From metatracker at psf.upfronthosting.co.za  Sun Mar 23 10:04:56 2014
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sun, 23 Mar 2014 09:04:56 +0000
Subject: [Tracker-discuss] [issue537] Proposal to migrate bugs.python.com to
	Jira
In-Reply-To: <1395497853.57.0.242557705939.issue537@psf.upfronthosting.co.za>
Message-ID: <1395565496.49.0.175919631877.issue537@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

This is almost the right place to bring this up; please use tracker-discuss (mail.python.org) instead.

The subject was indeed discussed and dismissed long ago. We set up a working group in 2005 to pick a new bug tracker for Python, moving away from SourceForge. Several tracker systems were considered, namely Jira, Roundup, and Trac. After a detailed study of these systems, Roundup was picked as the best choice.

I have had recent exposure to Jira, and must say that I'm glad that we picked Roundup. It is clearly superior to Jira in many aspects...

Please understand that people typically make a religious issue out of bug tracker choice, and consider all trackers but their own as poor and unusable.

In any case, if you want to continue the discussion, please use tracker-discuss.

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

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

From metatracker at psf.upfronthosting.co.za  Sun Mar 23 10:11:32 2014
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sun, 23 Mar 2014 09:11:32 +0000
Subject: [Tracker-discuss] [issue458] editing "homepage" field is not
	possible
In-Reply-To: <1334485569.34.0.217371137544.issue458@psf.upfronthosting.co.za>
Message-ID: <1395565892.65.0.62723403803.issue458@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

I don't think that the spam risk is high, so I think it might still be desirable to have it. Given that I had no time to work on this for the last two years, chances are that I won't have time in the coming two years, either.

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

From metatracker at psf.upfronthosting.co.za  Sun Mar 23 10:12:18 2014
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sun, 23 Mar 2014 09:12:18 +0000
Subject: [Tracker-discuss] [issue527] HTTPS / SSL / Secure access
In-Reply-To: <1380348162.36.0.964046648568.issue527@psf.upfronthosting.co.za>
Message-ID: <1395565938.06.0.79268254731.issue527@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

Yes, it can be closed

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

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

From metatracker at psf.upfronthosting.co.za  Mon Mar 31 19:05:37 2014
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Mon, 31 Mar 2014 17:05:37 +0000
Subject: [Tracker-discuss] [issue538] html-escaped link in message update
	collision message
Message-ID: <1396285537.51.0.358129889954.issue538@psf.upfronthosting.co.za>


New submission from R David Murray:

When Roundup detects that someone else has updated an issue, it tries to give you a link to use to open the message in a new window so you can see what changes were made to the metadata.  After the XSS issues were fixed, this link became escaped HTML and so did not work.  I reported this issue upstream here:

  http://issues.roundup-tracker.org/issue2550836

It has now been fixed, and the issue contains a request to test the fix.  I'm not sure how practical it is for us to test it, but either way I'm recording the issue here as something we need to check at some point, either by testing the patch now or by testing it after it gets released upstream and we upgrade.

Note that Ralph says he "completely changed" the way the XSS stuff is handled, which might or might not mean there are other adjustments we want to make on our tracker, depending on whether we previously "fixed" things in or templates or not.

----------
messages: 2848
nosy: r.david.murray
priority: feature
status: unread
title: html-escaped link in message update collision message

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

From metatracker at psf.upfronthosting.co.za  Mon Mar 31 19:56:23 2014
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Mon, 31 Mar 2014 17:56:23 +0000
Subject: [Tracker-discuss] [issue538] html-escaped link in message update
	collision message
In-Reply-To: <1396285537.51.0.358129889954.issue538@psf.upfronthosting.co.za>
Message-ID: <1396288583.49.0.190047365765.issue538@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

If somebody want to test this, I suggest that we should pull the upstream source, merge with our own branch, deploy this, test it, then revert to the version that we had deployed before (hoping that there won't be any schema upgrades in between).

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

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