[Tracker-discuss] Feature/Change request handling procedure

Brett Cannon brett at python.org
Tue Nov 21 20:54:01 CET 2006

On 11/21/06, "Martin v. Löwis" <martin at v.loewis.de> wrote:
> Stefan Seefeld schrieb:
> > * What time scale should we expect this whole migration to take to
> >   move forward ? Would it make sense to set up a time frame to not
> >   let this drag on for too long ?
> I think so. Some people (GvR in particular) have been asking why
> this isn't completed, yet.
> It would be good if it completed this year.

Ditto from me.  This might be a situation where people just want it done and
don't care about the final solution since it is better than what we have

> * I have made various fine-grained change proposals on the meta
> >   tracker. Would it be more efficient I made an overall proposal
> >   that allows to think in terms of the 'big picture', instead of
> >   piece meal changes ?
> I think people won't respond at all to tracker schema changes,
> no matter how much feedback you request. Instead, they want to
> see the complete solution, life.

I bet if you make the initial changes to what you think is reasonable based
on any suggestions people make, we can then say, "here is the rough draft of
the tracker; make comments now before we push out the first version
publicly".  That should light some fires under people.  Plus it gives
everyone something concrete to play with.

In other words, take the current ideas, implement them in a schema, push it
to the test tracker, and we can play with it a little and give feedback.
With that done, we then make the tweaks and do the switch.  After that we
can make gradual changes.  I am sure people will come to realize that
certain things are needed as time goes on and people have more experience
with the tracker.

> * What exactly do we need in order to consider a change to be
> >   approved ?
> The tracker team can do whatever they want, IMO. The infrastructure
> committee should back them up and support them as long as we had a
> chance to comment.

Same from me.  Basically you guys present to us what you got, we comment,
and then was fix and go.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20061121/e2ebb88c/attachment.html 

More information about the Tracker-discuss mailing list