From metatracker at psf.upfronthosting.co.za  Sat Jul 12 14:12:18 2014
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Sat, 12 Jul 2014 12:12:18 +0000
Subject: [Tracker-discuss] [issue549] myopenid.com image no longer works
Message-ID: <1405167138.73.0.551899172239.issue549@psf.upfronthosting.co.za>


New submission from Brett C.:

Since myopenid.com is now shut down the image for it to log in no longer works, leaving a gap between the Google and Launchpad login buttons.

----------
messages: 2878
nosy: brett.cannon
priority: bug
status: unread
title: myopenid.com image no longer works

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

From metatracker at psf.upfronthosting.co.za  Sat Jul 12 18:29:22 2014
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sat, 12 Jul 2014 16:29:22 +0000
Subject: [Tracker-discuss] [issue549] myopenid.com image no longer works
In-Reply-To: <1405167138.73.0.551899172239.issue549@psf.upfronthosting.co.za>
Message-ID: <1405182562.42.0.974797910508.issue549@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Is it just the image that needs to be replaced or is the myopenid login no longer available?

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

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

From metatracker at psf.upfronthosting.co.za  Sat Jul 12 21:46:59 2014
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Sat, 12 Jul 2014 19:46:59 +0000
Subject: [Tracker-discuss] [issue549] myopenid.com image no longer works
In-Reply-To: <1405167138.73.0.551899172239.issue549@psf.upfronthosting.co.za>
Message-ID: <CAP1=2W5WbBjN3MbS1hYre3_ddW=ZqaYrjXHB+QStJzFCf1n7Gg@mail.gmail.com>


Brett C. added the comment:

Myopenid is no longer available

On Sat, Jul 12, 2014, 12:29 Ezio Melotti <
metatracker at psf.upfronthosting.co.za> wrote:

>
> Ezio Melotti added the comment:
>
> Is it just the image that needs to be replaced or is the myopenid login no
> longer available?
>
> ----------
> nosy: +ezio.melotti, loewis
> status: unread -> chatting
>
> _______________________________________________________
> PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
> <http://psf.upfronthosting.co.za/roundup/meta/issue549>
> _______________________________________________________
>

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

From techtonik at gmail.com  Tue Jul 15 09:12:19 2014
From: techtonik at gmail.com (anatoly techtonik)
Date: Tue, 15 Jul 2014 10:12:19 +0300
Subject: [Tracker-discuss] External bug report monitoring
Message-ID: <CAPkN8xLDiAExOknf0ZD5cfL46PCsQTF6uNaidTmUDTqO+sxQnw@mail.gmail.com>

If Roundup plugin system is reworked a bit, it is
possible to make extensions to create and monitor
upstream bugs (Debian). Maybe even exchange
messages with it.

-- 
anatoly t.

From rdmurray at bitdance.com  Tue Jul 15 14:57:38 2014
From: rdmurray at bitdance.com (R. David Murray)
Date: Tue, 15 Jul 2014 08:57:38 -0400
Subject: [Tracker-discuss] External bug report monitoring
In-Reply-To: <CAPkN8xLDiAExOknf0ZD5cfL46PCsQTF6uNaidTmUDTqO+sxQnw@mail.gmail.com>
References: <CAPkN8xLDiAExOknf0ZD5cfL46PCsQTF6uNaidTmUDTqO+sxQnw@mail.gmail.com>
Message-ID: <20140715125739.470CF250030@webabinitio.net>

On Tue, 15 Jul 2014 10:12:19 +0300, anatoly techtonik <techtonik at gmail.com> wrote:
> If Roundup plugin system is reworked a bit, it is
> possible to make extensions to create and monitor
> upstream bugs (Debian). Maybe even exchange
> messages with it.

That would be downstream, and I'm not sure why we would want to do that.
I can see them wanting to track our bugs, since we are the upstream for
them, but I'm not seeing the value of vice-versa.  I've followed links
to bugs that were initially reported downstream, and that is helpful,
but having the chatter from the downstream bug reflected in our tracker
would probably be more confusing than helpful, especially since downstream
bugs tend to include "system" chatter about the status and disposition
of the bug (just as ours do).

If someone wants to go to the trouble of writing code to try it out,
I wouldn't object to the trial, but it's not an area I'd recommend
someone spend time on.  Also, if upstream changes are required in the
plugin system, it'll have to land there first, so there's not much
point in discussing it here until then.

--David

From techtonik at gmail.com  Tue Jul 15 20:21:51 2014
From: techtonik at gmail.com (anatoly techtonik)
Date: Tue, 15 Jul 2014 21:21:51 +0300
Subject: [Tracker-discuss] External bug report monitoring
In-Reply-To: <20140715125739.470CF250030@webabinitio.net>
References: <CAPkN8xLDiAExOknf0ZD5cfL46PCsQTF6uNaidTmUDTqO+sxQnw@mail.gmail.com>
 <20140715125739.470CF250030@webabinitio.net>
Message-ID: <CAPkN8x+ee60avCnnhcUtaURM_Qk2_Mqfqq6RBv1+Cqr_hCSufA@mail.gmail.com>

On Tue, Jul 15, 2014 at 3:57 PM, R. David Murray <rdmurray at bitdance.com> wrote:
> On Tue, 15 Jul 2014 10:12:19 +0300, anatoly techtonik <techtonik at gmail.com> wrote:
>> If Roundup plugin system is reworked a bit, it is
>> possible to make extensions to create and monitor
>> upstream bugs (Debian). Maybe even exchange
>> messages with it.
>
> That would be downstream, and I'm not sure why we would want to do that.
> I can see them wanting to track our bugs, since we are the upstream for
> them, but I'm not seeing the value of vice-versa.

How can they choose bugs that are only related to Debian?

> I've followed links
> to bugs that were initially reported downstream, and that is helpful,
> but having the chatter from the downstream bug reflected in our tracker
> would probably be more confusing than helpful, especially since downstream
> bugs tend to include "system" chatter about the status and disposition
> of the bug (just as ours do).

I think it will be more helpful that confusing, because Debian bugs can be
plainly marked as such and mark can lead to wiki page with definition of
Debian stuff for Python folks. Also this is the only way to get feedback from
Python people who are not registered at Debian tracker. This will benefit
both Debian and Python.

> If someone wants to go to the trouble of writing code to try it out,
> I wouldn't object to the trial, but it's not an area I'd recommend
> someone spend time on.

Which area do you recommend instead?

> Also, if upstream changes are required in the
> plugin system, it'll have to land there first, so there's not much
> point in discussing it here until then.

Not sure I get this paragraph. Which changes in plugin system are you
talking about? If you about patching Roundup for extensions then
bugs.python.org already runs patched version.

From stephen at xemacs.org  Wed Jul 16 16:57:25 2014
From: stephen at xemacs.org (Stephen J. Turnbull)
Date: Wed, 16 Jul 2014 23:57:25 +0900
Subject: [Tracker-discuss] External bug report monitoring
In-Reply-To: <CAPkN8x+ee60avCnnhcUtaURM_Qk2_Mqfqq6RBv1+Cqr_hCSufA@mail.gmail.com>
References: <CAPkN8xLDiAExOknf0ZD5cfL46PCsQTF6uNaidTmUDTqO+sxQnw@mail.gmail.com>
 <20140715125739.470CF250030@webabinitio.net>
 <CAPkN8x+ee60avCnnhcUtaURM_Qk2_Mqfqq6RBv1+Cqr_hCSufA@mail.gmail.com>
Message-ID: <87oawpl5be.fsf@uwakimon.sk.tsukuba.ac.jp>

anatoly techtonik writes:

 > How can they choose bugs that are only related to Debian?

They can't.  But they certainly do get a lot of them.  I made an
effort to follow the Debian bugs for XEmacs for almost a year, but
it's sort of like checking your spam folder for false positives.
There's some gold there, but not enough to make it worthwhile.  Many
of their bugs have to do with packaging, or worse with patches that
they apply to fit things into their standard package organization, and
occasionally to fix bugs -- the latter often backports of fixes
already in upstream trunk.

 > Also this is the only way to get feedback from Python people who
 > are not registered at Debian tracker. This will benefit both Debian
 > and Python.

For use, in the end it did pretty much nothing for XEmacs or Debian;
that's why I stopped.  *They* were pretty good about forwarding
relevant bugs upstream, but very little came from my efforts -- and
not because I wasn't diligent for those months, but because there just
wasn't that much of any relevance left after their forwards.

The situation here would be worse, because AIUI you propose to collect
those bugs automaticly: somebody would have to close all the
irrelevant bugs.




From rdmurray at bitdance.com  Wed Jul 16 17:40:51 2014
From: rdmurray at bitdance.com (R. David Murray)
Date: Wed, 16 Jul 2014 11:40:51 -0400
Subject: [Tracker-discuss] External bug report monitoring
In-Reply-To: <87oawpl5be.fsf@uwakimon.sk.tsukuba.ac.jp>
References: <CAPkN8xLDiAExOknf0ZD5cfL46PCsQTF6uNaidTmUDTqO+sxQnw@mail.gmail.com>
 <20140715125739.470CF250030@webabinitio.net>
 <CAPkN8x+ee60avCnnhcUtaURM_Qk2_Mqfqq6RBv1+Cqr_hCSufA@mail.gmail.com>
 <87oawpl5be.fsf@uwakimon.sk.tsukuba.ac.jp>
Message-ID: <20140716154051.A1B07B14086@webabinitio.net>

On Wed, 16 Jul 2014 23:57:25 +0900, "Stephen J. Turnbull" <stephen at xemacs.org> wrote:
> For use, in the end it did pretty much nothing for XEmacs or Debian;
> that's why I stopped.  *They* were pretty good about forwarding
> relevant bugs upstream, but very little came from my efforts -- and
> not because I wasn't diligent for those months, but because there just
> wasn't that much of any relevance left after their forwards.

I did the same with ubuntu and python bugs for a couple months, same
results.  Their tracker can link their bug to a specific upstream bug.
(I don't remember if it cross posts the traffic, or is just metadata on
the bug tracking the upstream bugs status...I believe it is the latter.)

Even for those few that merited and got such links, almost all of the
ubuntu traffic was irrelevant to us...and either the actual useful info
was posted to our bug tracker by someone from their side from the get go,
or someone (other than me) reposted the relevant bits to our tracker.

Given the (relatively) small amount of such relevant traffic, it is
probably better for a human to do the filtering rather than try to write
a smart filter that will have both false positives and false negatives.

Two months isn't a large sample, but it is probably large enough.

--David

From techtonik at gmail.com  Fri Jul 18 10:07:34 2014
From: techtonik at gmail.com (anatoly techtonik)
Date: Fri, 18 Jul 2014 11:07:34 +0300
Subject: [Tracker-discuss] Production server setup for bpo?
Message-ID: <CAPkN8x+Kxtw0gJDD82kQBRxUYNdprtAHJ95H_foUp=C7z5i+cg@mail.gmail.com>

Hi,

I am setting up VM for bpo development and to keep it as
close as possible to production setup, can anybody tell me
what the current setup is?

I need versions of Linux dist (as well as bitness), PostreSQL,
Python, and bindings as described here:

  https://wiki.python.org/moin/TrackerDevelopment#Requirements

Also need to know if Roundup is served from virtualenv or
not, if there is any caching, if there is an additional search
service, what is the web server, is there a reverse proxy,
who serves static resources.

Seems that's all.
-- 
anatoly t.

From techtonik at gmail.com  Fri Jul 18 10:15:20 2014
From: techtonik at gmail.com (anatoly techtonik)
Date: Fri, 18 Jul 2014 11:15:20 +0300
Subject: [Tracker-discuss] MyOpenID is down and page loading is slow
Message-ID: <CAPkN8xLrKfuy_6d+aHXV3mm7RE0MBHOf5TjdCik5i0+Upo0dKA@mail.gmail.com>

Browser, when pointed to http://bugs.python.org tries
to load MyOpenID icon, but since MyOpenID is down
it just waits for 10 seconds.

Who can remove MyOpenID support from b.p.o?
What is the current bus factor?
-- 
anatoly t.

From techtonik at gmail.com  Sat Jul 19 15:19:11 2014
From: techtonik at gmail.com (anatoly techtonik)
Date: Sat, 19 Jul 2014 16:19:11 +0300
Subject: [Tracker-discuss] Quick start with tracker development
Message-ID: <CAPkN8xJJ4gsDoQbzDOsSB=J8WfKP2HGXue34aHDhev+firt_LA@mail.gmail.com>

hg clone https://bitbucket.org/techtonik/pydotorg-bpo
cd pydotorg-bpo
vagrant up
vagrant -c ./server-start.sh

https://bitbucket.org/techtonik/pydotorg-bpo
-- 
anatoly t.

From techtonik at gmail.com  Tue Jul 22 17:16:22 2014
From: techtonik at gmail.com (anatoly techtonik)
Date: Tue, 22 Jul 2014 18:16:22 +0300
Subject: [Tracker-discuss] Production server setup for bpo?
In-Reply-To: <CAPkN8x+Kxtw0gJDD82kQBRxUYNdprtAHJ95H_foUp=C7z5i+cg@mail.gmail.com>
References: <CAPkN8x+Kxtw0gJDD82kQBRxUYNdprtAHJ95H_foUp=C7z5i+cg@mail.gmail.com>
Message-ID: <CAPkN8xKygFLbn_eBPfFv+KxqikGEqkqxFTMqR0cEP_58LG+HcQ@mail.gmail.com>

On Fri, Jul 18, 2014 at 11:07 AM, anatoly techtonik <techtonik at gmail.com> wrote:
>
> I am setting up VM for bpo development and to keep it as
> close as possible to production setup, can anybody tell me
> what the current setup is?
>
> I need versions of Linux dist (as well as bitness), PostreSQL,
> Python, and bindings as described here:
>
>   https://wiki.python.org/moin/TrackerDevelopment#Requirements
>
> Also need to know if Roundup is served from virtualenv or
> not, if there is any caching, if there is an additional search
> service, what is the web server, is there a reverse proxy,
> who serves static resources.
>
> Seems that's all.

ping?

Something like this will do:
http://sourceforge.net/p/forge/documentation/Project%20Web%20and%20Developer%20Web/#available-software

Thanks.

From metatracker at psf.upfronthosting.co.za  Tue Jul 29 16:16:07 2014
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Tue, 29 Jul 2014 14:16:07 +0000
Subject: [Tracker-discuss] [issue523] Spam tracker accounts
In-Reply-To: <1377117574.59.0.846835097823.issue523@psf.upfronthosting.co.za>
Message-ID: <1406643367.25.0.106943480878.issue523@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

I have now removed the notices about SourceForge.

As for spam accounts: it doesn't appear to be an urgent issue (remaining untreated for a year). There is spam protection already in place, preventing registration from bots who fill out the form too quickly. I don't think a captcha is really needed - closing this issue.

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

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

From metatracker at psf.upfronthosting.co.za  Tue Jul 29 16:27:47 2014
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Tue, 29 Jul 2014 14:27:47 +0000
Subject: [Tracker-discuss] [issue505] Abuse Message
In-Reply-To: <CAGscxN3xwoJ-qhgumYe9DQjxMgP60V71ZTr0Xxafe2cngMJsFg@mail.gmail.com>
Message-ID: <1406644067.43.0.434648156331.issue505@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

It's actually simpler than that. Roundup reports the value of _file._type for Content-type when a file is downloaded. This is what the auditor sets, but it remains unchanged for the already-uploaded files. I have now changed it for all existing files in the meta tracker.

----------
nosy: +loewis
priority:  -> bug

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

From metatracker at psf.upfronthosting.co.za  Tue Jul 29 16:29:21 2014
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Tue, 29 Jul 2014 14:29:21 +0000
Subject: [Tracker-discuss] [issue549] myopenid.com image no longer works
In-Reply-To: <1405167138.73.0.551899172239.issue549@psf.upfronthosting.co.za>
Message-ID: <1406644161.55.0.0482593454163.issue549@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

I have now removed it from the tracker.

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

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

From metatracker at psf.upfronthosting.co.za  Tue Jul 29 16:37:07 2014
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Tue, 29 Jul 2014 14:37:07 +0000
Subject: [Tracker-discuss] [issue547] Status has invalid option "- no
	selection -"
In-Reply-To: <1402272108.65.0.45914297888.issue547@psf.upfronthosting.co.za>
Message-ID: <1406644627.23.0.0853153409574.issue547@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

Why did you want to change the status to "- no selection -"?

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

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

From metatracker at psf.upfronthosting.co.za  Tue Jul 29 16:48:43 2014
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Tue, 29 Jul 2014 14:48:43 +0000
Subject: [Tracker-discuss] [issue546] Add notice of setuptools tracker
	relocation
In-Reply-To: <1401023176.55.0.62561630372.issue546@psf.upfronthosting.co.za>
Message-ID: <1406645323.23.0.340368052772.issue546@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

I have now moved the notice to the page level.

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

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

From metatracker at psf.upfronthosting.co.za  Tue Jul 29 17:07:35 2014
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Tue, 29 Jul 2014 15:07:35 +0000
Subject: [Tracker-discuss] [issue488] Broken RSS links on Rietveld
In-Reply-To: <1350284695.53.0.757594589874.issue488@psf.upfronthosting.co.za>
Message-ID: <1406646455.02.0.983216540294.issue488@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

The "official" way seems to be the SQL shell of django, so I did

roundup at psf:~/trackers/tracker/rietveld$ python manage.py shell

>>> from django.contrib.sites.models import Site
>>> Site.objects.create(name='bugs.python.org', domain='bugs.python.org')
<Site: bugs.python.org>

I should have specified the id, but it turns out that django automatically used ID 1.

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

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

From metatracker at psf.upfronthosting.co.za  Tue Jul 29 20:01:44 2014
From: metatracker at psf.upfronthosting.co.za (Terry Reedy)
Date: Tue, 29 Jul 2014 18:01:44 +0000
Subject: [Tracker-discuss] [issue547] Status has invalid option "- no
	selection -"
In-Reply-To: <1402272108.65.0.45914297888.issue547@psf.upfronthosting.co.za>
Message-ID: <1406656904.75.0.496168141107.issue547@psf.upfronthosting.co.za>


Terry Reedy added the comment:

I didn't. Please focus on the issue. The tracker (and meta-tracker) are mis-behaving by inviting answers that they reject. Proper list boxes do not do that.

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

From metatracker at psf.upfronthosting.co.za  Wed Jul 30 14:08:18 2014
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Wed, 30 Jul 2014 12:08:18 +0000
Subject: [Tracker-discuss] [issue547] Status has invalid option "- no
	selection -"
In-Reply-To: <1402272108.65.0.45914297888.issue547@psf.upfronthosting.co.za>
Message-ID: <1406722098.62.0.601641466172.issue547@psf.upfronthosting.co.za>


R David Murray added the comment:

I've used plenty of web sites where the equivalent of 'no selection' was not a valid choice (ie: you had to select something before the form would be accepted for submission).

Your argument appears to be that once the issue has been created, 'no selection' should no longer be generated as an option for status.  That would be nice, but I would consider it a very low priority thing to fix.  

If someone does want to work on a patch, I'm not sure if it should be approached at the roundup level in a generic fashion, or if it would be better to just make it a special case in the issue template.  The latter would be the easiest.

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

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

From metatracker at psf.upfronthosting.co.za  Wed Jul 30 17:56:38 2014
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Wed, 30 Jul 2014 15:56:38 +0000
Subject: [Tracker-discuss] [issue547] Status has invalid option "- no
	selection -"
In-Reply-To: <1402272108.65.0.45914297888.issue547@psf.upfronthosting.co.za>
Message-ID: <1406735798.23.0.943335639224.issue547@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

I cannot reproduce the issue. On http://bugs.python.org/issue2771, I just changed the value of "Status" successfully to "no selection". I got a green bar saying that the change was successful, and the issue log shows that the status was changed.

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

From metatracker at psf.upfronthosting.co.za  Wed Jul 30 21:10:26 2014
From: metatracker at psf.upfronthosting.co.za (Terry Reedy)
Date: Wed, 30 Jul 2014 19:10:26 +0000
Subject: [Tracker-discuss] [issue547] Status has invalid option "- no
	selection -"
In-Reply-To: <1402272108.65.0.45914297888.issue547@psf.upfronthosting.co.za>
Message-ID: <1406747426.72.0.793160131352.issue547@psf.upfronthosting.co.za>


Terry Reedy added the comment:

Something changed, though I am not sure that accepting '- no selection -' is an improvement. My suggestion is that after an issue is initially opened, Status be handled the same as Priority. I would try to submit a patch if I had the necessary info. (I once did DB admin, including form templates and squ inquiries, as part of a job.)

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