From metatracker at psf.upfronthosting.co.za  Wed Aug  3 20:07:52 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Wed, 03 Aug 2011 18:07:52 +0000
Subject: [Tracker-discuss] [issue134] Exception viewing issue
	with	superseder - should	superseder be Link or Multilink
In-Reply-To: <1187893000.91.0.555834863275.issue134@psf.upfronthosting.co.za>
Message-ID: <1312394872.53.0.949472564539.issue134@psf.upfronthosting.co.za>


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

I agree with Georg, so I'll close this.

----------
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/issue134>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Aug  3 20:13:06 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Wed, 03 Aug 2011 18:13:06 +0000
Subject: [Tracker-discuss] [issue324] Add repository info to tracker
	components
In-Reply-To: <1269343030.93.0.79046519877.issue324@psf.upfronthosting.co.za>
Message-ID: <1312395186.56.0.0317026354246.issue324@psf.upfronthosting.co.za>


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

I agree that adding the links to the tracker clutters the UI.
Now that we have the devguide and better autolinking (including from the tracebacks, so that you can jump directly to the file/line where the error is) I don't think this will bring anything useful.

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

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

From metatracker at psf.upfronthosting.co.za  Sat Aug  6 16:37:06 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sat, 06 Aug 2011 14:37:06 +0000
Subject: [Tracker-discuss] [issue394] Better integration with Rietveld code
	review tool
In-Reply-To: <1303156350.85.0.792534425783.issue394@psf.upfronthosting.co.za>
Message-ID: <1312641426.13.0.797088585026.issue394@psf.upfronthosting.co.za>


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

Ezio added the backlink from Rietveld to Roundup in r88874 \o/

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

From metatracker at psf.upfronthosting.co.za  Sat Aug  6 16:48:18 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sat, 06 Aug 2011 14:48:18 +0000
Subject: [Tracker-discuss] [issue413] Mercurial integration: impossible to
	remove a repo
Message-ID: <1312642098.58.0.714079362013.issue413@psf.upfronthosting.co.za>


New submission from ?ric Araujo <merwok at netwok.org>:

When I try to remove the second repo on http://bugs.python.org/issue12666, I get this cryptic error:
property "files": "51" not currently in list

----------
messages: 2205
nosy: eric.araujo, loewis
priority: bug
status: unread
title: Mercurial integration: impossible to remove a repo

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

From metatracker at psf.upfronthosting.co.za  Sat Aug  6 16:52:13 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sat, 06 Aug 2011 14:52:13 +0000
Subject: [Tracker-discuss] [issue414] Mercurial integration: verify repo
	when adding
Message-ID: <1312642333.95.0.845747072773.issue414@psf.upfronthosting.co.za>


New submission from ?ric Araujo <merwok at netwok.org>:

It has happened more than one time that people put an ssh or private https URI in the remote repo field, which makes Roundup error when someone wants to create a patch.  If possible, access should be checked when a repo is added.

(FTR, the Bitbucket https URIs are not private, this may be yet another bug.)

----------
messages: 2206
nosy: eric.araujo, loewis
priority: bug
status: unread
title: Mercurial integration: verify repo when adding

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

From metatracker at psf.upfronthosting.co.za  Sat Aug  6 16:55:12 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sat, 06 Aug 2011 14:55:12 +0000
Subject: [Tracker-discuss] [issue415] Mercurial integration: regression in
	diff generation
Message-ID: <1312642512.39.0.425778233696.issue415@psf.upfronthosting.co.za>


New submission from ?ric Araujo <merwok at netwok.org>:

There seems to be a regression with diff generation: if you look at http://bugs.python.org/file22839/bc362109eed8.diff (created from the repo http://bitbucket.org/jaraco/cpython-issue12666 added to http://bugs.python.org/issue12666), you?ll find first that the diff uses the old format, not the git format, and second that the diff seems to revert some upstream changes.

----------
messages: 2207
nosy: eric.araujo, loewis, pitrou
priority: urgent
status: unread
title: Mercurial integration: regression in diff generation

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

From metatracker at psf.upfronthosting.co.za  Tue Aug  9 01:12:56 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Mon, 08 Aug 2011 23:12:56 +0000
Subject: [Tracker-discuss] [issue278] 1.4.8 fixes for other PSF trackers
In-Reply-To: <1240793302.05.0.121079776163.issue278@psf.upfronthosting.co.za>
Message-ID: <1312845176.31.0.0584170374752.issue278@psf.upfronthosting.co.za>


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

I applied the patch in r88878.

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

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

From metatracker at psf.upfronthosting.co.za  Tue Aug  9 01:29:34 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Mon, 08 Aug 2011 23:29:34 +0000
Subject: [Tracker-discuss] [issue409] Spam on jython tracker.
In-Reply-To: <1310843975.4.0.271262889404.issue409@psf.upfronthosting.co.za>
Message-ID: <1312846174.54.0.112797949348.issue409@psf.upfronthosting.co.za>


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

The problem with the files was that it required a POST request while the remove button was trying to use GET.  This is now fixed in r88878 in both the Jython and meta trackers, so you can remove files and messages from the issues.

OTOH I still haven't figured out how to retire those issue/messages/files.

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

From metatracker at psf.upfronthosting.co.za  Tue Aug  9 05:24:44 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Tue, 09 Aug 2011 03:24:44 +0000
Subject: [Tracker-discuss] [issue411] Roundup instance is outdated
In-Reply-To: <1311602492.71.0.972062932119.issue411@psf.upfronthosting.co.za>
Message-ID: <1312860284.57.0.952825554549.issue411@psf.upfronthosting.co.za>


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

I applied the update to Roundup 1.4.19 in r88872, to the python-dev instance in r88876/7, and updated the other instances to Roundup 1.4.8.  The attached patch contains the 1.4.19 updates for the other instances as well.  It might be necessary to apply the r88877 fix[0] to them as well.

FWIW I can't tests this instances on my machine.  Also I didn't include the python-dev-spambayes-integration instance in the update.  Is it used? Does it need to be updated?

The updated instances are: board, jobs, jython, meta, security, setuptools.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue411>
_______________________________________________________
-------------- next part --------------
Index: setuptools/html/style.css
===================================================================
--- setuptools/html/style.css	(revision 88877)
+++ setuptools/html/style.css	(working copy)
@@ -50,15 +50,7 @@
   padding: 5px;
   border-bottom: 1px solid #444;
 }
-#searchbox {
-    float: right;
-}
 
-div#body-title {
-  float: left;
-}
-
-
 div#searchbox {
   float: right;
   padding-top: 1em;
@@ -421,6 +413,7 @@
   font-weight: bold;
   text-align: left;
 }
+
 input[type="text"]:focus,
 input[type="checkbox"]:focus,
 input[type="radio"]:focus,
@@ -429,6 +422,18 @@
   background-color: #ffffc0;
 }
 
+.calendar_display {
+  text-align: center;
+}
+
+.calendar_display td {
+  padding: 1px 4px 1px 4px;
+}
+
+.calendar_display .today {
+  background-color: #afafaf;
+}
+
 /* vim: sts=2 sw=2 et
 */
 /* SHA: 7243da9b4e481a0b95a5367b45baaaa45fab8998 */
Index: setuptools/html/page.html
===================================================================
--- setuptools/html/page.html	(revision 88877)
+++ setuptools/html/page.html	(working copy)
@@ -28,9 +28,6 @@
 <tr>
  <td class="page-header-left">&nbsp;</td>
  <td class="page-header-top">
-   <div id="body-title">
-     <h2><span metal:define-slot="body_title">body title</span></h2>
-   </div>
    <div id="searchbox">
      <form method="GET" action="issue">
        <input type="hidden" name="@columns"
@@ -43,7 +40,10 @@
        <input type="submit" id="submit" name="submit" value="Search"
               i18n:attributes="value" />
      </form>
-  </div>
+   </div>
+   <div id="body-title">
+     <h2><span metal:define-slot="body_title">body title</span></h2>
+   </div>
  </td>
 </tr>
 
@@ -164,7 +164,7 @@
   </p>
   <p class="userblock">
    <b i18n:translate="">Help</b><br>
-   <a href="http://roundup.sourceforge.net/doc-1.0/"
+   <a href="http://www.roundup-tracker.org"
     i18n:translate="">Roundup docs</a>
   </p>
  </td>
@@ -231,7 +231,7 @@
   <input tal:attributes="value python:request.form.getvalue(name) or nothing;
                          name name;
                          id name">
-  <span tal:replace="structure python:db.issue.classhelp(columns,
+  <span tal:replace="structure python:db[db_klass].classhelp(columns,
                                       property=name)" />
 </td>
 
@@ -247,6 +247,22 @@
   </select>
 </td>
 
+<td metal:define-macro="search_select_keywords">
+  <div tal:attributes="id python:'''keywords_%s'''%name">
+    <select tal:attributes="name name; id name"
+            tal:define="value python:request.form.getvalue(name)">
+      <option value="" i18n:translate="">don't care</option>
+      <metal:slot define-slot="extra_options" />
+      <option value="" i18n:translate="" disabled="disabled">------------</option>
+      <option tal:repeat="s python:db[db_klass].list()"
+              tal:attributes="value s/id; selected python:value == s.id"
+              tal:content="python:s[db_content]"></option>
+    </select>
+    <a class="classhelp"
+	   tal:attributes="href python:'''javascript:help_window('issue?@template=keywords_expr&property=%s&form=itemSynopsis', 350, 200)'''%name">(expr)</a>
+  </div>
+</td>
+
 <!-- like search_select, but translates the further values.
 Could extend it (METAL 1.1 attribute "extend-macro")
 -->
Index: setuptools/html/_generic.index.html
===================================================================
--- setuptools/html/_generic.index.html	(revision 88877)
+++ setuptools/html/_generic.index.html	(working copy)
@@ -39,7 +39,8 @@
 
 <p class="form-help">
  Remove entries by deleting their line. Add new entries by appending
- them to the table - put an X in the id column.
+ them to the table - put an X in the id column. If you wish to restore a
+ removed item and you know its id then just put that id in the id column.
 </p>
 </tal:block>
 <form onSubmit="return submit_once()" method="POST"
Index: setuptools/html/issue.search.html
===================================================================
--- setuptools/html/issue.search.html	(revision 88877)
+++ setuptools/html/issue.search.html	(working copy)
@@ -12,10 +12,10 @@
    cols python:request.columns or 'id activity title status assignedto'.split();
    sort_on python:request.sort and request.sort[0] or nothing;
    sort_desc python:sort_on and sort_on[0] == '-';
-   sort_on python:(sort_on and sort_on[1]) or 'activity';
+   sort_on python:(sort_on and sort_on[1]) or (not request.nodeid and 'activity') or '';
    group_on python:request.group and request.group[0] or nothing;
    group_desc python:group_on and group_on[0] == '-';
-   group_on python:(group_on and group_on[1]) or 'priority';
+   group_on python:(group_on and group_on[1]) or (not request.nodeid and 'priority') or '';
 
    search_input templates/page/macros/search_input;
    search_date templates/page/macros/search_date;
@@ -23,6 +23,7 @@
    sort_input templates/page/macros/sort_input;
    group_input templates/page/macros/group_input;
    search_select templates/page/macros/search_select;
+   search_select_keywords templates/page/macros/search_select_keywords;
    search_select_translated templates/page/macros/search_select_translated;
    search_multiselect templates/page/macros/search_multiselect;">
 
@@ -54,7 +55,7 @@
                 db_klass string:keyword;
                 db_content string:name;">
   <th i18n:translate="">Keyword:</th>
-  <td metal:use-macro="search_select">
+  <td metal:use-macro="search_select_keywords">
     <option metal:fill-slot="extra_options" value="-1" i18n:translate=""
             tal:attributes="selected python:value == '-1'">not selected</option>
   </td>
@@ -167,8 +168,8 @@
  <th i18n:translate="">No Sort or group:</th>
  <td>&nbsp;</td>
  <td>&nbsp;</td>
- <td><input type="radio" name="@sort" value=""></td>
- <td><input type="radio" name="@group" value=""></td>
+ <td><input type="radio" name="@sort" value="" tal:attributes="checked python:sort_on == ''"></td>
+ <td><input type="radio" name="@group" value="" tal:attributes="checked python:group_on == ''"></td>
 </tr>
 
 <tr>
Index: setuptools/html/_generic.item.html
===================================================================
--- setuptools/html/_generic.item.html	(revision 88877)
+++ setuptools/html/_generic.item.html	(working copy)
@@ -44,7 +44,12 @@
 
 </form>
 
-<tal:block tal:condition="context/id" tal:replace="structure context/history" />
+<tal:block tal:condition="context/id"
+    tal:define="limit python:[10, None][request.form.has_key('show_all_history')]"
+    tal:replace="structure python:context.history(limit=limit)" />
+<p tal:condition="not:exists:request/form/show_all_history" i18n:translate="">Showing 10 items.
+<a tal:attributes="href string:${context/_classname}${context/id}?show_all_history=yes">Show all history</a>
+(warning: this could be VERY long)</p>
 
 </div>
 
Index: meta/html/style.css
===================================================================
--- meta/html/style.css	(revision 88878)
+++ meta/html/style.css	(working copy)
@@ -50,15 +50,7 @@
   padding: 5px;
   border-bottom: 1px solid #444;
 }
-#searchbox {
-    float: right;
-}
 
-div#body-title {
-  float: left;
-}
-
-
 div#searchbox {
   float: right;
   padding-top: 1em;
@@ -431,6 +423,7 @@
   font-weight: bold;
   text-align: left;
 }
+
 input[type="text"]:focus,
 input[type="checkbox"]:focus,
 input[type="radio"]:focus,
@@ -440,6 +433,18 @@
   background-color: #ffffc0;
 }
 
+.calendar_display {
+  text-align: center;
+}
+
+.calendar_display td {
+  padding: 1px 4px 1px 4px;
+}
+
+.calendar_display .today {
+  background-color: #afafaf;
+}
+
 /* vim: sts=2 sw=2 et
 */
 /* SHA: 7243da9b4e481a0b95a5367b45baaaa45fab8998 */
Index: meta/html/page.html
===================================================================
--- meta/html/page.html	(revision 88878)
+++ meta/html/page.html	(working copy)
@@ -28,9 +28,6 @@
 <tr>
  <td class="page-header-left">&nbsp;</td>
  <td class="page-header-top">
-   <div id="body-title">
-     <h2><span metal:define-slot="body_title">body title</span></h2>
-   </div>
    <div id="searchbox">
      <form method="GET" action="issue">
        <input type="hidden" name="@columns"
@@ -41,7 +38,10 @@
        <input id="search-text" name="@search_text" size="10"/>
        <input type="submit" id="submit" name="submit" value="Search" i18n:attributes="value" />
      </form>
-  </div>
+   </div>
+   <div id="body-title">
+     <h2><span metal:define-slot="body_title">body title</span></h2>
+   </div>
  </td>
 </tr>
 
@@ -162,7 +162,7 @@
   </p>
   <p class="userblock">
    <b i18n:translate="">Help</b><br>
-   <a href="http://roundup.sourceforge.net/doc-1.0/"
+   <a href="http://www.roundup-tracker.org"
     i18n:translate="">Roundup docs</a>
   </p>
  </td>
@@ -229,7 +229,7 @@
   <input tal:attributes="value python:request.form.getvalue(name) or nothing;
                          name name;
                          id name">
-  <span tal:replace="structure python:db.issue.classhelp(columns,
+  <span tal:replace="structure python:db[db_klass].classhelp(columns,
                                       property=name)" />
 </td>
 
@@ -245,6 +245,22 @@
   </select>
 </td>
 
+<td metal:define-macro="search_select_keywords">
+  <div tal:attributes="id python:'''keywords_%s'''%name">
+    <select tal:attributes="name name; id name"
+            tal:define="value python:request.form.getvalue(name)">
+      <option value="" i18n:translate="">don't care</option>
+      <metal:slot define-slot="extra_options" />
+      <option value="" i18n:translate="" disabled="disabled">------------</option>
+      <option tal:repeat="s python:db[db_klass].list()"
+              tal:attributes="value s/id; selected python:value == s.id"
+              tal:content="python:s[db_content]"></option>
+    </select>
+    <a class="classhelp"
+	   tal:attributes="href python:'''javascript:help_window('issue?@template=keywords_expr&property=%s&form=itemSynopsis', 350, 200)'''%name">(expr)</a>
+  </div>
+</td>
+
 <!-- like search_select, but translates the further values.
 Could extend it (METAL 1.1 attribute "extend-macro")
 -->
Index: meta/html/_generic.index.html
===================================================================
--- meta/html/_generic.index.html	(revision 88878)
+++ meta/html/_generic.index.html	(working copy)
@@ -39,7 +39,8 @@
 
 <p class="form-help">
  Remove entries by deleting their line. Add new entries by appending
- them to the table - put an X in the id column.
+ them to the table - put an X in the id column. If you wish to restore a
+ removed item and you know its id then just put that id in the id column.
 </p>
 </tal:block>
 <form onSubmit="return submit_once()" method="POST"
Index: meta/html/issue.search.html
===================================================================
--- meta/html/issue.search.html	(revision 88878)
+++ meta/html/issue.search.html	(working copy)
@@ -7,15 +7,15 @@
 
 <form method="GET" name="itemSynopsis"
       tal:attributes="action request/classname">
-      
+
 <table class="form" tal:define="
    cols python:request.columns or 'id activity title status assignedto'.split();
    sort_on python:request.sort and request.sort[0] or nothing;
    sort_desc python:sort_on and sort_on[0] == '-';
-   sort_on python:(sort_on and sort_on[1]) or 'activity';
+   sort_on python:(sort_on and sort_on[1]) or (not request.nodeid and 'activity') or '';
    group_on python:request.group and request.group[0] or nothing;
    group_desc python:group_on and group_on[0] == '-';
-   group_on python:(group_on and group_on[1]) or 'priority';
+   group_on python:(group_on and group_on[1]) or (not request.nodeid and 'priority') or '';
 
    search_input templates/page/macros/search_input;
    search_date templates/page/macros/search_date;
@@ -164,8 +164,8 @@
  <th i18n:translate="">No Sort or group:</th>
  <td>&nbsp;</td>
  <td>&nbsp;</td>
- <td><input type="radio" name="@sort" value=""></td>
- <td><input type="radio" name="@group" value=""></td>
+ <td><input type="radio" name="@sort" value="" tal:attributes="checked python:sort_on == ''"></td>
+ <td><input type="radio" name="@group" value="" tal:attributes="checked python:group_on == ''"></td>
 </tr>
 
 <tr>
Index: meta/html/_generic.item.html
===================================================================
--- meta/html/_generic.item.html	(revision 88878)
+++ meta/html/_generic.item.html	(working copy)
@@ -44,7 +44,12 @@
 
 </form>
 
-<tal:block tal:condition="context/id" tal:replace="structure context/history" />
+<tal:block tal:condition="context/id"
+    tal:define="limit python:[10, None][request.form.has_key('show_all_history')]"
+    tal:replace="structure python:context.history(limit=limit)" />
+<p tal:condition="not:exists:request/form/show_all_history" i18n:translate="">Showing 10 items.
+<a tal:attributes="href string:${context/_classname}${context/id}?show_all_history=yes">Show all history</a>
+(warning: this could be VERY long)</p>
 
 </div>
 
Index: board/html/style.css
===================================================================
--- board/html/style.css	(revision 88877)
+++ board/html/style.css	(working copy)
@@ -33,13 +33,6 @@
     #searchbox { display: none;}
 }
 
-#searchbox { float: right;}
-
-div#body-title {
-  float: left;
-}
-
-
 div#searchbox 
 {
   float: right;
@@ -456,7 +449,18 @@
   background-color: #ffffc0;
 }
 
+.calendar_display {
+  text-align: center;
+}
 
+.calendar_display td {
+  padding: 1px 4px 1px 4px;
+}
+
+.calendar_display .today {
+  background-color: #afafaf;
+}
+
 #demowarning {
    position: absolute;
    top: 10px;
Index: board/html/page.html
===================================================================
--- board/html/page.html	(revision 88877)
+++ board/html/page.html	(working copy)
@@ -130,7 +130,7 @@
        </li>
        <li>
        <a href="user?@template=register"
-          tal:condition="python:request.user.hasPermission('Create', 'user')"
+          tal:condition="python:request.user.hasPermission('Register', 'user')"
           i18n:translate="">Register</a>
 	</li>
        <li><a href="user?@template=forgotten" i18n:translate="">Lost&nbsp;your&nbsp;login?</a>
@@ -283,7 +283,7 @@
   <input tal:attributes="value python:request.form.getvalue(name) or nothing;
                          name name;
                          id name"/>
-  <span tal:replace="structure python:db.issue.classhelp(columns,
+  <span tal:replace="structure python:db[db_klass].classhelp(columns,
                                       property=name)" />
 </td>
 
@@ -299,6 +299,22 @@
   </select>
 </td>
 
+<td metal:define-macro="search_select_keywords">
+  <div tal:attributes="id python:'''keywords_%s'''%name">
+    <select tal:attributes="name name; id name"
+            tal:define="value python:request.form.getvalue(name)">
+      <option value="" i18n:translate="">don't care</option>
+      <metal:slot define-slot="extra_options" />
+      <option value="" i18n:translate="" disabled="disabled">------------</option>
+      <option tal:repeat="s python:db[db_klass].list()"
+              tal:attributes="value s/id; selected python:value == s.id"
+              tal:content="python:s[db_content]"></option>
+    </select>
+    <a class="classhelp"
+	   tal:attributes="href python:'''javascript:help_window('issue?@template=keywords_expr&property=%s&form=itemSynopsis', 350, 200)'''%name">(expr)</a>
+  </div>
+</td>
+
 <!-- like search_select, but translates the further values.
 Could extend it (METAL 1.1 attribute "extend-macro")
 -->
Index: board/html/_generic.index.html
===================================================================
--- board/html/_generic.index.html	(revision 88877)
+++ board/html/_generic.index.html	(working copy)
@@ -37,7 +37,8 @@
 
 <p class="form-help">
  Remove entries by deleting their line. Add new entries by appending
- them to the table - put an X in the id column.
+ them to the table - put an X in the id column. If you wish to restore a
+ removed item and you know its id then just put that id in the id column.
 </p>
 </tal:block>
 <form onSubmit="return submit_once()" method="POST"
Index: board/html/issue.search.html
===================================================================
--- board/html/issue.search.html	(revision 88877)
+++ board/html/issue.search.html	(working copy)
@@ -12,10 +12,10 @@
    cols python:request.columns or 'id activity title status assignedto'.split();
    sort_on python:request.sort and request.sort[0] or nothing;
    sort_desc python:sort_on and sort_on[0] == '-';
-   sort_on python:(sort_on and sort_on[1]) or 'activity';
+   sort_on python:(sort_on and sort_on[1]) or (not request.nodeid and 'activity') or '';
    group_on python:request.group and request.group[0] or nothing;
    group_desc python:group_on and group_on[0] == '-';
-   group_on python:(group_on and group_on[1]) or 'priority';
+   group_on python:(group_on and group_on[1]) or (not request.nodeid and 'priority') or '';
 
    search_input templates/page/macros/search_input;
    search_date templates/page/macros/search_date;
@@ -23,6 +23,7 @@
    sort_input templates/page/macros/sort_input;
    group_input templates/page/macros/group_input;
    search_select templates/page/macros/search_select;
+   search_select_keywords templates/page/macros/search_select_keywords;
    search_select_translated templates/page/macros/search_select_translated;
    search_multiselect templates/page/macros/search_multiselect;">
 
@@ -191,7 +192,7 @@
                 db_klass string:keyword;
                 db_content string:name;">
   <th i18n:translate="">Keyword:</th>
-  <td metal:use-macro="search_select_translated">
+  <td metal:use-macro="search_select_keywords">
     <option metal:fill-slot="extra_options" value="-1" i18n:translate=""
             tal:attributes="selected python:value == '-1'">not set</option>
   </td>
@@ -244,8 +245,8 @@
  <th i18n:translate="">No Sort or group:</th>
  <td>&nbsp;</td>
  <td>&nbsp;</td>
- <td><input type="radio" name="@sort" value=""/></td>
- <td><input type="radio" name="@group" value=""/></td>
+ <td><input type="radio" name="@sort" value="" tal:attributes="checked python:sort_on == ''" /></td>
+ <td><input type="radio" name="@group" value="" tal:attributes="checked python:group_on == ''" /></td>
 </tr>
 
 <tr>
Index: board/html/_generic.item.html
===================================================================
--- board/html/_generic.item.html	(revision 88877)
+++ board/html/_generic.item.html	(working copy)
@@ -44,7 +44,12 @@
 
 </form>
 
-<tal:block tal:condition="context/id" tal:replace="structure context/history" />
+<tal:block tal:condition="context/id"
+    tal:define="limit python:[10, None][request.form.has_key('show_all_history')]"
+    tal:replace="structure python:context.history(limit=limit)" />
+<p tal:condition="not:exists:request/form/show_all_history" i18n:translate="">Showing 10 items.
+<a tal:attributes="href string:${context/_classname}${context/id}?show_all_history=yes">Show all history</a>
+(warning: this could be VERY long)</p>
 
 </div>
 
Index: board/schema.py
===================================================================
--- board/schema.py	(revision 88877)
+++ board/schema.py	(working copy)
@@ -80,6 +80,8 @@
              roles=String(),     # comma-separated string of Role names
              timezone=String())
 user.setkey("username")
+db.security.addPermission(name='Register', klass='user',
+                          description='User is allowed to register new user')
 
 # FileClass automatically gets this property in addition to the Class ones:
 #   content = String()    [saved to disk in <tracker home>/db/files/]
@@ -287,6 +289,9 @@
     description="User is allowed to view their own and public queries")
 for r in 'User', 'Board', 'Coordinator':
     db.security.addPermissionToRole(r, p)
+p = db.security.addPermission(name='Search', klass='query')
+for r in 'User', 'Board', 'Coordinator':
+    db.security.addPermissionToRole(r, p)
 p = db.security.addPermission(name='Edit', klass='query', check=edit_query,
     description="User is allowed to edit their queries")
 for r in 'User', 'Board', 'Coordinator':
@@ -315,7 +320,7 @@
 # Assign the appropriate permissions to the anonymous user's Anonymous
 # Role. Choices here are:
 # - Allow anonymous users to register
-#db.security.addPermissionToRole('Anonymous', 'Create', 'user')
+#db.security.addPermissionToRole('Anonymous', 'Register', 'user')
 
 # Allow anonymous users access to view issues (and the related, linked
 # information).
Index: security/html/style.css
===================================================================
--- security/html/style.css	(revision 88877)
+++ security/html/style.css	(working copy)
@@ -33,13 +33,6 @@
     #searchbox { display: none;}
 }
 
-#searchbox { float: right;}
-
-div#body-title {
-  float: left;
-}
-
-
 div#searchbox 
 {
   float: right;
@@ -456,7 +449,18 @@
   background-color: #ffffc0;
 }
 
+.calendar_display {
+  text-align: center;
+}
 
+.calendar_display td {
+  padding: 1px 4px 1px 4px;
+}
+
+.calendar_display .today {
+  background-color: #afafaf;
+}
+
 #demowarning {
    position: absolute;
    top: 10px;
Index: security/html/page.html
===================================================================
--- security/html/page.html	(revision 88877)
+++ security/html/page.html	(working copy)
@@ -130,7 +130,7 @@
        </li>
        <li>
        <a href="user?@template=register"
-          tal:condition="python:request.user.hasPermission('Create', 'user')"
+          tal:condition="python:request.user.hasPermission('Register', 'user')"
           i18n:translate="">Register</a>
 	</li>
        <li><a href="user?@template=forgotten" i18n:translate="">Lost&nbsp;your&nbsp;login?</a>
@@ -283,7 +283,7 @@
   <input tal:attributes="value python:request.form.getvalue(name) or nothing;
                          name name;
                          id name"/>
-  <span tal:replace="structure python:db.issue.classhelp(columns,
+  <span tal:replace="structure python:db[db_klass].classhelp(columns,
                                       property=name)" />
 </td>
 
@@ -299,6 +299,22 @@
   </select>
 </td>
 
+<td metal:define-macro="search_select_keywords">
+  <div tal:attributes="id python:'''keywords_%s'''%name">
+    <select tal:attributes="name name; id name"
+            tal:define="value python:request.form.getvalue(name)">
+      <option value="" i18n:translate="">don't care</option>
+      <metal:slot define-slot="extra_options" />
+      <option value="" i18n:translate="" disabled="disabled">------------</option>
+      <option tal:repeat="s python:db[db_klass].list()"
+              tal:attributes="value s/id; selected python:value == s.id"
+              tal:content="python:s[db_content]"></option>
+    </select>
+    <a class="classhelp"
+	   tal:attributes="href python:'''javascript:help_window('issue?@template=keywords_expr&property=%s&form=itemSynopsis', 350, 200)'''%name">(expr)</a>
+  </div>
+</td>
+
 <!-- like search_select, but translates the further values.
 Could extend it (METAL 1.1 attribute "extend-macro")
 -->
Index: security/html/_generic.index.html
===================================================================
--- security/html/_generic.index.html	(revision 88877)
+++ security/html/_generic.index.html	(working copy)
@@ -37,7 +37,8 @@
 
 <p class="form-help">
  Remove entries by deleting their line. Add new entries by appending
- them to the table - put an X in the id column.
+ them to the table - put an X in the id column. If you wish to restore a
+ removed item and you know its id then just put that id in the id column.
 </p>
 </tal:block>
 <form onSubmit="return submit_once()" method="POST"
Index: security/html/issue.search.html
===================================================================
--- security/html/issue.search.html	(revision 88877)
+++ security/html/issue.search.html	(working copy)
@@ -12,10 +12,10 @@
    cols python:request.columns or 'id activity title status assignedto'.split();
    sort_on python:request.sort and request.sort[0] or nothing;
    sort_desc python:sort_on and sort_on[0] == '-';
-   sort_on python:(sort_on and sort_on[1]) or 'activity';
+   sort_on python:(sort_on and sort_on[1]) or (not request.nodeid and 'activity') or '';
    group_on python:request.group and request.group[0] or nothing;
    group_desc python:group_on and group_on[0] == '-';
-   group_on python:(group_on and group_on[1]) or 'priority';
+   group_on python:(group_on and group_on[1]) or (not request.nodeid and 'priority') or '';
 
    search_input templates/page/macros/search_input;
    search_date templates/page/macros/search_date;
@@ -23,6 +23,7 @@
    sort_input templates/page/macros/sort_input;
    group_input templates/page/macros/group_input;
    search_select templates/page/macros/search_select;
+   search_select_keywords templates/page/macros/search_select_keywords;
    search_select_translated templates/page/macros/search_select_translated;
    search_multiselect templates/page/macros/search_multiselect;">
 
@@ -191,7 +192,7 @@
                 db_klass string:keyword;
                 db_content string:name;">
   <th i18n:translate="">Keyword:</th>
-  <td metal:use-macro="search_select_translated">
+  <td metal:use-macro="search_select_keywords">
     <option metal:fill-slot="extra_options" value="-1" i18n:translate=""
             tal:attributes="selected python:value == '-1'">not set</option>
   </td>
@@ -244,8 +245,8 @@
  <th i18n:translate="">No Sort or group:</th>
  <td>&nbsp;</td>
  <td>&nbsp;</td>
- <td><input type="radio" name="@sort" value=""/></td>
- <td><input type="radio" name="@group" value=""/></td>
+ <td><input type="radio" name="@sort" value="" tal:attributes="checked python:sort_on == ''" /></td>
+ <td><input type="radio" name="@group" value="" tal:attributes="checked python:group_on == ''" /></td>
 </tr>
 
 <tr>
Index: security/html/_generic.item.html
===================================================================
--- security/html/_generic.item.html	(revision 88877)
+++ security/html/_generic.item.html	(working copy)
@@ -44,7 +44,12 @@
 
 </form>
 
-<tal:block tal:condition="context/id" tal:replace="structure context/history" />
+<tal:block tal:condition="context/id"
+    tal:define="limit python:[10, None][request.form.has_key('show_all_history')]"
+    tal:replace="structure python:context.history(limit=limit)" />
+<p tal:condition="not:exists:request/form/show_all_history" i18n:translate="">Showing 10 items.
+<a tal:attributes="href string:${context/_classname}${context/id}?show_all_history=yes">Show all history</a>
+(warning: this could be VERY long)</p>
 
 </div>
 
Index: security/schema.py
===================================================================
--- security/schema.py	(revision 88877)
+++ security/schema.py	(working copy)
@@ -87,6 +87,8 @@
              roles=String(),     # comma-separated string of Role names
              timezone=String())
 user.setkey("username")
+db.security.addPermission(name='Register', klass='user',
+                          description='User is allowed to register new user')
 
 # FileClass automatically gets this property in addition to the Class ones:
 #   content = String()    [saved to disk in <tracker home>/db/files/]
@@ -299,6 +301,9 @@
     description="User is allowed to view their own and public queries")
 for r in 'User', 'Developer', 'Coordinator':
     db.security.addPermissionToRole(r, p)
+p = db.security.addPermission(name='Search', klass='query')
+for r in 'User', 'Developer', 'Coordinator':
+    db.security.addPermissionToRole(r, p)
 p = db.security.addPermission(name='Edit', klass='query', check=edit_query,
     description="User is allowed to edit their queries")
 for r in 'User', 'Developer', 'Coordinator':
@@ -327,7 +332,7 @@
 # Assign the appropriate permissions to the anonymous user's Anonymous
 # Role. Choices here are:
 # - Allow anonymous users to register
-#db.security.addPermissionToRole('Anonymous', 'Create', 'user')
+#db.security.addPermissionToRole('Anonymous', 'Register', 'user')
 
 # Allow anonymous users access to view issues (and the related, linked
 # information).
Index: jython/html/style.css
===================================================================
--- jython/html/style.css	(revision 88877)
+++ jython/html/style.css	(working copy)
@@ -33,13 +33,6 @@
     #searchbox { display: none;}
 }
 
-#searchbox { float: right;}
-
-div#body-title {
-  float: left;
-}
-
-
 div#searchbox 
 {
   float: right;
@@ -453,7 +446,18 @@
   background-color: #ffffc0;
 }
 
+.calendar_display {
+  text-align: center;
+}
 
+.calendar_display td {
+  padding: 1px 4px 1px 4px;
+}
+
+.calendar_display .today {
+  background-color: #afafaf;
+}
+
 #demowarning {
    position: absolute;
    top: 10px;
Index: jython/html/page.html
===================================================================
--- jython/html/page.html	(revision 88877)
+++ jython/html/page.html	(working copy)
@@ -349,7 +349,7 @@
     string (eg. "id,title" or "id,name,description") as well as name
   -->
   <input tal:attributes="value python:request.form.getvalue(name) or nothing; name name; id name" />
-  <span tal:replace="structure python:db.issue.classhelp(columns, property=name)" />
+  <span tal:replace="structure python:db[db_klass].classhelp(columns, property=name)" />
 </td>
 <td metal:define-macro="search_select">
   <select tal:attributes="name name; id name"
@@ -363,6 +363,21 @@
     tal:content="python:s[db_content]"></option>
   </select>
 </td>
+<td metal:define-macro="search_select_keywords">
+  <div tal:attributes="id python:'''keywords_%s'''%name">
+    <select tal:attributes="name name; id name"
+            tal:define="value python:request.form.getvalue(name)">
+      <option value="" i18n:translate="">don't care</option>
+      <metal:slot define-slot="extra_options" />
+      <option value="" i18n:translate="" disabled="disabled">------------</option>
+      <option tal:repeat="s python:db[db_klass].list()"
+              tal:attributes="value s/id; selected python:value == s.id"
+              tal:content="python:s[db_content]"></option>
+    </select>
+    <a class="classhelp"
+      tal:attributes="href python:'''javascript:help_window('issue?@template=keywords_expr&property=%s&form=itemSynopsis', 350, 200)'''%name">(expr)</a>
+  </div>
+</td>
 <!-- like search_select, but translates the further values.
 Could extend it (METAL 1.1 attribute "extend-macro")
 -->
Index: jython/html/_generic.index.html
===================================================================
--- jython/html/_generic.index.html	(revision 88877)
+++ jython/html/_generic.index.html	(working copy)
@@ -37,7 +37,8 @@
 
 <p class="form-help">
  Remove entries by deleting their line. Add new entries by appending
- them to the table - put an X in the id column.
+ them to the table - put an X in the id column. If you wish to restore a
+ removed item and you know its id then just put that id in the id column.
 </p>
 </tal:block>
 <form onSubmit="return submit_once()" method="POST"
Index: jython/html/issue.search.html
===================================================================
--- jython/html/issue.search.html	(revision 88877)
+++ jython/html/issue.search.html	(working copy)
@@ -12,10 +12,10 @@
    cols python:request.columns or 'id activity title status assignedto'.split();
    sort_on python:request.sort and request.sort[0] or nothing;
    sort_desc python:sort_on and sort_on[0] == '-';
-   sort_on python:(sort_on and sort_on[1]) or 'activity';
+   sort_on python:(sort_on and sort_on[1]) or (not request.nodeid and 'activity') or '';
    group_on python:request.group and request.group[0] or nothing;
    group_desc python:group_on and group_on[0] == '-';
-   group_on python:(group_on and group_on[1]) or 'priority';
+   group_on python:(group_on and group_on[1]) or (not request.nodeid and 'priority') or '';
 
    search_input templates/page/macros/search_input;
    search_date templates/page/macros/search_date;
@@ -23,6 +23,7 @@
    sort_input templates/page/macros/sort_input;
    group_input templates/page/macros/group_input;
    search_select templates/page/macros/search_select;
+   search_select_keywords templates/page/macros/search_select_keywords;
    search_select_translated templates/page/macros/search_select_translated;
    search_multiselect templates/page/macros/search_multiselect;">
 
@@ -191,9 +192,9 @@
                 db_klass string:keyword;
                 db_content string:name;">
   <th i18n:translate="">Keyword:</th>
-  <td metal:use-macro="search_select_translated">
+  <td metal:use-macro="search_select_keywords">
     <option metal:fill-slot="extra_options" value="-1" i18n:translate=""
-            tal:attributes="selected python:value == '-1'">not set</option>
+            tal:attributes="selected python:value == '-1'">not selected</option>
   </td>
   <td metal:use-macro="column_input"></td>
   <td metal:use-macro="sort_input"></td>
@@ -244,8 +245,8 @@
  <th i18n:translate="">No Sort or group:</th>
  <td>&nbsp;</td>
  <td>&nbsp;</td>
- <td><input type="radio" name="@sort" value=""/></td>
- <td><input type="radio" name="@group" value=""/></td>
+ <td><input type="radio" name="@sort" value="" tal:attributes="checked python:sort_on == ''" /></td>
+ <td><input type="radio" name="@group" value="" tal:attributes="checked python:group_on == ''" /></td>
 </tr>
 
 <tr>
Index: jython/html/_generic.item.html
===================================================================
--- jython/html/_generic.item.html	(revision 88877)
+++ jython/html/_generic.item.html	(working copy)
@@ -44,7 +44,12 @@
 
 </form>
 
-<tal:block tal:condition="context/id" tal:replace="structure context/history" />
+<tal:block tal:condition="context/id"
+    tal:define="limit python:[10, None][request.form.has_key('show_all_history')]"
+    tal:replace="structure python:context.history(limit=limit)" />
+<p tal:condition="not:exists:request/form/show_all_history" i18n:translate="">Showing 10 items.
+<a tal:attributes="href string:${context/_classname}${context/id}?show_all_history=yes">Show all history</a>
+(warning: this could be VERY long)</p>
 
 </div>
 
Index: jobs/html/style.css
===================================================================
--- jobs/html/style.css	(revision 88877)
+++ jobs/html/style.css	(working copy)
@@ -33,13 +33,6 @@
     #searchbox { display: none;}
 }
 
-#searchbox { float: right;}
-
-div#body-title {
-  float: left;
-}
-
-
 div#searchbox 
 {
   float: right;
@@ -452,7 +445,18 @@
   background-color: #ffffc0;
 }
 
+.calendar_display {
+  text-align: center;
+}
 
+.calendar_display td {
+  padding: 1px 4px 1px 4px;
+}
+
+.calendar_display .today {
+  background-color: #afafaf;
+}
+
 #demowarning {
    position: absolute;
    top: 10px;
Index: jobs/html/page.html
===================================================================
--- jobs/html/page.html	(revision 88877)
+++ jobs/html/page.html	(working copy)
@@ -272,7 +272,7 @@
   <input tal:attributes="value python:request.form.getvalue(name) or nothing;
                          name name;
                          id name"/>
-  <span tal:replace="structure python:db.offer.classhelp(columns,
+  <span tal:replace="structure python:db[db_klass].classhelp(columns,
                                       property=name)" />
 </td>
 
@@ -288,6 +288,22 @@
   </select>
 </td>
 
+<td metal:define-macro="search_select_keywords">
+  <div tal:attributes="id python:'''keywords_%s'''%name">
+    <select tal:attributes="name name; id name"
+            tal:define="value python:request.form.getvalue(name)">
+      <option value="" i18n:translate="">don't care</option>
+      <metal:slot define-slot="extra_options" />
+      <option value="" i18n:translate="" disabled="disabled">------------</option>
+      <option tal:repeat="s python:db[db_klass].list()"
+              tal:attributes="value s/id; selected python:value == s.id"
+              tal:content="python:s[db_content]"></option>
+    </select>
+    <a class="classhelp"
+	   tal:attributes="href python:'''javascript:help_window('issue?@template=keywords_expr&property=%s&form=itemSynopsis', 350, 200)'''%name">(expr)</a>
+  </div>
+</td>
+
 <!-- like search_select, but translates the further values.
 Could extend it (METAL 1.1 attribute "extend-macro")
 -->
Index: jobs/html/_generic.index.html
===================================================================
--- jobs/html/_generic.index.html	(revision 88877)
+++ jobs/html/_generic.index.html	(working copy)
@@ -37,7 +37,8 @@
 
 <p class="form-help">
  Remove entries by deleting their line. Add new entries by appending
- them to the table - put an X in the id column.
+ them to the table - put an X in the id column. If you wish to restore a
+ removed item and you know its id then just put that id in the id column.
 </p>
 </tal:block>
 <form onSubmit="return submit_once()" method="POST"
Index: jobs/html/offer.search.html
===================================================================
--- jobs/html/offer.search.html	(revision 88877)
+++ jobs/html/offer.search.html	(working copy)
@@ -12,10 +12,10 @@
    cols python:request.columns or 'id activity title status assignedto'.split();
    sort_on python:request.sort and request.sort[0] or nothing;
    sort_desc python:sort_on and sort_on[0] == '-';
-   sort_on python:(sort_on and sort_on[1]) or 'activity';
+   sort_on python:(sort_on and sort_on[1]) or (not request.nodeid and 'activity') or '';
    group_on python:request.group and request.group[0] or nothing;
    group_desc python:group_on and group_on[0] == '-';
-   group_on python:(group_on and group_on[1]) or 'status';
+   group_on python:(group_on and group_on[1]) or (not request.nodeid and 'priority') or '';
 
    search_input templates/page/macros/search_input;
    search_date templates/page/macros/search_date;
@@ -156,8 +156,8 @@
  <th i18n:translate="">No Sort or group:</th>
  <td>&nbsp;</td>
  <td>&nbsp;</td>
- <td><input type="radio" name="@sort" value=""/></td>
- <td><input type="radio" name="@group" value=""/></td>
+ <td><input type="radio" name="@sort" value="" tal:attributes="checked python:sort_on == ''" /></td>
+ <td><input type="radio" name="@group" value="" tal:attributes="checked python:group_on == ''" /></td>
 </tr>
 
 <tr>
Index: jobs/html/_generic.item.html
===================================================================
--- jobs/html/_generic.item.html	(revision 88877)
+++ jobs/html/_generic.item.html	(working copy)
@@ -44,7 +44,12 @@
 
 </form>
 
-<tal:block tal:condition="context/id" tal:replace="structure context/history" />
+<tal:block tal:condition="context/id"
+    tal:define="limit python:[10, None][request.form.has_key('show_all_history')]"
+    tal:replace="structure python:context.history(limit=limit)" />
+<p tal:condition="not:exists:request/form/show_all_history" i18n:translate="">Showing 10 items.
+<a tal:attributes="href string:${context/_classname}${context/id}?show_all_history=yes">Show all history</a>
+(warning: this could be VERY long)</p>
 
 </div>
 

From metatracker at psf.upfronthosting.co.za  Tue Aug  9 05:38:00 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Tue, 09 Aug 2011 03:38:00 +0000
Subject: [Tracker-discuss] [issue413] Mercurial integration: impossible to
	remove a repo
In-Reply-To: <1312642098.58.0.714079362013.issue413@psf.upfronthosting.co.za>
Message-ID: <1312861080.52.0.23474428907.issue413@psf.upfronthosting.co.za>


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

The error seems pretty clear to me :)
Should be fixed in r88879.

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

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

From metatracker at psf.upfronthosting.co.za  Tue Aug  9 15:50:29 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Tue, 09 Aug 2011 13:50:29 +0000
Subject: [Tracker-discuss] [issue413] Mercurial integration: impossible to
	remove a repo
In-Reply-To: <1312642098.58.0.714079362013.issue413@psf.upfronthosting.co.za>
Message-ID: <1312897829.69.0.937298196124.issue413@psf.upfronthosting.co.za>


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

*reads the checkin email*
Oh, I see :)  Thanks.

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

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

From metatracker at psf.upfronthosting.co.za  Wed Aug 10 18:10:58 2011
From: metatracker at psf.upfronthosting.co.za (Feth AREZKI)
Date: Wed, 10 Aug 2011 16:10:58 +0000
Subject: [Tracker-discuss] [issue416] Show bug status with a nice
	colour/image
Message-ID: <1312992658.94.0.650426627964.issue416@psf.upfronthosting.co.za>


New submission from Feth AREZKI <feth at tuttu.info>:

In order to increase legibility on the bugtracker, I would like nice icons to visually signal the status and/or priority of an issue.

A smaller version (16x16?) could be displayed in the leftmost column the HTML listing (and we'd keep the written version).
A large version (64x64?) could be displayed on the page of the issue.

I suggest using stock icons from openclipart or the like, such as:

- open: open folder
- closed: closed folder
- resolved: tick
?

Priority could be represented altogether with badges on the large icon:

- urgent: clock
- important: exclamation mark sign
- wish: wand?
?

What do you think?

----------
messages: 2213
nosy: feth
priority: wish
status: unread
title: Show bug status with a nice colour/image

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

From metatracker at psf.upfronthosting.co.za  Wed Aug 10 18:25:42 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Wed, 10 Aug 2011 16:25:42 +0000
Subject: [Tracker-discuss] [issue416] Show bug status with a nice
	colour/image
In-Reply-To: <1312992658.94.0.650426627964.issue416@psf.upfronthosting.co.za>
Message-ID: <1312993542.16.0.762049366285.issue416@psf.upfronthosting.co.za>


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

While I agree that icons might be helpful (especially in the search page), I think most of the developers will find them distracting and would rather prefer a simple and clean look without icons and colors.

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

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

From metatracker at psf.upfronthosting.co.za  Thu Aug 11 03:18:46 2011
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Thu, 11 Aug 2011 01:18:46 +0000
Subject: [Tracker-discuss] [issue416] Show bug status with a nice
	colour/image
In-Reply-To: <1312992658.94.0.650426627964.issue416@psf.upfronthosting.co.za>
Message-ID: <1313025526.2.0.350873336647.issue416@psf.upfronthosting.co.za>


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

Count me as one of those developers who find icons distracting.

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

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

From metatracker at psf.upfronthosting.co.za  Fri Aug 12 07:04:46 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Fri, 12 Aug 2011 05:04:46 +0000
Subject: [Tracker-discuss] [issue417] Add autocomplete for the nosy list
Message-ID: <1313125486.66.0.367655724531.issue417@psf.upfronthosting.co.za>


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

The attached patch adds an autocomplete to the nosy list.

TL;DR: see screenshot.

This is how it works:
  * server-side, the entries are taken from 2 places:
    1) the experts index of the devguide.  This is done downloading and
       parsing the rst source.  The new user.experts.html page returns
       this data as JSON.
    2) the list of committers from the Roundup database.  This is done
       retrieving the username and realname from the database.  The new
       user.devs.html page returns this data as JSON to logged in users.
    The Python code to retrieve this data and convert to JSON is in a
    new extension called jnosy.py.

  * client-side, when the page loads, the browser:
    1) checks if the two JSON files are cached in the HTML5 storage;
    2) if HTML storage is not supported or if they are not cached,
       it requests from the JSON from the server (through the two
       user.*.html pages), and possibly caches the result;
    3) the two JSON files are adapted and combined, in order to
       form a list of entries for the autocomplete.

When the user writes in the nosy list, the autocomplete will list all the elements that match divided by category.
The categories are the ones of the experts index (one per table), plus a "developer" category.
The "developer" entries are listed first, and look like "Name Surname (username)".  Once selected, only the username is added to the nosy.
The "experts" entries list the name of the module/interest area/etc. followed by the list of names (e.g. 'unittest: michael.foord,ezio.melotti'), and once selected it adds all the names to the nosy.

A few more random comments about the patch:
  * HTML5 storage allows the script to save data on the client's
    machine and it's available on all the major browsers (FF3.5+,
    IE8+, Chrome4+, Opera10.5+, Safari4+).
  * If the HTML5 storage is not available the script will request
    the data from the server, once for each issue page visited
    (all the data are downloaded only once when the page loads).
  * Both the pages return less than 5 kB of JSON, and both seem
    quite fast.
  * If JS is not available the autocomplete is not available, with
    no other side effects.
  * Having autocomplete for all the registered users, even if 
    technically doable, has two major problems:
    1) it takes about 10s for the server to put together a JSON
       object with all the names and usernames of 10k+ users and
       send it to the client (that's about 200+ kB of JSON);
    2) it's probably really slow to process on the client-side
       and it will flood the autocomplete with lot of matching
       names (I haven't tried it though).
  * The user.devs.html page is not visible to not-logged in users.
  * Some server-side caching should be added, so that at least the
    expert page is not downloaded and parsed every time.
    I'm not sure if this should be done via the Cache-Control
    and/or Expires HTTP headers (that would prevent the browsers
    to send requests at all), or just keep the generated JSON
    in memory or in a local file, and update it, say, once a day.
  * The HTML5 storage cache should also be invalidated after a
    while, and the JSON requested again to the server.
  * Instead of having two separates files, a single file that
    returns a single JSON object with both developers and experts
    can be used.

Unless there are problems with this design, I'll commit it and see what the users think about it.

----------
assignedto: ezio.melotti
files: issue417.diff
messages: 2216
nosy: ezio.melotti
priority: feature
status: in-progress
title: Add autocomplete for the nosy list

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue417>
_______________________________________________________
-------------- next part --------------
Index: extensions/jnosy.py
===================================================================
--- extensions/jnosy.py	(revision 0)
+++ extensions/jnosy.py	(revision 0)
@@ -0,0 +1,84 @@
+"""
+This module provides two helper functions used by the Javascript autocomplete
+of the nosy list:
+  1) a simple state machine to parse the tables of the
+     experts index and turn them in a JSON object;
+  2) a function to get the list of developers as a JSON object;
+"""
+
+import urllib
+try:
+    import json
+except ImportError:
+    import simplejson as json
+
+url = 'http://hg.python.org/devguide/raw-file/default/experts.rst'
+
+# possible states
+no_table = 0  # not parsing a table
+table_header = 1  # parsing the header
+table_content = 2  # parsing the content
+table_end = 3  # reached the end of the table
+
+def experts_as_json():
+    """
+    Parse the tables of the experts index and turn them into a JSON object.
+    """
+    data = {}
+    table_state = no_table
+
+    try:
+        page = urllib.urlopen(url)
+    except Exception:
+        # if something goes wrong just return an empty JSON object
+        return '{}'
+
+    for line in page:
+        columns = [column.strip() for column in line.split('  ', 1)]
+        # all the tables have 2 columns (some entries might not have experts,
+        # so we just skip them)
+        if len(columns) != 2:
+            continue
+        first, second = columns
+        # check if we found a table separator
+        if set(first) == set(second) == set('='):
+            table_state += 1
+            if table_state == table_end:
+                table_state = no_table
+            continue
+        if table_state == table_header:
+            # create a dict for the category (e.g. 'Modules', 'Interest areas')
+            category = first
+            data[category] = {}
+        if table_state == table_content:
+            # add to the category dict the entries for that category
+            # (e.g.module names) and the list of experts
+            # if the entry is empty the names belong to the previous entry
+            entry = first or entry
+            names = (name.strip(' *') for name in second.split(','))
+            names = ','.join(name for name in names if '(inactive)' not in name)
+            if not first:
+                data[category][entry] += names
+            else:
+                data[category][entry] = names
+    return json.dumps(data, separators=(',',':'))
+
+
+def devs_as_json(cls):
+    """
+    Generate a JSON object that contains the username and realname of all
+    the committers.
+    """
+    users = []
+    for user in cls.filter(None, {'iscommitter': 1}):
+        username = user.username.plain()
+        realname = user.realname.plain(unchecked=1)
+        if not realname:
+            continue
+        users.append([username, realname])
+    return json.dumps(users, separators=(',',':'))
+
+
+def init(instance):
+    instance.registerUtil('experts_as_json', experts_as_json)
+    instance.registerUtil('devs_as_json', devs_as_json)
Index: html/issue.item.js
===================================================================
--- html/issue.item.js	(revision 88880)
+++ html/issue.item.js	(working copy)
@@ -62,3 +62,153 @@
         }
     });
 })
+
+$(document).ready(function() {
+    /* Add an autocomplete to the nosy list that searches the term in two lists:
+         1) the list of users (both the user and the real name);
+         2) the list of experts in the devguide;
+       Note: most of this code comes from the "categories" and "multiple values"
+             examples in http://jqueryui.com/demos/autocomplete/. */
+
+    // create a custom widget to group the entries in categories
+    $.widget("custom.catcomplete", $.ui.autocomplete, {
+        _renderMenu: function(ul, items) {
+            var self = this, current_category = "";
+            // loop through the items, adding a <li> when a new category is
+            // found, and then render the item in the <ul>
+            $.each(items, function(index, item) {
+                if (item.category != current_category) {
+                    ul.append("<li class='ui-autocomplete-category'>" + item.category + "</li>");
+                    current_category = item.category;
+                }
+                self._renderItem(ul, item);
+            });
+        }
+    });
+
+    function split(val) {
+        return val.split(/,\s*/);
+    }
+    function extractLast(term) {
+        return split(term).pop();
+    }
+
+    // this will be called once we have retrieved the data
+    function add_autocomplete(data) {
+        $("[name=nosy]")
+            // don't navigate away from the field on tab when selecting an item
+            .bind("keydown", function(event) {
+                if (event.keyCode === $.ui.keyCode.TAB &&
+                        $(this).data("autocomplete").menu.active) {
+                    event.preventDefault();
+                }
+            })
+            .catcomplete({
+                minLength: 2, // this doesn't seem to work
+                delay: 0,
+                source: function(request, response) {
+                    // delegate back to autocomplete, but extract the last term
+                    response($.ui.autocomplete.filter(
+                        data, extractLast(request.term)));
+                },
+                focus: function() {
+                    // prevent value inserted on focus
+                    return false;
+                },
+                select: function(event, ui) {
+                    var terms = split(this.value);
+                    // remove the current input
+                    terms.pop();
+                    // add the selected item
+                    terms.push(ui.item.value);
+                    // add placeholder to get the comma at the end
+                    terms.push("");
+                    this.value = terms.join(",") ;
+                    return false;
+                }
+            });
+    }
+
+
+    // check if we have HTML5 storage available
+    try {
+        var supports_html5_storage = !!localStorage.getItem;
+    } catch(e) {
+        var supports_html5_storage = false;
+    }
+    alert('storage ' + supports_html5_storage);
+
+    // this object receives the entries for the devs and experts and
+    // when it has both it calls add_autocomplete
+    var data = {
+        devs: null,
+        experts: null,
+        add: function(data, type) {
+            // type is either 'devs' or 'experts'
+            this[type] = data;
+            if (this.devs && this.experts)
+                add_autocomplete(this.devs.concat(this.experts))
+        }
+    };
+
+    /* Note: instead of using a nested structure like:
+       {"Platform": {"plat1": "name1,name2", "plat2": "name3,name4", ...},
+        "Module": {"mod1": "name1,name2", "mod2": "name3,name4", ...},
+        ...}
+       (i.e. the same format sent by the server), we have to flat it down and
+       repeat the category for each entry, because the autocomplete wants a
+       flat structure like:
+       [{label: "plat1: name1,name2", value: "name1,name2", category: "Platform"},
+        {label: "plat2: name3,name4", value: "name3,name4", category: "Platform"},
+        {label: "mod1: name1,name2", value: "name1,name2", category: "Module"},
+        {label: "mod2: name3,name4", value: "name3,name4", category: "Module"},
+        ...].
+       Passing a nested structure to ui.autocomplete.filter() and attempt
+       further parsing in _renderMenu doesn't seem to work.
+    */
+    function get_json(file, callback) {
+        // Get the JSON from either the HTML5 storage or the server.
+        //   file is either 'devs' or 'experts',
+        //   the callback is called once the json is retrieved
+        var json;
+        if (supports_html5_storage &&
+                (json = localStorage[file]) != null) {
+            // if we have HTML5 storage and already cached the JSON, use it
+            callback(JSON.parse(json), file);
+        }
+        else {
+            // if we don't have HTML5 storage or the cache is empty, request
+            // the JSON to the server
+            $.getJSON('user?@template='+file, function(rawdata) {
+                var objects = []; // array of objs with label, value, category
+                if (file == 'devs') {
+                    // save devs as 'Name Surname (user.name)'
+                    $.each(users, function(index, names) {
+                        objects.push({label: names[1] + ' (' + names[0] + ')',
+                                      value: names[0], category: 'Developer'});
+                    });
+                }
+                else {
+                    // save experts as e.g. 'modname: user1,user2'
+                    $.each(rawdata, function(category, entries) {
+                        $.each(entries, function(entry, names) {
+                            objects.push({label: entry + ': ' + names,
+                                          value: names, category: category});
+                        });
+                    });
+                }
+                // cache the objects if we have HTML5 storage
+                if (supports_html5_storage)
+                    localStorage[file] = JSON.stringify(objects);
+                callback(objects, file);
+            });
+        }
+    }
+
+    // request the JSON.  This will get it from the HTML5 storage if it's there
+    // or request it to the server if it's not,  The JSON will be passed to the
+    // data object, that will wait to get both the files before calling the
+    // add_autocomplete function.
+    get_json('experts', data.add);
+    get_json('devs', data.add);
+});
Index: html/user.experts.html
===================================================================
--- html/user.experts.html	(revision 0)
+++ html/user.experts.html	(revision 0)
@@ -0,0 +1,5 @@
+<tal:block content="python:utils.experts_as_json()">
+{"Platform":{"platname":"name1,name2",...},
+ "Module":{"modname":"name1,name2",...},
+ ...}
+</tal:block>
Index: html/user.devs.html
===================================================================
--- html/user.devs.html	(revision 0)
+++ html/user.devs.html	(revision 0)
@@ -0,0 +1,4 @@
+<tal:block tal:condition="context/is_view_ok"
+           content="python:utils.devs_as_json(context)">
+    [["username1","Real Name1"],["username2", "Real Name2"],...]
+</tal:block>
Index: html/issue.item.html
===================================================================
--- html/issue.item.html	(revision 88880)
+++ html/issue.item.html	(working copy)
@@ -11,8 +11,11 @@
 </title>
 
 <metal:slot fill-slot="more-javascript">
-<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.6.1/jquery.min.js"></script>
+<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.6.2/jquery.min.js"></script>
+<script type="text/javascript"
+src="http://ajax.googleapis.com/ajax/libs/jqueryui/1.8.15/jquery-ui.js"></script>
 <script type="text/javascript" src="@@file/issue.item.js"></script>
+<link rel="stylesheet" type="text/css"  href="http://ajax.googleapis.com/ajax/libs/jqueryui/1.8/themes/smoothness/jquery-ui.css" />
 </metal:slot>
 
 <tal:block metal:fill-slot="body_title">
Index: html/style.css
===================================================================
--- html/style.css	(revision 88880)
+++ html/style.css	(working copy)
@@ -513,3 +513,16 @@
 .calendar_display .today {
   background-color: #afafaf;
 }
+
+.ui-autocomplete-category {
+    font-weight: bold;
+    padding: 0 .2em;
+    line-height: 1.2;
+}
+
+.ui-autocomplete {
+    font-size: 75% !important;
+    max-height: 25em;
+    max-width: 20em;
+    overflow: auto;
+}

From metatracker at psf.upfronthosting.co.za  Sat Aug 13 10:06:11 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sat, 13 Aug 2011 08:06:11 +0000
Subject: [Tracker-discuss] [issue417] Add autocomplete for the nosy list
In-Reply-To: <1313125486.66.0.367655724531.issue417@psf.upfronthosting.co.za>
Message-ID: <1313222771.05.0.671012359959.issue417@psf.upfronthosting.co.za>


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

I committed an updated version in r88881.  The things I changed are:
  * the autocomplete is not loaded anymore if the user can't edit the nosy;
  * names are added only once, duplicated are now discarded;
  * if the JSON in the local storage is older than one day, it will be downloaded again;

----------
status: in-progress -> testing

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

From metatracker at psf.upfronthosting.co.za  Sun Aug 14 08:57:47 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sun, 14 Aug 2011 06:57:47 +0000
Subject: [Tracker-discuss] [issue416] Show bug status with a nice
	colour/image
In-Reply-To: <1312992658.94.0.650426627964.issue416@psf.upfronthosting.co.za>
Message-ID: <1313305067.31.0.86562436129.issue416@psf.upfronthosting.co.za>


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

I also think that adding icons would be no improvement. In addition, I find the proposed icons counter-intuitive: an "open bug report" is open in a different way than an "open folder".

Resolving this as "won't fix".
feth: if you find people supporting your idea, we may reconsider.

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

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

From metatracker at psf.upfronthosting.co.za  Mon Aug 15 11:05:15 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Mon, 15 Aug 2011 09:05:15 +0000
Subject: [Tracker-discuss] [issue417] Add autocomplete for the nosy list
In-Reply-To: <1313125486.66.0.367655724531.issue417@psf.upfronthosting.co.za>
Message-ID: <1313399115.84.0.746483233423.issue417@psf.upfronthosting.co.za>


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

No one complained yet, so I documented it in the devguide and I'm closing this.

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

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

From metatracker at psf.upfronthosting.co.za  Mon Aug 15 11:15:49 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Mon, 15 Aug 2011 09:15:49 +0000
Subject: [Tracker-discuss] [issue296] XSS vulnerability in ok_message
In-Reply-To: <1248205874.61.0.225589760626.issue296@psf.upfronthosting.co.za>
Message-ID: <1313399749.92.0.907874565221.issue296@psf.upfronthosting.co.za>


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

Now the XSS vulnerability should be fixed (see #411), e.g.:
issue?@template=<b>xss</b>
issue?@ok_message=<script>alert('xss');</script>
issue?@error_message=<script>alert('xss');</script>

the ok_message supports a few tags, like <b> and <br>, but not <script>.
If you can find any way to make the script work, please reopen this.

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

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

From metatracker at psf.upfronthosting.co.za  Mon Aug 15 11:23:11 2011
From: metatracker at psf.upfronthosting.co.za (Victor Stinner)
Date: Mon, 15 Aug 2011 09:23:11 +0000
Subject: [Tracker-discuss] [issue418] Change background color if an issue is
	closed
Message-ID: <1313400191.88.0.747529213931.issue418@psf.upfronthosting.co.za>


New submission from Victor Stinner <victor.stinner at haypocalc.com>:

It is difficult for me to see if an issue is open or close if I read an issue too quickly. It's a least the third time that I comment a closed issue by mistake.

----------
messages: 2221
nosy: haypo
priority: feature
status: unread
title: Change background color if an issue is closed

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

From metatracker at psf.upfronthosting.co.za  Mon Aug 15 11:26:40 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Mon, 15 Aug 2011 09:26:40 +0000
Subject: [Tracker-discuss] [issue418] Change background color if an issue is
	closed
In-Reply-To: <1313400191.88.0.747529213931.issue418@psf.upfronthosting.co.za>
Message-ID: <1313400400.86.0.476306354193.issue418@psf.upfronthosting.co.za>


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

Attached a few possibilities to make the "closed" status more evident.
I like the version 4, but it might not be evident enough.
The version 1 is also OK IMHO.  I don't like versions 2 and 3 too much.

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

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

From metatracker at psf.upfronthosting.co.za  Sat Aug 20 02:08:51 2011
From: metatracker at psf.upfronthosting.co.za (Ross Anderson)
Date: Sat, 20 Aug 2011 00:08:51 +0000
Subject: [Tracker-discuss] [issue419] Blank Field
Message-ID: <1313798931.82.0.939144004553.issue419@psf.upfronthosting.co.za>


New submission from Ross Anderson <andersonseven at xtra.co.nz>:

In Python 2.7.2 when you go into options in the pull down window and there's only one option to choose. then under the general tab you get to choose the screen width and height and you choose a blank for both. then go apply. then exit out of python then start python 2.7.2 it hangs and won't start. I've tried reinstalling the program and also downloading python 3.2.1 and installing that but the same problem appears. help

----------
assignedto: Ross Anderson
messages: 2223
nosy: Ross Anderson
priority: bug
status: unread
title: Blank Field

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

From metatracker at psf.upfronthosting.co.za  Sat Aug 20 09:36:12 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sat, 20 Aug 2011 07:36:12 +0000
Subject: [Tracker-discuss] [issue419] Blank Field
In-Reply-To: <1313798931.82.0.939144004553.issue419@psf.upfronthosting.co.za>
Message-ID: <1313825772.46.0.123414928486.issue419@psf.upfronthosting.co.za>


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

I'm not sure what are you referring to here (maybe IDLE?).
This meta tracker is about problems of the Python bug tracker at bugs.python.org.
If you think you have found a bug with Python and/or IDLE you should report it there instead (providing some more context so it's clear what you are talking about), or even better ask on some mailing list / forum / IRC channel and make sure that it's really a bug.  If you have this problem with some application written in Python you should report it on the bug tracker used by that application.

----------
assignedto: Ross Anderson -> ezio.melotti
nosy: +ezio.melotti
status: unread -> resolved

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

From metatracker at psf.upfronthosting.co.za  Sat Aug 20 10:07:37 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sat, 20 Aug 2011 08:07:37 +0000
Subject: [Tracker-discuss] [issue336] 'problem encountered' message when
	giving invalid nosy	entry
In-Reply-To: <1272542446.94.0.703576196344.issue336@psf.upfronthosting.co.za>
Message-ID: <1313827657.94.0.384065804217.issue336@psf.upfronthosting.co.za>


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

This seems to be fixed now.
I tried the steps in the first message and now I get:
"""
Error: property nosy: 'facundo.batista' is not a user.
"""
Apparently this got fixed in Roundup in r4523 [0], after that I reported this problem in the Roundup issue #2550663 [1], and the update of Roundup (see #411) included this fix.

[0]: http://svn.roundup-tracker.org/viewvc/roundup/roundup/trunk/roundup/cgi/templating.py?r1=4519&r2=4523
[1]: http://issues.roundup-tracker.org/issue2550663

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

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

From metatracker at psf.upfronthosting.co.za  Sat Aug 20 10:24:57 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sat, 20 Aug 2011 08:24:57 +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: <1313828697.87.0.181982358097.issue298@psf.upfronthosting.co.za>


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

The autocomplete I added to the nosy list (see #417) has a case-insensitive search that works for both usernames and real names of committers.
It's only available when Javascript is active though.
It works with non-ASCII chars (e.g. searching for '?ric' finds '?ric' too), but it doesn't strip accents (e.g. searching for 'Ziade' won't find 'Ziad?').
I don't think it's worth spending more time trying to fix the normal search too, so I'm closing this.

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

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

From metatracker at psf.upfronthosting.co.za  Sat Aug 20 10:30:13 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sat, 20 Aug 2011 08:30:13 +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: <1313829013.74.0.140852098707.issue343@psf.upfronthosting.co.za>


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

This is now (partially) solved by the nosy autocomplete (see #417 and #298).
I was thinking about removing the '(list)' from the nosy when the autocomplete is active too.  If the autocomplete is not active the '(list)' will still be available.

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

From metatracker at psf.upfronthosting.co.za  Sat Aug 20 10:42:32 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sat, 20 Aug 2011 08:42:32 +0000
Subject: [Tracker-discuss] [issue411] Roundup instance is outdated
In-Reply-To: <1311602492.71.0.972062932119.issue411@psf.upfronthosting.co.za>
Message-ID: <1313829752.55.0.108356393635.issue411@psf.upfronthosting.co.za>


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

If the patch (all_inst1-4-19.diff) is OK, I'll commit it soon (without the python-dev-spambayes-integration).

Note that there are also changes in the schema.py and that I can't test them on my machine.

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

From metatracker at psf.upfronthosting.co.za  Sat Aug 20 14:51:20 2011
From: metatracker at psf.upfronthosting.co.za (Antoine Pitrou)
Date: Sat, 20 Aug 2011 12:51:20 +0000
Subject: [Tracker-discuss] [issue393] Security policy should be visible on
	top page of tracker, maybe every page
In-Reply-To: <1303048324.83.0.514918059654.issue393@psf.upfronthosting.co.za>
Message-ID: <1313844680.11.0.727579875666.issue393@psf.upfronthosting.co.za>


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

Judging from the response, it certainly seems there's no actice security team :)

----------
nosy: +pitrou

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

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


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

I wrote them to see if there's someone on the other side.
In http://bugs.python.org/issue12792 I proposed a doc patch to document security at python.org.
If they don't reply I'll just commit that patch and close this.

----------
assignedto:  -> ezio.melotti

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

From metatracker at psf.upfronthosting.co.za  Sun Aug 21 08:52:44 2011
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Sun, 21 Aug 2011 06:52:44 +0000
Subject: [Tracker-discuss] [issue393] Security policy should be visible on
	top page of tracker, maybe every page
In-Reply-To: <1303048324.83.0.514918059654.issue393@psf.upfronthosting.co.za>
Message-ID: <1313909564.3.0.734788115759.issue393@psf.upfronthosting.co.za>


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

Another way would be to find out if Roundup supports "private" issues that are not visible to default users. Then security could use these to track the security issues.

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

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

From metatracker at psf.upfronthosting.co.za  Sun Aug 21 09:56:50 2011
From: metatracker at psf.upfronthosting.co.za (Stephen Turnbull)
Date: Sun, 21 Aug 2011 07:56:50 +0000
Subject: [Tracker-discuss] [issue393] Security policy should be visible on
	top page of tracker, maybe every page
In-Reply-To: <1303048324.83.0.514918059654.issue393@psf.upfronthosting.co.za>
Message-ID: <1313913410.64.0.431506743869.issue393@psf.upfronthosting.co.za>


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

It's possible to do this, although I don't have a patch offhand.  The basic idea is that given in the attached patch, which uses the existing concepts of "assigned to" and "admin role" rather than a separate configurable group.  Probably you can just create a security role and substitute that check for "assigned to".

I don't know if deleting "admin" makes sense or not.  Of course admins can add the security role to themselves anyway, so convenience in dealing with security issues that need to be deleted because they're spam etc is one consideration.  OTOH, "if I don't need to know I don't wanna see it" is another factor.

Note that the patch defaults to privacy (which is appropriate in my situation).  Probably for Python you would want this dependent on the issue type or priority of "security".

I also don't know how secure this really is.  I know it's more secure than the people who are using it, which is good enough for me.<wink/>

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue393>
_______________________________________________________
-------------- next part --------------
diff --git a/html/issue.item.html b/html/issue.item.html
index 3a397c2..6e84f26 100644
--- a/html/issue.item.html
+++ b/html/issue.item.html
@@ -81,6 +81,10 @@ python:db.user.classhelp('username,realname,address', property='nosy', width='60
   <span tal:condition="context/is_edit_ok" tal:replace="structure python:db.keyword.classhelp(property='keyword')" />
  </td>
 </tr>
+<tr>
+ <th i18n:translate="">Public</th>
+ <td tal:content="structure context/ispublic/field">is issue public?</td>
+</tr>
 
 <tr tal:condition="context/is_edit_ok">
  <th i18n:translate="">Change Note</th>
diff --git a/schema.py b/schema.py
index 9c13df9..4db8c7f 100644
--- a/schema.py
+++ b/schema.py
@@ -75,7 +75,8 @@ issue = IssueClass(db, "issue",
                 assignedto=Link("user"),
                 keyword=Multilink("keyword"),
                 priority=Link("priority"),
-                status=Link("status"))
+                status=Link("status")
+                ispublic=Boolean())
 
 #
 # TRACKER SECURITY SETTINGS
@@ -90,9 +91,32 @@ issue = IssueClass(db, "issue",
 db.security.addPermissionToRole('User', 'Web Access')
 db.security.addPermissionToRole('User', 'Email Access')
 
+# Users should be able to edit and view their assigned issues. They
+# should also be able to view any marked as public. They should not
+# be able to edit others' issues, even if they're public.
+def view_issue(db, userid, itemid):
+    # ispublic checking not implemented yet
+    # if not db.issue.get(itemid, 'ispublic'): return True
+    return userid == db.issue.get(itemid, 'assignedto')
+def edit_issue(db, userid, itemid):
+    return userid == db.issue.get(itemid, 'assignedto')
+p = db.security.addPermission(name='View', klass='issue', check=view_issue,
+    description="User is allowed to view their own and public issues")
+db.security.addPermissionToRole('User', p)
+p = db.security.addPermission(name='Edit', klass='issue', check=edit_issue,
+    description="User is allowed to edit their issues")
+db.security.addPermissionToRole('User', p)
+p = db.security.addPermission(name='Retire', klass='issue', check=edit_issue,
+    description="User is allowed to retire their issues")
+db.security.addPermissionToRole('User', p)
+p = db.security.addPermission(name='Create', klass='issue',
+    description="User is allowed to create issues")
+db.security.addPermissionToRole('User', p)
+
 # Assign the access and edit Permissions for issue, file and message
-# to regular users now
-for cl in 'issue', 'file', 'msg', 'keyword':
+# to regular users now.  These are way too lenient for files and
+# messages, but it's unlikely that students will figure that out.
+for cl in 'file', 'msg', 'keyword':
     db.security.addPermissionToRole('User', 'View', cl)
     db.security.addPermissionToRole('User', 'Edit', cl)
     db.security.addPermissionToRole('User', 'Create', cl)

From metatracker at psf.upfronthosting.co.za  Sun Aug 21 13:58:04 2011
From: metatracker at psf.upfronthosting.co.za (Antoine Pitrou)
Date: Sun, 21 Aug 2011 11:58:04 +0000
Subject: [Tracker-discuss] [issue393] Security policy should be visible on
	top page of tracker, maybe every page
In-Reply-To: <1303048324.83.0.514918059654.issue393@psf.upfronthosting.co.za>
Message-ID: <1313927884.95.0.285238302405.issue393@psf.upfronthosting.co.za>


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

> Another way would be to find out if Roundup supports "private" issues that are 
> not visible to default users. Then security could use these to track the
> security issues.

Who would it be visible to? If the security team is pining for the trees, isn't this proposal unconstructive?

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

From metatracker at psf.upfronthosting.co.za  Sun Aug 21 16:04:38 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sun, 21 Aug 2011 14:04:38 +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: <1313935478.45.0.167578843189.issue298@psf.upfronthosting.co.za>


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

I don?t think it would be a waste of time to fix the normal search too.

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

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

From metatracker at psf.upfronthosting.co.za  Sun Aug 21 17:29:01 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sun, 21 Aug 2011 15:29:01 +0000
Subject: [Tracker-discuss] [issue418] Change background color if an issue is
	closed
In-Reply-To: <1313400191.88.0.747529213931.issue418@psf.upfronthosting.co.za>
Message-ID: <1313940541.87.0.623391587664.issue418@psf.upfronthosting.co.za>


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

I committed 6) after more discussion on IRC in r88885.  7) was YAGNI.

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

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

From metatracker at psf.upfronthosting.co.za  Sun Aug 21 19:47:13 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sun, 21 Aug 2011 17:47:13 +0000
Subject: [Tracker-discuss] [issue418] Change background color if an issue is
	closed
In-Reply-To: <1313400191.88.0.747529213931.issue418@psf.upfronthosting.co.za>
Message-ID: <1313948833.23.0.157197584228.issue418@psf.upfronthosting.co.za>


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

The most intrusive approach to prevent posting to a closed issue is to have an additional check box that needs to be checked if the issue is closed.

The check box would only appear if the issue is closed, and an auditor would prevent accepting the change (redisplaying the pre-filled form) if the user has failed to check the box.

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

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

From metatracker at psf.upfronthosting.co.za  Sun Aug 21 20:19:44 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sun, 21 Aug 2011 18:19:44 +0000
Subject: [Tracker-discuss] [issue418] Change background color if an issue is
	closed
In-Reply-To: <1313400191.88.0.747529213931.issue418@psf.upfronthosting.co.za>
Message-ID: <1313950784.35.0.834409944745.issue418@psf.upfronthosting.co.za>


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

I don't think the goal is to prevent that users comment on a closed issue, but rather just to signal it in some way so that they know that they are going to comment on a closed issue.

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

From metatracker at psf.upfronthosting.co.za  Sun Aug 21 15:32:05 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sun, 21 Aug 2011 13:32:05 +0000
Subject: [Tracker-discuss] [issue418] Change background color if an issue is
	closed
In-Reply-To: <1313400191.88.0.747529213931.issue418@psf.upfronthosting.co.za>
Message-ID: <1313933525.47.0.747019198553.issue418@psf.upfronthosting.co.za>


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

Attached another option.
It would be also possible to write "Issue closed by *username*, on *date-time*." but that's more involved (it needs some grepping through the issue history and an extension to do it -- the roundup-summary script has something similar).
It's also possible to add an orange "pending" (and possibly a green "open"), but that will just end up duplicating the information that it's already in the status field IMHO.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue418>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: closed-issue5.png
Type: image/png
Size: 33525 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20110821/3c43201f/attachment-0001.png>

From metatracker at psf.upfronthosting.co.za  Sun Aug 21 16:02:10 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sun, 21 Aug 2011 14:02:10 +0000
Subject: [Tracker-discuss] [issue418] Change background color if an issue is
	closed
In-Reply-To: <1313400191.88.0.747529213931.issue418@psf.upfronthosting.co.za>
Message-ID: <1313935330.35.0.378304251367.issue418@psf.upfronthosting.co.za>


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

After short discussion on IRC: bold and red is scary (people might see it as a warning that they shouldn't touch the issue anymore).
I painted it blue.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue418>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: closed-issue6.png
Type: image/png
Size: 33423 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20110821/95a696bc/attachment-0001.png>

From metatracker at psf.upfronthosting.co.za  Sun Aug 21 16:49:48 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sun, 21 Aug 2011 14:49:48 +0000
Subject: [Tracker-discuss] [issue418] Change background color if an issue is
	closed
In-Reply-To: <1313400191.88.0.747529213931.issue418@psf.upfronthosting.co.za>
Message-ID: <1313938188.87.0.931308506048.issue418@psf.upfronthosting.co.za>


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

Yet another version, that includes the name of the "closer" and the closing date.
This adds a new line, so it's more visible, but I still left the blue.  It can be removed too.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue418>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: closed-issue7.png
Type: image/png
Size: 35901 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20110821/3cef3726/attachment-0001.png>

From metatracker at psf.upfronthosting.co.za  Tue Aug 23 15:58:55 2011
From: metatracker at psf.upfronthosting.co.za (Nick Coghlan)
Date: Tue, 23 Aug 2011 13:58:55 +0000
Subject: [Tracker-discuss] [issue420] Display 'dependency of' and
	'superseder of'
Message-ID: <1314107935.82.0.0721577384536.issue420@psf.upfronthosting.co.za>


New submission from Nick Coghlan <ncoghlan at gmail.com>:

In adding the mailcap unit tests (issue #6494), I missed that there was another related issue (#9923) that fixed a minor bug on Windows that was picked up by the new tests.

When looking at an issue page, it would be nice to be able to see the other issues that are either dependent on or superseded by the current issue.

----------
messages: 2241
nosy: ncoghlan
priority: feature
status: unread
title: Display 'dependency of' and 'superseder of'

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

From metatracker at psf.upfronthosting.co.za  Mon Aug 29 10:05:53 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Mon, 29 Aug 2011 08:05:53 +0000
Subject: [Tracker-discuss] [issue411] Roundup instance is outdated
In-Reply-To: <1311602492.71.0.972062932119.issue411@psf.upfronthosting.co.za>
Message-ID: <1314605153.92.0.772425994445.issue411@psf.upfronthosting.co.za>


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

For me the proper way would be to maintain tracker customization in Mercurial Queue. This can be done by splitting customization diff into a sequence of diffs feature by feature. Git may be even better for this kind of work.

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

From metatracker at psf.upfronthosting.co.za  Wed Aug 31 05:24:03 2011
From: metatracker at psf.upfronthosting.co.za (Eric Snow)
Date: Wed, 31 Aug 2011 03:24:03 +0000
Subject: [Tracker-discuss] [issue402] Unable to log in to Rietveld code
	review interface
In-Reply-To: <1306534797.29.0.437152892578.issue402@psf.upfronthosting.co.za>
Message-ID: <1314761043.29.0.35897634147.issue402@psf.upfronthosting.co.za>


Eric Snow <ericsnowcurrently at gmail.com> added the comment:

I had the same symptoms as Nadeem and Eric's fix resolved it for me:

1. change "Login Name" in roundup to ericsnow (which is used to be),
2. successfully log in to rietveld,
3. change "Nickname" in rietveld settings to eric.snow,
4. change "Login Name" in roundup back to eric.snow.

Thanks!

----------
nosy: +eric.snow

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

From metatracker at psf.upfronthosting.co.za  Wed Aug 31 10:04:24 2011
From: metatracker at psf.upfronthosting.co.za (Nadeem Vawda)
Date: Wed, 31 Aug 2011 08:04:24 +0000
Subject: [Tracker-discuss] [issue402] Unable to log in to Rietveld code
	review interface
In-Reply-To: <1306534797.29.0.437152892578.issue402@psf.upfronthosting.co.za>
Message-ID: <1314777864.53.0.0887328461056.issue402@psf.upfronthosting.co.za>


Nadeem Vawda <nadeem.vawda at gmail.com> added the comment:

Note, though, that this fix is only temporary - you'll need to do the
rename dance again if you log in from a different computer, or if your
session expires and you need to log in to Rietveld again. At least,
that's been my experience.

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