From amk at amk.ca  Sun Feb  3 14:58:06 2008
From: amk at amk.ca (A.M. Kuchling)
Date: Sun, 3 Feb 2008 08:58:06 -0500
Subject: [Tracker-discuss] Creating a Jython tracker
Message-ID: <20080203135806.GA512@amk.local>

Frank Wierzbicki sent me a note:
>Not sure if you are the right person to contact -- but has roundup
>reached a level of comfort for Python where they might consider
>hosting Jython as well?  I think my Jython time is going to expand
>greatly in a couple of weeks, and I can't take the sf bug tracker any
>more :)

So, are we in a position to set up a Jython tracker?  For simplicity,
we could probably assume that the bug-handling workflow will be the
same as Python's and use the same schema, detectors, etc.  I'd expect
the most labor-intensive step would be importing the old SF bugs.

--amk

From martin at v.loewis.de  Sun Feb  3 19:02:26 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Sun, 03 Feb 2008 19:02:26 +0100
Subject: [Tracker-discuss] Creating a Jython tracker
In-Reply-To: <20080203135806.GA512@amk.local>
References: <20080203135806.GA512@amk.local>
Message-ID: <47A601B2.2010700@v.loewis.de>

> So, are we in a position to set up a Jython tracker?  For simplicity,
> we could probably assume that the bug-handling workflow will be the
> same as Python's and use the same schema, detectors, etc.  I'd expect
> the most labor-intensive step would be importing the old SF bugs.

I could work on that over the next week(s). It would be best
if I could get admin rights on the tracker, so that I could run
the exporter myself. I would then produce a demo installation, so
people can check whether it looks correctly.

A few other things that need to be decided:
- what URL should that tracker use? who needs to set up DNS so that
   it works?
- what is the email submission address?
   (the DNS person would also have to make the upfronthosting machine
    the mail exchanger for that domain)
- what email messages should be sent to what addresses under what
   conditions, and who should be the sender?

I'll probably need help from upfronthosting for the SMTP stuff, and
somebody's help for the DNS stuff; the rest I can do on my own (unless
I forgot something).

Regards,
Martin

From fwierzbicki at gmail.com  Sun Feb  3 19:31:18 2008
From: fwierzbicki at gmail.com (Frank Wierzbicki)
Date: Sun, 3 Feb 2008 13:31:18 -0500
Subject: [Tracker-discuss] Creating a Jython tracker
In-Reply-To: <47A601B2.2010700@v.loewis.de>
References: <20080203135806.GA512@amk.local> <47A601B2.2010700@v.loewis.de>
Message-ID: <4dab5f760802031031r38fd4387uc92fb2f794c88bb7@mail.gmail.com>

On Feb 3, 2008 1:02 PM, "Martin v. L?wis" <martin at v.loewis.de> wrote:
> I could work on that over the next week(s). It would be best
> if I could get admin rights on the tracker, so that I could run
> the exporter myself. I would then produce a demo installation, so
> people can check whether it looks correctly.
Sounds good to me, thanks!

Martin: What is your sourceforge id so I can give you the rights?

-Frank

From roche at upfrontsystems.co.za  Sun Feb  3 19:26:34 2008
From: roche at upfrontsystems.co.za (=?ISO-8859-1?Q?Roch=E9?= Compaan)
Date: Sun, 03 Feb 2008 20:26:34 +0200
Subject: [Tracker-discuss] Creating a Jython tracker
In-Reply-To: <47A601B2.2010700@v.loewis.de>
References: <20080203135806.GA512@amk.local>  <47A601B2.2010700@v.loewis.de>
Message-ID: <1202063194.16695.77.camel@localhost>

On Sun, 2008-02-03 at 19:02 +0100, "Martin v. L?wis" wrote:
> > So, are we in a position to set up a Jython tracker?  For simplicity,
> > we could probably assume that the bug-handling workflow will be the
> > same as Python's and use the same schema, detectors, etc.  I'd expect
> > the most labor-intensive step would be importing the old SF bugs.
> 
> I could work on that over the next week(s). It would be best
> if I could get admin rights on the tracker, so that I could run
> the exporter myself. I would then produce a demo installation, so
> people can check whether it looks correctly.
> 
> A few other things that need to be decided:
> - what URL should that tracker use? who needs to set up DNS so that
>    it works?
> - what is the email submission address?
>    (the DNS person would also have to make the upfronthosting machine
>     the mail exchanger for that domain)
> - what email messages should be sent to what addresses under what
>    conditions, and who should be the sender?
> 
> I'll probably need help from upfronthosting for the SMTP stuff, and
> somebody's help for the DNS stuff; the rest I can do on my own (unless
> I forgot something).

Just shout and I'll Izak to help.

-- 
Roch? Compaan
Upfront Systems                   http://www.upfrontsystems.co.za


From brett at python.org  Sun Feb  3 21:56:43 2008
From: brett at python.org (Brett Cannon)
Date: Sun, 3 Feb 2008 12:56:43 -0800
Subject: [Tracker-discuss] Creating a Jython tracker
In-Reply-To: <47A601B2.2010700@v.loewis.de>
References: <20080203135806.GA512@amk.local> <47A601B2.2010700@v.loewis.de>
Message-ID: <bbaeab100802031256j7f42330al3e53581241ea7694@mail.gmail.com>

On Feb 3, 2008 10:02 AM, "Martin v. L?wis" <martin at v.loewis.de> wrote:
> > So, are we in a position to set up a Jython tracker?  For simplicity,
> > we could probably assume that the bug-handling workflow will be the
> > same as Python's and use the same schema, detectors, etc.  I'd expect
> > the most labor-intensive step would be importing the old SF bugs.
>
> I could work on that over the next week(s). It would be best
> if I could get admin rights on the tracker, so that I could run
> the exporter myself. I would then produce a demo installation, so
> people can check whether it looks correctly.
>
> A few other things that need to be decided:
> - what URL should that tracker use? who needs to set up DNS so that
>    it works?
> - what is the email submission address?
>    (the DNS person would also have to make the upfronthosting machine
>     the mail exchanger for that domain)
> - what email messages should be sent to what addresses under what
>    conditions, and who should be the sender?
>
> I'll probably need help from upfronthosting for the SMTP stuff, and
> somebody's help for the DNS stuff; the rest I can do on my own (unless
> I forgot something).
>

I really need to get off my ass and write up that announcement that we
need more tracker admins. Expect an email on that shortly. But it
would be great if the Jython community could possibly wrangle someone
into helping out on a permanent basis. Since Upfront maintains the
machine its mostly Roundup maintenance/customization and database
stuff (am I missing something, Martin or Erik?).

-Brett

From georg at python.org  Sun Feb  3 22:24:37 2008
From: georg at python.org (Georg Brandl)
Date: Sun, 03 Feb 2008 22:24:37 +0100
Subject: [Tracker-discuss] Creating a Jython tracker
In-Reply-To: <bbaeab100802031256j7f42330al3e53581241ea7694@mail.gmail.com>
References: <20080203135806.GA512@amk.local> <47A601B2.2010700@v.loewis.de>
	<bbaeab100802031256j7f42330al3e53581241ea7694@mail.gmail.com>
Message-ID: <47A63115.2070109@python.org>

Brett Cannon schrieb:
> On Feb 3, 2008 10:02 AM, "Martin v. L?wis" <martin at v.loewis.de> wrote:
>> > So, are we in a position to set up a Jython tracker?  For simplicity,
>> > we could probably assume that the bug-handling workflow will be the
>> > same as Python's and use the same schema, detectors, etc.  I'd expect
>> > the most labor-intensive step would be importing the old SF bugs.
>>
>> I could work on that over the next week(s). It would be best
>> if I could get admin rights on the tracker, so that I could run
>> the exporter myself. I would then produce a demo installation, so
>> people can check whether it looks correctly.
>>
>> A few other things that need to be decided:
>> - what URL should that tracker use? who needs to set up DNS so that
>>    it works?
>> - what is the email submission address?
>>    (the DNS person would also have to make the upfronthosting machine
>>     the mail exchanger for that domain)
>> - what email messages should be sent to what addresses under what
>>    conditions, and who should be the sender?
>>
>> I'll probably need help from upfronthosting for the SMTP stuff, and
>> somebody's help for the DNS stuff; the rest I can do on my own (unless
>> I forgot something).
>>
> 
> I really need to get off my ass and write up that announcement that we
> need more tracker admins.

Can you add that we need more people actually fixing issues from the
tracker too? :)

Georg


From brett at python.org  Sun Feb  3 22:32:33 2008
From: brett at python.org (Brett Cannon)
Date: Sun, 3 Feb 2008 13:32:33 -0800
Subject: [Tracker-discuss] Creating a Jython tracker
In-Reply-To: <47A63115.2070109@python.org>
References: <20080203135806.GA512@amk.local> <47A601B2.2010700@v.loewis.de>
	<bbaeab100802031256j7f42330al3e53581241ea7694@mail.gmail.com>
	<47A63115.2070109@python.org>
Message-ID: <bbaeab100802031332w69846fc8hde34021994f95e00@mail.gmail.com>

On Feb 3, 2008 1:24 PM, Georg Brandl <georg at python.org> wrote:
> Brett Cannon schrieb:
> > On Feb 3, 2008 10:02 AM, "Martin v. L?wis" <martin at v.loewis.de> wrote:
> >> > So, are we in a position to set up a Jython tracker?  For simplicity,
> >> > we could probably assume that the bug-handling workflow will be the
> >> > same as Python's and use the same schema, detectors, etc.  I'd expect
> >> > the most labor-intensive step would be importing the old SF bugs.
> >>
> >> I could work on that over the next week(s). It would be best
> >> if I could get admin rights on the tracker, so that I could run
> >> the exporter myself. I would then produce a demo installation, so
> >> people can check whether it looks correctly.
> >>
> >> A few other things that need to be decided:
> >> - what URL should that tracker use? who needs to set up DNS so that
> >>    it works?
> >> - what is the email submission address?
> >>    (the DNS person would also have to make the upfronthosting machine
> >>     the mail exchanger for that domain)
> >> - what email messages should be sent to what addresses under what
> >>    conditions, and who should be the sender?
> >>
> >> I'll probably need help from upfronthosting for the SMTP stuff, and
> >> somebody's help for the DNS stuff; the rest I can do on my own (unless
> >> I forgot something).
> >>
> >
> > I really need to get off my ass and write up that announcement that we
> > need more tracker admins.
>
> Can you add that we need more people actually fixing issues from the
> tracker too? :)

Promote the development tutorial at PyCon and I can. =)

-Brett

From martin at v.loewis.de  Sun Feb  3 23:05:20 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Sun, 03 Feb 2008 23:05:20 +0100
Subject: [Tracker-discuss] Creating a Jython tracker
In-Reply-To: <47A601B2.2010700@v.loewis.de>
References: <20080203135806.GA512@amk.local> <47A601B2.2010700@v.loewis.de>
Message-ID: <47A63AA0.50303@v.loewis.de>

> I'll probably need help from upfronthosting for the SMTP stuff, and
> somebody's help for the DNS stuff; the rest I can do on my own (unless
> I forgot something).

As a further follow-up, I also need a list of components (the things
where the Python tracker has "Build", "Distutils" etc), and any mapping
between SF categories and roundup components - take particular notice
that all three SF trackers will be merged into a single one.

The same is also needed for priorities: the existing config maps
1..4 to low, 5 to normal, 6 and 7 to high, 8 to immediate, and 9
to urgent. I see that the Jython tracker has nothing above 5, but
also has 4, 3, 2.

Also, the SF "Group" maps to the Roundup "Version"; I need a list
of mappings here, as well.

Then, we need a list of issue_types; the Python tracker has
crash, compile error, resource usage, security, behaviour, rfe;
it's not clear whether this aspect is even useful, though.

The resolutions will map 1:1 unless you want customization there,
as well.

It would best to specify all this on either a Wiki page somewhere,
or in a meta-tracker issue, at

   http://psf.upfronthosting.co.za/roundup/meta/

Regards,
Martin

From fwierzbicki at gmail.com  Sun Feb  3 23:19:50 2008
From: fwierzbicki at gmail.com (Frank Wierzbicki)
Date: Sun, 3 Feb 2008 17:19:50 -0500
Subject: [Tracker-discuss] Creating a Jython tracker
In-Reply-To: <bbaeab100802031256j7f42330al3e53581241ea7694@mail.gmail.com>
References: <20080203135806.GA512@amk.local> <47A601B2.2010700@v.loewis.de>
	<bbaeab100802031256j7f42330al3e53581241ea7694@mail.gmail.com>
Message-ID: <4dab5f760802031419i2fce5fa0xa77300fbe5d9d663@mail.gmail.com>

On Feb 3, 2008 3:56 PM, Brett Cannon <brett at python.org> wrote:
> I really need to get off my ass and write up that announcement that we
> need more tracker admins. Expect an email on that shortly. But it
> would be great if the Jython community could possibly wrangle someone
> into helping out on a permanent basis. Since Upfront maintains the
> machine its mostly Roundup maintenance/customization and database
> stuff (am I missing something, Martin or Erik?).
Certainly we should pull our weight.  I will try to round up
volunteer(s) from the Jython community.  I'll wait a day or so to see
if there is more to the job description than "roundup
maintenance/customization and database stuff" before I check with the
Jython folks.

-Frank

From fwierzbicki at gmail.com  Sun Feb  3 23:27:42 2008
From: fwierzbicki at gmail.com (Frank Wierzbicki)
Date: Sun, 3 Feb 2008 17:27:42 -0500
Subject: [Tracker-discuss] Creating a Jython tracker
In-Reply-To: <4dab5f760802031419i2fce5fa0xa77300fbe5d9d663@mail.gmail.com>
References: <20080203135806.GA512@amk.local> <47A601B2.2010700@v.loewis.de>
	<bbaeab100802031256j7f42330al3e53581241ea7694@mail.gmail.com>
	<4dab5f760802031419i2fce5fa0xa77300fbe5d9d663@mail.gmail.com>
Message-ID: <4dab5f760802031427n5559e236x359f31b238517ed2@mail.gmail.com>

Martin and others,

There is more discussion than I expected about moving to roundup.  No
one wants to stay with SF, but there are a couple of voices that want
to look at other options. I personally think Python's roundup makes
the most sense, but I want to get a little more consensus before you
guys put work into this.  Sorry that I appear to have put the cart
before the horse here.  I should be able to get back with more
certainty in a day or two.

-Frank

From brett at python.org  Sun Feb  3 23:42:01 2008
From: brett at python.org (Brett Cannon)
Date: Sun, 3 Feb 2008 14:42:01 -0800
Subject: [Tracker-discuss] Creating a Jython tracker
In-Reply-To: <4dab5f760802031427n5559e236x359f31b238517ed2@mail.gmail.com>
References: <20080203135806.GA512@amk.local> <47A601B2.2010700@v.loewis.de>
	<bbaeab100802031256j7f42330al3e53581241ea7694@mail.gmail.com>
	<4dab5f760802031419i2fce5fa0xa77300fbe5d9d663@mail.gmail.com>
	<4dab5f760802031427n5559e236x359f31b238517ed2@mail.gmail.com>
Message-ID: <bbaeab100802031442p7db4be63xb8cfb6f3019b6def@mail.gmail.com>

On Feb 3, 2008 2:27 PM, Frank Wierzbicki <fwierzbicki at gmail.com> wrote:
> Martin and others,
>
> There is more discussion than I expected about moving to roundup.  No
> one wants to stay with SF, but there are a couple of voices that want
> to look at other options. I personally think Python's roundup makes
> the most sense, but I want to get a little more consensus before you
> guys put work into this.  Sorry that I appear to have put the cart
> before the horse here.  I should be able to get back with more
> certainty in a day or two.

Sure thing. Just something to realize is that we went through a lot of
work as a group to choose Roundup as a tracker. Unless you go with
something that is totally self-hosted and run by someone else (and
thus needs no volunteers) be careful about jumping for Trac, etc.

-Brett

From fwierzbicki at gmail.com  Sun Feb  3 23:50:49 2008
From: fwierzbicki at gmail.com (Frank Wierzbicki)
Date: Sun, 3 Feb 2008 17:50:49 -0500
Subject: [Tracker-discuss] Creating a Jython tracker
In-Reply-To: <bbaeab100802031442p7db4be63xb8cfb6f3019b6def@mail.gmail.com>
References: <20080203135806.GA512@amk.local> <47A601B2.2010700@v.loewis.de>
	<bbaeab100802031256j7f42330al3e53581241ea7694@mail.gmail.com>
	<4dab5f760802031419i2fce5fa0xa77300fbe5d9d663@mail.gmail.com>
	<4dab5f760802031427n5559e236x359f31b238517ed2@mail.gmail.com>
	<bbaeab100802031442p7db4be63xb8cfb6f3019b6def@mail.gmail.com>
Message-ID: <4dab5f760802031450q642b9a86o5127d5cca7c84238@mail.gmail.com>

On Feb 3, 2008 5:42 PM, Brett Cannon <brett at python.org> wrote:
> Sure thing. Just something to realize is that we went through a lot of
> work as a group to choose Roundup as a tracker. Unless you go with
> something that is totally self-hosted and run by someone else (and
> thus needs no volunteers) be careful about jumping for Trac, etc.
This exactly describes my opinion, but I want to listen to what the
others have to say.  Jython's needs may be a bit different from
Python's.  Having said that, I definitely do not want to try to handle
a bug tracker with all of the issues like spam filtering, etc. all by
ourselves.

-Frank

From izak at upfrontsystems.co.za  Mon Feb  4 07:07:35 2008
From: izak at upfrontsystems.co.za (Izak Burger)
Date: Mon, 04 Feb 2008 08:07:35 +0200
Subject: [Tracker-discuss] Creating a Jython tracker
In-Reply-To: <1202063194.16695.77.camel@localhost>
References: <20080203135806.GA512@amk.local> <47A601B2.2010700@v.loewis.de>
	<1202063194.16695.77.camel@localhost>
Message-ID: <47A6ABA7.1060803@upfrontsystems.co.za>

Roch? Compaan wrote:
>> I'll probably need help from upfronthosting for the SMTP stuff, and
>> somebody's help for the DNS stuff; the rest I can do on my own (unless
>> I forgot something).
> 
> Just shout and I'll Izak to help.

I am on the list :-)

From fwierzbicki at gmail.com  Mon Feb  4 20:18:33 2008
From: fwierzbicki at gmail.com (Frank Wierzbicki)
Date: Mon, 4 Feb 2008 14:18:33 -0500
Subject: [Tracker-discuss] Creating a Jython tracker
In-Reply-To: <bbaeab100802031442p7db4be63xb8cfb6f3019b6def@mail.gmail.com>
References: <20080203135806.GA512@amk.local> <47A601B2.2010700@v.loewis.de>
	<bbaeab100802031256j7f42330al3e53581241ea7694@mail.gmail.com>
	<4dab5f760802031419i2fce5fa0xa77300fbe5d9d663@mail.gmail.com>
	<4dab5f760802031427n5559e236x359f31b238517ed2@mail.gmail.com>
	<bbaeab100802031442p7db4be63xb8cfb6f3019b6def@mail.gmail.com>
Message-ID: <4dab5f760802041118w3f6fe570le04854dc1e507623@mail.gmail.com>

On Feb 3, 2008 5:42 PM, Brett Cannon <brett at python.org> wrote:
> Sure thing. Just something to realize is that we went through a lot of
> work as a group to choose Roundup as a tracker. Unless you go with
> something that is totally self-hosted and run by someone else (and
> thus needs no volunteers) be careful about jumping for Trac, etc.
So hosting our own trac is indeed the other contender, and I share
your concerns.  I read the executive summary for the decision to go
with Roundup over Trac, etc here:

http://mail.python.org/pipermail/python-dev/2006-October/069139.html

But it is thin on reasons for not going with Trac.  Does anyone
remember the particular problems with Trac?  I don't want to stir
anything up, just looking for some data to use in our decision.

-Frank

From brett at python.org  Mon Feb  4 21:28:22 2008
From: brett at python.org (Brett Cannon)
Date: Mon, 4 Feb 2008 12:28:22 -0800
Subject: [Tracker-discuss] Creating a Jython tracker
In-Reply-To: <4dab5f760802041118w3f6fe570le04854dc1e507623@mail.gmail.com>
References: <20080203135806.GA512@amk.local> <47A601B2.2010700@v.loewis.de>
	<bbaeab100802031256j7f42330al3e53581241ea7694@mail.gmail.com>
	<4dab5f760802031419i2fce5fa0xa77300fbe5d9d663@mail.gmail.com>
	<4dab5f760802031427n5559e236x359f31b238517ed2@mail.gmail.com>
	<bbaeab100802031442p7db4be63xb8cfb6f3019b6def@mail.gmail.com>
	<4dab5f760802041118w3f6fe570le04854dc1e507623@mail.gmail.com>
Message-ID: <bbaeab100802041228s2cc7a8a5nf32e6cf3dcd3ca87@mail.gmail.com>

On Feb 4, 2008 11:18 AM, Frank Wierzbicki <fwierzbicki at gmail.com> wrote:
> On Feb 3, 2008 5:42 PM, Brett Cannon <brett at python.org> wrote:
> > Sure thing. Just something to realize is that we went through a lot of
> > work as a group to choose Roundup as a tracker. Unless you go with
> > something that is totally self-hosted and run by someone else (and
> > thus needs no volunteers) be careful about jumping for Trac, etc.
> So hosting our own trac is indeed the other contender, and I share
> your concerns.  I read the executive summary for the decision to go
> with Roundup over Trac, etc here:
>
> http://mail.python.org/pipermail/python-dev/2006-October/069139.html
>
> But it is thin on reasons for not going with Trac.  Does anyone
> remember the particular problems with Trac?  I don't want to stir
> anything up, just looking for some data to use in our decision.

Trac required a huge amount of customization to really become useful.
The default UI, for instance, was no where near as nice as the other
systems. It also seemed the most immature compared to Roundup.

-Brett

From martin at v.loewis.de  Mon Feb  4 23:01:28 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Mon, 04 Feb 2008 23:01:28 +0100
Subject: [Tracker-discuss] Creating a Jython tracker
In-Reply-To: <4dab5f760802041118w3f6fe570le04854dc1e507623@mail.gmail.com>
References: <20080203135806.GA512@amk.local> <47A601B2.2010700@v.loewis.de>	
	<bbaeab100802031256j7f42330al3e53581241ea7694@mail.gmail.com>	
	<4dab5f760802031419i2fce5fa0xa77300fbe5d9d663@mail.gmail.com>	
	<4dab5f760802031427n5559e236x359f31b238517ed2@mail.gmail.com>	
	<bbaeab100802031442p7db4be63xb8cfb6f3019b6def@mail.gmail.com>
	<4dab5f760802041118w3f6fe570le04854dc1e507623@mail.gmail.com>
Message-ID: <47A78B38.2030600@v.loewis.de>

> But it is thin on reasons for not going with Trac.  Does anyone
> remember the particular problems with Trac?  

There are still AMK's notes out there:

http://wiki.python.org/moin/AndrewKuchling/TrackerNotes

Unfortunately, the trac demo was provided very late in the call for
trackers, so it wasn't studied as intensively as the others.

I remember that not being able to do custom queries sounded like
a severe limitation to me. You can probably fix that with a plugin

It's not clear to me whether Trac supports email interaction; we
believed that this is a must-have feature.

One specific concern I had is that all issues came out on a single
page always, which is just unacceptable if you have 1000+ open
issues (as we have now). I understand that this can be fixed with
a plugin.

In any case, you need some formal process to take a decision;
people will never agree on a tracker. So it's either a dictator
decision, a committee decision, or a community decision - use
whatever process works best for your community, and then implement
it.

In the case of Python, it was essential to the success of the
migration that people had to show-case their trackers *before*
a decision was made, as admin-type people already got attached
to getting this up-and-running. If you want to see a similar
dog-and-pony show for possible future Jython trackers, I could
still try to get the Roundup tracker up-and-running, even at
the risk that the community decides in favor of Trac afterwards.

In such a scenario, the Trac supporters would have get together
and volunteer some people to actually perform the necessary
setup work, so if Trac wins, you have already volunteers for
the first three months into the tracker's life (our experience
tells that most volunteers will run away within the first 6
months after getting this set-up and adopted). For Python, it's
currently just me that does any maintenance on the tracker.

Regards,
Martin


From turnbull at sk.tsukuba.ac.jp  Tue Feb  5 01:59:31 2008
From: turnbull at sk.tsukuba.ac.jp (Stephen J. Turnbull)
Date: Tue, 05 Feb 2008 09:59:31 +0900
Subject: [Tracker-discuss] Creating a Jython tracker
In-Reply-To: <4dab5f760802041118w3f6fe570le04854dc1e507623@mail.gmail.com>
References: <20080203135806.GA512@amk.local> <47A601B2.2010700@v.loewis.de>
	<bbaeab100802031256j7f42330al3e53581241ea7694@mail.gmail.com>
	<4dab5f760802031419i2fce5fa0xa77300fbe5d9d663@mail.gmail.com>
	<4dab5f760802031427n5559e236x359f31b238517ed2@mail.gmail.com>
	<bbaeab100802031442p7db4be63xb8cfb6f3019b6def@mail.gmail.com>
	<4dab5f760802041118w3f6fe570le04854dc1e507623@mail.gmail.com>
Message-ID: <87tzkow74c.fsf@uwakimon.sk.tsukuba.ac.jp>

Frank Wierzbicki writes:

 > But it is thin on reasons for not going with Trac.  Does anyone
 > remember the particular problems with Trac?  I don't want to stir
 > anything up, just looking for some data to use in our decision.

I wasn't party to the decision at Python, but I do use Trac on a
weekly or so basis for MacPorts.  The MacPorts tracker was horrible,
and it's still not good.  I append a bug report I submitted against
their Trac tracker and the reply.  Or you can find the original and
some additional discussion at

Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/11376>

A few comments: "jmpp" pretty clearly didn't understand what I was
getting at with #6.  The problem is that if you submit just a port
name, you get every ticket that mentions the port, including several
dozen where a user dumped their entire list of packages into the bug
report, and all svn commits that touch a file in that port!  I've
never seen one return less than 100 tickets.

This was partly alleviated when they added a standard query for "all
tickets submitted by me", but that encourages submitting a new query
and then waiting for a MacPorts staffer to cross-reference to another
ticket where the problem is discussed in depth.  (A technique that has
served me well twice, I'm ashamed to admit.)

I get the feeling that a lot of this is problems in Trac itself, or at
least in the default configuration, as only the easy ones were really
solved.

>From the MacPorts staffer's reply, it appears that a lot of the
customization of Trac has to be done offline, and may require a reload
of the database or something icky like that.

With Roundup, almost everything I asked for can be done online if you
have admin permissions.  New keywords, retiring keywords, adding
priorities, changing the sort order of priorities, etc.  And users can
store their own queries.  And the database schema can be changed on
the fly, since it's object oriented.  Old objects won't forget their
properties (although the UI may not display them any more), and
nothing crashes if an old object doesn't have newly defined properties
accessed by the UI: they just show up as undefined.  This makes it
really easy to make small frequent improvements in the user
experience.

The Roundup UI is easy to adapt, too (you do need access to the
tracker's HTML templates and a server restart).  You'll note complaint
#3 about 1200px wide windows, which still have not been fixed as of
last Friday.  I had a problem in my Roundup tracker where a popup
window was a tiny bit too narrow (on Firefox/Mac, when the scrollbar
appears, the usable area gets smaller), and a nice row of 3 buttons
became two rows.  Ugly.  All I needed to do was find the appropriate
template, and change the window's width attribute from 600 to 625, and
restart the server.  While I've not administered a Trac myself, the
exchange attached below suggests that it's not very adaptable.

You'll also see three subissues about help, again, still not
addressed.  In Roundup, it was simply a matter of changing the "Doc"
anchor to "Vendor docs" (so people would know these were not suppose
to apply specifically to our tracker, and than links to a revised
version of the user guide specific to our config, our bug reporting
guidelines, and our debugging advice.  It's still not as good as I
would like, but I no longer feel like I'm just begging for a user and
developer revolt.  Trac seems to make this kind of gradual improvement
hard, though.

Oh, and here's my in progress tracker (which includes several
improvements I learned about from Python's tracker, all remaining
infelicities the responsibility of yours truly, of course):

                http://tracker.xemacs.org/XEmacs/its/

----------------------------------------------------------------

Sender: trac at macosforge.org
Message-ID: <057.908c181aa25b03008c0587a78dbb4a16 at macosforge.org>
From: "MacPorts" <trac at macosforge.org>
To: stephen at xemacs.org, jmpp at macports.org
Cc: macports-tickets at lists.macosforge.org
Subject: Re: [MacPorts] #11376: Tracker discourages use
Date: Tue, 18 Dec 2007 18:36:00 -0000

#11376: Tracker discourages use
---------------------------------+------------------------------------------
  Reporter:  stephen at xemacs.org  |       Owner:  jmpp at macports.org
      Type:  defect              |      Status:  new              
  Priority:  Normal              |   Milestone:                   
 Component:  infrastructure      |     Version:                   
Resolution:                      |    Keywords:                   
---------------------------------+------------------------------------------
Old description:

> Trac may be wonderful, but what I wonder is how regular users can stand
> it!
>
> 1. Trac forgets my login when following most links.  I'm not really sure
> what's going on here, because it doesn't always do this.  For example, if
> I enter "http://www.macports.org/", then go there, it remembers earlier
> logins in the current browser sessin, and if there is no login session,
> the password memory makes logging in easy.  Both facilities fail when I
> follow links into the tracker.  Maybe it's that trac doesn't live at
> www.macports.org, but at trac.macports.org, and my browser doesn't send
> the cookie.
>
> 2. ''All'' trac pages should have a New Bug button.
>
> 3. Many displays assume I have space for a 1200 pixel width window.  (a)
> I don't on several of my workstations (subnotebooks), and (b) I am not a
> fan of letting any application take over my entire screen, especially not
> one subject to network delays.
>
> 4. This wouldn't be so bad (the wide display does contain a lot of
> information, and it's quite useful to keep it on one line), except that a
> lot of useful controls are right-justified and end up off-screen (login,
> search).
>
> 5. There's no easy way to search for bugs against a single port.
>
> 6. The custom query as initialized looks for bugs assigned to me.  Make
> that a standard query, for heaven's sake.  The custom query is the only
> available workaround for #5, so you're encouraging users to enter
> duplicate bugs by making it annoying to search for existing bugs.  The
> custom query should be initialized to search the summary.
>
> 7. Ticket properties are insane.  Yes, I've come to "expect" MacPorts to
> throw at least one reportable bug a week, not to mention frequent minor
> annoyances, but what does "Priority: expected" mean in terms of getting
> things ''fixed''?
>
> Version: Most bugs have nothing to do with the version of "port", and
> everything to do with the portfile.  Furthermore, there doesn't seem to
> be a way to express the fact that you're tracking base by subversion,
> which is where you'd expect the most "port" bugs to show up.
>
> Component: is trac "www" or "infrastructure"?  Does "Uninstaller" really
> need its own component?
>
> Severity: hardly seems the right way to describe an enum of "Crash/data
> loss", "Serious", "Security", "Performance", "Other".
>
> Keywords: What keywords are acceptable?
>
> 8. Help isn't very visible.
>
> 9. Help doesn't describe this tracker in any detail.
>
> 10. Help doesn't describe this tracker accurately (it implies that
> Priority/Severity should not be separate properties).

New description:

 Trac may be wonderful, but what I wonder is how regular users can stand
 it!

 1. Trac forgets my login when following most links.  I'm not really sure
 what's going on here, because it doesn't always do this.  For example, if
 I enter "http://www.macports.org/", then go there, it remembers earlier
 logins in the current browser sessin, and if there is no login session,
 the password memory makes logging in easy.  Both facilities fail when I
 follow links into the tracker.  Maybe it's that trac doesn't live at
 www.macports.org, but at trac.macports.org, and my browser doesn't send
 the cookie.

 2. ~~''All'' trac pages should have a New Bug button.~~

 3. Many displays assume I have space for a 1200 pixel width window.  (a) I
 don't on several of my workstations (subnotebooks), and (b) I am not a fan
 of letting any application take over my entire screen, especially not one
 subject to network delays.

 4. This wouldn't be so bad (the wide display does contain a lot of
 information, and it's quite useful to keep it on one line), except that a
 lot of useful controls are right-justified and end up off-screen (login,
 search).

 5. There's no easy way to search for bugs against a single port.

 6. ~~The custom query as initialized looks for bugs assigned to me.  Make
 that a standard query, for heaven's sake.  The custom query is the only
 available workaround for #5, so you're encouraging users to enter
 duplicate bugs by making it annoying to search for existing bugs.  The
 custom query should be initialized to search the summary.~~

 7. ~~Ticket properties are insane.  Yes, I've come to "expect" MacPorts to
 throw at least one reportable bug a week, not to mention frequent minor
 annoyances, but what does "Priority: expected" mean in terms of getting
 things ''fixed''?~~

 ~~Version: Most bugs have nothing to do with the version of "port", and
 everything to do with the portfile.  Furthermore, there doesn't seem to be
 a way to express the fact that you're tracking base by subversion, which
 is where you'd expect the most "port" bugs to show up.~~

 ~~Component: is trac "www" or "infrastructure"?  Does "Uninstaller" really
 need its own component?~~

 ~~Severity: hardly seems the right way to describe an enum of "Crash/data
 loss", "Serious", "Security", "Performance", "Other".~~

 ~~Keywords: What keywords are acceptable?~~

 8. Help isn't very visible.

 9. ~~Help doesn't describe this tracker in any detail.~~

 10. ~~Help doesn't describe this tracker accurately (it implies that
 Priority/Severity should not be separate properties).~~

Comment (by jmpp at macports.org):

 It should be noted that this ticket spans multiple issues and the
 preferred way to report them is one issue per ticket. Nevertheless, since
 discussion already happened on this ticket, I'm going to comment on each
 of the points raised and will cross them out of the original description
 if already fixed:

  1. This is a Mac OS Forge issue related to virtual hostnames, if I'm not
 mistaken, and there's nothing the MacPorts team can do about it. I don't
 think it's fixed, as I've personally seen jumps from http based URLs to
 https ones, from trac.macports.org based URLs to trac.macosforge.org ones,
 and even from and to svn.macports.org URLs (with the /projects/macports
 path). Tickets #10665 and #13428 are presumably related to this issue.

  2. This is fixed, crossed out from the original description.

  3. See 4 below.

  4. I'd love it if our Trac portal could be unified into the look of our
 new website, but I'm not too sure this is possible. Mac OS Forge personnel
 has to get back to us on this one, but I'd think they still have more
 pressing matters to attend to so this might be a low priority issue.

  5. If you could provide the SQL glue to build up per port queries I'd
 happily set them up at the
 [http://trac.macports.org/projects/macports/query query] page. Maybe the
 TracReports page might come in handy for this.

  6. You mean to make the query that searches for tickets assigned to the
 logged in user a standard
 [http://trac.macports.org/projects/macports/report report]? If so, then
 {7} and {8} serve that purpose, but you have to be logged in for them to
 work. In any case, I don't see how this helps with item 5 above. Lastly,
 what do you mean by initializing the custom query to search the summary?
 Its initialization doesn't take any user input parameters, so it's hard to
 search the summary for anything in particular. Custom query initializes to
 tickets assigned to the logged in user, displaying the summary among other
 ticket fields, so I'd say this is also covered for. Crossing out from
 original description.

  7. Ticket properties have been standardized to the most common values:
 "Priorities" range from High to Low, including "Not set"; "Version" should
 always match the version of MacPorts you're using, with the svn trunk
 version always being $current_release + 1 (which is always accounted for
 in the "Version" property of tickets), or simply not set ("blank") for
 issues unrelated to MacPorts releases (like the guide or website); Trac
 belongs to the infrastructure component, Installer is no longer a valid
 component; the "Severity" property has been removed; for a particular
 report, any keyword which you might think is related to the issue itself
 and/or might help find it through Trac searches is an appropriate value
 for the corresponding field. Reading our
 [http://guide.macports.org/#project.tickets ticketing guidelines] will
 help in understanding our workflow. Crossing out from original
 description.

  8. If you mean the Help link on the sidebar, then this is more than
 anything related to the visual design of our Trac portal, see item 4 above
 in my reply.

  9. That help link is about Trac itself. When you say "describe this
 tracker" I can only assume you are referring to a description of MacPorts
 itself and our particular Trac workflow. Our new [http://www.macports.org
 web page] and [http://guide.macports.org/#project.tickets ticketing
 guidelines] fill that void. Crossing out from original description.

  10. We don't maintain that help document and, above all, "Severity" is no
 longer a valid ticket property for us. Crossing out from original
 description.

  11. (from the first ticket comment) Assigning to a port  maintainer is as
 simple as selecting his/her e-mail address from the "Assign to" pop-up
 menu for the corresponding ticket property. even though currently not all
 maintainers are listed in that menu, as per the discussion in ticket
 #13352. Nevertheless, the facility to assign tickets is there and readily
 available, so this issue is also covered for.


 -jmpp

-- 

MacPorts </projects/macports>
Ports system for Mac OS

From turnbull at sk.tsukuba.ac.jp  Tue Feb  5 09:05:05 2008
From: turnbull at sk.tsukuba.ac.jp (Stephen J. Turnbull)
Date: Tue, 05 Feb 2008 17:05:05 +0900
Subject: [Tracker-discuss] Creating a Jython tracker
In-Reply-To: <47A78B38.2030600@v.loewis.de>
References: <20080203135806.GA512@amk.local> <47A601B2.2010700@v.loewis.de>
	<bbaeab100802031256j7f42330al3e53581241ea7694@mail.gmail.com>
	<4dab5f760802031419i2fce5fa0xa77300fbe5d9d663@mail.gmail.com>
	<4dab5f760802031427n5559e236x359f31b238517ed2@mail.gmail.com>
	<bbaeab100802031442p7db4be63xb8cfb6f3019b6def@mail.gmail.com>
	<4dab5f760802041118w3f6fe570le04854dc1e507623@mail.gmail.com>
	<47A78B38.2030600@v.loewis.de>
Message-ID: <87y79zu8um.fsf@uwakimon.sk.tsukuba.ac.jp>

"Martin v. L?wis" writes:
 > In such a scenario, the [Tracker X] supporters would have get
 > together and volunteer some people to actually perform the
 > necessary setup work, so if [Tracker X] wins, you have already
 > volunteers for the first three months into the tracker's life (our
 > experience tells that most volunteers will run away within the
 > first 6 months after getting this set-up and adopted). For Python,
 > it's currently just me that does any maintenance on the tracker.

Yep.  This is precisely why I ended up with Roundup: (a) I liked it
already, and (b) I knew I could trust Python to do a good job and
stick with it, so I'd have a good implementation to refer to.  By
contrast, I couldn't even get accurate feature lists from the RT,
Trac, and Bugzilla advocates, let alone a commitment to some months of
support.  "He who does the work makes the choices."

BTW, Martin, I went with the SVN tip of Roundup (1.4.1 + a couple
patches) instead of the stable 1.3.x that the Python tracker is based
on, and it does a very good job of preventing bad input that results
in tracebacks in the user's browser.  For example, I just confirmed that
the "no such user in Actor or Creator" bug is fixed (1.4.x has a nice
Javascript-based selection menu for such input, so you *can't* enter a
nonexistent user AFAICT).

From forsberg at efod.se  Tue Feb  5 19:17:38 2008
From: forsberg at efod.se (Erik Forsberg)
Date: Tue, 5 Feb 2008 19:17:38 +0100
Subject: [Tracker-discuss] Creating a Jython tracker
In-Reply-To: <bbaeab100802031256j7f42330al3e53581241ea7694@mail.gmail.com>
References: <20080203135806.GA512@amk.local> <47A601B2.2010700@v.loewis.de>
	<bbaeab100802031256j7f42330al3e53581241ea7694@mail.gmail.com>
Message-ID: <20080205191738.0ae79ea1@uterus>

> into helping out on a permanent basis. Since Upfront maintains the
> machine its mostly Roundup maintenance/customization and database
> stuff (am I missing something, Martin or Erik?).

Nope, that's about it. 

\EF
-- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9

From fwierzbicki at gmail.com  Wed Feb  6 19:12:08 2008
From: fwierzbicki at gmail.com (Frank Wierzbicki)
Date: Wed, 6 Feb 2008 13:12:08 -0500
Subject: [Tracker-discuss] Creating a Jython tracker
In-Reply-To: <47A63AA0.50303@v.loewis.de>
References: <20080203135806.GA512@amk.local> <47A601B2.2010700@v.loewis.de>
	<47A63AA0.50303@v.loewis.de>
Message-ID: <4dab5f760802061012t36879de7t1080eabc65216fdb@mail.gmail.com>

On Feb 3, 2008 5:05 PM, "Martin v. L?wis" <martin at v.loewis.de> wrote:
> As a further follow-up, I also need a list of components (the things
> where the Python tracker has "Build", "Distutils" etc), and any mapping
> between SF categories and roundup components - take particular notice
> that all three SF trackers will be merged into a single one.
Okay, we are settled on Roundup for Jython's tracker.  I'll gather up
the required mappings and report back here.  A member of the Jython
community, Raghuram Devarakonda, has kindly volunteered to help out.

Raghuram: if you aren't subscribed to this list
(tracker-discuss at python.org) this is the list where roundup is
discussed.  The place to do that is here:
http://mail.python.org/mailman/listinfo/tracker-discuss

Thanks,

-Frank

From draghuram at gmail.com  Wed Feb  6 19:37:49 2008
From: draghuram at gmail.com (Raghuram Devarakonda)
Date: Wed, 6 Feb 2008 13:37:49 -0500
Subject: [Tracker-discuss] Creating a Jython tracker
In-Reply-To: <4dab5f760802061012t36879de7t1080eabc65216fdb@mail.gmail.com>
References: <20080203135806.GA512@amk.local> <47A601B2.2010700@v.loewis.de>
	<47A63AA0.50303@v.loewis.de>
	<4dab5f760802061012t36879de7t1080eabc65216fdb@mail.gmail.com>
Message-ID: <2c51ecee0802061037g18569970sd39133aaf650581d@mail.gmail.com>

> Raghuram: if you aren't subscribed to this list

I am already subscribed to the list.

Martin, I will try to gather some details you asked for in a previous
mail in this thread. I am thinking of creating a meta-tracker issue
and add the info there. Please let me know if this is ok with you.

Thanks,
Raghu

From martin at v.loewis.de  Wed Feb  6 20:11:36 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Wed, 06 Feb 2008 20:11:36 +0100
Subject: [Tracker-discuss] Creating a Jython tracker
In-Reply-To: <2c51ecee0802061037g18569970sd39133aaf650581d@mail.gmail.com>
References: <20080203135806.GA512@amk.local> <47A601B2.2010700@v.loewis.de>	
	<47A63AA0.50303@v.loewis.de>	
	<4dab5f760802061012t36879de7t1080eabc65216fdb@mail.gmail.com>
	<2c51ecee0802061037g18569970sd39133aaf650581d@mail.gmail.com>
Message-ID: <47AA0668.50205@v.loewis.de>

> Martin, I will try to gather some details you asked for in a previous
> mail in this thread. I am thinking of creating a meta-tracker issue
> and add the info there. Please let me know if this is ok with you.

That's fine. I created a jython keyword; feel free to tag anything
relevant with that keyword.

As for helping out - I'd like to give precedence to issues tagged
as jython. If you can help with any other issues reported in the
metatracker, that would be appreciated, but you shouldn't feel
obliged to.

Regards,
Martin

From metatracker at psf.upfronthosting.co.za  Wed Feb  6 22:45:12 2008
From: metatracker at psf.upfronthosting.co.za (Raghuram Devarakonda)
Date: Wed, 06 Feb 2008 21:45:12 -0000
Subject: [Tracker-discuss] [issue184] Create a tracker instance for jython
In-Reply-To: <1202334312.21.0.456420573798.issue184@psf.upfronthosting.co.za>
Message-ID: <1202334312.21.0.456420573798.issue184@psf.upfronthosting.co.za>


New submission from Raghuram Devarakonda:

It has been decided to switch jython's tracker from SF to roundup. This issue
will be used to track it's progress.

----------
messages: 933
nosy: draghuram
priority: feature
status: unread
title: Create a tracker instance for jython

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

From metatracker at psf.upfronthosting.co.za  Fri Feb  8 04:10:26 2008
From: metatracker at psf.upfronthosting.co.za (Raghuram Devarakonda)
Date: Fri, 08 Feb 2008 03:10:26 -0000
Subject: [Tracker-discuss] [issue184] Create a tracker instance for jython
In-Reply-To: <1202334312.21.0.456420573798.issue184@psf.upfronthosting.co.za>
Message-ID: <1202440226.59.0.97424310849.issue184@psf.upfronthosting.co.za>


Raghuram Devarakonda added the comment:

Martin,

I gathered the following information from jython's SF trackers.

components (merged from three SF trackers)
   Any
   Core
   Documentation
   Installer
   Jythonc compiler
   Library
   website
   zxjdbc

Priorities
   We can use same mapping as for python.

Versions (SF's Groups)
   Deferred
   Fixed in 2.1a3
   Fixed in 2.1b1
   Fixed in 2.1b2
   Fixed in 2.1final
   Fixed in 2.2a0
   targeted for 2.2.1rc1
   targeted for 2.2beta1
   targeted for 2.2beta2
   targeted for 2.2rc1
   targeted for 2.2rc2
   targeted for 2.2rc3
   test failure causes

issue_types
   behaviour
   security
   rfe
   crash

resolutions
   We can use python's values.

Please let me know if you want any help from me in further progress of this
issue. BTW, in your earlier mail, you said "I see that the Jython tracker has
nothing above 5, but also has 4, 3, 2". When I sorted the bugs by priority, I do
see values starting from 9 downwards. Am I missing something?

Thanks,
Raghu

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

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

From metatracker at psf.upfronthosting.co.za  Sat Feb  9 12:05:38 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Sat, 09 Feb 2008 11:05:38 -0000
Subject: [Tracker-discuss] [issue184] Create a tracker instance for jython
In-Reply-To: <1202334312.21.0.456420573798.issue184@psf.upfronthosting.co.za>
Message-ID: <1202555138.1.0.951713051264.issue184@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

I have now created a Jython tracker at

http://psf.upfronthosting.co.za/roundup/jython/

and imported all issues at time 1202518715. The tracker instance is checked in at

http://svn.python.org/projects/tracker/instances/jython/

Nosy email is currently disabled until the emailing details are resolved;
password recovery through email should work.

As the next step, we should tackle email and DNS issues (DNS only if you want to
use a different tracker URL than the one that the tracker currently has)

----------
assignedto: loewis -> draghuram

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

From metatracker at psf.upfronthosting.co.za  Sat Feb  9 23:50:44 2008
From: metatracker at psf.upfronthosting.co.za (Charlie Groves)
Date: Sat, 09 Feb 2008 22:50:44 -0000
Subject: [Tracker-discuss] [issue184] Create a tracker instance for jython
In-Reply-To: <1202334312.21.0.456420573798.issue184@psf.upfronthosting.co.za>
Message-ID: <1202597444.87.0.231677116358.issue184@psf.upfronthosting.co.za>


Charlie Groves added the comment:

Are there tracker docs beyond what's at http://wiki.python.org/moin/TrackerDocs/
 I'm trying to figure out if it's possible to batch edit items ie we're going to
want to close everything with the "Jythonc compiler" component when we finally
finish transitioning away from it.

Do we need to find someone to integrate the look of the tracker into Jython's site?

The initial import looks good from my poking around.  It's great to see the
r<number> messages I've been adding to messages actually link to fisheye.

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

From metatracker at psf.upfronthosting.co.za  Sat Feb  9 23:54:56 2008
From: metatracker at psf.upfronthosting.co.za (Charlie Groves)
Date: Sat, 09 Feb 2008 22:54:56 -0000
Subject: [Tracker-discuss] [issue184] Create a tracker instance for jython
In-Reply-To: <1202334312.21.0.456420573798.issue184@psf.upfronthosting.co.za>
Message-ID: <1202597696.86.0.559509049774.issue184@psf.upfronthosting.co.za>


Charlie Groves added the comment:

For versions, it'd be nice to make "test failure causes" a keyword, and then the
remaining items would uniformly be the version when an issue was resolved.

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

From martin at v.loewis.de  Sun Feb 10 00:14:38 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Sun, 10 Feb 2008 00:14:38 +0100
Subject: [Tracker-discuss] [issue184] Create a tracker instance for
	jython
In-Reply-To: <1202597444.87.0.231677116358.issue184@psf.upfronthosting.co.za>
References: <1202597444.87.0.231677116358.issue184@psf.upfronthosting.co.za>
Message-ID: <47AE33DE.20108@v.loewis.de>

> Are there tracker docs beyond what's at http://wiki.python.org/moin/TrackerDocs/
>  I'm trying to figure out if it's possible to batch edit items ie we're going to
> want to close everything with the "Jythonc compiler" component when we finally
> finish transitioning away from it.

To batch-edit, the easiest thing would be to submit an issue here; I'll 
do the batch edit.

> Do we need to find someone to integrate the look of the tracker into Jython's site?

I don't understand the question. What else needs to be done?

Regards,
Martin

From metatracker at psf.upfronthosting.co.za  Sun Feb 10 00:14:43 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Sat, 09 Feb 2008 23:14:43 -0000
Subject: [Tracker-discuss] [issue184] Create a tracker instance for jython
In-Reply-To: <1202597444.87.0.231677116358.issue184@psf.upfronthosting.co.za>
Message-ID: <47AE33DE.20108@v.loewis.de>


Martin v. L?wis added the comment:

> Are there tracker docs beyond what's at http://wiki.python.org/moin/TrackerDocs/
>  I'm trying to figure out if it's possible to batch edit items ie we're going to
> want to close everything with the "Jythonc compiler" component when we finally
> finish transitioning away from it.

To batch-edit, the easiest thing would be to submit an issue here; I'll 
do the batch edit.

> Do we need to find someone to integrate the look of the tracker into Jython's site?

I don't understand the question. What else needs to be done?

Regards,
Martin

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

From martin at v.loewis.de  Sun Feb 10 00:16:34 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Sun, 10 Feb 2008 00:16:34 +0100
Subject: [Tracker-discuss] [issue184] Create a tracker instance for
	jython
In-Reply-To: <1202597696.86.0.559509049774.issue184@psf.upfronthosting.co.za>
References: <1202597696.86.0.559509049774.issue184@psf.upfronthosting.co.za>
Message-ID: <47AE3452.4070601@v.loewis.de>

> For versions, it'd be nice to make "test failure causes" a keyword, and then the
> remaining items would uniformly be the version when an issue was resolved.

I don't understand. What are "the remaining items", what is "uniformly",
and what is "the version when an issue was resolved"?

Perhaps you can give a specific example?

From metatracker at psf.upfronthosting.co.za  Sun Feb 10 00:16:37 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Sat, 09 Feb 2008 23:16:37 -0000
Subject: [Tracker-discuss] [issue184] Create a tracker instance for jython
In-Reply-To: <1202597696.86.0.559509049774.issue184@psf.upfronthosting.co.za>
Message-ID: <47AE3452.4070601@v.loewis.de>


Martin v. L?wis added the comment:

> For versions, it'd be nice to make "test failure causes" a keyword, and then the
> remaining items would uniformly be the version when an issue was resolved.

I don't understand. What are "the remaining items", what is "uniformly",
and what is "the version when an issue was resolved"?

Perhaps you can give a specific example?

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

From metatracker at psf.upfronthosting.co.za  Sun Feb 10 01:02:17 2008
From: metatracker at psf.upfronthosting.co.za (Charlie Groves)
Date: Sun, 10 Feb 2008 00:02:17 -0000
Subject: [Tracker-discuss] [issue184] Create a tracker instance for jython
In-Reply-To: <1202334312.21.0.456420573798.issue184@psf.upfronthosting.co.za>
Message-ID: <1202601737.89.0.437962203468.issue184@psf.upfronthosting.co.za>


Charlie Groves added the comment:

>> Do we need to find someone to integrate the look of the tracker into Jython's
site?

>I don't understand the question. What else needs to be done?

Not much at the moment.  That the colors for the roundup stuff doesn't match the
rest of the site makes it look like it was pasted in there.

I asked if we should get someone to do this kinda stuff as I didn't want to
bother you with a bunch of fiddly UI requests, and I'm sure more will come up.

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

From metatracker at psf.upfronthosting.co.za  Sun Feb 10 01:07:35 2008
From: metatracker at psf.upfronthosting.co.za (Charlie Groves)
Date: Sun, 10 Feb 2008 00:07:35 -0000
Subject: [Tracker-discuss] [issue184] Create a tracker instance for jython
In-Reply-To: <1202334312.21.0.456420573798.issue184@psf.upfronthosting.co.za>
Message-ID: <1202602054.99.0.298432630457.issue184@psf.upfronthosting.co.za>


Charlie Groves added the comment:

>I don't understand. What are "the remaining items", what is "uniformly",
>and what is "the version when an issue was resolved"?

I'm referring to the Versions field that came from groups on Sourceforge.  These
are the values right now:
   Deferred
   Fixed in 2.1a3
   Fixed in 2.1b1
   Fixed in 2.1b2
   Fixed in 2.1final
   Fixed in 2.2a0
   targeted for 2.2.1rc1
   targeted for 2.2beta1
   targeted for 2.2beta2
   targeted for 2.2rc1
   targeted for 2.2rc2
   targeted for 2.2rc3
   test failure causes

I'd like to take anything that has the version "test failure causes", give it a
keyword of the same name, and unset its version value.  Then we could delete the
"test failure causes" version and the values for versions would "uniformly" be
versions.

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

From martin at v.loewis.de  Sun Feb 10 07:43:03 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Sun, 10 Feb 2008 07:43:03 +0100
Subject: [Tracker-discuss] [issue184] Create a tracker instance for
	jython
In-Reply-To: <1202601737.89.0.437962203468.issue184@psf.upfronthosting.co.za>
References: <1202601737.89.0.437962203468.issue184@psf.upfronthosting.co.za>
Message-ID: <47AE9CF7.9020002@v.loewis.de>

> I asked if we should get someone to do this kinda stuff as I didn't want to
> bother you with a bunch of fiddly UI requests, and I'm sure more will come up.

Yes: if the UI doesn't look right, please provide patches against the 
tracker instance.

From metatracker at psf.upfronthosting.co.za  Sun Feb 10 07:43:08 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Sun, 10 Feb 2008 06:43:08 -0000
Subject: [Tracker-discuss] [issue184] Create a tracker instance for jython
In-Reply-To: <1202601737.89.0.437962203468.issue184@psf.upfronthosting.co.za>
Message-ID: <47AE9CF7.9020002@v.loewis.de>


Martin v. L?wis added the comment:

> I asked if we should get someone to do this kinda stuff as I didn't want to
> bother you with a bunch of fiddly UI requests, and I'm sure more will come up.

Yes: if the UI doesn't look right, please provide patches against the 
tracker instance.

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

From martin at v.loewis.de  Sun Feb 10 07:45:27 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Sun, 10 Feb 2008 07:45:27 +0100
Subject: [Tracker-discuss] [issue184] Create a tracker instance for
	jython
In-Reply-To: <1202602054.99.0.298432630457.issue184@psf.upfronthosting.co.za>
References: <1202602054.99.0.298432630457.issue184@psf.upfronthosting.co.za>
Message-ID: <47AE9D87.6080107@v.loewis.de>

> I'd like to take anything that has the version "test failure causes", give it a
> keyword of the same name, and unset its version value.  Then we could delete the
> "test failure causes" version and the values for versions would "uniformly" be
> versions.

Ah, ok. I'll fix the importer to do so on the next round.

From metatracker at psf.upfronthosting.co.za  Sun Feb 10 07:45:30 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Sun, 10 Feb 2008 06:45:30 -0000
Subject: [Tracker-discuss] [issue184] Create a tracker instance for jython
In-Reply-To: <1202602054.99.0.298432630457.issue184@psf.upfronthosting.co.za>
Message-ID: <47AE9D87.6080107@v.loewis.de>


Martin v. L?wis added the comment:

> I'd like to take anything that has the version "test failure causes", give it a
> keyword of the same name, and unset its version value.  Then we could delete the
> "test failure causes" version and the values for versions would "uniformly" be
> versions.

Ah, ok. I'll fix the importer to do so on the next round.

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

From skip at pobox.com  Sun Feb 10 15:27:36 2008
From: skip at pobox.com (skip at pobox.com)
Date: Sun, 10 Feb 2008 08:27:36 -0600
Subject: [Tracker-discuss] Another Python tracker spinoff...
Message-ID: <18351.2520.58411.591694@montanaro-dyndns-org.local>

FYI...  From a posting to the XEmacs Beta mailing list:

>>>>> "Stephen" == Stephen J Turnbull <stephen at xemacs.org> writes:

    Stephen> At long last the XEmacs Project enters the 21st century with a
    Stephen> modern issue tracker of its own.

    Stephen> It's based on the Roundup tracker designed by Ka-Ping Yee and
    Stephen> implemented by Richard Jones, with a few pieces (and probably
    Stephen> more to come) borrowed from the Python issue tracker.

    Stephen> It's been primed with about 125 XEmacs issues from the
    Stephen> xemacs-beta mailing list since October 1, 2007, and 60 or so
    Stephen> tracker-specific issues.  Currently users are expected to
    Stephen> interact with the tracker via the web interface, but a filter
    Stephen> on the xemacs-beta list which will automatically forward bug
    Stephen> reports to the tracker is planned for the near future.

    Stephen> To get started with the tracker, visit

    Stephen>     http://tracker.xemacs.org/XEmacs/its/

    ...

Skip

From metatracker at psf.upfronthosting.co.za  Sun Feb 10 19:10:18 2008
From: metatracker at psf.upfronthosting.co.za (Raghuram Devarakonda)
Date: Sun, 10 Feb 2008 18:10:18 -0000
Subject: [Tracker-discuss] [issue184] Create a tracker instance for jython
In-Reply-To: <1202555138.1.0.951713051264.issue184@psf.upfronthosting.co.za>
Message-ID: <2c51ecee0802101010j443470edrb7339752fa92bcc7@mail.gmail.com>


Raghuram Devarakonda added the comment:

On Feb 9, 2008 6:05 AM, Martin v. L?wis
<metatracker at psf.upfronthosting.co.za> wrote:
>
> Martin v. L?wis added the comment:
>
> I have now created a Jython tracker at
>
> http://psf.upfronthosting.co.za/roundup/jython/

The messages in each tracker item show up very small by default on my
laptop. The python tracker items look fine. Has any one else noticed
this?

> and imported all issues at time 1202518715. The tracker instance is checked in at
>
> http://svn.python.org/projects/tracker/instances/jython/

I will try to set up a local tracker instance. Last week, I tried to
set up local python tracker as detailed in
http://wiki.python.org/moin/TrackerDevelopment?highlight=%28tracker%29
but I ran into some problems. The page needs to mention spambayes and
psycopg2 (I can do that once I have a successful setup). After I
checked them out, I got an error about a missing user in the data
base. I will start a separate thread for it.

> Nosy email is currently disabled until the emailing details are resolved;
> password recovery through email should work.

> As the next step, we should tackle email and DNS issues (DNS only if you want to
> use a different tracker URL than the one that the tracker currently has)

Can you please mention what needs to be done for email? I think we
should go for "bugs.jython.org" so that would require DNS change.

Thanks,
Raghu

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

From metatracker at psf.upfronthosting.co.za  Sun Feb 10 19:49:40 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Sun, 10 Feb 2008 18:49:40 -0000
Subject: [Tracker-discuss] [issue184] Create a tracker instance for jython
In-Reply-To: <2c51ecee0802101010j443470edrb7339752fa92bcc7@mail.gmail.com>
Message-ID: <47AF4741.5000004@v.loewis.de>


Martin v. L?wis added the comment:

>> I have now created a Jython tracker at
>>
>> http://psf.upfronthosting.co.za/roundup/jython/
> 
> The messages in each tracker item show up very small by default on my
> laptop. The python tracker items look fine. Has any one else noticed
> this?

I'm using the jython.org style sheets. I assumed the font sizes are 
intentional. If not, please provide patches (or change the style sheets
themselves).

>> and imported all issues at time 1202518715. The tracker instance is checked in at
>>
>> http://svn.python.org/projects/tracker/instances/jython/
> 
> I will try to set up a local tracker instance. Last week, I tried to
> set up local python tracker as detailed in
> http://wiki.python.org/moin/TrackerDevelopment?highlight=%28tracker%29
> but I ran into some problems. The page needs to mention spambayes and
> psycopg2 (I can do that once I have a successful setup).

You need psycopg or psycopg2, yes. You don't need spambayes installed,
but you do need to check out the spambayes_integration.

Please do edit the Wiki to add any missing pieces.

>> As the next step, we should tackle email and DNS issues (DNS only if you want to
>> use a different tracker URL than the one that the tracker currently has)
> 
> Can you please mention what needs to be done for email? I think we
> should go for "bugs.jython.org" so that would require DNS change.

I think the first step should then be the DNS setup. We need

bugs.jython.org.        86400   IN      MX      10 bugs.python.org
bugs.jython.org.        86400   IN      A       88.198.142.26

The reverse lookup will point to bugs.python.org; there isn't much
we can do about that. Perhaps it's better to make bugs.jython.org
a CNAME instead.

Then, I need to know
a) the submission address for new issues, and reply address for
    follow-ups (report at bugs.python.org for the python-dev tracker)
    (config.ini:[tracker]:email)
b) an email list where new bug reports are sent to (optional)
c) an email list where just any change in the tracker is sent to
    (optional)
d) an email list where weekly status reports are sent to (optional)
e) a recipient (list) for admin_email

Regards,
Martin

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

From metatracker at psf.upfronthosting.co.za  Sun Feb 10 23:49:08 2008
From: metatracker at psf.upfronthosting.co.za (Stephen Turnbull)
Date: Sun, 10 Feb 2008 22:49:08 -0000
Subject: [Tracker-discuss] [issue184] Create a tracker instance for jython
In-Reply-To: <47AF4741.5000004@v.loewis.de>
Message-ID: <87ejbk4e1c.fsf@uwakimon.sk.tsukuba.ac.jp>


Stephen Turnbull added the comment:

Martin v. L?wis writes:
 > I think the first step should then be the DNS setup. We need
 > 
 > bugs.jython.org.        86400   IN      MX      10 bugs.python.org
 > bugs.jython.org.        86400   IN      A       88.198.142.26
 > 
 > The reverse lookup will point to bugs.python.org; there isn't much
 > we can do about that. Perhaps it's better to make bugs.jython.org
 > a CNAME instead.

I personally prefer the CNAME approach for my own installation.  I run
Roundup behind Apache, on an Apache vhost with that name.  So far in
light testing I've been unable to "escape" from the published name to
the canonical name of the host, although of course I can get to the
tracker by using the canonical name.  So I don't really see a need for
PTRs to point to the published domain.

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

From stephen at xemacs.org  Sun Feb 10 23:55:43 2008
From: stephen at xemacs.org (Stephen J. Turnbull)
Date: Mon, 11 Feb 2008 07:55:43 +0900
Subject: [Tracker-discuss] [issue184] Create a tracker instance for jython
In-Reply-To: <47AF4741.5000004@v.loewis.de>
References: <2c51ecee0802101010j443470edrb7339752fa92bcc7@mail.gmail.com>
	<47AF4741.5000004@v.loewis.de>
Message-ID: <87ejbk4e1c.fsf@uwakimon.sk.tsukuba.ac.jp>

Martin v. L?wis writes:
 > I think the first step should then be the DNS setup. We need
 > 
 > bugs.jython.org.        86400   IN      MX      10 bugs.python.org
 > bugs.jython.org.        86400   IN      A       88.198.142.26
 > 
 > The reverse lookup will point to bugs.python.org; there isn't much
 > we can do about that. Perhaps it's better to make bugs.jython.org
 > a CNAME instead.

I personally prefer the CNAME approach for my own installation.  I run
Roundup behind Apache, on an Apache vhost with that name.  So far in
light testing I've been unable to "escape" from the published name to
the canonical name of the host, although of course I can get to the
tracker by using the canonical name.  So I don't really see a need for
PTRs to point to the published domain.



From metatracker at psf.upfronthosting.co.za  Mon Feb 11 17:48:40 2008
From: metatracker at psf.upfronthosting.co.za (Raghuram Devarakonda)
Date: Mon, 11 Feb 2008 16:48:40 -0000
Subject: [Tracker-discuss] [issue184] Create a tracker instance for jython
In-Reply-To: <47AF4741.5000004@v.loewis.de>
Message-ID: <2c51ecee0802110848u762dbe35k3924d80f200102d@mail.gmail.com>


Raghuram Devarakonda added the comment:

On Feb 10, 2008 1:49 PM, Martin v. L?wis
<metatracker at psf.upfronthosting.co.za> wrote:

> I'm using the jython.org style sheets. I assumed the font sizes are
> intentional. If not, please provide patches (or change the style sheets
> themselves).

The font size looks ok from my linux desktop but it looked unreadable
on my xp laptop. I don't know if any one else observed this or not. I
do like the way cpython's tracker items look (which is pretty much
same on both my machines).

> You need psycopg or psycopg2, yes. You don't need spambayes installed,
> but you do need to check out the spambayes_integration.

> Please do edit the Wiki to add any missing pieces.

Done.

> I think the first step should then be the DNS setup. We need
>
> bugs.jython.org.        86400   IN      MX      10 bugs.python.org
> bugs.jython.org.        86400   IN      A       88.198.142.26
>
> The reverse lookup will point to bugs.python.org; there isn't much
> we can do about that. Perhaps it's better to make bugs.jython.org
> a CNAME instead.

I am not expert at these things but I guess some one who is
maintaining jython.org needs to do this. Frank, Charlie?

> Then, I need to know
> a) the submission address for new issues, and reply address for
>     follow-ups (report at bugs.python.org for the python-dev tracker)
>     (config.ini:[tracker]:email)
> b) an email list where new bug reports are sent to (optional)
> c) an email list where just any change in the tracker is sent to
>     (optional)
> d) an email list where weekly status reports are sent to (optional)
> e) a recipient (list) for admin_email

AFAICT, jython.org doesn't operate any mailing lists on it's own. It
would be nice if we (jython community) can set up at least few of
these lists. I found python's New-Bugs-Announce list very useful and
am sure the same will be true for jython. Frank, Charile: comments?

As for the admin_email, I am ok for my email to be added there.

Thanks,
Raghu

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

From metatracker at psf.upfronthosting.co.za  Mon Feb 11 17:51:24 2008
From: metatracker at psf.upfronthosting.co.za (Raghuram Devarakonda)
Date: Mon, 11 Feb 2008 16:51:24 -0000
Subject: [Tracker-discuss] [issue184] Create a tracker instance for jython
In-Reply-To: <2c51ecee0802110848u762dbe35k3924d80f200102d@mail.gmail.com>
Message-ID: <2c51ecee0802110851w2944a1f5ue27dcb8344c38848@mail.gmail.com>


Raghuram Devarakonda added the comment:

I just noticed that Charile Groves id does not appear in nosy list
even though he posted messages for this issue. Doesn't adding a
comment automatically result in addition to nosy list?

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

From metatracker at psf.upfronthosting.co.za  Mon Feb 11 19:09:43 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Mon, 11 Feb 2008 18:09:43 -0000
Subject: [Tracker-discuss] [issue184] Create a tracker instance for jython
In-Reply-To: <2c51ecee0802110851w2944a1f5ue27dcb8344c38848@mail.gmail.com>
Message-ID: <47B08F64.7000401@v.loewis.de>


Martin v. L?wis added the comment:

> I just noticed that Charile Groves id does not appear in nosy list
> even though he posted messages for this issue. Doesn't adding a
> comment automatically result in addition to nosy list?

Not in this tracker, no.

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

From metatracker at psf.upfronthosting.co.za  Tue Feb 12 01:18:44 2008
From: metatracker at psf.upfronthosting.co.za (Frank Wierzbicki)
Date: Tue, 12 Feb 2008 00:18:44 -0000
Subject: [Tracker-discuss] [issue184] Create a tracker instance for jython
In-Reply-To: <1202334312.21.0.456420573798.issue184@psf.upfronthosting.co.za>
Message-ID: <1202775524.43.0.668078246475.issue184@psf.upfronthosting.co.za>


Frank Wierzbicki added the comment:

draghuram: does the Jython website appear too small on your laptop?  If so maybe
the css needs to be edited in general.

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

From metatracker at psf.upfronthosting.co.za  Tue Feb 12 07:55:10 2008
From: metatracker at psf.upfronthosting.co.za (Charlie Groves)
Date: Tue, 12 Feb 2008 06:55:10 -0000
Subject: [Tracker-discuss] [issue184] Create a tracker instance for jython
In-Reply-To: <1202334312.21.0.456420573798.issue184@psf.upfronthosting.co.za>
Message-ID: <1202799310.83.0.599510458535.issue184@psf.upfronthosting.co.za>


Charlie Groves added the comment:

>> I think the first step should then be the DNS setup.
>I am not expert at these things but I guess some one who is
>maintaining jython.org needs to do this. Frank, Charlie?

The last time we needed to change something in the DNS, Khalid said it was
managed by XS4ALL.  He said he emailed the pydotorg mailing list and they took
care of it.

> AFAICT, jython.org doesn't operate any mailing lists on it's own. It
> would be nice if we (jython community) can set up at least few of
> these lists. I found python's New-Bugs-Announce list very useful and
> am sure the same will be true for jython. Frank, Charile: comments?

All of our lists are run by sourceforge.  We have
https://lists.sourceforge.net/lists/listinfo/jython-bugs which has been working
well for me, and I think it can serve as the bugs list for the new tracker too.

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

From brett at python.org  Tue Feb 12 11:43:14 2008
From: brett at python.org (Brett Cannon)
Date: Tue, 12 Feb 2008 02:43:14 -0800
Subject: [Tracker-discuss] draft of call for more volunteers
Message-ID: <bbaeab100802120243y4db36e91v683c56112e3c9efb@mail.gmail.com>

Let me know what you think:


The Python Software Foundation's infrastructure committee is looking
for volunteers to help maintain the Roundup issue tracker installed
for http://bugs.python.org. Responsibilities revolve around
maintaining the Roundup installation itself (tracker schema, modifying
the installed copy of Roundup, etc.) and the occasional database work
(changes to the database, etc.).

You do not have to be an expert at Roundup to volunteer! You can learn
"on the job" by doing offline development and submitting patches until
you are of a proper level of experience to gain commit access to the
code (which can be seen at XXX). If you still have a New Years
resolution to help Python out this is a great way to fulfill the
promise you made yourself for 2008!

If you are interested in volunteering, please email tracker-discuss at
python.org. Thanks to all who have helped with the tracker already and
those that will in the future!

-Brett Cannon
Chairman, PSF infrastructure committee

From metatracker at psf.upfronthosting.co.za  Tue Feb 12 14:44:21 2008
From: metatracker at psf.upfronthosting.co.za (Raghuram Devarakonda)
Date: Tue, 12 Feb 2008 13:44:21 -0000
Subject: [Tracker-discuss] [issue184] Create a tracker instance for jython
In-Reply-To: <1202775524.43.0.668078246475.issue184@psf.upfronthosting.co.za>
Message-ID: <2c51ecee0802120544u6c1d39bepbe0d35c532b821cb@mail.gmail.com>


Raghuram Devarakonda added the comment:

On Feb 11, 2008 7:18 PM, Frank Wierzbicki
<metatracker at psf.upfronthosting.co.za> wrote:
> draghuram: does the Jython website appear too small on your laptop?  If so maybe
> the css needs to be edited in general.

The web site looks ok. Even the top page of tracker looks fine.
However, when I click on a bug, the messages look very small,
practically unreadable.

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

From metatracker at psf.upfronthosting.co.za  Tue Feb 12 18:35:37 2008
From: metatracker at psf.upfronthosting.co.za (Raghuram Devarakonda)
Date: Tue, 12 Feb 2008 17:35:37 -0000
Subject: [Tracker-discuss] [issue184] Create a tracker instance for jython
In-Reply-To: <47AF4741.5000004@v.loewis.de>
Message-ID: <2c51ecee0802120935m3f01eb15lc87ee9aff2c5e38a@mail.gmail.com>


Raghuram Devarakonda added the comment:

> I think the first step should then be the DNS setup. We need
>
> bugs.jython.org.        86400   IN      MX      10 bugs.python.org
> bugs.jython.org.        86400   IN      A       88.198.142.26

As per Charlie's mail, a mail to the pydotorg is required for this
change. Frank, Charlie, can one of you take care of sending mail and
getting this change done? I think it would be better if ti comes from
maintainers of the project.

> Then, I need to know
> a) the submission address for new issues, and reply address for
>     follow-ups (report at bugs.python.org for the python-dev tracker)  (config.ini:[tracker]:email)

How about report at bugs.jython.org (assuming DNS change is done)?

> b) an email list where new bug reports are sent to (optional)
> c) an email list where just any change in the tracker is sent to
>     (optional)

jython-bugs at lists.sourceforge.net. This is the only bugs list
available and we can use it for both purposes for now.

> d) an email list where weekly status reports are sent to (optional)

jython-dev at lists.sourceforge.net.

> e) a recipient (list) for admin_email

draghuram at gmail.com (my address)

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

From amk at amk.ca  Tue Feb 12 18:36:10 2008
From: amk at amk.ca (A.M. Kuchling)
Date: Tue, 12 Feb 2008 12:36:10 -0500
Subject: [Tracker-discuss] draft of call for more volunteers
In-Reply-To: <bbaeab100802120243y4db36e91v683c56112e3c9efb@mail.gmail.com>
References: <bbaeab100802120243y4db36e91v683c56112e3c9efb@mail.gmail.com>
Message-ID: <20080212173610.GA10198@amk-desktop.matrixgroup.net>

On Tue, Feb 12, 2008 at 02:43:14AM -0800, Brett Cannon wrote:
> Let me know what you think:

Seems fine to me.

--amk

From metatracker at psf.upfronthosting.co.za  Tue Feb 12 20:16:16 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Tue, 12 Feb 2008 19:16:16 -0000
Subject: [Tracker-discuss] [issue184] Create a tracker instance for jython
In-Reply-To: <2c51ecee0802120935m3f01eb15lc87ee9aff2c5e38a@mail.gmail.com>
Message-ID: <47B1F07D.7010300@v.loewis.de>


Martin v. L?wis added the comment:

> As per Charlie's mail, a mail to the pydotorg is required for this
> change. Frank, Charlie, can one of you take care of sending mail and
> getting this change done? I think it would be better if ti comes from
> maintainers of the project.

Let me talk to Sean Reifschneider first - he might be the one who
ultimately implements the change.

>> e) a recipient (list) for admin_email
> 
> draghuram at gmail.com (my address)

Ok. I'll add Erik Forsberg and myself as well.

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

From metatracker at psf.upfronthosting.co.za  Tue Feb 12 22:17:49 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Tue, 12 Feb 2008 21:17:49 -0000
Subject: [Tracker-discuss] [issue185] Receive email for bugs.jython.org
In-Reply-To: <1202851069.53.0.243700085327.issue185@psf.upfronthosting.co.za>
Message-ID: <1202851069.53.0.243700085327.issue185@psf.upfronthosting.co.za>


New submission from Martin v. L?wis:

bugs.jython.org is now a CNAME for bugs.python.org, so email to
report at bugs.jython.org gets sent to psf.upfronthosting.co.za. Can 
you please arrange that it gets delivered to the jython tracker instance?

----------
assignedto: izak
messages: 955
nosy: izak, loewis
priority: bug
status: unread
title: Receive email for bugs.jython.org

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

From metatracker at psf.upfronthosting.co.za  Tue Feb 12 22:18:43 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Tue, 12 Feb 2008 21:18:43 -0000
Subject: [Tracker-discuss] [issue184] Create a tracker instance for jython
In-Reply-To: <1202334312.21.0.456420573798.issue184@psf.upfronthosting.co.za>
Message-ID: <1202851123.45.0.35637555693.issue184@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

The DNS change has now been made.

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

From metatracker at psf.upfronthosting.co.za  Tue Feb 12 23:16:23 2008
From: metatracker at psf.upfronthosting.co.za (Amaury Forgeot d'Arc)
Date: Tue, 12 Feb 2008 22:16:23 -0000
Subject: [Tracker-discuss] [issue186] All texts are displayed in German
In-Reply-To: <1202854583.13.0.876460923161.issue186@psf.upfronthosting.co.za>
Message-ID: <1202854583.13.0.876460923161.issue186@psf.upfronthosting.co.za>


New submission from Amaury Forgeot d'Arc:

I learned German in the past, and this helps me today: all the tracker texts are
now displayed in German on my computer (The title of this page is "Neue Aufgabe
bearbeiten")
Is this normal? I could not find any language preference. German is not bad, but
personally I would have chosen French instead...

----------
messages: 957
nosy: amaury.forgeotdarc
priority: bug
status: unread
title: All texts are displayed in German

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

From metatracker at psf.upfronthosting.co.za  Tue Feb 12 23:41:00 2008
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Tue, 12 Feb 2008 22:41:00 -0000
Subject: [Tracker-discuss] [issue186] All texts are displayed in German
In-Reply-To: <1202854583.13.0.876460923161.issue186@psf.upfronthosting.co.za>
Message-ID: <bbaeab100802121440p324c727eh6357e717eb75e596@mail.gmail.com>


Brett C. added the comment:

On Feb 12, 2008 2:16 PM, Amaury Forgeot d'Arc
<metatracker at psf.upfronthosting.co.za> wrote:
>
> New submission from Amaury Forgeot d'Arc:
>
> I learned German in the past, and this helps me today: all the tracker texts are
> now displayed in German on my computer (The title of this page is "Neue Aufgabe
> bearbeiten")
> Is this normal? I could not find any language preference. German is not bad, but
> personally I would have chosen French instead...

No, this is not normal. I am having the same issue.

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

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

From metatracker at psf.upfronthosting.co.za  Tue Feb 12 23:49:47 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Tue, 12 Feb 2008 22:49:47 -0000
Subject: [Tracker-discuss] [issue186] All texts are displayed in German
In-Reply-To: <1202854583.13.0.876460923161.issue186@psf.upfronthosting.co.za>
Message-ID: <1202856587.78.0.193286136452.issue186@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

It happened when I restarted it. Should I make it French instead?

In any case, I restarted it again, in the C locale.

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

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

From metatracker at psf.upfronthosting.co.za  Wed Feb 13 11:57:01 2008
From: metatracker at psf.upfronthosting.co.za (Izak Burger)
Date: Wed, 13 Feb 2008 10:57:01 -0000
Subject: [Tracker-discuss] [issue185] Receive email for bugs.jython.org
In-Reply-To: <1202851069.53.0.243700085327.issue185@psf.upfronthosting.co.za>
Message-ID: <47B2CCF6.6020109@upfrontsystems.co.za>


Izak Burger added the comment:

Martin v. L?wis wrote:
> bugs.jython.org is now a CNAME for bugs.python.org, so email to
> report at bugs.jython.org gets sent to psf.upfronthosting.co.za. Can 
> you please arrange that it gets delivered to the jython tracker instance?

Ok I am on it.

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

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

From izak at upfrontsystems.co.za  Wed Feb 13 11:56:54 2008
From: izak at upfrontsystems.co.za (Izak Burger)
Date: Wed, 13 Feb 2008 12:56:54 +0200
Subject: [Tracker-discuss] [issue185] Receive email for bugs.jython.org
In-Reply-To: <1202851069.53.0.243700085327.issue185@psf.upfronthosting.co.za>
References: <1202851069.53.0.243700085327.issue185@psf.upfronthosting.co.za>
Message-ID: <47B2CCF6.6020109@upfrontsystems.co.za>

Martin v. L?wis wrote:
> bugs.jython.org is now a CNAME for bugs.python.org, so email to
> report at bugs.jython.org gets sent to psf.upfronthosting.co.za. Can 
> you please arrange that it gets delivered to the jython tracker instance?

Ok I am on it.

From metatracker at psf.upfronthosting.co.za  Wed Feb 13 12:25:57 2008
From: metatracker at psf.upfronthosting.co.za (Facundo Batista)
Date: Wed, 13 Feb 2008 11:25:57 -0000
Subject: [Tracker-discuss] [issue187] Unclear error message on bug reporting
In-Reply-To: <1202901957.68.0.276512587124.issue187@psf.upfronthosting.co.za>
Message-ID: <1202901957.68.0.276512587124.issue187@psf.upfronthosting.co.za>


New submission from Facundo Batista:

Taking this from bugs.python.org, issue 2099.

"""
When filing a new bug on http://bugs.python.org/issue and not filling
the "Change Note" the following message appears: "Error: list index out
of range"... instead of "please fill the change notes" or something alike...
"""

----------
messages: 961
nosy: facundobatista
priority: bug
status: unread
title: Unclear error message on bug reporting

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

From metatracker at psf.upfronthosting.co.za  Wed Feb 13 13:08:52 2008
From: metatracker at psf.upfronthosting.co.za (Izak Burger)
Date: Wed, 13 Feb 2008 12:08:52 -0000
Subject: [Tracker-discuss] [issue185] Receive email for bugs.jython.org
In-Reply-To: <47B2CCF6.6020109@upfrontsystems.co.za>
Message-ID: <47B2DDC7.4020602@upfrontsystems.co.za>


Izak Burger added the comment:

> Ok I am on it.

Done and tested with issue1000.

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

From metatracker at psf.upfronthosting.co.za  Wed Feb 13 13:12:06 2008
From: metatracker at psf.upfronthosting.co.za (Izak Burger)
Date: Wed, 13 Feb 2008 12:12:06 -0000
Subject: [Tracker-discuss] [issue186] All texts are displayed in German
In-Reply-To: <1202856587.78.0.193286136452.issue186@psf.upfronthosting.co.za>
Message-ID: <47B2DE8B.7030004@upfrontsystems.co.za>


Izak Burger added the comment:

Martin v. L?wis wrote:
> In any case, I restarted it again, in the C locale.

Perhaps we should explicitly set the LANG in the startup script?

Assuming you use the one I made way back that lives in 
/etc/init.d/roundup, you could just add "export LANG=C" to the top of 
the script so that it does not use your user's settings?

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

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

From metatracker at psf.upfronthosting.co.za  Wed Feb 13 20:37:11 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Wed, 13 Feb 2008 19:37:11 -0000
Subject: [Tracker-discuss] [issue185] Receive email for bugs.jython.org
In-Reply-To: <1202851069.53.0.243700085327.issue185@psf.upfronthosting.co.za>
Message-ID: <1202931431.59.0.508395914179.issue185@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

Thanks!

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

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

From martin at v.loewis.de  Wed Feb 13 20:39:23 2008
From: martin at v.loewis.de (=?UTF-8?B?Ik1hcnRpbiB2LiBMw7Z3aXMi?=)
Date: Wed, 13 Feb 2008 20:39:23 +0100
Subject: [Tracker-discuss] [issue186] All texts are displayed in German
In-Reply-To: <47B2DE8B.7030004@upfrontsystems.co.za>
References: <47B2DE8B.7030004@upfrontsystems.co.za>
Message-ID: <47B3476B.2020900@v.loewis.de>

> Assuming you use the one I made way back that lives in 
> /etc/init.d/roundup, you could just add "export LANG=C" to the top of 
> the script so that it does not use your user's settings?

Yes, I've done that now.

From metatracker at psf.upfronthosting.co.za  Wed Feb 13 20:39:26 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Wed, 13 Feb 2008 19:39:26 -0000
Subject: [Tracker-discuss] [issue186] All texts are displayed in German
In-Reply-To: <47B2DE8B.7030004@upfrontsystems.co.za>
Message-ID: <47B3476B.2020900@v.loewis.de>


Martin v. L?wis added the comment:

> Assuming you use the one I made way back that lives in 
> /etc/init.d/roundup, you could just add "export LANG=C" to the top of 
> the script so that it does not use your user's settings?

Yes, I've done that now.

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

From metatracker at psf.upfronthosting.co.za  Wed Feb 13 21:16:34 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Wed, 13 Feb 2008 20:16:34 -0000
Subject: [Tracker-discuss] [issue184] Create a tracker instance for jython
In-Reply-To: <1202334312.21.0.456420573798.issue184@psf.upfronthosting.co.za>
Message-ID: <1202933794.08.0.696766410997.issue184@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

With the help of izak, I also made all the Email changes.

I'm beginning to lose track of any open issues with that installation, so I will
close this issue now as resolved. Any remaining issues with that instance should
be reported separately.

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

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

From metatracker at psf.upfronthosting.co.za  Wed Feb 13 21:17:53 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Wed, 13 Feb 2008 20:17:53 -0000
Subject: [Tracker-discuss] [issue188] Keyword "test failure causes"
In-Reply-To: <1202933873.53.0.944157220552.issue188@psf.upfronthosting.co.za>
Message-ID: <1202933873.53.0.944157220552.issue188@psf.upfronthosting.co.za>


New submission from Martin v. L?wis:

The Jython importer should convert the version "test failure causes" into a
keyword with the same name.

----------
messages: 967
nosy: loewis
priority: urgent
status: unread
title: Keyword "test failure causes"
topic: jython

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

From martin at v.loewis.de  Wed Feb 13 21:29:26 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Wed, 13 Feb 2008 21:29:26 +0100
Subject: [Tracker-discuss] Jython installation
Message-ID: <47B35326.8070503@v.loewis.de>

The Jython roundup installation is nearly complete, AFAICT.
I won't look myself at all in HTML rendering issues; if it's
incorrect/ugly somehow, please submit patches.

Feel free to submit any remaining issues to the meta tracker.
Please tag them with "jython". If they have to be done
before the switchover happens, please give them a priority
"urgent"; use "critical" if it requires immediate attention.
Anything at "bug" or lower should only be considered after
the switchover.

Regards,
Martin

From draghuram at gmail.com  Wed Feb 13 21:52:49 2008
From: draghuram at gmail.com (Raghuram Devarakonda)
Date: Wed, 13 Feb 2008 15:52:49 -0500
Subject: [Tracker-discuss] Jython installation
In-Reply-To: <47B35326.8070503@v.loewis.de>
References: <47B35326.8070503@v.loewis.de>
Message-ID: <2c51ecee0802131252u2bde9b5cmd993a5236eed280d@mail.gmail.com>

On Feb 13, 2008 3:29 PM, "Martin v. L?wis" <martin at v.loewis.de> wrote:
> The Jython roundup installation is nearly complete, AFAICT.

Thanks a lot.

> Feel free to submit any remaining issues to the meta tracker.

I don't think emails are getting sent to jython-bugs as I haven't
received one for my comment in issue 1001. Frank, Charile, did you
receive an email for issue 1001 (which was created by Martin to test)?
It is possible that roundup is sending emails to jython-bugs but they
are getting ignored at SF end.

Thanks,
Raghu

From martin at v.loewis.de  Wed Feb 13 23:22:05 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Wed, 13 Feb 2008 23:22:05 +0100
Subject: [Tracker-discuss] Jython installation
In-Reply-To: <2c51ecee0802131252u2bde9b5cmd993a5236eed280d@mail.gmail.com>
References: <47B35326.8070503@v.loewis.de>
	<2c51ecee0802131252u2bde9b5cmd993a5236eed280d@mail.gmail.com>
Message-ID: <47B36D8D.3010900@v.loewis.de>

> I don't think emails are getting sent to jython-bugs as I haven't
> received one for my comment in issue 1001. Frank, Charile, did you
> receive an email for issue 1001 (which was created by Martin to test)?
> It is possible that roundup is sending emails to jython-bugs but they
> are getting ignored at SF end.

Oops, I had still disabled the sendmail detector. This is now fixed,
and it seems to work fine.

Notice that I have opted to only send new reports to jython-bugs.
If you rather prefer to send all changes to this list instead,
please let me know.

(Some roundup users, Paul Dubois in particular, claim that this would
be overkill - roundup creates its own mini mailing lists for each
issue, so anybody interested in a particular issue could just add
himself to the nosy list. Myself, I only subscribe to new issues
for bugs.python.org)

Regards,
Martin

From draghuram at gmail.com  Thu Feb 14 17:42:02 2008
From: draghuram at gmail.com (Raghuram Devarakonda)
Date: Thu, 14 Feb 2008 11:42:02 -0500
Subject: [Tracker-discuss] Jython installation
In-Reply-To: <47B36D8D.3010900@v.loewis.de>
References: <47B35326.8070503@v.loewis.de>
	<2c51ecee0802131252u2bde9b5cmd993a5236eed280d@mail.gmail.com>
	<47B36D8D.3010900@v.loewis.de>
Message-ID: <2c51ecee0802140842m5669dae0gdab3425fe3a6bee9@mail.gmail.com>

>  Oops, I had still disabled the sendmail detector. This is now fixed,
>  and it seems to work fine.
>
>  Notice that I have opted to only send new reports to jython-bugs.
>  If you rather prefer to send all changes to this list instead,

I think this is fine. I also agree that sending *all* changes to
jython-bugs is not a good idea. It would have been another matter if
there is second list for this purpose (as is the case with cpython).

So what is left now? style sheet issues can be tackled after the
switch-over. Can we announce the impending switch-over on jython-users
and jython-dev and proceed with switch-over in few days time? We can
follow similar procedure as detailed in

http://wiki.python.org/moin/TrackerTransition

From martin at v.loewis.de  Thu Feb 14 22:17:49 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Thu, 14 Feb 2008 22:17:49 +0100
Subject: [Tracker-discuss] Jython installation
In-Reply-To: <2c51ecee0802140842m5669dae0gdab3425fe3a6bee9@mail.gmail.com>
References: <47B35326.8070503@v.loewis.de>	
	<2c51ecee0802131252u2bde9b5cmd993a5236eed280d@mail.gmail.com>	
	<47B36D8D.3010900@v.loewis.de>
	<2c51ecee0802140842m5669dae0gdab3425fe3a6bee9@mail.gmail.com>
Message-ID: <47B4AFFD.2000903@v.loewis.de>

> So what is left now? style sheet issues can be tackled after the
> switch-over. Can we announce the impending switch-over on jython-users
> and jython-dev and proceed with switch-over in few days time? We can
> follow similar procedure as detailed in
> 
> http://wiki.python.org/moin/TrackerTransition

That's what I would propose. Just give me the date (nearly
every day next week would work fine), and I'll run the entire
switchover (including closing the SF tracker).

Regards,
Martin


From metatracker at psf.upfronthosting.co.za  Thu Feb 14 23:18:21 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 14 Feb 2008 22:18:21 -0000
Subject: [Tracker-discuss] [issue188] Keyword "test failure causes"
In-Reply-To: <1202933873.53.0.944157220552.issue188@psf.upfronthosting.co.za>
Message-ID: <1203027501.88.0.630110700789.issue188@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

This was fixed in r60821. I reran the import; please take a look.

(as the consequence of the reimport, anybody who had recovered his password
needs to do so again).

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

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 14 23:53:34 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 14 Feb 2008 22:53:34 -0000
Subject: [Tracker-discuss] [issue187] Unclear error message on bug reporting
In-Reply-To: <1202901957.68.0.276512587124.issue187@psf.upfronthosting.co.za>
Message-ID: <1203029614.56.0.193636055359.issue187@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

Thanks for the report. This is now fixed in r60823

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

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

From brett at python.org  Fri Feb 15 00:14:21 2008
From: brett at python.org (Brett Cannon)
Date: Thu, 14 Feb 2008 15:14:21 -0800
Subject: [Tracker-discuss] draft of call for more volunteers
In-Reply-To: <20080212173610.GA10198@amk-desktop.matrixgroup.net>
References: <bbaeab100802120243y4db36e91v683c56112e3c9efb@mail.gmail.com>
	<20080212173610.GA10198@amk-desktop.matrixgroup.net>
Message-ID: <bbaeab100802141514h52e128dbrbc234656b48a1467@mail.gmail.com>

On Tue, Feb 12, 2008 at 9:36 AM, A.M. Kuchling <amk at amk.ca> wrote:
> On Tue, Feb 12, 2008 at 02:43:14AM -0800, Brett Cannon wrote:
>  > Let me know what you think:
>
>  Seems fine to me.

I suspect I will be sending this announcement out tomorrow or Monday,
so if anyone else has something to say, speak up now.

-Brett

From draghuram at gmail.com  Fri Feb 15 06:21:44 2008
From: draghuram at gmail.com (Raghuram Devarakonda)
Date: Fri, 15 Feb 2008 00:21:44 -0500
Subject: [Tracker-discuss] Jython installation
In-Reply-To: <47B4AFFD.2000903@v.loewis.de>
References: <47B35326.8070503@v.loewis.de>
	<2c51ecee0802131252u2bde9b5cmd993a5236eed280d@mail.gmail.com>
	<47B36D8D.3010900@v.loewis.de>
	<2c51ecee0802140842m5669dae0gdab3425fe3a6bee9@mail.gmail.com>
	<47B4AFFD.2000903@v.loewis.de>
Message-ID: <2c51ecee0802142121g476469a9k18ced055a81af57@mail.gmail.com>

>  > http://wiki.python.org/moin/TrackerTransition
>
>  That's what I would propose. Just give me the date (nearly
>  every day next week would work fine), and I'll run the entire
>  switchover (including closing the SF tracker).

Frank, Charlie,

How about next Wednesday for the switch-over? We can announce it
tomorrow and ask for comments.

Thanks,
Raghu

ps. Martin, please ignore my previous email (which got sent by mistake
to you alone).

From fwierzbicki at gmail.com  Fri Feb 15 13:01:23 2008
From: fwierzbicki at gmail.com (Frank Wierzbicki)
Date: Fri, 15 Feb 2008 07:01:23 -0500
Subject: [Tracker-discuss] Jython installation
In-Reply-To: <2c51ecee0802142121g476469a9k18ced055a81af57@mail.gmail.com>
References: <47B35326.8070503@v.loewis.de>
	<2c51ecee0802131252u2bde9b5cmd993a5236eed280d@mail.gmail.com>
	<47B36D8D.3010900@v.loewis.de>
	<2c51ecee0802140842m5669dae0gdab3425fe3a6bee9@mail.gmail.com>
	<47B4AFFD.2000903@v.loewis.de>
	<2c51ecee0802142121g476469a9k18ced055a81af57@mail.gmail.com>
Message-ID: <4dab5f760802150401n653b3992lc7c26e825741379c@mail.gmail.com>

On Fri, Feb 15, 2008 at 12:21 AM, Raghuram Devarakonda
<draghuram at gmail.com> wrote:
> >  > http://wiki.python.org/moin/TrackerTransition
>  >
>  >  That's what I would propose. Just give me the date (nearly
>  >  every day next week would work fine), and I'll run the entire
>  >  switchover (including closing the SF tracker).
>
>  Frank, Charlie,
>
>  How about next Wednesday for the switch-over? We can announce it
>  tomorrow and ask for comments.
That sounds good to me, thanks!

-Frank

From fwierzbicki at gmail.com  Fri Feb 15 13:02:08 2008
From: fwierzbicki at gmail.com (Frank Wierzbicki)
Date: Fri, 15 Feb 2008 07:02:08 -0500
Subject: [Tracker-discuss] Jython installation
In-Reply-To: <4dab5f760802150401n653b3992lc7c26e825741379c@mail.gmail.com>
References: <47B35326.8070503@v.loewis.de>
	<2c51ecee0802131252u2bde9b5cmd993a5236eed280d@mail.gmail.com>
	<47B36D8D.3010900@v.loewis.de>
	<2c51ecee0802140842m5669dae0gdab3425fe3a6bee9@mail.gmail.com>
	<47B4AFFD.2000903@v.loewis.de>
	<2c51ecee0802142121g476469a9k18ced055a81af57@mail.gmail.com>
	<4dab5f760802150401n653b3992lc7c26e825741379c@mail.gmail.com>
Message-ID: <4dab5f760802150402v32d7c2d7kc9d7f9b893fadfdb@mail.gmail.com>

On Fri, Feb 15, 2008 at 7:01 AM, Frank Wierzbicki <fwierzbicki at gmail.com> wrote:
> On Fri, Feb 15, 2008 at 12:21 AM, Raghuram Devarakonda
>  <draghuram at gmail.com> wrote:
>  > >  > http://wiki.python.org/moin/TrackerTransition
>  >  >
>  >  >  That's what I would propose. Just give me the date (nearly
>  >  >  every day next week would work fine), and I'll run the entire
>  >  >  switchover (including closing the SF tracker).
>  >
>  >  Frank, Charlie,
>  >
>  >  How about next Wednesday for the switch-over? We can announce it
>  >  tomorrow and ask for comments.
>  That sounds good to me, thanks!
Though do wait for Charlie's okay -- Charlie?

-Frank

From charlie.groves at gmail.com  Fri Feb 15 18:01:40 2008
From: charlie.groves at gmail.com (Charlie Groves)
Date: Fri, 15 Feb 2008 09:01:40 -0800
Subject: [Tracker-discuss] Jython installation
In-Reply-To: <4dab5f760802150402v32d7c2d7kc9d7f9b893fadfdb@mail.gmail.com>
References: <47B35326.8070503@v.loewis.de>
	<2c51ecee0802131252u2bde9b5cmd993a5236eed280d@mail.gmail.com>
	<47B36D8D.3010900@v.loewis.de>
	<2c51ecee0802140842m5669dae0gdab3425fe3a6bee9@mail.gmail.com>
	<47B4AFFD.2000903@v.loewis.de>
	<2c51ecee0802142121g476469a9k18ced055a81af57@mail.gmail.com>
	<4dab5f760802150401n653b3992lc7c26e825741379c@mail.gmail.com>
	<4dab5f760802150402v32d7c2d7kc9d7f9b893fadfdb@mail.gmail.com>
Message-ID: <96c4692d0802150901l7d9fe94ck397cc0cbe9b89a1d@mail.gmail.com>

On Fri, Feb 15, 2008 at 4:02 AM, Frank Wierzbicki <fwierzbicki at gmail.com> wrote:
>
> On Fri, Feb 15, 2008 at 7:01 AM, Frank Wierzbicki <fwierzbicki at gmail.com> wrote:
>  > On Fri, Feb 15, 2008 at 12:21 AM, Raghuram Devarakonda
>  >  <draghuram at gmail.com> wrote:
>  >  > >  > http://wiki.python.org/moin/TrackerTransition
>  >  >  >
>  >  >  >  That's what I would propose. Just give me the date (nearly
>  >  >  >  every day next week would work fine), and I'll run the entire
>  >  >  >  switchover (including closing the SF tracker).
>  >  >
>  >  >  Frank, Charlie,
>  >  >
>  >  >  How about next Wednesday for the switch-over? We can announce it
>  >  >  tomorrow and ask for comments.
>  >  That sounds good to me, thanks!
>  Though do wait for Charlie's okay -- Charlie?

Sounds fine to me.

Charlie

From metatracker at psf.upfronthosting.co.za  Sat Feb 16 17:00:16 2008
From: metatracker at psf.upfronthosting.co.za (Kurt B. Kaiser)
Date: Sat, 16 Feb 2008 16:00:16 -0000
Subject: [Tracker-discuss] [issue189] Tracker Weekly Summary: 'Closed by'
	sometimes incorrect
In-Reply-To: <1203177616.06.0.45592637075.issue189@psf.upfronthosting.co.za>
Message-ID: <1203177616.06.0.45592637075.issue189@psf.upfronthosting.co.za>


New submission from Kurt B. Kaiser:

If comments are subsequently made on an issue which is closed in the period, the 
Closed By field on the weekly report is set to the name of the last commenter when the 
report is run instead of the person who closed the issue.

cf. http://bugs.python.org/issue2049  and
http://mail.python.org/pipermail/python-dev/2008-February/076896.html

----------
assignedto: dubois
messages: 970
nosy: dubois, kbk
priority: bug
status: unread
title: Tracker Weekly Summary: 'Closed by' sometimes incorrect

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

From martin at v.loewis.de  Sat Feb 16 20:39:47 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Sat, 16 Feb 2008 20:39:47 +0100
Subject: [Tracker-discuss] Demo Roundup Jobs Tracker
Message-ID: <47B73C03.9050607@v.loewis.de>

I just completed a prototype of a jobs tracker, at

http://psf.upfronthosting.co.za/roundup/jobs

The basic operation of this tracker involves users (who
submit job offers) and editors (who post them).

Users need to get an account, login, and post their
offer. This will (but currently doesn't) send an
email message to jobs at python.org. Users can then edit
their offer until it gets posted, in case they made
mistakes. They can also withdraw the offer, or bring
them back to the submission state.

Editors can perform edits to an offer, and then approve
it for posting (by setting the file to "posted"). This
will generate the file

http://psf.upfronthosting.co.za/roundup/jobs/@@file/posted.txt

It should (but currently doesn't) also trigger a rebuild
of the life page on python.org.

There is also a discussion track for a job offer, in
case the offer is unclear and further feedback from the
submitter is required.

Security-wise, users can only view their own jobs offers
(and, of course, the ones posted on the life site). Editors
can do essentially anything about an offer.

Please let me know what you think. If you want to report
a bug in this tracker, it would be best if you post to

http://psf.upfronthosting.co.za/roundup/meta/

and put the "jobs" keyword into the issue. If you want
to your tracker account to be promoted to editor,
please let me know.

Regards,
Martin

From brett at python.org  Mon Feb 18 23:52:51 2008
From: brett at python.org (Brett Cannon)
Date: Mon, 18 Feb 2008 14:52:51 -0800
Subject: [Tracker-discuss] Call for volunteers to help maintain
	bugs.python.org's issue tracker
Message-ID: <bbaeab100802181452g4b9c43e1sc1ace073da8488a@mail.gmail.com>

The Python Software Foundation's infrastructure committee is looking
for volunteers to help maintain the Roundup issue tracker installed
for http://bugs.python.org. Responsibilities revolve around
maintaining the Roundup installation itself (tracker schema, modifying
the installed copy of Roundup, etc.) and the occasional database work
(changes to the database, etc.).

You do not have to be an expert at Roundup to volunteer! You can learn
"on the job" by doing offline development and submitting patches until
you are of a proper level of experience to gain commit access to the
code (which can be seen at XXX). If you still have a New Years
resolution to help Python out this is a great way to fulfill the
promise you made yourself for 2008!

If you are interested in volunteering, please email tracker-discuss at
python.org. Thanks to all who have helped with the tracker already and
those that will in the future!

-Brett Cannon
Chairman, PSF infrastructure committee

From dstanek at dstanek.com  Tue Feb 19 13:52:25 2008
From: dstanek at dstanek.com (David Stanek)
Date: Tue, 19 Feb 2008 07:52:25 -0500
Subject: [Tracker-discuss] Helping Out
Message-ID: <de32cc030802190452r66db2188w1c98f3ef89896aca@mail.gmail.com>

I just saw Brett's email to python-list and I am interested in helping out.
Just point me to the code and the list of things that needs to be done :-)

-- 
David
http://www.traceback.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20080219/179bdc20/attachment.htm 

From martin at marcher.name  Tue Feb 19 19:05:05 2008
From: martin at marcher.name (Martin Marcher)
Date: Tue, 19 Feb 2008 19:05:05 +0100
Subject: [Tracker-discuss] *raising hand* [WAS: Call for volunteers to help
	maintain bugs.python.org's issue tracker]
Message-ID: <5fa6c12e0802191005w685de2fau4b94e238818e25eb@mail.gmail.com>

Hi,

I'd be willing to participate (eager to actually) - no roundup
experience yet.

smaller python stuff, but I'd place myself in the medium experienced
system adminstration area (maintaining 20 servers, most of them are
virtualized, a couple of them out in the wild, didn't have any
security breakage yet)

So where/how do I get started :)

cheers
martin

-- 
http://noneisyours.marcher.name
https://twitter.com/MartinMarcher
http://www.xing.com/profile/Martin_Marcher
http://www.linkedin.com/in/martinmarcher

You are not free to read this message,
by doing so, you have violated my licence
and are required to urinate publicly. Thank you.

From draghuram at gmail.com  Tue Feb 19 19:30:49 2008
From: draghuram at gmail.com (Raghuram Devarakonda)
Date: Tue, 19 Feb 2008 13:30:49 -0500
Subject: [Tracker-discuss] *raising hand* [WAS: Call for volunteers to
	help maintain bugs.python.org's issue tracker]
In-Reply-To: <5fa6c12e0802191005w685de2fau4b94e238818e25eb@mail.gmail.com>
References: <5fa6c12e0802191005w685de2fau4b94e238818e25eb@mail.gmail.com>
Message-ID: <2c51ecee0802191030h534de8b6obf9610d0d69b5b18@mail.gmail.com>

On Feb 19, 2008 1:05 PM, Martin Marcher <martin at marcher.name> wrote:

> So where/how do I get started :)

You may want to start by checking the page at
http://wiki.python.org/moin/TrackerDevelopment. It has details on how
to set up a local roundup instance. That should be the first step
before contributing any patches. Once the local set up is done, you
may check the meta-tracker at
http://psf.upfronthosting.co.za/roundup/meta/ and see if you can
submit patches for any problems reported there.

Thanks,
Raghu

From daryl.spitzer at gmail.com  Tue Feb 19 15:40:33 2008
From: daryl.spitzer at gmail.com (Daryl Spitzer)
Date: Tue, 19 Feb 2008 06:40:33 -0800
Subject: [Tracker-discuss] Call for volunteers to help maintain
	bugs.python.org's issue tracker
In-Reply-To: <bbaeab100802181452g4b9c43e1sc1ace073da8488a@mail.gmail.com>
References: <bbaeab100802181452g4b9c43e1sc1ace073da8488a@mail.gmail.com>
Message-ID: <fbf2758a0802190640k198d626ap2364432c8ad0287e@mail.gmail.com>

I'm interested in volunteering--I quickly skimmed
http://roundup.sourceforge.net/doc-1.0/design.html and
http://roundup.sourceforge.net/doc-1.0/developers.html and it sounds
like a learning opportunity for me, and a chance to help Python of
course.

I have three kids (5 and under), so my free time is limited.  I could
probably only commit to two or three hours a week.

And I find the time for my personal work early in the mornings--I get
to my office early and delay working on my day-job for a couple hours.
 But that means I'm using my employer's Internet connection, so I'm
behind a firewall.  I noticed (in
http://roundup.sourceforge.net/doc-1.0/developers.html#cvs-access) at
you're using CVS for the Roundup sources.  I've never been able to use
CVS through my employer's firewall.

I've been programming in Python for a couple years now, and working
pretty much full time in Python for almost a year and a half.  I don't
have any trouble reading and understanding any Python code, and (I
think) I'm well-versed in most of Python's features.

--
Daryl Spitzer


---------- Forwarded message ----------
From: Brett Cannon <brett at python.org>
Date: Feb 18, 2008 2:52 PM
Subject: Call for volunteers to help maintain bugs.python.org's issue tracker
To: Python Tracker-discuss <tracker-discuss at python.org>


The Python Software Foundation's infrastructure committee is looking
for volunteers to help maintain the Roundup issue tracker installed
for http://bugs.python.org. Responsibilities revolve around
maintaining the Roundup installation itself (tracker schema, modifying
the installed copy of Roundup, etc.) and the occasional database work
(changes to the database, etc.).

You do not have to be an expert at Roundup to volunteer! You can learn
"on the job" by doing offline development and submitting patches until
you are of a proper level of experience to gain commit access to the
code (which can be seen at XXX). If you still have a New Years
resolution to help Python out this is a great way to fulfill the
promise you made yourself for 2008!

If you are interested in volunteering, please email tracker-discuss at
python.org. Thanks to all who have helped with the tracker already and
those that will in the future!

-Brett Cannon
Chairman, PSF infrastructure committee
--
http://mail.python.org/mailman/listinfo/python-list

From dmitrikozhevin at gmail.com  Tue Feb 19 12:22:33 2008
From: dmitrikozhevin at gmail.com (Dmitry Kozhevin)
Date: Tue, 19 Feb 2008 13:22:33 +0200
Subject: [Tracker-discuss] Call for volunteers to help maintain
	bugs.python.org's issue tracker
Message-ID: <765bf0040802190322g220344a3k4f008e54de5ce4df@mail.gmail.com>

Hi.

I have working with Roundup about few years and still have good
filling about this product. Richard does  right things on the solid
base.

My thought that is very good idea to use Roudnup on bugs.python.org. I
will help PSF with glad and enthusiasm.

--
DK

From wyldwolf at gmail.com  Tue Feb 19 16:13:46 2008
From: wyldwolf at gmail.com (Kevin)
Date: Tue, 19 Feb 2008 09:13:46 -0600
Subject: [Tracker-discuss] Volunteer to help maintain tracker
Message-ID: <77895c1d0802190713u1a804341o8f491971d678a6fe@mail.gmail.com>

Hello,
I would like to offer to help maintain Tracker. Thanks.

Kevin Kelley
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20080219/b3bfc75b/attachment.htm 

From brett at python.org  Tue Feb 19 21:15:08 2008
From: brett at python.org (Brett Cannon)
Date: Tue, 19 Feb 2008 12:15:08 -0800
Subject: [Tracker-discuss] Helping Out
In-Reply-To: <de32cc030802190452r66db2188w1c98f3ef89896aca@mail.gmail.com>
References: <de32cc030802190452r66db2188w1c98f3ef89896aca@mail.gmail.com>
Message-ID: <bbaeab100802191215u7fd1035dp5e6f127ad83ca543@mail.gmail.com>

On Feb 19, 2008 4:52 AM, David Stanek <dstanek at dstanek.com> wrote:
> I just saw Brett's email to python-list and I am interested in helping out.
> Just point me to the code and the list of things that needs to be done :-)
>

Code is at http://svn.python.org/view/tracker/ .

Things that need to be done are at
http://psf.upfronthosting.co.za/roundup/meta/ .

Thanks for stepping forward, David!

-Brett

From brett at python.org  Tue Feb 19 21:17:13 2008
From: brett at python.org (Brett Cannon)
Date: Tue, 19 Feb 2008 12:17:13 -0800
Subject: [Tracker-discuss] Helping Out
In-Reply-To: <bbaeab100802191215u7fd1035dp5e6f127ad83ca543@mail.gmail.com>
References: <de32cc030802190452r66db2188w1c98f3ef89896aca@mail.gmail.com>
	<bbaeab100802191215u7fd1035dp5e6f127ad83ca543@mail.gmail.com>
Message-ID: <bbaeab100802191217j85938b5i4bf96131de0bfe7b@mail.gmail.com>

On Feb 19, 2008 12:15 PM, Brett Cannon <brett at python.org> wrote:
> On Feb 19, 2008 4:52 AM, David Stanek <dstanek at dstanek.com> wrote:
> > I just saw Brett's email to python-list and I am interested in helping out.
> > Just point me to the code and the list of things that needs to be done :-)
> >
>
> Code is at http://svn.python.org/view/tracker/ .
>
> Things that need to be done are at
> http://psf.upfronthosting.co.za/roundup/meta/ .

I also forgot to point out the tracker docs are at
http://wiki.python.org/moin/TrackerDocs/. That page includes a link to
http://wiki.python.org/moin/TrackerDevelopment which details how to
get up and going.

-Brett

From brett at python.org  Tue Feb 19 21:18:26 2008
From: brett at python.org (Brett Cannon)
Date: Tue, 19 Feb 2008 12:18:26 -0800
Subject: [Tracker-discuss] Volunteer to help maintain tracker
In-Reply-To: <77895c1d0802190713u1a804341o8f491971d678a6fe@mail.gmail.com>
References: <77895c1d0802190713u1a804341o8f491971d678a6fe@mail.gmail.com>
Message-ID: <bbaeab100802191218p1c46a784s2c6c69b747d2efef@mail.gmail.com>

On Feb 19, 2008 7:13 AM, Kevin <wyldwolf at gmail.com> wrote:
> Hello,
> I would like to offer to help maintain Tracker. Thanks.

Great! Just subscribe to this mailing list, and read the docs at
http://wiki.python.org/moin/TrackerDocs/ . That includes links to the
meta-tracker which hold bug reports for the tracker and a link to
another wiki page which details how to get up and going with your own
instance of the tracker for testing purposes.

-Brett

From brett at python.org  Tue Feb 19 21:20:38 2008
From: brett at python.org (Brett Cannon)
Date: Tue, 19 Feb 2008 12:20:38 -0800
Subject: [Tracker-discuss] Call for volunteers to help maintain
	bugs.python.org's issue tracker
In-Reply-To: <fbf2758a0802190640k198d626ap2364432c8ad0287e@mail.gmail.com>
References: <bbaeab100802181452g4b9c43e1sc1ace073da8488a@mail.gmail.com>
	<fbf2758a0802190640k198d626ap2364432c8ad0287e@mail.gmail.com>
Message-ID: <bbaeab100802191220l435d82a6uef89097cd1e4b692@mail.gmail.com>

On Feb 19, 2008 6:40 AM, Daryl Spitzer <daryl.spitzer at gmail.com> wrote:
> I'm interested in volunteering--I quickly skimmed
> http://roundup.sourceforge.net/doc-1.0/design.html and
> http://roundup.sourceforge.net/doc-1.0/developers.html and it sounds
> like a learning opportunity for me, and a chance to help Python of
> course.
>
> I have three kids (5 and under), so my free time is limited.  I could
> probably only commit to two or three hours a week.
>

Any help is appreciated. At this point we just want people submitting
patches to help closing issues with the tracker.

> And I find the time for my personal work early in the mornings--I get
> to my office early and delay working on my day-job for a couple hours.
>  But that means I'm using my employer's Internet connection, so I'm
> behind a firewall.  I noticed (in
> http://roundup.sourceforge.net/doc-1.0/developers.html#cvs-access) at
> you're using CVS for the Roundup sources.  I've never been able to use
> CVS through my employer's firewall.

We have our own instance of Roundup in svn.


>
> I've been programming in Python for a couple years now, and working
> pretty much full time in Python for almost a year and a half.  I don't
> have any trouble reading and understanding any Python code, and (I
> think) I'm well-versed in most of Python's features.
>

Great!

To get started, read http://wiki.python.org/moin/TrackerDocs/ . You
will find a link to the meta-tracker which is the issue tracker for
the issue tracker. There is also a link at the bottom on how to get an
testing instance of the tracker up and going to work with.

-Brett

From brett at python.org  Tue Feb 19 21:21:50 2008
From: brett at python.org (Brett Cannon)
Date: Tue, 19 Feb 2008 12:21:50 -0800
Subject: [Tracker-discuss] Call for volunteers to help maintain
	bugs.python.org's issue tracker
In-Reply-To: <765bf0040802190322g220344a3k4f008e54de5ce4df@mail.gmail.com>
References: <765bf0040802190322g220344a3k4f008e54de5ce4df@mail.gmail.com>
Message-ID: <bbaeab100802191221v708abe74sb9e9759cfc501174@mail.gmail.com>

On Feb 19, 2008 3:22 AM, Dmitry Kozhevin <dmitrikozhevin at gmail.com> wrote:
> Hi.
>
> I have working with Roundup about few years and still have good
> filling about this product. Richard does  right things on the solid
> base.
>
> My thought that is very good idea to use Roudnup on bugs.python.org. I
> will help PSF with glad and enthusiasm.
>

Thanks, Dmitry!

After subscribing to tracker-discuss, read
http://wiki.python.org/moin/TrackerDocs/ . There you will find links
to the meta-tracker which is the issue tracker for the issue tracker
along with docs that explain how to get a test instance up and going.

-Brett

From martin at v.loewis.de  Tue Feb 19 23:06:17 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Tue, 19 Feb 2008 23:06:17 +0100
Subject: [Tracker-discuss] *raising hand* [WAS: Call for volunteers to
 help	maintain bugs.python.org's issue tracker]
In-Reply-To: <5fa6c12e0802191005w685de2fau4b94e238818e25eb@mail.gmail.com>
References: <5fa6c12e0802191005w685de2fau4b94e238818e25eb@mail.gmail.com>
Message-ID: <47BB52D9.1060907@v.loewis.de>

> I'd be willing to participate (eager to actually) - no roundup
> experience yet.
> 
> smaller python stuff, but I'd place myself in the medium experienced
> system adminstration area (maintaining 20 servers, most of them are
> virtualized, a couple of them out in the wild, didn't have any
> security breakage yet)
> 
> So where/how do I get started :)

In addition to what Raghu said: the list of open bugs is at

http://psf.upfronthosting.co.za/roundup/meta

The top issues I would like to see fixed are 130 (submitters should
be able to close their own issues), and 16 (pending issues with no
activity should get closed by a cronjob; pending issues with activity
should re-open on activity).

Regards,
Martin

From musiccomposition at gmail.com  Wed Feb 20 05:02:47 2008
From: musiccomposition at gmail.com (Benjamin Peterson)
Date: Tue, 19 Feb 2008 22:02:47 -0600
Subject: [Tracker-discuss] volunteering...
Message-ID: <1afaf6160802192002v4f092f5ck58ea163eed8a05ca@mail.gmail.com>

Hi,
I'm answering Brett's call for volunteers. I love Python and want to get
involved; I ready to do what needs to be done!

Thanks,
Benjamin Peterson
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20080219/699737aa/attachment.htm 

From brett at python.org  Wed Feb 20 05:42:06 2008
From: brett at python.org (Brett Cannon)
Date: Tue, 19 Feb 2008 20:42:06 -0800
Subject: [Tracker-discuss] volunteering...
In-Reply-To: <1afaf6160802192002v4f092f5ck58ea163eed8a05ca@mail.gmail.com>
References: <1afaf6160802192002v4f092f5ck58ea163eed8a05ca@mail.gmail.com>
Message-ID: <bbaeab100802192042y1d2407m2aa10febc2eff6ac@mail.gmail.com>

On Feb 19, 2008 8:02 PM, Benjamin Peterson <musiccomposition at gmail.com> wrote:
> Hi,
> I'm answering Brett's call for volunteers. I love Python and want to get
> involved; I ready to do what needs to be done!
>

Great!

Go to http://wiki.python.org/moin/TrackerDocs/ and you can read about
how stuff is supposed to work. You will also find a link to the
meta-tracker which holds issues about the issue tracker. And at the
bottom of the wiki page is instructions on how to set up your own
testing instance of the tracker.

-Brett

From brett at python.org  Wed Feb 20 07:52:43 2008
From: brett at python.org (Brett Cannon)
Date: Tue, 19 Feb 2008 22:52:43 -0800
Subject: [Tracker-discuss] tracker maintenance
In-Reply-To: <20080220064315.GA81956@nexus.in-nomine.org>
References: <20080107094349.GC82115@nexus.in-nomine.org>
	<bbaeab100802181453l6aaf08a9s9810d77895611dcd@mail.gmail.com>
	<20080220064315.GA81956@nexus.in-nomine.org>
Message-ID: <bbaeab100802192252m7dc896f0nd440f43ccf4460c@mail.gmail.com>

On Feb 19, 2008 10:43 PM, Jeroen Ruigrok van der Werven
<asmodai at in-nomine.org> wrote:
> Hi Brett,
>
> -On [20080218 23:53], Brett Cannon (brett at python.org) wrote:
> >You do not have to be an expert at Roundup to volunteer! You can learn
> >"on the job" by doing offline development and submitting patches until
> >you are of a proper level of experience to gain commit access to the
> >code (which can be seen at XXX). If you still have a New Years
> >resolution to help Python out this is a great way to fulfill the
> >promise you made yourself for 2008!
>
> I guess the XXX was supposed to be filled in? ;)

Damn it, I even spotted that just before I sent the email and still forgot.

The code can be browsed at http://svn.python.org/view/tracker/ .

> So it basically means the Roundup stuff needs patches mostly that others
> will apply at first? Or is there also sysadmin maintenance needed?

Mostly patches and database manipulation. Maintaining the system is up
to Upfront, our host provider.

>
> >If you are interested in volunteering, please email tracker-discuss at
> >python.org. Thanks to all who have helped with the tracker already and
> >those that will in the future!
>
> Yes, I am still interested in volunteering.
>
> Like I told you before in private, I help out on the Trac project and prior
> to that I've hacked on RT2 and Bugzilla. I have helped maintain a few issue
> tracking instances (the GNATS one back in the day when I was a FreeBSD
> committer, Jira at my current job, and some Trac instances) and still
> maintain some.

Glad you are still interested! Have a look at
http://wiki.python.org/moin/TrackerDocs/ which also has links to our
meta-tracker as well as a link to docs on how to get a testing
instance of the tracker up.

-Brett

From asmodai at in-nomine.org  Wed Feb 20 07:43:15 2008
From: asmodai at in-nomine.org (Jeroen Ruigrok van der Werven)
Date: Wed, 20 Feb 2008 07:43:15 +0100
Subject: [Tracker-discuss] tracker maintenance
In-Reply-To: <bbaeab100802181453l6aaf08a9s9810d77895611dcd@mail.gmail.com>
References: <20080107094349.GC82115@nexus.in-nomine.org>
	<bbaeab100802181453l6aaf08a9s9810d77895611dcd@mail.gmail.com>
Message-ID: <20080220064315.GA81956@nexus.in-nomine.org>

Hi Brett,

-On [20080218 23:53], Brett Cannon (brett at python.org) wrote:
>You do not have to be an expert at Roundup to volunteer! You can learn
>"on the job" by doing offline development and submitting patches until
>you are of a proper level of experience to gain commit access to the
>code (which can be seen at XXX). If you still have a New Years
>resolution to help Python out this is a great way to fulfill the
>promise you made yourself for 2008!

I guess the XXX was supposed to be filled in? ;)
So it basically means the Roundup stuff needs patches mostly that others
will apply at first? Or is there also sysadmin maintenance needed?

>If you are interested in volunteering, please email tracker-discuss at
>python.org. Thanks to all who have helped with the tracker already and
>those that will in the future!

Yes, I am still interested in volunteering.

Like I told you before in private, I help out on the Trac project and prior
to that I've hacked on RT2 and Bugzilla. I have helped maintain a few issue
tracking instances (the GNATS one back in the day when I was a FreeBSD
committer, Jira at my current job, and some Trac instances) and still
maintain some.

-- 
Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai
????? ?????? ??? ?? ??????
http://www.in-nomine.org/ | http://www.rangaku.org/
When left with nothing to say, rest content in the knowledge that there
is really nothing to say...

From bigboss64 at ippimail.com  Wed Feb 20 05:48:33 2008
From: bigboss64 at ippimail.com (Terry Poulin)
Date: Wed, 20 Feb 2008 04:48:33 -0000 (UTC)
Subject: [Tracker-discuss] Call for volunteers to help maintain
 bugs.python.org's issue tracker
Message-ID: <51145.65.13.19.19.1203482913.squirrel@www.ippimail.com>

Call for volunteers to help maintain bugs.python.org's issue tracker

From:
Brett Cannon <brett at python.org>
  Date:
Monday 18 February 2008 17:52:51
  To:
Python Tracker-discuss <tracker-discuss at python.org>
  Groups:
comp.lang.python


The Python Software Foundation's infrastructure committee is looking
for volunteers to help maintain the Roundup issue tracker installed
for http://bugs.python.org. Responsibilities revolve around
maintaining the Roundup installation itself (tracker schema, modifying
the installed copy of Roundup, etc.) and the occasional database work
(changes to the database, etc.).

You do not have to be an expert at Roundup to volunteer! You can learn
"on the job" by doing offline development and submitting patches until
you are of a proper level of experience to gain commit access to the
code (which can be seen at XXX). If you still have a New Years
resolution to help Python out this is a great way to fulfill the
promise you made yourself for 2008!

If you are interested in volunteering, please email tracker-discuss at
python.org. Thanks to all who have helped with the tracker already and
those that will in the future!

-Brett Cannon
Chairman, PSF infrastructure committee

###########################################


I don't know if I could be helpful enough to warrant the time for it but I
would like to learn more to see if there is any thing I could help with.


TerryP.



--
    
Email and shopping with the feelgood factor!
55% of income to good causes. http://www.ippimail.com


From jonathansamuel at yahoo.com  Wed Feb 20 05:56:01 2008
From: jonathansamuel at yahoo.com (Jonathan Mark)
Date: Tue, 19 Feb 2008 20:56:01 -0800 (PST)
Subject: [Tracker-discuss] I will spend a few hours a week helping on the
	bug tracker.
Message-ID: <701178.18215.qm@web32513.mail.mud.yahoo.com>

If you would like me to help on the Python bug tracker respond with the particulars.

Jonathan Mark
goodbyecorey.com
703-921-5259

7055 Chesley Search Way
Alexandria, VA 22315.

From shitizb at yahoo.com  Wed Feb 20 07:37:16 2008
From: shitizb at yahoo.com (Shitiz Bansal)
Date: Tue, 19 Feb 2008 22:37:16 -0800 (PST)
Subject: [Tracker-discuss] Call for volunteers to help maintain
	bugs.python.org's issue tracker
In-Reply-To: <bbaeab100802181452g4b9c43e1sc1ace073da8488a@mail.gmail.com>
Message-ID: <631215.66757.qm@web53804.mail.re2.yahoo.com>

Hi,
I am a python enthusiast willing to help. I am based in India and working as a software professional for 2 and a half years. Let me know how i can help and how much of my time it will take if i get involved.
Thanks and Regards,
Shitiz Bansal

Brett Cannon <brett at python.org> wrote: The Python Software Foundation's infrastructure committee is looking
for volunteers to help maintain the Roundup issue tracker installed
for http://bugs.python.org. Responsibilities revolve around
maintaining the Roundup installation itself (tracker schema, modifying
the installed copy of Roundup, etc.) and the occasional database work
(changes to the database, etc.).

You do not have to be an expert at Roundup to volunteer! You can learn
"on the job" by doing offline development and submitting patches until
you are of a proper level of experience to gain commit access to the
code (which can be seen at XXX). If you still have a New Years
resolution to help Python out this is a great way to fulfill the
promise you made yourself for 2008!

If you are interested in volunteering, please email tracker-discuss at
python.org. Thanks to all who have helped with the tracker already and
those that will in the future!

-Brett Cannon
Chairman, PSF infrastructure committee
-- 
http://mail.python.org/mailman/listinfo/python-list


       
---------------------------------
Looking for last minute shopping deals?  Find them fast with Yahoo! Search.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20080219/97596dce/attachment.htm 

From brett at python.org  Wed Feb 20 07:55:07 2008
From: brett at python.org (Brett Cannon)
Date: Tue, 19 Feb 2008 22:55:07 -0800
Subject: [Tracker-discuss] Call for volunteers to help maintain
	bugs.python.org's issue tracker
In-Reply-To: <51145.65.13.19.19.1203482913.squirrel@www.ippimail.com>
References: <51145.65.13.19.19.1203482913.squirrel@www.ippimail.com>
Message-ID: <bbaeab100802192255m3f53d015t8923db8a367660cc@mail.gmail.com>

On Feb 19, 2008 8:48 PM, Terry Poulin <bigboss64 at ippimail.com> wrote:
> Call for volunteers to help maintain bugs.python.org's issue tracker
>
> From:
> Brett Cannon <brett at python.org>
>   Date:
> Monday 18 February 2008 17:52:51
>   To:
> Python Tracker-discuss <tracker-discuss at python.org>
>   Groups:
> comp.lang.python
>
>
> The Python Software Foundation's infrastructure committee is looking
> for volunteers to help maintain the Roundup issue tracker installed
> for http://bugs.python.org. Responsibilities revolve around
> maintaining the Roundup installation itself (tracker schema, modifying
> the installed copy of Roundup, etc.) and the occasional database work
> (changes to the database, etc.).
>
> You do not have to be an expert at Roundup to volunteer! You can learn
> "on the job" by doing offline development and submitting patches until
> you are of a proper level of experience to gain commit access to the
> code (which can be seen at XXX). If you still have a New Years
> resolution to help Python out this is a great way to fulfill the
> promise you made yourself for 2008!
>
> If you are interested in volunteering, please email tracker-discuss at
> python.org. Thanks to all who have helped with the tracker already and
> those that will in the future!
>
> -Brett Cannon
> Chairman, PSF infrastructure committee
>
> ###########################################
>
>
> I don't know if I could be helpful enough to warrant the time for it but I
> would like to learn more to see if there is any thing I could help with.

Read the following pages to find out more:

http://wiki.python.org/moin/TrackerDocs/
http://wiki.python.org/moin/TrackerDevelopment
http://psf.upfronthosting.co.za/roundup/meta/

-Brett

From brett at python.org  Wed Feb 20 07:55:27 2008
From: brett at python.org (Brett Cannon)
Date: Tue, 19 Feb 2008 22:55:27 -0800
Subject: [Tracker-discuss] I will spend a few hours a week helping on
	the bug tracker.
In-Reply-To: <701178.18215.qm@web32513.mail.mud.yahoo.com>
References: <701178.18215.qm@web32513.mail.mud.yahoo.com>
Message-ID: <bbaeab100802192255s4013945bo752cec2c7a42b3b8@mail.gmail.com>

On Feb 19, 2008 8:56 PM, Jonathan Mark <jonathansamuel at yahoo.com> wrote:
> If you would like me to help on the Python bug tracker respond with the particulars.

Read the following pages to find out more:

http://wiki.python.org/moin/TrackerDocs/
http://wiki.python.org/moin/TrackerDevelopment
http://psf.upfronthosting.co.za/roundup/meta/

-Brett

From brett at python.org  Wed Feb 20 07:55:57 2008
From: brett at python.org (Brett Cannon)
Date: Tue, 19 Feb 2008 22:55:57 -0800
Subject: [Tracker-discuss] Call for volunteers to help maintain
	bugs.python.org's issue tracker
In-Reply-To: <631215.66757.qm@web53804.mail.re2.yahoo.com>
References: <bbaeab100802181452g4b9c43e1sc1ace073da8488a@mail.gmail.com>
	<631215.66757.qm@web53804.mail.re2.yahoo.com>
Message-ID: <bbaeab100802192255k9a5d9f2pd9a0a433daa0a048@mail.gmail.com>

On Feb 19, 2008 10:37 PM, Shitiz Bansal <shitizb at yahoo.com> wrote:
> Hi,
> I am a python enthusiast willing to help. I am based in India and working as
> a software professional for 2 and a half years. Let me know how i can help
> and how much of my time it will take if i get involved.

Read the following pages to find out more:

http://wiki.python.org/moin/TrackerDocs/
http://wiki.python.org/moin/TrackerDevelopment
http://psf.upfronthosting.co.za/roundup/meta/

As for time commitment, that's totally up to you.

-Brett

> Thanks and Regards,
> Shitiz Bansal
>
>
>
> Brett Cannon <brett at python.org> wrote:
>
>  The Python Software Foundation's infrastructure committee is looking
> for volunteers to help maintain the Roundup issue tracker installed
> for http://bugs.python.org. Responsibilities revolve around
> maintaining the Roundup installation itself (tracker schema, modifying
> the installed copy of Roundup, etc.) and the occasional database work
> (changes to the database, etc.).
>
> You do not have to be an expert at Roundup to volunteer! You can learn
> "on the job" by doing offline development and submitting patches until
> you are of a proper level of experience to gain commit access to the
> code (which can be seen at XXX). If you still have a New Years
> resolution to help Python out this is a great way to fulfill the
> promise you made yourself for 2008!
>
> If you are interested in volunteering, please email tracker-discuss at
> python.org. Thanks to all who have helped with the tracker already and
> those that will in the future!
>
> -Brett Cannon
> Chairman, PSF infrastructure committee
> --
>
> http://mail.python.org/mailman/listinfo/python-list
>
>
>
>  ________________________________
> Looking for last minute shopping deals? Find them fast with Yahoo! Search.
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>
>

From martin at v.loewis.de  Wed Feb 20 08:39:35 2008
From: martin at v.loewis.de (=?UTF-8?B?Ik1hcnRpbiB2LiBMw7Z3aXMi?=)
Date: Wed, 20 Feb 2008 08:39:35 +0100
Subject: [Tracker-discuss] tracker maintenance
In-Reply-To: <20080220064315.GA81956@nexus.in-nomine.org>
References: <20080107094349.GC82115@nexus.in-nomine.org>	<bbaeab100802181453l6aaf08a9s9810d77895611dcd@mail.gmail.com>
	<20080220064315.GA81956@nexus.in-nomine.org>
Message-ID: <47BBD937.1030501@v.loewis.de>

> I guess the XXX was supposed to be filled in? ;)
> So it basically means the Roundup stuff needs patches mostly that others
> will apply at first? Or is there also sysadmin maintenance needed?

As a follow-up to Brett's message - yes, it's mostly roundup hacking,
in particular in the python-dev instance (detectors specifically).

It is also monitoring the meta tracker. In some cases, urgent action
might be necessary, so it's good if people are spread around the globe.
In the past, urgent action was necessary to remove spam, and to fix
bogus changes to tracker (e.g. when I committed a patch that would
raise exceptions in certain cases, which would then prevent people from
following up to some issues).

Regards,
Martin

From ybc2084 at gmail.com  Wed Feb 20 09:19:11 2008
From: ybc2084 at gmail.com (Yunchuan Chen)
Date: Wed, 20 Feb 2008 16:19:11 +0800
Subject: [Tracker-discuss] apply to be maintainer of bugs.python.org's issue
	tracker
Message-ID: <b664b8250802200019h40f2afc9sc619c755ce0cfed2@mail.gmail.com>

Hi,

I'm willing to contribute to python and I apply to be a maintainer of
bugs.python.org's issue tracker. Thank you for your reviewing.

BRs,
Rockins Chen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20080220/357ea69a/attachment.htm 

From brett at python.org  Wed Feb 20 21:42:18 2008
From: brett at python.org (Brett Cannon)
Date: Wed, 20 Feb 2008 12:42:18 -0800
Subject: [Tracker-discuss] apply to be maintainer of bugs.python.org's
	issue tracker
In-Reply-To: <b664b8250802200019h40f2afc9sc619c755ce0cfed2@mail.gmail.com>
References: <b664b8250802200019h40f2afc9sc619c755ce0cfed2@mail.gmail.com>
Message-ID: <bbaeab100802201242h76cc35cdg92b5a7190167299e@mail.gmail.com>

On Feb 20, 2008 12:19 AM, Yunchuan Chen <ybc2084 at gmail.com> wrote:
> Hi,
>
> I'm willing to contribute to python and I apply to be a maintainer of
> bugs.python.org's issue tracker. Thank you for your reviewing.

Read http://wiki.python.org/moin/TrackerDocs/ to get started. You will
find links to the meta-tracker which lists what needs work. There is
also a link to how to develop for the tracker at the bottom of the
linked page.

-Brett

From martin at v.loewis.de  Wed Feb 20 21:32:30 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Wed, 20 Feb 2008 21:32:30 +0100
Subject: [Tracker-discuss] Jython tracker now live
Message-ID: <47BC8E5E.4030805@v.loewis.de>

For those who haven't been following jython-dev: bugs.jython.org
is now live.

Regards,
Martin

From martin at v.loewis.de  Wed Feb 20 22:03:33 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Wed, 20 Feb 2008 22:03:33 +0100
Subject: [Tracker-discuss] [Python-Dev] Small RFEs and the Bug Tracker
In-Reply-To: <ca471dc20802201243k3fc751b5j734fafe392cd8032@mail.gmail.com>
References: <e04bdf310802180322g412a6309la776603307e9df75@mail.gmail.com>	
	<bbaeab100802181241s162f586esb3f6f44c51b988a6@mail.gmail.com>	
	<47BAB718.4050000@gmail.com> <fpf7gb$mdq$1@ger.gmane.org>	
	<e04bdf310802191222i7c259bebya9a6407c769f8a2e@mail.gmail.com>	
	<47BB5CDC.60705@v.loewis.de> <fpglhv$2cf$1@ger.gmane.org>	
	<8b943f2b0802200025h6fa7fb03q13bacde16b0cbd82@mail.gmail.com>	
	<47BC8F34.4020601@v.loewis.de>	
	<bbaeab100802201239w224fb604s39343cccc2d2633@mail.gmail.com>
	<ca471dc20802201243k3fc751b5j734fafe392cd8032@mail.gmail.com>
Message-ID: <47BC95A5.9030807@v.loewis.de>

Guido van Rossum wrote:
> On Feb 20, 2008 12:39 PM, Brett Cannon <brett at python.org> wrote:
>> On Feb 20, 2008 12:36 PM, "Martin v. L?wis" <martin at v.loewis.de> wrote:
>>>> I agree, the name is a bit confusing when you're not used to it.
>>> Renaming it is easy. To the native speakers reading it: What should
>>> it be called? (please try to come up with something shorter than
>>> "request for enhancement")
>> "feature request"?

I already had it at enhancement :-)

In any case, by BDFL pronouncement, it's "feature request" now.

http://bugs.python.org/issue_type6

(as an aside - can anybody tell me how to suppress link/unlink
notifications in the history of each issue_type? I don't think
we need them (unlike the reverse link's history, i.e. the
history of the issue's type field))


Regards,
Martin


From brett at python.org  Wed Feb 20 22:53:20 2008
From: brett at python.org (Brett Cannon)
Date: Wed, 20 Feb 2008 13:53:20 -0800
Subject: [Tracker-discuss] Jython tracker now live
In-Reply-To: <47BC8E5E.4030805@v.loewis.de>
References: <47BC8E5E.4030805@v.loewis.de>
Message-ID: <bbaeab100802201353p2142961frcacd2779ebaa7e15@mail.gmail.com>

On Wed, Feb 20, 2008 at 12:32 PM, "Martin v. L?wis" <martin at v.loewis.de> wrote:
> For those who haven't been following jython-dev: bugs.jython.org
>  is now live.

Very cool! Great work, Martin!

-Brett

From metatracker at psf.upfronthosting.co.za  Thu Feb 21 15:41:47 2008
From: metatracker at psf.upfronthosting.co.za (Dmitry Kozhevin)
Date: Thu, 21 Feb 2008 14:41:47 -0000
Subject: [Tracker-discuss] [issue179] KeyError when searching for usernames
	that don't exist
In-Reply-To: <1200740111.19.0.300144918506.issue179@psf.upfronthosting.co.za>
Message-ID: <1203604907.51.0.237694846512.issue179@psf.upfronthosting.co.za>


Dmitry Kozhevin added the comment:

site-packages/roundup/backends/rdbms_common.py
@@ -2175,7 +2175,7 @@
                                 d[entry] = entry                               
                             l = []                                             
                             if d.has_key(None) or not d:                       
-                                d.pop(None, 'dummy')                           
+                                del d[None]                                    
                                 l.append('_%s._%s is NULL'%(pln, k))           
                             if d:                                              
                                 v = d.keys()

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

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

From gortan at gmail.com  Thu Feb 21 18:54:08 2008
From: gortan at gmail.com (Philipp Gortan)
Date: Thu, 21 Feb 2008 18:54:08 +0100
Subject: [Tracker-discuss] Call for volunteers to help maintain
	bugs.python.org's issue tracker
In-Reply-To: <bbaeab100802181452g4b9c43e1sc1ace073da8488a@mail.gmail.com>
References: <bbaeab100802181452g4b9c43e1sc1ace073da8488a@mail.gmail.com>
Message-ID: <fdc138080802210954v188d693fycfb5d93391dc71e2@mail.gmail.com>

On Mon, Feb 18, 2008 at 11:52 PM, Brett Cannon <brett at python.org> wrote:
> The Python Software Foundation's infrastructure committee is looking
>  for volunteers to help maintain the Roundup issue tracker

Hi Python geeks,

May I introduce myself: my name is Philipp,
I'm 28 years old and I'm a full-time Python developer for four years now.
I started to co-maintain our company's roundup tracker one year ago,
so I know the basics regarding roundup schemas, templating, and detectors.

My spare-time is of course always limited (as yours is too, I'm certain),
so I cannot promise too much, but I'd definitely love to contribute,
so I'll do my best!

I'll do my homework (read the tracker docs in the python wiki) and see
what I can do...

cu, Philipp

-- 
Philipp Gortan <gortan at gmail.com>

Obviously I was either onto something, or on something.
 -- Larry Wall on the creation of Perl

From metatracker at psf.upfronthosting.co.za  Thu Feb 21 21:38:03 2008
From: metatracker at psf.upfronthosting.co.za (phr)
Date: Thu, 21 Feb 2008 20:38:03 -0000
Subject: [Tracker-discuss] [issue190] security problem
In-Reply-To: <1203626283.96.0.396993149865.issue190@psf.upfronthosting.co.za>
Message-ID: <1203626283.96.0.396993149865.issue190@psf.upfronthosting.co.za>


New submission from phr:

The tracker doesn't appear to have a way to privately report a security problem.

----------
messages: 972
nosy: phr
priority: bug
status: unread
title: security problem

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 21 21:41:03 2008
From: metatracker at psf.upfronthosting.co.za (phr)
Date: Thu, 21 Feb 2008 20:41:03 -0000
Subject: [Tracker-discuss] [issue191] security problem
In-Reply-To: <1203626463.38.0.128510210089.issue191@psf.upfronthosting.co.za>
Message-ID: <1203626463.38.0.128510210089.issue191@psf.upfronthosting.co.za>


New submission from phr:

There is a security problem that I'd consider significant that I don't want to
describe here until it is fixed.  Any suggestions?

----------
messages: 973
nosy: phr
priority: urgent
status: unread
title: security problem

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

From brett at python.org  Thu Feb 21 21:46:29 2008
From: brett at python.org (Brett Cannon)
Date: Thu, 21 Feb 2008 12:46:29 -0800
Subject: [Tracker-discuss] Call for volunteers to help maintain
	bugs.python.org's issue tracker
In-Reply-To: <fdc138080802210954v188d693fycfb5d93391dc71e2@mail.gmail.com>
References: <bbaeab100802181452g4b9c43e1sc1ace073da8488a@mail.gmail.com>
	<fdc138080802210954v188d693fycfb5d93391dc71e2@mail.gmail.com>
Message-ID: <bbaeab100802211246o7f75fdd6xbddac2257a2b5790@mail.gmail.com>

On Thu, Feb 21, 2008 at 9:54 AM, Philipp Gortan <gortan at gmail.com> wrote:
> On Mon, Feb 18, 2008 at 11:52 PM, Brett Cannon <brett at python.org> wrote:
>  > The Python Software Foundation's infrastructure committee is looking
>  >  for volunteers to help maintain the Roundup issue tracker
>
>  Hi Python geeks,
>
>  May I introduce myself: my name is Philipp,
>  I'm 28 years old and I'm a full-time Python developer for four years now.
>  I started to co-maintain our company's roundup tracker one year ago,
>  so I know the basics regarding roundup schemas, templating, and detectors.
>
>  My spare-time is of course always limited (as yours is too, I'm certain),
>  so I cannot promise too much, but I'd definitely love to contribute,
>  so I'll do my best!
>
>  I'll do my homework (read the tracker docs in the python wiki) and see
>  what I can do...

Great, Philipp! When reading the docs note the links to the
meta-tracker which has all the issues related to the tracker. And also
note the link to the tracker development doc which gives details on
how to set up a testing instance.

-Brett

From metatracker at psf.upfronthosting.co.za  Thu Feb 21 21:54:25 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 21 Feb 2008 20:54:25 -0000
Subject: [Tracker-discuss] [issue191] security problem
In-Reply-To: <1203626463.38.0.128510210089.issue191@psf.upfronthosting.co.za>
Message-ID: <1203627265.03.0.665288587068.issue191@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

Please report it to security at python.org

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

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

From martin at v.loewis.de  Thu Feb 21 21:55:33 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Thu, 21 Feb 2008 21:55:33 +0100
Subject: [Tracker-discuss] [issue190] security problem
In-Reply-To: <1203626283.96.0.396993149865.issue190@psf.upfronthosting.co.za>
References: <1203626283.96.0.396993149865.issue190@psf.upfronthosting.co.za>
Message-ID: <47BDE545.80504@v.loewis.de>

> The tracker doesn't appear to have a way to privately report a security problem.

That's mostly intentional. Issues that shouldn't be disclosed should be 
reported to security at python.org.

Regards,
Martin

From metatracker at psf.upfronthosting.co.za  Thu Feb 21 21:55:37 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 21 Feb 2008 20:55:37 -0000
Subject: [Tracker-discuss] [issue190] security problem
In-Reply-To: <1203626283.96.0.396993149865.issue190@psf.upfronthosting.co.za>
Message-ID: <47BDE545.80504@v.loewis.de>


Martin v. L?wis added the comment:

> The tracker doesn't appear to have a way to privately report a security problem.

That's mostly intentional. Issues that shouldn't be disclosed should be 
reported to security at python.org.

Regards,
Martin

----------
status: unread -> chatting
title: tracker has no way to mark a problem as private -> security problem

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

From draghuram at gmail.com  Thu Feb 21 22:00:54 2008
From: draghuram at gmail.com (Raghuram Devarakonda)
Date: Thu, 21 Feb 2008 16:00:54 -0500
Subject: [Tracker-discuss] Call for volunteers to help maintain
	bugs.python.org's issue tracker
In-Reply-To: <bbaeab100802211246o7f75fdd6xbddac2257a2b5790@mail.gmail.com>
References: <bbaeab100802181452g4b9c43e1sc1ace073da8488a@mail.gmail.com>
	<fdc138080802210954v188d693fycfb5d93391dc71e2@mail.gmail.com>
	<bbaeab100802211246o7f75fdd6xbddac2257a2b5790@mail.gmail.com>
Message-ID: <2c51ecee0802211300o70222ae4i103946f7faa3f980@mail.gmail.com>

>  meta-tracker which has all the issues related to the tracker. And also
>  note the link to the tracker development doc which gives details on
>  how to set up a testing instance.

I would like to point out that the document at
http://wiki.python.org/moin/TrackerDevelopment is not an accurate
description of setting up a local instance with the *latest* source
(confirmed by Martin). I have updated it with couple of notes that I
needed to get going. I suggest that any one who is setting up a local
instance to actively update this document with their experiences. For
the record, I reached a point where the tracker is up and running but
when I create an issue, there is an error - something about wrong
SPAMBAYES_URI configuration parameter. I will post more details (and
update the wiki page) once I get some time to look into it more.

From neduma at gmail.com  Thu Feb 21 20:44:25 2008
From: neduma at gmail.com (nedu)
Date: Thu, 21 Feb 2008 11:44:25 -0800 (PST)
Subject: [Tracker-discuss] Fwd: Call for volunteers to help maintain
	bugs.python.org's issue tracker
In-Reply-To: <mailman.963.1203417804.9267.python-announce-list@python.org>
References: <mailman.963.1203417804.9267.python-announce-list@python.org>
Message-ID: <654a8abe-7888-46f3-94a1-85f1ca70f911@s12g2000prg.googlegroups.com>

Hi,

I'm interested to volunteering here. Please let me know the process.

regards,
Nedu.


---------- Forwarded message ----------
From: "Brett Cannon" <br... at python.org>
Date: Feb 18, 2:52?pm
Subject: Call for volunteers to help maintain bugs.python.org's issue
tracker
To: comp.lang.python.announce


The Python Software Foundation's infrastructure committee is looking
for volunteers to help maintain the Roundup issue tracker installed
forhttp://bugs.python.org. Responsibilities revolve around
maintaining the Roundup installation itself (tracker schema, modifying
the installed copy of Roundup, etc.) and the occasional database work
(changes to the database, etc.).

You do not have to be an expert at Roundup to volunteer! You can learn
"on the job" by doing offline development and submitting patches until
you are of a proper level of experience to gain commit access to the
code (which can be seen at XXX). If you still have a New Years
resolution to help Python out this is a great way to fulfill the
promise you made yourself for 2008!

If you are interested in volunteering, please email tracker-discuss at
python.org. Thanks to all who have helped with the tracker already and
those that will in the future!

-Brett Cannon
Chairman, PSF infrastructure committee

From brett at python.org  Thu Feb 21 22:06:35 2008
From: brett at python.org (Brett Cannon)
Date: Thu, 21 Feb 2008 13:06:35 -0800
Subject: [Tracker-discuss] Fwd: Call for volunteers to help maintain
	bugs.python.org's issue tracker
In-Reply-To: <654a8abe-7888-46f3-94a1-85f1ca70f911@s12g2000prg.googlegroups.com>
References: <mailman.963.1203417804.9267.python-announce-list@python.org>
	<654a8abe-7888-46f3-94a1-85f1ca70f911@s12g2000prg.googlegroups.com>
Message-ID: <bbaeab100802211306r76fc2864n873afa0af4337ff9@mail.gmail.com>

On Thu, Feb 21, 2008 at 11:44 AM, nedu <neduma at gmail.com> wrote:
> Hi,
>
>  I'm interested to volunteering here. Please let me know the process.
>

Read the docs at http://wiki.python.org/moin/TrackerDocs/ , noting the
links to the meta-tracker and tracker development docs. Please be
aware, though, that the tracker development docs are not completely
up-to-date so please update anything you come across that needs
changing.

-Brett



>  regards,
>  Nedu.
>
>
>
>  ---------- Forwarded message ----------
>  From: "Brett Cannon" <br... at python.org>
>  Date: Feb 18, 2:52 pm
>  Subject: Call for volunteers to help maintain bugs.python.org's issue
>  tracker
>
> To: comp.lang.python.announce
>
>
>  The Python Software Foundation's infrastructure committee is looking
>  for volunteers to help maintain the Roundup issue tracker installed
>  forhttp://bugs.python.org. Responsibilities revolve around
>
> maintaining the Roundup installation itself (tracker schema, modifying
>  the installed copy of Roundup, etc.) and the occasional database work
>  (changes to the database, etc.).
>
>  You do not have to be an expert at Roundup to volunteer! You can learn
>  "on the job" by doing offline development and submitting patches until
>  you are of a proper level of experience to gain commit access to the
>  code (which can be seen at XXX). If you still have a New Years
>  resolution to help Python out this is a great way to fulfill the
>  promise you made yourself for 2008!
>
>  If you are interested in volunteering, please email tracker-discuss at
>  python.org. Thanks to all who have helped with the tracker already and
>  those that will in the future!
>
>  -Brett Cannon
>  Chairman, PSF infrastructure committee
>
>
> _______________________________________________
>  Tracker-discuss mailing list
>  Tracker-discuss at python.org
>  http://mail.python.org/mailman/listinfo/tracker-discuss
>

From metatracker at psf.upfronthosting.co.za  Thu Feb 21 22:12:30 2008
From: metatracker at psf.upfronthosting.co.za (phr)
Date: Thu, 21 Feb 2008 21:12:30 -0000
Subject: [Tracker-discuss] [issue191] security problem
In-Reply-To: <1203626463.38.0.128510210089.issue191@psf.upfronthosting.co.za>
Message-ID: <1203628350.14.0.489804729281.issue191@psf.upfronthosting.co.za>


phr added the comment:

Thanks, reported there.

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

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

From metatracker at psf.upfronthosting.co.za  Fri Feb 22 04:59:12 2008
From: metatracker at psf.upfronthosting.co.za (phr)
Date: Fri, 22 Feb 2008 03:59:12 -0000
Subject: [Tracker-discuss] [issue190] security problem
In-Reply-To: <1203626283.96.0.396993149865.issue190@psf.upfronthosting.co.za>
Message-ID: <1203652752.57.0.462621361329.issue190@psf.upfronthosting.co.za>


phr added the comment:

Well, ok, but a link or explanation of that somewhere on the tracker would be
helpful.  Eventually it may be worth adding this, depending on how the
maintainers want to handle such reports.  I know that launchpad and bugzilla can
accept private reports and the feature is helpful.  They also normally serve
pages through SSL which should be more secure than email.  Anything really
sensitive is probably better off on a single well-secured server than in the
mailboxes of N different maintainers.  However, this probably isn't an
overriding issue for Python right now.

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

From metatracker at psf.upfronthosting.co.za  Fri Feb 22 09:25:40 2008
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Fri, 22 Feb 2008 08:25:40 -0000
Subject: [Tracker-discuss] [issue192] change roundup date format
In-Reply-To: <1203668740.94.0.693003763887.issue192@psf.upfronthosting.co.za>
Message-ID: <1203668740.94.0.693003763887.issue192@psf.upfronthosting.co.za>


New submission from Georg Brandl:

The current date format (2008-02-13.08:20:34) is not very readable.
If this is easily changeable, I propose 2008-02-13 08:20 as the date format
(i.e., remove the dot between date and time, and leave out the seconds).

----------
messages: 978
nosy: gbrandl
priority: wish
status: unread
title: change roundup date format

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

From martin at marcher.name  Fri Feb 22 11:57:03 2008
From: martin at marcher.name (Martin Marcher)
Date: Fri, 22 Feb 2008 11:57:03 +0100
Subject: [Tracker-discuss] Call for volunteers to help maintain
	bugs.python.org's issue tracker
In-Reply-To: <2c51ecee0802211300o70222ae4i103946f7faa3f980@mail.gmail.com>
References: <bbaeab100802181452g4b9c43e1sc1ace073da8488a@mail.gmail.com>
	<fdc138080802210954v188d693fycfb5d93391dc71e2@mail.gmail.com>
	<bbaeab100802211246o7f75fdd6xbddac2257a2b5790@mail.gmail.com>
	<2c51ecee0802211300o70222ae4i103946f7faa3f980@mail.gmail.com>
Message-ID: <5fa6c12e0802220257v7d4516a5j4cdec9bc5acfd5b4@mail.gmail.com>

Hi,

On 2/21/08, Raghuram Devarakonda <draghuram at gmail.com> wrote:
> I would like to point out that the document at
>  http://wiki.python.org/moin/TrackerDevelopment is not an accurate
>  description of setting up a local instance with the *latest* source
>  (confirmed by Martin). I have updated it with couple of notes that I
>  needed to get going. I suggest that any one who is setting up a local
>  instance to actively update this document with their experiences. For
>  the record, I reached a point where the tracker is up and running but
>  when I create an issue, there is an error - something about wrong
>  SPAMBAYES_URI configuration parameter. I will post more details (and
>  update the wiki page) once I get some time to look into it more.

I had the same issue, i solved it by removing the xapian package from
my system. IIRC it says at the top something about a missing attribute
"stem" - still a description of what to change in the source to have
xapian installed _and_ a working python tracker would be very nice.

hth
martin

>
> _______________________________________________
>  Tracker-discuss mailing list
>  Tracker-discuss at python.org
>  http://mail.python.org/mailman/listinfo/tracker-discuss
>


-- 
http://noneisyours.marcher.name
https://twitter.com/MartinMarcher
http://www.xing.com/profile/Martin_Marcher
http://www.linkedin.com/in/martinmarcher

You are not free to read this message,
by doing so, you have violated my licence
and are required to urinate publicly. Thank you.

From wyldwolf at gmail.com  Fri Feb 22 15:33:10 2008
From: wyldwolf at gmail.com (Kevin)
Date: Fri, 22 Feb 2008 08:33:10 -0600
Subject: [Tracker-discuss] [issue192] change roundup date format
In-Reply-To: <1203668740.94.0.693003763887.issue192@psf.upfronthosting.co.za>
References: <1203668740.94.0.693003763887.issue192@psf.upfronthosting.co.za>
	<1203668740.94.0.693003763887.issue192@psf.upfronthosting.co.za>
Message-ID: <77895c1d0802220633x67387a6ch93d61391f43f5d20@mail.gmail.com>

This duplicates item #182:

Timestamps in the tracker currently look like this:

  2005-09-24.16:40:40

I'm proposing to replace the dot with a space, so it will look like this:

  2005-09-24 16:40:40

That makes it much easier to separate the date from the time at a glance -- I
realize I keep having trouble parsing dates because the "24.16:40:40" part
somehow tells my brain that it is the timestamp...

After all, these dates are for human consumption, not for some XML parser.


Thanks.

Kevin Kelley

On Fri, Feb 22, 2008 at 2:25 AM, Georg Brandl <
metatracker at psf.upfronthosting.co.za> wrote:

>
> New submission from Georg Brandl:
>
> The current date format (2008-02-13.08:20:34) is not very readable.
> If this is easily changeable, I propose 2008-02-13 08:20 as the date
> format
> (i.e., remove the dot between date and time, and leave out the seconds).
>
> ----------
> messages: 978
> nosy: gbrandl
> priority: wish
> status: unread
> title: change roundup date format
>
> _______________________________________________________
> Meta Tracker <metatracker at psf.upfronthosting.co.za>
> <http://psf.upfronthosting.co.za/roundup/meta/issue192>
> _______________________________________________________
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20080222/f08fca98/attachment.htm 

From metatracker at psf.upfronthosting.co.za  Fri Feb 22 15:51:39 2008
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Fri, 22 Feb 2008 14:51:39 -0000
Subject: [Tracker-discuss] [issue182] Format timestamps nicer
In-Reply-To: <1201120142.54.0.952798238955.issue182@psf.upfronthosting.co.za>
Message-ID: <1203691899.44.0.6276476446.issue182@psf.upfronthosting.co.za>


Georg Brandl added the comment:

I propose to additionally leave out the seconds. (marked #192 as duplicate)

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

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

From metatracker at psf.upfronthosting.co.za  Fri Feb 22 15:51:50 2008
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Fri, 22 Feb 2008 14:51:50 -0000
Subject: [Tracker-discuss] [issue192] change roundup date format
In-Reply-To: <1203668740.94.0.693003763887.issue192@psf.upfronthosting.co.za>
Message-ID: <1203691910.75.0.488301940555.issue192@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Duplicate of #182.

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

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

From metatracker at psf.upfronthosting.co.za  Fri Feb 22 16:36:43 2008
From: metatracker at psf.upfronthosting.co.za (Guido van Rossum)
Date: Fri, 22 Feb 2008 15:36:43 -0000
Subject: [Tracker-discuss] [issue182] Format timestamps nicer
In-Reply-To: <1201120142.54.0.952798238955.issue182@psf.upfronthosting.co.za>
Message-ID: <1203694603.55.0.522348319944.issue182@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

+1

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

From metatracker at psf.upfronthosting.co.za  Fri Feb 22 18:30:03 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Fri, 22 Feb 2008 17:30:03 -0000
Subject: [Tracker-discuss] [issue190] security problem
In-Reply-To: <1203626283.96.0.396993149865.issue190@psf.upfronthosting.co.za>
Message-ID: <1203701402.93.0.628798146787.issue190@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

The problem is that we would need to create a separate account role, and then
restrict classified issues to access only by that role, and by the submitter.
The security model of Roundup makes this fairly error-prone - this installation
gives "view" permissions to all issues to everybody, and restricting it requires
a lot of work,testing, and faith.

So email is *much* more secure.

Contributions are welcome.

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

From martin at v.loewis.de  Fri Feb 22 18:39:29 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Fri, 22 Feb 2008 18:39:29 +0100
Subject: [Tracker-discuss] SPAMBAYES_URI (Was: Call for volunteers to
 help maintain	bugs.python.org's issue tracker)
In-Reply-To: <5fa6c12e0802220257v7d4516a5j4cdec9bc5acfd5b4@mail.gmail.com>
References: <bbaeab100802181452g4b9c43e1sc1ace073da8488a@mail.gmail.com>	<fdc138080802210954v188d693fycfb5d93391dc71e2@mail.gmail.com>	<bbaeab100802211246o7f75fdd6xbddac2257a2b5790@mail.gmail.com>	<2c51ecee0802211300o70222ae4i103946f7faa3f980@mail.gmail.com>
	<5fa6c12e0802220257v7d4516a5j4cdec9bc5acfd5b4@mail.gmail.com>
Message-ID: <47BF08D1.9090804@v.loewis.de>

> I had the same issue, i solved it by removing the xapian package from
> my system. IIRC it says at the top something about a missing attribute
> "stem" - still a description of what to change in the source to have
> xapian installed _and_ a working python tracker would be very nice.

I'm truly surprised if there is any relationship between whether Xapian
is installed, and whether the python-dev instance complains about
a missing SPAMBAYES_URI. Instead, I would rather expect that that
complaint comes from detectors/config.ini missing spambayes_uri.

In any case, I have disabled the spambayes detected on my local 
instance, by putting "return" into its init function.

Contributions for a better way to disable it (e.g. by treating a
missing spambayes_uri as an indicator for no local spambayes
installation) would be welcome.

While we have little maintenance capacity for the tracker in general,
we have no maintenance capacity whatsoever for the spambayes
integration. Nobody knows what it does, how it works, and whether it
does what it should do correctly.

Regards,
Martin

From hfoffani at gmail.com  Fri Feb 22 18:55:06 2008
From: hfoffani at gmail.com (Hernan M Foffani)
Date: Fri, 22 Feb 2008 18:55:06 +0100
Subject: [Tracker-discuss] SPAMBAYES_URI (Was: Call for volunteers to
	help maintain bugs.python.org's issue tracker)
In-Reply-To: <47BF08D1.9090804@v.loewis.de>
References: <bbaeab100802181452g4b9c43e1sc1ace073da8488a@mail.gmail.com>
	<fdc138080802210954v188d693fycfb5d93391dc71e2@mail.gmail.com>
	<bbaeab100802211246o7f75fdd6xbddac2257a2b5790@mail.gmail.com>
	<2c51ecee0802211300o70222ae4i103946f7faa3f980@mail.gmail.com>
	<5fa6c12e0802220257v7d4516a5j4cdec9bc5acfd5b4@mail.gmail.com>
	<47BF08D1.9090804@v.loewis.de>
Message-ID: <11fab4bc0802220955s12b1e45fh36cdc147277dd736@mail.gmail.com>

Initialization of the tracker under Windows is a little trickier because the
extension contains (or used to contain) 'link ../ etc.' which doesn't work.
In my local installation I removed the spambayes extension.

I also removed the audit2to3 detector (because it has the user
'collinwinter' hardwired)


On Fri, Feb 22, 2008 at 6:39 PM, "Martin v. L?wis" <martin at v.loewis.de> wrote:
> > I had the same issue, i solved it by removing the xapian package from
> > my system. IIRC it says at the top something about a missing attribute
> > "stem" - still a description of what to change in the source to have
> > xapian installed _and_ a working python tracker would be very nice.
>
> I'm truly surprised if there is any relationship between whether Xapian
> is installed, and whether the python-dev instance complains about
> a missing SPAMBAYES_URI. Instead, I would rather expect that that
> complaint comes from detectors/config.ini missing spambayes_uri.
>
> In any case, I have disabled the spambayes detected on my local
> instance, by putting "return" into its init function.
>
> Contributions for a better way to disable it (e.g. by treating a
> missing spambayes_uri as an indicator for no local spambayes
> installation) would be welcome.
>
> While we have little maintenance capacity for the tracker in general,
> we have no maintenance capacity whatsoever for the spambayes
> integration. Nobody knows what it does, how it works, and whether it
> does what it should do correctly.
>
> Regards,
> Martin
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>

From skip at pobox.com  Fri Feb 22 19:23:20 2008
From: skip at pobox.com (skip at pobox.com)
Date: Fri, 22 Feb 2008 12:23:20 -0600
Subject: [Tracker-discuss] SPAMBAYES_URI (Was: Call for volunteers to
 help maintain bugs.python.org's issue tracker)
In-Reply-To: <47BF08D1.9090804@v.loewis.de>
References: <bbaeab100802181452g4b9c43e1sc1ace073da8488a@mail.gmail.com>
	<fdc138080802210954v188d693fycfb5d93391dc71e2@mail.gmail.com>
	<bbaeab100802211246o7f75fdd6xbddac2257a2b5790@mail.gmail.com>
	<2c51ecee0802211300o70222ae4i103946f7faa3f980@mail.gmail.com>
	<5fa6c12e0802220257v7d4516a5j4cdec9bc5acfd5b4@mail.gmail.com>
	<47BF08D1.9090804@v.loewis.de>
Message-ID: <18367.4888.56540.616271@montanaro-dyndns-org.local>


    Martin> While we have little maintenance capacity for the tracker in
    Martin> general, we have no maintenance capacity whatsoever for the
    Martin> spambayes integration. Nobody knows what it does, how it works,
    Martin> and whether it does what it should do correctly.

Well, I kinda do know what the SpamBayes subpackage does, but seem to have
lost a reference for the source code repository.  If you can provide a link
I will take a look.  (There are way too many source code repositories - even
in just the Python world - to keep them all straight.)

Skip

From martin at v.loewis.de  Fri Feb 22 19:46:02 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Fri, 22 Feb 2008 19:46:02 +0100
Subject: [Tracker-discuss] SPAMBAYES_URI (Was: Call for volunteers to
 help maintain bugs.python.org's issue tracker)
In-Reply-To: <18367.4888.56540.616271@montanaro-dyndns-org.local>
References: <bbaeab100802181452g4b9c43e1sc1ace073da8488a@mail.gmail.com>
	<fdc138080802210954v188d693fycfb5d93391dc71e2@mail.gmail.com>
	<bbaeab100802211246o7f75fdd6xbddac2257a2b5790@mail.gmail.com>
	<2c51ecee0802211300o70222ae4i103946f7faa3f980@mail.gmail.com>
	<5fa6c12e0802220257v7d4516a5j4cdec9bc5acfd5b4@mail.gmail.com>
	<47BF08D1.9090804@v.loewis.de>
	<18367.4888.56540.616271@montanaro-dyndns-org.local>
Message-ID: <47BF186A.30204@v.loewis.de>

> Well, I kinda do know what the SpamBayes subpackage does, but seem to have
> lost a reference for the source code repository.  If you can provide a link
> I will take a look.  

http://svn.python.org/projects/tracker/

Regards,
Martin

From metatracker at psf.upfronthosting.co.za  Sat Feb 23 00:36:02 2008
From: metatracker at psf.upfronthosting.co.za (phr)
Date: Fri, 22 Feb 2008 23:36:02 -0000
Subject: [Tracker-discuss] [issue190] security problem
In-Reply-To: <1203626283.96.0.396993149865.issue190@psf.upfronthosting.co.za>
Message-ID: <1203723362.18.0.157187436313.issue190@psf.upfronthosting.co.za>


phr added the comment:

I guess this is best left as a long term wish list item in that case.  Having
been through this kind of thing a few times before, I agree that if it's
complicated to do, it's likely to leave holes.  So it's best accomplished by
organizing the architecture in a way that makes it simple and solid.

I do think it's worth doing something about issue #191 (reported by email) even
if it's a short term hack.

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

From martin at v.loewis.de  Sat Feb 23 08:11:54 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Sat, 23 Feb 2008 08:11:54 +0100
Subject: [Tracker-discuss] [issue190] security problem
In-Reply-To: <1203723362.18.0.157187436313.issue190@psf.upfronthosting.co.za>
References: <1203723362.18.0.157187436313.issue190@psf.upfronthosting.co.za>
Message-ID: <47BFC73A.7000501@v.loewis.de>

> I do think it's worth doing something about issue #191 (reported by email) even
> if it's a short term hack.

If you are talking about the issue you reported privately - nobody here 
knows what the issue is; that's the point of a classified report.

From metatracker at psf.upfronthosting.co.za  Sat Feb 23 08:12:03 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Sat, 23 Feb 2008 07:12:03 -0000
Subject: [Tracker-discuss] [issue190] security problem
In-Reply-To: <1203723362.18.0.157187436313.issue190@psf.upfronthosting.co.za>
Message-ID: <47BFC73A.7000501@v.loewis.de>


Martin v. L?wis added the comment:

> I do think it's worth doing something about issue #191 (reported by email) even
> if it's a short term hack.

If you are talking about the issue you reported privately - nobody here 
knows what the issue is; that's the point of a classified report.

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

From metatracker at psf.upfronthosting.co.za  Sat Feb 23 20:40:02 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Sat, 23 Feb 2008 19:40:02 -0000
Subject: [Tracker-discuss] [issue182] Format timestamps nicer
In-Reply-To: <1201120142.54.0.952798238955.issue182@psf.upfronthosting.co.za>
Message-ID: <1203795602.52.0.671024806175.issue182@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

This is now fixed in r61010.

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

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

From metatracker at psf.upfronthosting.co.za  Sat Feb 23 21:01:47 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Sat, 23 Feb 2008 20:01:47 -0000
Subject: [Tracker-discuss] [issue179] KeyError when searching for usernames
	that don't exist
In-Reply-To: <1200740111.19.0.300144918506.issue179@psf.upfronthosting.co.za>
Message-ID: <1203796907.45.0.145651228815.issue179@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

Thanks for pointing to the right location. I checked the upstream source, and
they  fixed the problem in a similar way in 1.183. I merged that in r61012.

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

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

From metatracker at psf.upfronthosting.co.za  Sat Feb 23 21:06:57 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Sat, 23 Feb 2008 20:06:57 -0000
Subject: [Tracker-discuss] [issue132] Enable blocker/dependency detector
In-Reply-To: <1187889251.39.0.628325064137.issue132@psf.upfronthosting.co.za>
Message-ID: <1203797217.51.0.81895746458.issue132@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

Checking auto-addition to nosy list.

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

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

From martin at v.loewis.de  Sat Feb 23 21:08:23 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Sat, 23 Feb 2008 21:08:23 +0100
Subject: [Tracker-discuss] Nosy lists on the meta tracker
Message-ID: <47C07D37.9020900@v.loewis.de>

I changed the meta tracker to automatically add message authors to
the nosy list for all messages, not just when they create an issue.
This seems to match more closely what people expect.

Regards,
Martin

From metatracker at psf.upfronthosting.co.za  Sat Feb 23 21:51:38 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Sat, 23 Feb 2008 20:51:38 -0000
Subject: [Tracker-discuss] [issue177] Set content type of .diff,
	.patch and .py to text/plain
In-Reply-To: <1199987051.75.0.768683673246.issue177@psf.upfronthosting.co.za>
Message-ID: <1203799898.69.0.444382691616.issue177@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

This is now fixed in r61014.

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

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

From metatracker at psf.upfronthosting.co.za  Sat Feb 23 21:54:00 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Sat, 23 Feb 2008 20:54:00 -0000
Subject: [Tracker-discuss] [issue177] Set content type of .diff,
	.patch and .py to text/plain
In-Reply-To: <1199987051.75.0.768683673246.issue177@psf.upfronthosting.co.za>
Message-ID: <1203800040.64.0.183397903641.issue177@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

Reopening - the existing patches still need to be changed.

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

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

From metatracker at psf.upfronthosting.co.za  Sat Feb 23 21:54:17 2008
From: metatracker at psf.upfronthosting.co.za (Guido van Rossum)
Date: Sat, 23 Feb 2008 20:54:17 -0000
Subject: [Tracker-discuss] [issue182] Format timestamps nicer
In-Reply-To: <1203795602.52.0.671024806175.issue182@psf.upfronthosting.co.za>
Message-ID: <ca471dc20802231254y326a6743p6597b922699796a2@mail.gmail.com>


Guido van Rossum added the comment:

How long before it goes live?

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

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

From skip at pobox.com  Sat Feb 23 22:00:41 2008
From: skip at pobox.com (skip at pobox.com)
Date: Sat, 23 Feb 2008 15:00:41 -0600
Subject: [Tracker-discuss] SPAMBAYES_URI (Was: Call for volunteers to
 help maintain bugs.python.org's issue tracker)
In-Reply-To: <47BF186A.30204@v.loewis.de>
References: <bbaeab100802181452g4b9c43e1sc1ace073da8488a@mail.gmail.com>
	<fdc138080802210954v188d693fycfb5d93391dc71e2@mail.gmail.com>
	<bbaeab100802211246o7f75fdd6xbddac2257a2b5790@mail.gmail.com>
	<2c51ecee0802211300o70222ae4i103946f7faa3f980@mail.gmail.com>
	<5fa6c12e0802220257v7d4516a5j4cdec9bc5acfd5b4@mail.gmail.com>
	<47BF08D1.9090804@v.loewis.de>
	<18367.4888.56540.616271@montanaro-dyndns-org.local>
	<47BF186A.30204@v.loewis.de>
Message-ID: <18368.35193.173565.749954@montanaro-dyndns-org.local>


    >> Well, I kinda do know what the SpamBayes subpackage does, but seem to
    >> have lost a reference for the source code repository.  If you can
    >> provide a link I will take a look.

    Martin> http://svn.python.org/projects/tracker/

Thanks.  I checked out the code and began poking around.  I see six
instances.  It looks like the python-dev-spambayes-integration and
spambayes_integration instances haven't been updated since last July.  I
will assume those are inactive.  It appears the python-dev instance includes
the SpamBayes changes.  The jobs and jython instances seem to as well.  The
meta tracker has "spambayes" in a somewhat different set of files.  I'm not
sure why/how that differs.  I did the initial auditor creation, but Erik was
the person who integrated this into the python-dev Roundup instance.

The SpamBayes setup is supposed to connect to a running SpamBayes server.
In python-dev/detectors/config.ini.template it's listed as

    http://www.webfast.com:80/sbrpc

which I am not running.  I'm not sure what the actual config.ini file says.
I gave directions about installing it last June:

    http://mail.python.org/pipermail/tracker-discuss/2007-June/000930.html

It looks like Erik installed it in July:

    http://mail.python.org/pipermail/tracker-discuss/2007-July/000952.html

and confirmed its setup here:

    http://mail.python.org/pipermail/tracker-discuss/2007-July/000955.html

If you can login on the tracker host you should be able to fire up a web
server and connect to

    http://localhost:8880/

then use that interface to train submissions as spam or ham.  I have no idea
if that's been done since it was first installed.  Perhaps Erik knows.  The
problem with making the interface more widely available is that the XMLRPC
server doesn't really implement any security of its own.  Protecting it with
an Apache reverse proxy that only allows some hosts to connect and requires
some simple authentication is probably good enough security.  If that can be
set up at that end, I'd be happy to take care of training through the web.
OTOH, maybe Erik set things up so you could train through the tracker
interface given the proper role.  (If that's set up I don't see anything in
the issue display that suggests I have the proper privileges.)

Is that enough information to get this activity back on-track?

Skip

From metatracker at psf.upfronthosting.co.za  Sat Feb 23 22:09:02 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Sat, 23 Feb 2008 21:09:02 -0000
Subject: [Tracker-discuss] [issue182] Format timestamps nicer
In-Reply-To: <1201120142.54.0.952798238955.issue182@psf.upfronthosting.co.za>
Message-ID: <1203800942.69.0.329834113128.issue182@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

It's already, is it not? What page are you looking at?

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

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

From metatracker at psf.upfronthosting.co.za  Sat Feb 23 22:17:59 2008
From: metatracker at psf.upfronthosting.co.za (Guido van Rossum)
Date: Sat, 23 Feb 2008 21:17:59 -0000
Subject: [Tracker-discuss] [issue182] Format timestamps nicer
In-Reply-To: <1203800942.69.0.329834113128.issue182@psf.upfronthosting.co.za>
Message-ID: <ca471dc20802231317u6862cd2eue5c9f040961dfbfb@mail.gmail.com>


Guido van Rossum added the comment:

In http://bugs.python.org/issue1519 I see:

Created on 2007-11-29 06:20 by nvawda, last changed 2008-02-23.13:07:51 by
akuchling.

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue182>
_______________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20080223/a06717c8/attachment.htm 

From martin at v.loewis.de  Sat Feb 23 22:19:52 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Sat, 23 Feb 2008 22:19:52 +0100
Subject: [Tracker-discuss] SPAMBAYES_URI (Was: Call for volunteers to
 help maintain bugs.python.org's issue tracker)
In-Reply-To: <18368.35193.173565.749954@montanaro-dyndns-org.local>
References: <bbaeab100802181452g4b9c43e1sc1ace073da8488a@mail.gmail.com>
	<fdc138080802210954v188d693fycfb5d93391dc71e2@mail.gmail.com>
	<bbaeab100802211246o7f75fdd6xbddac2257a2b5790@mail.gmail.com>
	<2c51ecee0802211300o70222ae4i103946f7faa3f980@mail.gmail.com>
	<5fa6c12e0802220257v7d4516a5j4cdec9bc5acfd5b4@mail.gmail.com>
	<47BF08D1.9090804@v.loewis.de>
	<18367.4888.56540.616271@montanaro-dyndns-org.local>
	<47BF186A.30204@v.loewis.de>
	<18368.35193.173565.749954@montanaro-dyndns-org.local>
Message-ID: <47C08DF8.8020009@v.loewis.de>

> Thanks.  I checked out the code and began poking around.  I see six
> instances.  It looks like the python-dev-spambayes-integration and
> spambayes_integration instances haven't been updated since last July.  I
> will assume those are inactive.

spambayes_integration is not a tracker instance, but it needs to be
checked out together with python-dev (or else the symlink in 
detectors/spambayes.py) doesn't resolve.

I have no clue what python-dev-spambayes-integration is.

> The SpamBayes setup is supposed to connect to a running SpamBayes server.
> In python-dev/detectors/config.ini.template it's listed as
> 
>     http://www.webfast.com:80/sbrpc
> 
> which I am not running.  I'm not sure what the actual config.ini file says.

http://localhost:8001/sbrpc

> If you can login on the tracker host you should be able to fire up a web
> server and connect to
> 
>     http://localhost:8880/
> 
> then use that interface to train submissions as spam or ham.  I have no idea
> if that's been done since it was first installed.

Is it necessary to do that? There is no web browser installed on that 
machine, so it's fairly difficult to connect to that port.

> Is that enough information to get this activity back on-track?

Perhaps. It may take some time until I can manage to setup the reverse 
proxy. Perhaps Izak can help.

Regards,
Martin


From martin at v.loewis.de  Sat Feb 23 22:21:37 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Sat, 23 Feb 2008 22:21:37 +0100
Subject: [Tracker-discuss] SPAMBAYES_URI (Was: Call for volunteers to
 help maintain bugs.python.org's issue tracker)
In-Reply-To: <18368.35193.173565.749954@montanaro-dyndns-org.local>
References: <bbaeab100802181452g4b9c43e1sc1ace073da8488a@mail.gmail.com>
	<fdc138080802210954v188d693fycfb5d93391dc71e2@mail.gmail.com>
	<bbaeab100802211246o7f75fdd6xbddac2257a2b5790@mail.gmail.com>
	<2c51ecee0802211300o70222ae4i103946f7faa3f980@mail.gmail.com>
	<5fa6c12e0802220257v7d4516a5j4cdec9bc5acfd5b4@mail.gmail.com>
	<47BF08D1.9090804@v.loewis.de>
	<18367.4888.56540.616271@montanaro-dyndns-org.local>
	<47BF186A.30204@v.loewis.de>
	<18368.35193.173565.749954@montanaro-dyndns-org.local>
Message-ID: <47C08E61.8070203@v.loewis.de>

> Is that enough information to get this activity back on-track?

As a further follow-up: the *original* question is how the instructions
in the Wiki need to be changed to support local instances of Roundup,
preferably without the need to have a local spambayes installation as
well.

Regards,
Martin

From skip at pobox.com  Sat Feb 23 22:28:24 2008
From: skip at pobox.com (skip at pobox.com)
Date: Sat, 23 Feb 2008 15:28:24 -0600
Subject: [Tracker-discuss] SPAMBAYES_URI (Was: Call for volunteers to
 help maintain bugs.python.org's issue tracker)
In-Reply-To: <47C08DF8.8020009@v.loewis.de>
References: <bbaeab100802181452g4b9c43e1sc1ace073da8488a@mail.gmail.com>
	<fdc138080802210954v188d693fycfb5d93391dc71e2@mail.gmail.com>
	<bbaeab100802211246o7f75fdd6xbddac2257a2b5790@mail.gmail.com>
	<2c51ecee0802211300o70222ae4i103946f7faa3f980@mail.gmail.com>
	<5fa6c12e0802220257v7d4516a5j4cdec9bc5acfd5b4@mail.gmail.com>
	<47BF08D1.9090804@v.loewis.de>
	<18367.4888.56540.616271@montanaro-dyndns-org.local>
	<47BF186A.30204@v.loewis.de>
	<18368.35193.173565.749954@montanaro-dyndns-org.local>
	<47C08DF8.8020009@v.loewis.de>
Message-ID: <18368.36856.837516.982798@montanaro-dyndns-org.local>


    Martin> http://localhost:8001/sbrpc

    >> If you can login on the tracker host you should be able to fire up a
    >> web server and connect to
    >> 
    >> http://localhost:8880/
    >> 
    >> then use that interface to train submissions as spam or ham.  I have
    >> no idea if that's been done since it was first installed.

    Martin> Is it necessary to do that? There is no web browser installed on
    Martin> that machine, so it's fairly difficult to connect to that port.

Well, yeah, it's kind of important to train the classifier.  If Erik set up
some way to train through the actual tracker interface (via XML-RPC in the
background) that should work for most things as well, though you won't be
able to configure the server's setup.

    >> Is that enough information to get this activity back on-track?

    Martin> Perhaps. It may take some time until I can manage to setup the
    Martin> reverse proxy. Perhaps Izak can help.

Let me know if you need more help.  As I indicated, I'd be happy to handle
training of at least the python-dev instance.

Skip


From metatracker at psf.upfronthosting.co.za  Sat Feb 23 22:30:40 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Sat, 23 Feb 2008 21:30:40 -0000
Subject: [Tracker-discuss] [issue182] Format timestamps nicer
In-Reply-To: <1201120142.54.0.952798238955.issue182@psf.upfronthosting.co.za>
Message-ID: <1203802240.3.0.334218790013.issue182@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

I had only changed the creation date format; now I also changed the "last
changed" (activity) date.

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

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

From skip at pobox.com  Sat Feb 23 22:30:36 2008
From: skip at pobox.com (skip at pobox.com)
Date: Sat, 23 Feb 2008 15:30:36 -0600
Subject: [Tracker-discuss] SPAMBAYES_URI (Was: Call for volunteers to
 help maintain bugs.python.org's issue tracker)
In-Reply-To: <47C08E61.8070203@v.loewis.de>
References: <bbaeab100802181452g4b9c43e1sc1ace073da8488a@mail.gmail.com>
	<fdc138080802210954v188d693fycfb5d93391dc71e2@mail.gmail.com>
	<bbaeab100802211246o7f75fdd6xbddac2257a2b5790@mail.gmail.com>
	<2c51ecee0802211300o70222ae4i103946f7faa3f980@mail.gmail.com>
	<5fa6c12e0802220257v7d4516a5j4cdec9bc5acfd5b4@mail.gmail.com>
	<47BF08D1.9090804@v.loewis.de>
	<18367.4888.56540.616271@montanaro-dyndns-org.local>
	<47BF186A.30204@v.loewis.de>
	<18368.35193.173565.749954@montanaro-dyndns-org.local>
	<47C08E61.8070203@v.loewis.de>
Message-ID: <18368.36988.773844.31104@montanaro-dyndns-org.local>


    >> Is that enough information to get this activity back on-track?

    Martin> As a further follow-up: the *original* question is how the
    Martin> instructions in the Wiki need to be changed to support local
    Martin> instances of Roundup, preferably without the need to have a
    Martin> local spambayes installation as well.

Point me at the instructions.  What wiki?  I'm sorry, but I'm swimming in
wikis and trackers and other websites.

There should be no need to install a local SpamBayes instance.  Connection
should just fail and the issue will be accepted.  If that's not the case,
let me know.

Skip


From martin at v.loewis.de  Sat Feb 23 22:43:00 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Sat, 23 Feb 2008 22:43:00 +0100
Subject: [Tracker-discuss] SPAMBAYES_URI (Was: Call for volunteers to
 help maintain bugs.python.org's issue tracker)
In-Reply-To: <18368.36988.773844.31104@montanaro-dyndns-org.local>
References: <bbaeab100802181452g4b9c43e1sc1ace073da8488a@mail.gmail.com>
	<fdc138080802210954v188d693fycfb5d93391dc71e2@mail.gmail.com>
	<bbaeab100802211246o7f75fdd6xbddac2257a2b5790@mail.gmail.com>
	<2c51ecee0802211300o70222ae4i103946f7faa3f980@mail.gmail.com>
	<5fa6c12e0802220257v7d4516a5j4cdec9bc5acfd5b4@mail.gmail.com>
	<47BF08D1.9090804@v.loewis.de>
	<18367.4888.56540.616271@montanaro-dyndns-org.local>
	<47BF186A.30204@v.loewis.de>
	<18368.35193.173565.749954@montanaro-dyndns-org.local>
	<47C08E61.8070203@v.loewis.de>
	<18368.36988.773844.31104@montanaro-dyndns-org.local>
Message-ID: <47C09364.5000003@v.loewis.de>

> Point me at the instructions.  What wiki?  I'm sorry, but I'm swimming in
> wikis and trackers and other websites.

http://wiki.python.org/moin/TrackerDevelopment

> There should be no need to install a local SpamBayes instance.  Connection
> should just fail and the issue will be accepted.  If that's not the case,
> let me know.

If you comment out spambayes_uri, you get a roundup error saying

Edit Error: Unsupported configuration option: SPAMBAYES_URI

If you set it to an empty string, you get

IOError: unsupported XML-RPC protocol

Regards,
Martin

From skip at pobox.com  Sat Feb 23 23:14:48 2008
From: skip at pobox.com (skip at pobox.com)
Date: Sat, 23 Feb 2008 16:14:48 -0600
Subject: [Tracker-discuss] SPAMBAYES_URI (Was: Call for volunteers to
 help maintain bugs.python.org's issue tracker)
In-Reply-To: <47C09364.5000003@v.loewis.de>
References: <bbaeab100802181452g4b9c43e1sc1ace073da8488a@mail.gmail.com>
	<fdc138080802210954v188d693fycfb5d93391dc71e2@mail.gmail.com>
	<bbaeab100802211246o7f75fdd6xbddac2257a2b5790@mail.gmail.com>
	<2c51ecee0802211300o70222ae4i103946f7faa3f980@mail.gmail.com>
	<5fa6c12e0802220257v7d4516a5j4cdec9bc5acfd5b4@mail.gmail.com>
	<47BF08D1.9090804@v.loewis.de>
	<18367.4888.56540.616271@montanaro-dyndns-org.local>
	<47BF186A.30204@v.loewis.de>
	<18368.35193.173565.749954@montanaro-dyndns-org.local>
	<47C08E61.8070203@v.loewis.de>
	<18368.36988.773844.31104@montanaro-dyndns-org.local>
	<47C09364.5000003@v.loewis.de>
Message-ID: <18368.39640.355809.955501@montanaro-dyndns-org.local>


    Martin> If you comment out spambayes_uri, you get a roundup error saying

    Martin> Edit Error: Unsupported configuration option: SPAMBAYES_URI

    Martin> If you set it to an empty string, you get

    Martin> IOError: unsupported XML-RPC protocol

What if you set it to something valid but nonexistent like

    http://localhost:9999/sbrpc

?  Looking back at the archive of this thread I see no tracebacks.  Where
are the IOError and Edit Error exceptions raised?

Skip

From skip at pobox.com  Sat Feb 23 23:22:59 2008
From: skip at pobox.com (skip at pobox.com)
Date: Sat, 23 Feb 2008 16:22:59 -0600
Subject: [Tracker-discuss] SPAMBAYES_URI (Was: Call for volunteers to
 help maintain bugs.python.org's issue tracker)
In-Reply-To: <47C09364.5000003@v.loewis.de>
References: <bbaeab100802181452g4b9c43e1sc1ace073da8488a@mail.gmail.com>
	<fdc138080802210954v188d693fycfb5d93391dc71e2@mail.gmail.com>
	<bbaeab100802211246o7f75fdd6xbddac2257a2b5790@mail.gmail.com>
	<2c51ecee0802211300o70222ae4i103946f7faa3f980@mail.gmail.com>
	<5fa6c12e0802220257v7d4516a5j4cdec9bc5acfd5b4@mail.gmail.com>
	<47BF08D1.9090804@v.loewis.de>
	<18367.4888.56540.616271@montanaro-dyndns-org.local>
	<47BF186A.30204@v.loewis.de>
	<18368.35193.173565.749954@montanaro-dyndns-org.local>
	<47C08E61.8070203@v.loewis.de>
	<18368.36988.773844.31104@montanaro-dyndns-org.local>
	<47C09364.5000003@v.loewis.de>
Message-ID: <18368.40131.372605.964089@montanaro-dyndns-org.local>


    Martin> If you comment out spambayes_uri, you get a roundup error saying
    Martin> Edit Error: Unsupported configuration option: SPAMBAYES_URI

in instances/spambayes_integration/detectors/spambayes.py you should
probably change the dict access from

    spambayes_uri = db.config.detectors['SPAMBAYES_URI']

to something like

    try:
        spambayes_uri = db.config.detectors['SPAMBAYES_URI']
    except KeyError, e:
        return (False, str(e))

though I'm not sure just what kind of object db.config.detectors is.
Hopefully it raises KeyError, but it might raise something else.

    Martin> If you set it to an empty string, you get
    Martin> IOError: unsupported XML-RPC protocol

If you want the empty string to be a valid value for spambayes_uri, then
change the ServerProxy() call from

    server = xmlrpclib.ServerProxy(spambayes_uri, verbose=False)

to

    try:
        server = xmlrpclib.ServerProxy(spambayes_uri, verbose=False)
    except IOError, e:
        return (False, str(e))

Skip

From skip at pobox.com  Sat Feb 23 23:42:49 2008
From: skip at pobox.com (skip at pobox.com)
Date: Sat, 23 Feb 2008 16:42:49 -0600
Subject: [Tracker-discuss] SPAMBAYES_URI (Was: Call for volunteers to
 help maintain bugs.python.org's issue tracker)
In-Reply-To: <47C09364.5000003@v.loewis.de>
References: <bbaeab100802181452g4b9c43e1sc1ace073da8488a@mail.gmail.com>
	<fdc138080802210954v188d693fycfb5d93391dc71e2@mail.gmail.com>
	<bbaeab100802211246o7f75fdd6xbddac2257a2b5790@mail.gmail.com>
	<2c51ecee0802211300o70222ae4i103946f7faa3f980@mail.gmail.com>
	<5fa6c12e0802220257v7d4516a5j4cdec9bc5acfd5b4@mail.gmail.com>
	<47BF08D1.9090804@v.loewis.de>
	<18367.4888.56540.616271@montanaro-dyndns-org.local>
	<47BF186A.30204@v.loewis.de>
	<18368.35193.173565.749954@montanaro-dyndns-org.local>
	<47C08E61.8070203@v.loewis.de>
	<18368.36988.773844.31104@montanaro-dyndns-org.local>
	<47C09364.5000003@v.loewis.de>
Message-ID: <18368.41321.785700.976702@montanaro-dyndns-org.local>


I updated the SpamBayes-related text in the wiki.  I don't do Windows, so
someone else will have to edit the text to reflect differences on that
platform.

Skip

From martin at v.loewis.de  Sun Feb 24 00:57:27 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Sun, 24 Feb 2008 00:57:27 +0100
Subject: [Tracker-discuss] SPAMBAYES_URI (Was: Call for volunteers to
 help maintain bugs.python.org's issue tracker)
In-Reply-To: <18368.40131.372605.964089@montanaro-dyndns-org.local>
References: <bbaeab100802181452g4b9c43e1sc1ace073da8488a@mail.gmail.com>
	<fdc138080802210954v188d693fycfb5d93391dc71e2@mail.gmail.com>
	<bbaeab100802211246o7f75fdd6xbddac2257a2b5790@mail.gmail.com>
	<2c51ecee0802211300o70222ae4i103946f7faa3f980@mail.gmail.com>
	<5fa6c12e0802220257v7d4516a5j4cdec9bc5acfd5b4@mail.gmail.com>
	<47BF08D1.9090804@v.loewis.de>
	<18367.4888.56540.616271@montanaro-dyndns-org.local>
	<47BF186A.30204@v.loewis.de>
	<18368.35193.173565.749954@montanaro-dyndns-org.local>
	<47C08E61.8070203@v.loewis.de>
	<18368.36988.773844.31104@montanaro-dyndns-org.local>
	<47C09364.5000003@v.loewis.de>
	<18368.40131.372605.964089@montanaro-dyndns-org.local>
Message-ID: <47C0B2E7.2030609@v.loewis.de>

> in instances/spambayes_integration/detectors/spambayes.py you should
> probably change the dict access from
> 
>     spambayes_uri = db.config.detectors['SPAMBAYES_URI']
> 
> to something like
> 
>     try:
>         spambayes_uri = db.config.detectors['SPAMBAYES_URI']
>     except KeyError, e:
>         return (False, str(e))

I'm personally not going to experiment with that. I just accept that
it doesn't work for me; if somebody can come up with definite 
instructions, please put them into the Wiki.

Regards,
Martin



From nielsreijers at gmail.com  Sun Feb 24 23:28:31 2008
From: nielsreijers at gmail.com (Niels Reijers)
Date: Sun, 24 Feb 2008 23:28:31 +0100
Subject: [Tracker-discuss] Call for volunteers to help maintain
	bugs.python.org's issue tracker
Message-ID: <da3becd20802241428q209e30d1u63623e920c9fc547@mail.gmail.com>

Hello,

I'm responding to Brett Cannon's call for volunteers to help maintain
Python's issue tracker. I've been planning to get involved with an open
source project for a while, but just never got around to it, so maybe this
is a good opportunity to get going.
I only started to use Python about two years ago, but it quickly became my
favourite language. Especially the emphasis on simplicity and readability
really matched my own ideas on coding. My day job is at an insurance company
where I'm techlead on a fun project, but unfortunately it's a C#-only shop.
I'd love to get a chance to use Python in something bigger than my pet
projects, and do something that will hopefully be useful to the Python
community at the same time.
The only concern I have is how much time I should be investing? As much as
I'd like to get involved, my work and private schedule are usually very
busy, so I expect to be limitted to about one evening a week, maybe two.
Will this be sufficient to make a useful contribution? If so, what's the
best way to get started?

Regards,
 Niels Reijers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20080224/21736991/attachment.htm 

From brett at python.org  Sun Feb 24 23:48:44 2008
From: brett at python.org (Brett Cannon)
Date: Sun, 24 Feb 2008 14:48:44 -0800
Subject: [Tracker-discuss] Call for volunteers to help maintain
	bugs.python.org's issue tracker
In-Reply-To: <da3becd20802241428q209e30d1u63623e920c9fc547@mail.gmail.com>
References: <da3becd20802241428q209e30d1u63623e920c9fc547@mail.gmail.com>
Message-ID: <bbaeab100802241448v646c5156ydf2df22653454bb2@mail.gmail.com>

On Sun, Feb 24, 2008 at 2:28 PM, Niels Reijers <nielsreijers at gmail.com> wrote:
> Hello,
>
> I'm responding to Brett Cannon's call for volunteers to help maintain
> Python's issue tracker. I've been planning to get involved with an open
> source project for a while, but just never got around to it, so maybe this
> is a good opportunity to get going.
>  I only started to use Python about two years ago, but it quickly became my
> favourite language. Especially the emphasis on simplicity and readability
> really matched my own ideas on coding. My day job is at an insurance company
> where I'm techlead on a fun project, but unfortunately it's a C#-only shop.
> I'd love to get a chance to use Python in something bigger than my pet
> projects, and do something that will hopefully be useful to the Python
> community at the same time.
>  The only concern I have is how much time I should be investing? As much as
> I'd like to get involved, my work and private schedule are usually very
> busy, so I expect to be limitted to about one evening a week, maybe two.
> Will this be sufficient to make a useful contribution? If so, what's the
> best way to get started?

Your time investment is up to you. You do not need to dedicate a set
amount of time every week in order to help.

The best to get started is to read the tracker documentation at
http://wiki.python.org/moin/TrackerDocs/ . Note the link to the
meta-tracker that contains the issues related to the tracker. Also
note the link to the tracker development docs.

-Brett

From metatracker at psf.upfronthosting.co.za  Mon Feb 25 22:54:09 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Mon, 25 Feb 2008 21:54:09 -0000
Subject: [Tracker-discuss] [issue52] Easy way to tell when code is attached
	to an issue
In-Reply-To: <1164146511.14.0.843310476722.issue52@psf.upfronthosting.co.za>
Message-ID: <1203976449.0.0.372923138896.issue52@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

Considering this fixed now.

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

______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue52>
______________________________________________________

From brett at python.org  Tue Feb 26 04:29:54 2008
From: brett at python.org (Brett Cannon)
Date: Mon, 25 Feb 2008 19:29:54 -0800
Subject: [Tracker-discuss] Issues that could use some work (good for the new
	volunteers!)
Message-ID: <bbaeab100802251929o7859574fme870af82d8e4b278@mail.gmail.com>

Knowing that the whole tracker thing can be a little daunting and it
can help to have a specific goal to get going, here are some issues
that Martin thinks could use some attention.

Critical and easy: 16,130, (123/125 : solution exists, but wondering
if there is another one that doesn't involve editing Roundup)
Critical and possibly not easy: 144, 174, 87
Not critical but easy: 180

-Brett

From dmitrikozhevin at gmail.com  Tue Feb 26 11:33:16 2008
From: dmitrikozhevin at gmail.com (Dmitry Kozhevin)
Date: Tue, 26 Feb 2008 12:33:16 +0200
Subject: [Tracker-discuss] Issues that could use some work (good for the
	new volunteers!)
In-Reply-To: <bbaeab100802251929o7859574fme870af82d8e4b278@mail.gmail.com>
References: <bbaeab100802251929o7859574fme870af82d8e4b278@mail.gmail.com>
Message-ID: <765bf0040802260233t568fc40fl18ce20dc78a75336@mail.gmail.com>

Should I assign ticket for myself if I am going to do this task?

On Tue, Feb 26, 2008 at 5:29 AM, Brett Cannon <brett at python.org> wrote:
> Knowing that the whole tracker thing can be a little daunting and it
>  can help to have a specific goal to get going, here are some issues
>  that Martin thinks could use some attention.
>
>  Critical and easy: 16,130, (123/125 : solution exists, but wondering
>  if there is another one that doesn't involve editing Roundup)
>  Critical and possibly not easy: 144, 174, 87
>  Not critical but easy: 180
>
>  -Brett
>  _______________________________________________
>  Tracker-discuss mailing list
>  Tracker-discuss at python.org
>  http://mail.python.org/mailman/listinfo/tracker-discuss
>

From draghuram at gmail.com  Tue Feb 26 16:57:52 2008
From: draghuram at gmail.com (Raghuram Devarakonda)
Date: Tue, 26 Feb 2008 10:57:52 -0500
Subject: [Tracker-discuss] Issues that could use some work (good for the
	new volunteers!)
In-Reply-To: <765bf0040802260233t568fc40fl18ce20dc78a75336@mail.gmail.com>
References: <bbaeab100802251929o7859574fme870af82d8e4b278@mail.gmail.com>
	<765bf0040802260233t568fc40fl18ce20dc78a75336@mail.gmail.com>
Message-ID: <2c51ecee0802260757x19139cf6vdb0760801532ae90@mail.gmail.com>

On Tue, Feb 26, 2008 at 5:33 AM, Dmitry Kozhevin
<dmitrikozhevin at gmail.com> wrote:
> Should I assign ticket for myself if I am going to do this task?

It is generally enough to add a comment saying that you are going to
work on it. Of course, assigning is not a bad idea but you will need
tracker permissions for that.

Thanks,
Raghu

From martin at v.loewis.de  Tue Feb 26 21:18:28 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Tue, 26 Feb 2008 21:18:28 +0100
Subject: [Tracker-discuss] Issues that could use some work (good for the
 new volunteers!)
In-Reply-To: <765bf0040802260233t568fc40fl18ce20dc78a75336@mail.gmail.com>
References: <bbaeab100802251929o7859574fme870af82d8e4b278@mail.gmail.com>
	<765bf0040802260233t568fc40fl18ce20dc78a75336@mail.gmail.com>
Message-ID: <47C47414.20802@v.loewis.de>

> Should I assign ticket for myself if I am going to do this task?

As Raghu says: posting a note should be enough. In any case, I
just gave you the coordinator role, in case you want to assign
things to yourself (although the meta tracker probably allowed
assignments by any user to any user).

Regards,
Martin

From metatracker at psf.upfronthosting.co.za  Thu Feb 28 12:45:14 2008
From: metatracker at psf.upfronthosting.co.za (Alan Kennedy)
Date: Thu, 28 Feb 2008 11:45:14 -0000
Subject: [Tracker-discuss] [issue193] new jython versions for closing bugs.
In-Reply-To: <1204199114.52.0.598335593309.issue193@psf.upfronthosting.co.za>
Message-ID: <1204199114.52.0.598335593309.issue193@psf.upfronthosting.co.za>


New submission from Alan Kennedy:

Need new "versions" on the jython tracker; I want to close a bug that I have
fixed on trunk and on the release_2_2_maint branch. The 2.2 fix will be released
with version 2.2.2 (assuming that there will be a 2.2.2) and the trunk fix will
be released with whatever major version is next released from trunk (2.5?) If
the versions are properly recorded, then the fixing of the bugs should/will be
noted for the release notes for that version.

----------
assignedto: draghuram
messages: 995
nosy: amak, draghuram
priority: bug
status: unread
title: new jython versions for closing bugs.
topic: jython

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 28 15:54:54 2008
From: metatracker at psf.upfronthosting.co.za (Raghuram Devarakonda)
Date: Thu, 28 Feb 2008 14:54:54 -0000
Subject: [Tracker-discuss] [issue193] new jython versions for closing bugs.
In-Reply-To: <1204199114.52.0.598335593309.issue193@psf.upfronthosting.co.za>
Message-ID: <1204210494.81.0.817728354527.issue193@psf.upfronthosting.co.za>


Raghuram Devarakonda added the comment:

Martin, Can you please add two new versions in jython tracker? The new versions
are "2.2.2" and "2.5".

----------
assignedto: draghuram -> loewis
nosy: +loewis
priority: bug -> feature
status: unread -> chatting

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 28 17:59:36 2008
From: metatracker at psf.upfronthosting.co.za (Raghuram Devarakonda)
Date: Thu, 28 Feb 2008 16:59:36 -0000
Subject: [Tracker-discuss] [issue193] new jython versions for closing bugs.
In-Reply-To: <1204199114.52.0.598335593309.issue193@psf.upfronthosting.co.za>
Message-ID: <1204217976.49.0.935953969314.issue193@psf.upfronthosting.co.za>


Raghuram Devarakonda added the comment:

In addition to the above two versions, can you please add "2.5alpha1" as well?
In addition, the words "targeted for" and "fixed in" can be removed from
existing versions but please treat it as a low priority request.

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 28 18:49:04 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 28 Feb 2008 17:49:04 -0000
Subject: [Tracker-discuss] [issue193] new jython versions for closing bugs.
In-Reply-To: <1204199114.52.0.598335593309.issue193@psf.upfronthosting.co.za>
Message-ID: <1204220944.78.0.133626478414.issue193@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

Raghu, I just made you Coordinator; please feel free to edit the versions as you
like, see

http://bugs.jython.org/version

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 28 18:56:39 2008
From: metatracker at psf.upfronthosting.co.za (Raghuram Devarakonda)
Date: Thu, 28 Feb 2008 17:56:39 -0000
Subject: [Tracker-discuss] [issue193] new jython versions for closing bugs.
In-Reply-To: <1204220944.78.0.133626478414.issue193@psf.upfronthosting.co.za>
Message-ID: <2c51ecee0802280956k11d36a3bsdffe1747ced63e3@mail.gmail.com>


Raghuram Devarakonda added the comment:

On Thu, Feb 28, 2008 at 12:49 PM, Martin v. L?wis
<metatracker at psf.upfronthosting.co.za> wrote:

>  http://bugs.jython.org/version

Thanks. I will add the new versions. BTW, does removing the words
"targeted for" and "fixed in" from here affect existing issues? I am
guessing not but want to be sure.

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 28 19:13:38 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 28 Feb 2008 18:13:38 -0000
Subject: [Tracker-discuss] [issue193] new jython versions for closing bugs.
In-Reply-To: <1204199114.52.0.598335593309.issue193@psf.upfronthosting.co.za>
Message-ID: <1204222418.14.0.584183631449.issue193@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

No, editing anything but the ID is fine.

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 28 19:25:15 2008
From: metatracker at psf.upfronthosting.co.za (Raghuram Devarakonda)
Date: Thu, 28 Feb 2008 18:25:15 -0000
Subject: [Tracker-discuss] [issue193] new jython versions for closing bugs.
In-Reply-To: <1204199114.52.0.598335593309.issue193@psf.upfronthosting.co.za>
Message-ID: <1204223115.82.0.630320244735.issue193@psf.upfronthosting.co.za>


Raghuram Devarakonda added the comment:

Two new versions "2.2.2" and "2.5alpha1" are added. In addition, the words
"targeted for" and "fixed in" have been removed from existing version names.

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

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 28 19:39:32 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 28 Feb 2008 18:39:32 -0000
Subject: [Tracker-discuss] [issue193] new jython versions for closing bugs.
In-Reply-To: <1204199114.52.0.598335593309.issue193@psf.upfronthosting.co.za>
Message-ID: <1204223972.51.0.463178521937.issue193@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

Can this issue be considered "resolved" now?

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

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 28 19:40:48 2008
From: metatracker at psf.upfronthosting.co.za (Raghuram Devarakonda)
Date: Thu, 28 Feb 2008 18:40:48 -0000
Subject: [Tracker-discuss] [issue193] new jython versions for closing bugs.
In-Reply-To: <1204199114.52.0.598335593309.issue193@psf.upfronthosting.co.za>
Message-ID: <1204224048.17.0.626788540136.issue193@psf.upfronthosting.co.za>


Raghuram Devarakonda added the comment:

I think so. I did change the status to "resolved" with my previous comment.

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

From stephen at xemacs.org  Thu Feb 28 21:15:02 2008
From: stephen at xemacs.org (Stephen J. Turnbull)
Date: Fri, 29 Feb 2008 05:15:02 +0900
Subject: [Tracker-discuss] [issue193] new jython versions for closing bugs.
In-Reply-To: <2c51ecee0802280956k11d36a3bsdffe1747ced63e3@mail.gmail.com>
References: <1204220944.78.0.133626478414.issue193@psf.upfronthosting.co.za>
	<2c51ecee0802280956k11d36a3bsdffe1747ced63e3@mail.gmail.com>
Message-ID: <87mypkltx5.fsf@uwakimon.sk.tsukuba.ac.jp>

Raghuram Devarakonda writes:
 > 
 > Raghuram Devarakonda added the comment:
 > 
 > On Thu, Feb 28, 2008 at 12:49 PM, Martin v. L?wis
 > <metatracker at psf.upfronthosting.co.za> wrote:
 > 
 > >  http://bugs.jython.org/version
 > 
 > Thanks. I will add the new versions. BTW, does removing the words
 > "targeted for" and "fixed in" from here affect existing issues? I am
 > guessing not but want to be sure.

Yes, it does.  Issues refers to property values as objects, not by
their names.  If you change the name of a value, then all future pages
displays will reflect the name change.

From metatracker at psf.upfronthosting.co.za  Thu Feb 28 21:07:29 2008
From: metatracker at psf.upfronthosting.co.za (Stephen Turnbull)
Date: Thu, 28 Feb 2008 20:07:29 -0000
Subject: [Tracker-discuss] [issue193] new jython versions for closing bugs.
In-Reply-To: <2c51ecee0802280956k11d36a3bsdffe1747ced63e3@mail.gmail.com>
Message-ID: <87mypkltx5.fsf@uwakimon.sk.tsukuba.ac.jp>


Stephen Turnbull added the comment:

Raghuram Devarakonda writes:
 > 
 > Raghuram Devarakonda added the comment:
 > 
 > On Thu, Feb 28, 2008 at 12:49 PM, Martin v. L?wis
 > <metatracker at psf.upfronthosting.co.za> wrote:
 > 
 > >  http://bugs.jython.org/version
 > 
 > Thanks. I will add the new versions. BTW, does removing the words
 > "targeted for" and "fixed in" from here affect existing issues? I am
 > guessing not but want to be sure.

Yes, it does.  Issues refers to property values as objects, not by
their names.  If you change the name of a value, then all future pages
displays will reflect the name change.

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

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 28 23:21:18 2008
From: metatracker at psf.upfronthosting.co.za (Philipp Gortan)
Date: Thu, 28 Feb 2008 22:21:18 -0000
Subject: [Tracker-discuss] [issue148] 'Make a Copy' failed
In-Reply-To: <1188873360.02.0.256456370115.issue148@psf.upfronthosting.co.za>
Message-ID: <1204237278.11.0.456022490349.issue148@psf.upfronthosting.co.za>


Philipp Gortan added the comment:

This bug is caused by the nosy list being concatenated using comma-space instead
of just commas, when creating the target url for the "make a copy" link. To
reproduce, the first url works, whereas the second fails:
http://bugs.python.org/issue?@template=item&nosy=akuchling,gvanrossum
http://bugs.python.org/issue?@template=item&nosy=akuchling,+gvanrossum

----------
assignedto:  -> mephinet
status: unread -> chatting

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

From metatracker at psf.upfronthosting.co.za  Fri Feb 29 13:53:57 2008
From: metatracker at psf.upfronthosting.co.za (Philipp Gortan)
Date: Fri, 29 Feb 2008 12:53:57 -0000
Subject: [Tracker-discuss] [issue148] 'Make a Copy' failed
In-Reply-To: <1188873360.02.0.256456370115.issue148@psf.upfronthosting.co.za>
Message-ID: <1204289637.73.0.911837860846.issue148@psf.upfronthosting.co.za>


Philipp Gortan added the comment:

Detailed analysis: when the link is created, `copy_url` uses property.plain ()
to get the value. In the case of MultilinkHTMLProperty, this is: 
', '.join(labels)
(note the space).
When the link comes back as a GET request, it is parsed by `handleListCGIValue`
and then passed on to `lookupIds`.
`handleListCGIValue` just splits the input string by commas, so the additional
space survives and becomes part of the following username - and because of that,
`lookupIds` fails.

----------
status: chatting -> in-progress

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