[Tracker-discuss] Tracker for web-related issues

[Stefan Seefeld]

Brett Cannon wrote:

> What does everyone else think?  I know it has been said it is easy to
> add another instance, but I want Erik, Stephan, and Paul to agree to
> this as they would be the first people called upon to put out any
> fires.

Here are a couple of points:

* I guess it would be nice if any new python tracker would use templates
  similar to the ones presently in use by the python-dev tracker, and not
  the vanilla templates that ship with roundup.

* It seems the real complexities are in the workflow, which is mostly
  defined by the set of status enumerators, together with the detectors
  that enforce constraints on possible state changes.
  I believe it to be easier to start with a clone of the python-dev
  tracker and removing unwanted stuff, instead of starting over with
  a new vanilla tracker and trying to make it look like a python tracker.

* Most issues that require continuous attention from admins will probably
  be security and spam related, things that shouldn't vary much between
  tracker instances (thus another argument to keep trackers close to each
  other).

>> I'd be in favour of getting these steps done for the pydotorg
>> tracker, to see how it works out.
> 
> Yeah, pydotorg can be the guinea pig.  =)  Assuming the core admins
> agree to this we will end up needing someone to step up for pydotorg
> to play admin.

What is the timeframe for this ? Can this wait until the current migration
is over ? (In fact, what's the status of the migration now ? Are we only
waiting for sf.net to once again fix their data export ? Or is some further
work on the tracker needed ?)

Oh, and yes, I'd like to offer roundup itself a tracker, too, if that's ok
with the server admins. (Though this is just a minor point on my personal
wish list :-) )


Thanks,
		Stefan

-- 

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