[Tracker-discuss] Tracker hacking workflow

[Daniel (ajax) Diniz]

Hi,
I'd like to chat about the tracker hacking effort a little, so we can
work together more efficiently. Knowing how/what people want to
contribute allows us to think about what can be done to make it
easier. I'll throw a few ideas to get things started, but feel free to
discuss anything else :)

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?

The same 'public repository' approach can be useful for discussing
goals, using the Python wiki or something similar. When fleshed out
enough, goals/task should become tickets in the meta tracker, IMO.
Does this work for everybody?

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?

Cheers,
Daniel