[Tracker-discuss] Tracker hacking workflow

["Martin v. Löwis"]

> Right now, I'm working just like I work on Python issues: small
> patches (that may be incompatible with each other) sent to the (meta)
> tracker. Maybe using a public DVCS repository (e.g. at Bitbucket)
> would make sharing our modifications (before SVN commits) easier. What
> do you think?

I'm not able to use DVCS software. Feel free to set something up, but
please continue to submit patches. The way your progress looks like,
I'm willing to grant svn write access shortly (assuming you want it).

> I'm planning to create a public python-dev instance for testing: that
> way, we could get useful feedback from people that don't have a local
> instance running (or are too busy to patch and test). Maybe a buildbot
> could be set just for restarting the server after commits. Would that
> be interesting? Martin, would you prefer another setup?

I think you are overestimating the amount of volunteers that you can
attract (although I would be happy to be proven wrong). For the moment,
I'm just assuming that is just us two.

Regards,
Martin