From seefeld at sympatico.ca  Tue Feb 20 01:20:38 2007
From: seefeld at sympatico.ca (Stefan Seefeld)
Date: Mon, 19 Feb 2007 19:20:38 -0500
Subject: [Tracker-discuss] status ?
Message-ID: <45DA3ED6.7070905@sympatico.ca>

An error notification I just received through roundup-admin at psf.upfronthosting.co.za
reminded me that there haven't been any updates in recent weeks.
What is the status of this project ? Is the migration blocked on anything in particular ?
What does it take to unblock ?

Thanks,
		Stefan

--

      ...ich hab' noch einen Koffer in Berlin...

From brett at python.org  Tue Feb 20 02:10:54 2007
From: brett at python.org (Brett Cannon)
Date: Mon, 19 Feb 2007 17:10:54 -0800
Subject: [Tracker-discuss] status ?
In-Reply-To: <45DA3ED6.7070905@sympatico.ca>
References: <45DA3ED6.7070905@sympatico.ca>
Message-ID: <bbaeab100702191710g4cb381ady933088e828554944@mail.gmail.com>

On 2/19/07, Stefan Seefeld <seefeld at sympatico.ca> wrote:
> An error notification I just received through roundup-admin at psf.upfronthosting.co.za
> reminded me that there haven't been any updates in recent weeks.
> What is the status of this project ? Is the migration blocked on anything in particular ?
> What does it take to unblock ?
>

We need docs on how to use the thing.

I am going to give an update at PyCon at the PSF general meeting
stating that the work is basically done but we need to write the
documentation so people know how to file a bug or patch (are we even
supporting feature requests?  If we are we can keep them for posterity
but I honestly think they are useless).  We need the docs for
python-dev to initially learn what the workflow is expected to be and
for anybody who is wants to submit something and has never used
Roundup.

Once we have those docs we can get clearance from python-dev to do the
transition so we don't do it just before or after a release.  I was
hoping to start working on them in the Python wiki post-PyCon.

-Brett

From pfdubois at gmail.com  Tue Feb 20 18:20:14 2007
From: pfdubois at gmail.com (Paul Dubois)
Date: Tue, 20 Feb 2007 09:20:14 -0800
Subject: [Tracker-discuss] status ?
In-Reply-To: <45DA3ED6.7070905@sympatico.ca>
References: <45DA3ED6.7070905@sympatico.ca>
Message-ID: <f74a6c2f0702200920w1ad7543fi51447e25e2c0993b@mail.gmail.com>

The decision was to have keyword(s) denoting that an issue has a patch
attached; I think I remember that another keyword could be added to denote
that the patch had been verified, but I'm not certain -- I was not a direct
party to the discussion and something may have happened via another channel
that I did not see. Anyway, it is important according to Martin that the
import from sf preserve information about patches. AFAIK we are awaiting the
choice of the keyword(s), and modification of the importer. We should be
ready to go other than that.

I have not seen people need much education, outside of the existing Roundup
user guide, as to how to use Roundup. While having a document for python-dev
is nice it probably only needs to be a short explanation of the fields that
have choices.

On 2/19/07, Stefan Seefeld <seefeld at sympatico.ca> wrote:
>
> An error notification I just received through
> roundup-admin at psf.upfronthosting.co.za
> reminded me that there haven't been any updates in recent weeks.
> What is the status of this project ? Is the migration blocked on anything
> in particular ?
> What does it take to unblock ?
>
> Thanks,
>                 Stefan
>
> --
>
>       ...ich hab' noch einen Koffer in Berlin...
> _______________________________________________
> 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/20070220/c55d3180/attachment.htm 

From martin at v.loewis.de  Tue Feb 20 19:12:18 2007
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Tue, 20 Feb 2007 19:12:18 +0100
Subject: [Tracker-discuss] status ?
In-Reply-To: <f74a6c2f0702200920w1ad7543fi51447e25e2c0993b@mail.gmail.com>
References: <45DA3ED6.7070905@sympatico.ca>
	<f74a6c2f0702200920w1ad7543fi51447e25e2c0993b@mail.gmail.com>
Message-ID: <45DB3A02.8030200@v.loewis.de>

Paul Dubois schrieb:
> The decision was to have keyword(s) denoting that an issue has a patch 
> attached;

This is indeed pending, yet.

> I think I remember that another keyword could be added to 
> denote that the patch had been verified, but I'm not certain

I don't think we agreed here. If I find that the attachment is indeed
not a proper patch, I would just remove the patch keyword. If it is
merely incorrect, this could be put in a comment first, and then wait
and see what happens.

> I have not seen people need much education, outside of the existing 
> Roundup user guide, as to how to use Roundup. While having a document 
> for python-dev is nice it probably only needs to be a short explanation 
> of the fields that have choices.

For python-dev people, yes. All the Python users need to be directed
to the rounup installation, rather than SF, in particular as there is
no way to turn off the SF tracker.

Regards,
Martin


From brett at python.org  Tue Feb 20 21:11:30 2007
From: brett at python.org (Brett Cannon)
Date: Tue, 20 Feb 2007 12:11:30 -0800
Subject: [Tracker-discuss] status ?
In-Reply-To: <f74a6c2f0702200920w1ad7543fi51447e25e2c0993b@mail.gmail.com>
References: <45DA3ED6.7070905@sympatico.ca>
	<f74a6c2f0702200920w1ad7543fi51447e25e2c0993b@mail.gmail.com>
Message-ID: <bbaeab100702201211x76ef4ba8k19115e9e89470398@mail.gmail.com>

On 2/20/07, Paul Dubois <pfdubois at gmail.com> wrote:
> The decision was to have keyword(s) denoting that an issue has a patch
> attached; I think I remember that another keyword could be added to denote
> that the patch had been verified, but I'm not certain -- I was not a direct
> party to the discussion and something may have happened via another channel
> that I did not see. Anyway, it is important according to Martin that the
> import from sf preserve information about patches. AFAIK we are awaiting the
> choice of the keyword(s), and modification of the importer. We should be
> ready to go other than that.
>
> I have not seen people need much education, outside of the existing Roundup
> user guide, as to how to use Roundup.

It's not so much using Roundup itself as what we want fields to be set to.

> While having a document for python-dev
> is nice it probably only needs to be a short explanation of the fields that
> have choices.
>

Yep.  I am not thinking of some epic document.  Just something that
says "In the keywords field, set 'patch' if the issue has a patch",
etc.  Simple, straightforward, and makes it obvious what the basic
workflow is.

-Brett

> On 2/19/07, Stefan Seefeld <seefeld at sympatico.ca> wrote:
> > An error notification I just received through
> roundup-admin at psf.upfronthosting.co.za
> > reminded me that there haven't been any updates in recent weeks.
> > What is the status of this project ? Is the migration blocked on anything
> in particular ?
> > What does it take to unblock ?
> >
> > Thanks,
> >                 Stefan
> >
> > --
> >
> >       ...ich hab' noch einen Koffer in Berlin...
> > _______________________________________________
> > Tracker-discuss mailing list
> > Tracker-discuss at python.org
> > http://mail.python.org/mailman/listinfo/tracker-discuss
> >
>
>
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>
>

From forsberg at efod.se  Wed Feb 21 22:46:12 2007
From: forsberg at efod.se (Erik Forsberg)
Date: Wed, 21 Feb 2007 22:46:12 +0100
Subject: [Tracker-discuss] status ?
In-Reply-To: <f74a6c2f0702200920w1ad7543fi51447e25e2c0993b@mail.gmail.com>
	(Paul Dubois's message of "Tue, 20 Feb 2007 09:20:14 -0800")
References: <45DA3ED6.7070905@sympatico.ca>
	<f74a6c2f0702200920w1ad7543fi51447e25e2c0993b@mail.gmail.com>
Message-ID: <87k5yb89qz.fsf@uterus.efod.se>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Paul Dubois" <pfdubois at gmail.com> writes:

> Anyway, it is important according to Martin that the
> import from sf preserve information about patches. AFAIK we are awaiting the
> choice of the keyword(s), and modification of the importer. We should be
> ready to go other than that.

The importer has now been modified to set the 'patch' keyword on all
issues that had the 'Patches' artifact_type on sf. New import based on
xml backup downloaded this evening is currently underway.

Regards,
\EF
- -- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFF3L2jrJurFAusidkRAliMAKCfqwTErsO5LIT9blIj2PnyiY0ZLgCghX7m
F9CcYFRb7sT/8+KIdZSKrLU=
=m+vg
-----END PGP SIGNATURE-----

From metatracker at psf.upfronthosting.co.za  Sun Feb 25 21:40:33 2007
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Sun, 25 Feb 2007 20:40:33 -0000
Subject: [Tracker-discuss] [issue85] prevent comment duplication
Message-ID: <1172436033.61.0.00273271628417.issue85@psf.upfronthosting.co.za>


New submission from Georg Brandl:

I don't know how complicated that would be, but can it be implemented that if a
comment is submitted that exactly is the same as the previous comment, it is not
added to the bug? (other changes to metadata could be made though)

I've seen this frequently with the SF.net tracker, obviously because of some
user-side reload/back-forward issues.

----------
messages: 412
nosy: gbrandl
priority: feature
status: unread
title: prevent comment duplication

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

From brett at python.org  Sun Feb 25 22:22:58 2007
From: brett at python.org (Brett Cannon)
Date: Sun, 25 Feb 2007 15:22:58 -0600
Subject: [Tracker-discuss] status of switch to Roundup off of SF
Message-ID: <bbaeab100702251322u77c01351wb7695229f5a970f0@mail.gmail.com>

When I gave the PSF members an update on the work to move the
python-dev tracker over to Roundup Andrew Kuchling asked me to also
send an email to python-dev since October/November.

As of right now the biggest thing holding up the transition is
documentation.  A doc needs to get written explaining basic workflow
of how issues should be handled.  Also need to go through and remove
SF references and make them more general (e.g., mention an "issue
tracker" when possible).

After that some redirects need to be tweaked.  www.python.org/sf/
needs to redirect to the Roundup installation (which is keeping SF bug
numbers).  bugs.python.org will also be set to point to the Roundup
server.

After all of that we will find out from Anthony and Neal when a
release is going to be so as to do the switch when it won't run into a
release (before or after).

The current test tracker is at
http://psf.upfronthosting.co.za/roundup/tracker/ .  The meta tracker
for dealing with this stuff is at
http://psf.upfronthosting.co.za/roundup/meta/ .  Feel free to have a
look, but please don't go overboard with the suggestions on changes.
It is not difficult to change the tracker after it launches.  The last
thing any of us want to see is the tracker launch delayed because
someone wants a feature that takes a while to implement.  Unless there
is a critical issue you find it would be appreciated if you file the
suggestion and just let us push after the launch if it is deemed it
will take too much time to implement.

The mailing list where all discussions take place is
http://mail.python.org/mailman/listinfo/tracker-discuss .  Fairly
low-traffic although all updates to the meta tracker get sent there.

Obviously if you have questions feel free to ask.  And if you want to
help with getting the switch to happen just speak up.  =)

-Brett

From Doug.Napoleone at nuance.com  Wed Feb 28 01:19:18 2007
From: Doug.Napoleone at nuance.com (Napoleone, Doug)
Date: Tue, 27 Feb 2007 19:19:18 -0500
Subject: [Tracker-discuss] Vanilla Roundup instance for PyCon issues
Message-ID: <37E3DF6920CC664D924AFA9966C33EE86D01D8@bn-exchdmz>

Hello,
    We really need a bug tracking system for the PyCon and python.org sites.
The old trac for python.org was taken down due to spamers. We don't need
anything special, we don't need it connected to the pythod-dev stuff, a
generic instance should do the job.

How hard would this be to set up? Who do I talk to about getting this done?

The svn for the pycon apps is currently:
https://svn.python.org/conference/django/trunk/

Thanks in advance!

    -Doug Napoleone

From roche at upfrontsystems.co.za  Wed Feb 28 08:25:16 2007
From: roche at upfrontsystems.co.za (=?ISO-8859-1?Q?Roch=E9?= Compaan)
Date: Wed, 28 Feb 2007 09:25:16 +0200
Subject: [Tracker-discuss] Vanilla Roundup instance for PyCon issues
In-Reply-To: <37E3DF6920CC664D924AFA9966C33EE86D01D8@bn-exchdmz>
References: <37E3DF6920CC664D924AFA9966C33EE86D01D8@bn-exchdmz>
Message-ID: <1172647516.26201.4.camel@localhost.localdomain>

On Tue, 2007-02-27 at 19:19 -0500, Napoleone, Doug wrote:
> Hello,
>     We really need a bug tracking system for the PyCon and python.org sites.
> The old trac for python.org was taken down due to spamers. We don't need
> anything special, we don't need it connected to the pythod-dev stuff, a
> generic instance should do the job.
> 
> How hard would this be to set up? Who do I talk to about getting this done?
> 
> The svn for the pycon apps is currently:
> https://svn.python.org/conference/django/trunk/
> 
> Thanks in advance!

We're happy to set up another tracker instance on the Roundup server
that will eventually host the PSF tracker. Do you have a URL that you
can point to the tracker or would
http://roundup.upfronthosting.co.za/roundup/pycon be ok?

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


From forsberg at efod.se  Wed Feb 28 09:31:12 2007
From: forsberg at efod.se (Erik Forsberg)
Date: Wed, 28 Feb 2007 09:31:12 +0100
Subject: [Tracker-discuss] Vanilla Roundup instance for PyCon issues
In-Reply-To: <1172647516.26201.4.camel@localhost.localdomain>
References: <37E3DF6920CC664D924AFA9966C33EE86D01D8@bn-exchdmz>
	<1172647516.26201.4.camel@localhost.localdomain>
Message-ID: <200702280931.12721.forsberg@efod.se>

onsdag 28 februari 2007 08:25 skrev Roch? Compaan:
> We're happy to set up another tracker instance on the Roundup server
> that will eventually host the PSF tracker. Do you have a URL that you
> can point to the tracker or would
> http://roundup.upfronthosting.co.za/roundup/pycon be ok?

Just for clarity - will Upfront take responsibility for the maintenance of 
this tracker? 

I remember that we discussed adding more trackers, and if I remember 
correctly, we agreed that we wanted to know who is responsible for each 
tracker.

Regards,
\EF
-- 
http://efod.se/

From roche at upfrontsystems.co.za  Wed Feb 28 10:26:21 2007
From: roche at upfrontsystems.co.za (=?ISO-8859-1?Q?Roch=E9?= Compaan)
Date: Wed, 28 Feb 2007 11:26:21 +0200
Subject: [Tracker-discuss] Vanilla Roundup instance for PyCon issues
In-Reply-To: <200702280931.12721.forsberg@efod.se>
References: <37E3DF6920CC664D924AFA9966C33EE86D01D8@bn-exchdmz>
	<1172647516.26201.4.camel@localhost.localdomain>
	<200702280931.12721.forsberg@efod.se>
Message-ID: <1172654781.26201.40.camel@localhost.localdomain>

On Wed, 2007-02-28 at 09:31 +0100, Erik Forsberg wrote:
> onsdag 28 februari 2007 08:25 skrev Roch? Compaan:
> > We're happy to set up another tracker instance on the Roundup server
> > that will eventually host the PSF tracker. Do you have a URL that you
> > can point to the tracker or would
> > http://roundup.upfronthosting.co.za/roundup/pycon be ok?
> 
> Just for clarity - will Upfront take responsibility for the maintenance of 
> this tracker? 

We will, if none of the current administrators want to. It is a vanilla
instance so I don't foresee that it will require to much work or
maintenance.

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