From metatracker at psf.upfronthosting.co.za  Fri Mar  4 16:51:40 2016
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Fri, 04 Mar 2016 21:51:40 +0000
Subject: [Tracker-discuss] [issue582] Placing the issue tracker under the
 PSF CoC
Message-ID: <1457128300.85.0.279066060282.issue582@psf.upfronthosting.co.za>


New submission from Brett C.:

I was figuring something as simple as linking to https://www.python.org/psf/codeofconduct/ with the text of "Code of Conduct" next to "Legal Statement" in the footer, e.g. "Legal Statements, Code of Conduct" or it could replace the "Website maintained by the Python community" text since that is more about www.python.org.

----------
messages: 3015
nosy: brett.cannon
priority: feature
status: unread
title: Placing the issue tracker under the PSF CoC

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

From metatracker at psf.upfronthosting.co.za  Fri Mar  4 19:09:19 2016
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Sat, 05 Mar 2016 00:09:19 +0000
Subject: [Tracker-discuss] [issue582] Placing the issue tracker under the
 PSF CoC
In-Reply-To: <1457128300.85.0.279066060282.issue582@psf.upfronthosting.co.za>
Message-ID: <1457136559.33.0.189358076114.issue582@psf.upfronthosting.co.za>


Brett C. added the comment:

I'm getting push-back on python-committers for this, so closing instead of fighting for it.

----------
status: unread -> resolved

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

From metatracker at psf.upfronthosting.co.za  Sat Mar  5 07:26:38 2016
From: metatracker at psf.upfronthosting.co.za (francis)
Date: Sat, 05 Mar 2016 12:26:38 +0000
Subject: [Tracker-discuss] [issue581] Add rest endpoint to roundup
In-Reply-To: <1456613089.91.0.963732827198.issue581@psf.upfronthosting.co.za>
Message-ID: <1457180798.74.0.82584417717.issue581@psf.upfronthosting.co.za>


francis added the comment:

A small review:
- Some code is outcommented and could be cleaned (deleted)
- print 'EXCEPTION AT', ts --> shouldn't be print(...) or use logging ?

----------
nosy: +francis

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

From metatracker at psf.upfronthosting.co.za  Thu Mar 10 02:59:56 2016
From: metatracker at psf.upfronthosting.co.za (Peter Funk)
Date: Thu, 10 Mar 2016 07:59:56 +0000
Subject: [Tracker-discuss] [issue581] Add rest endpoint to roundup
In-Reply-To: <1456613089.91.0.963732827198.issue581@psf.upfronthosting.co.za>
Message-ID: <1457596796.49.0.796134001623.issue581@psf.upfronthosting.co.za>


Peter Funk added the comment:

See also: http://issues.roundup-tracker.org/issue2550734

----------
nosy: +pefu512

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

From metatracker at psf.upfronthosting.co.za  Thu Mar 10 13:18:53 2016
From: metatracker at psf.upfronthosting.co.za (Maciej Szulik)
Date: Thu, 10 Mar 2016 18:18:53 +0000
Subject: [Tracker-discuss] [issue581] Add rest endpoint to roundup
In-Reply-To: <1456613089.91.0.963732827198.issue581@psf.upfronthosting.co.za>
Message-ID: <1457633933.3.0.991133238484.issue581@psf.upfronthosting.co.za>


Maciej Szulik added the comment:

Pefu my work is based on top of work started during GSoC. For now I've decided to cut the current implementation just to have GET working (needed for github migration). I'm hoping to work on enabling other actions as well. At the end of the day my hope is we can upstream this feature.

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

From metatracker at psf.upfronthosting.co.za  Sun Mar 20 10:35:40 2016
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sun, 20 Mar 2016 14:35:40 +0000
Subject: [Tracker-discuss] [issue458] editing "homepage" field is not
 possible
In-Reply-To: <1334485569.34.0.217371137544.issue458@psf.upfronthosting.co.za>
Message-ID: <1458484540.25.0.122945330388.issue458@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed in c25088641f39, thanks for the patches!

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

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

From metatracker at psf.upfronthosting.co.za  Wed Mar 23 02:42:43 2016
From: metatracker at psf.upfronthosting.co.za (xiang.zhang)
Date: Wed, 23 Mar 2016 06:42:43 +0000
Subject: [Tracker-discuss] [issue583] Failed to alter nosy list when
 someone's name has a comma in
Message-ID: <1458715363.18.0.462965037696.issue583@psf.upfronthosting.co.za>


New submission from xiang.zhang:

I failed to add myself to the nosy list when someone's name has a comma in it. The error reported is: property nosy: 'Guo' is not a user. The error happened in http://bugs.python.org/issue26617.

----------
messages: 3021
nosy: xiang.zhang
priority: bug
status: unread
title: Failed to alter nosy list when someone's name has a comma in
topic: tracker

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

From metatracker at psf.upfronthosting.co.za  Wed Mar 23 03:03:49 2016
From: metatracker at psf.upfronthosting.co.za (xiang.zhang)
Date: Wed, 23 Mar 2016 07:03:49 +0000
Subject: [Tracker-discuss] [issue583] Failed to alter nosy list when
 someone's name has a comma in
In-Reply-To: <1458715363.18.0.462965037696.issue583@psf.upfronthosting.co.za>
Message-ID: <1458716629.57.0.424867547229.issue583@psf.upfronthosting.co.za>


xiang.zhang added the comment:

Since the OP of the issue has changed his user name so it can be reproduced. But from the history you can see when someone create a new message the OP is removed from the nosy list.

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

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

From metatracker at psf.upfronthosting.co.za  Wed Mar 30 20:27:57 2016
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Thu, 31 Mar 2016 00:27:57 +0000
Subject: [Tracker-discuss] [issue579] Add github field in user profile
In-Reply-To: <1455314670.59.0.81694080109.issue579@psf.upfronthosting.co.za>
Message-ID: <1459384077.16.0.330208994946.issue579@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

After discussing with Brett and R. David, I modified Maciej patch to make GitHub usernames public.  The previous patch I uploaded has stricter permissions checks in case we change our mind.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue579>
_______________________________________________________
-------------- next part --------------
diff --git a/html/user.index.html b/html/user.index.html
--- a/html/user.index.html
+++ b/html/user.index.html
@@ -19,7 +19,7 @@
 <table class="form" tal:define="
        search_input templates/page/macros/search_input;">
 
-   <tr><th class="header" colspan="5">Search for users</th></tr>
+   <tr><th class="header" colspan="7">Search for users</th></tr>
    <tr>
        <th class="header">Username</th>
        <td tal:define="name string:username">
@@ -33,6 +33,12 @@
                          name name;
                          id name"/>
        </td>
+       <th class="header">GitHub</th>
+       <td tal:define="name string:github">
+           <input tal:attributes="value python:request.form.getvalue(name) or nothing;
+                         name name;
+                         id name"/>
+       </td>
 
        <td><input class="form-small" type="submit" value="Search" i18n:attributes="value"/></td>
    </tr>
@@ -46,6 +52,7 @@
        tal:define="batch request/batch">
 <tr>
  <th i18n:translate="">Username</th>
+ <th>GitHub</th>
  <th i18n:translate="">Real name</th>
  <th i18n:translate="">Organisation</th>
  <th i18n:translate="">Email address</th>
@@ -57,6 +64,7 @@
   <a tal:attributes="href string:user${user/id}"
      tal:content="user/username">username</a><tal:if condition="user/contrib_form"><span tal:attributes="title string:Contributor form received on ${user/contrib_form_date/pretty}">&nbsp;*</span></tal:if>
  </td>
+ <td tal:content="python:user.github.plain() or default">&nbsp;</td>
  <td tal:content="python:user.realname.plain() or default">&nbsp;</td>
  <td tal:content="python:user.organisation.plain() or default">&nbsp;</td>
  <td tal:content="python:user.address.email() or default">&nbsp;</td>
diff --git a/html/user.item.html b/html/user.item.html
--- a/html/user.item.html
+++ b/html/user.item.html
@@ -90,6 +90,11 @@
  </tr>
  </tal:if>
 
+ <tr tal:condition="context/github/is_view_ok" tal:define="name string:github; label string:GitHub Name; value context/github">
+  <th metal:use-macro="th_label">GitHub Name</th>
+  <td><input name="github" metal:use-macro="normal_input"></td>
+ </tr>
+
  <tr tal:define="name string:organisation; label string:Organisation; value context/organisation">
   <th metal:use-macro="th_label">Organisation</th>
   <td><input name="organisation" metal:use-macro="normal_input"></td>
diff --git a/schema.py b/schema.py
--- a/schema.py
+++ b/schema.py
@@ -97,6 +97,7 @@
              openids=String(), # space separated list
              iscommitter=Boolean(),
              homepage=String(),
+             github=String(),
              )
 user.setkey("username")
 db.security.addPermission(name='Register', klass='user',
@@ -349,7 +350,8 @@
 p = db.security.addPermission(name='View', klass='user',
         properties=('id', 'username', 'address', 'realname', 'phone',
                     'organisation', 'alternate_addresses', 'timezone',
-                    'roles', 'contrib_form', 'iscommitter', 'homepage'))
+                    'roles', 'contrib_form', 'iscommitter', 'homepage',
+                    'github'))
 db.security.addPermissionToRole('User', p)
 db.security.addPermissionToRole('Developer', p)
 # Coordinator may view all user properties.
@@ -375,7 +377,7 @@
                 'phone', 'organisation',
                 'alternate_addresses',
                 'queries', 'timezone',
-                'homepage'))
+                'homepage', 'github'))
                 # Note: 'roles' excluded - users should not be able to edit their own roles.
                 # Also excluded: contrib_form, contrib_form_date, iscommitter
 for r in 'User', 'Developer':

From metatracker at psf.upfronthosting.co.za  Wed Mar 30 20:48:48 2016
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Thu, 31 Mar 2016 00:48:48 +0000
Subject: [Tracker-discuss] [issue579] Add github field in user profile
In-Reply-To: <1455314670.59.0.81694080109.issue579@psf.upfronthosting.co.za>
Message-ID: <1459385328.0.0.125569300243.issue579@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

I committed the latest patch in https://hg.python.org/tracker/python-dev/rev/deefac77e9dd
Thanks for the initial patch!

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

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