TITLE OF PAPER:
The Roundup Issue Tracker
URL OF PRESENTATION:
http://www.python.org/pycon/2005/papers/12/
PRESENTED BY:
Richard Jones
REPRESENTING: _name_of_the_company_they_represent_
CONFERENCE: PyCon 2005
DATE:
03/24/2005
LOCATION:
Grand
--------------------------------------------------------------------------
REAL-TIME NOTES / ANNOTATIONS OF THE PAPER:
{If you've contributed, add your name, e-mail & URL at the bottom}
[ all slides (looks like they're kinda sparse) available at url above ]
Highlights:
Pure Python, no external dependencies
Clean, simple interface
Mini mailing lists around issues
Can run by downloading, unpacking, "python demo.py"
Projects / Milestones, pretty graphs thereof
Speaker uses roundup to manage paper submissions for a conference they run
Can make a wiki out of it
Handles attachments well, with or without content-type
Uses subject line magic to associate email with tracked items
Nosy list: will add CCs for you (JB: not sure I get how that worked)
Automatic behaviors:
Auditors -- happen before things change in the DB
ex verify PGP key of email submitter
Reactors -- happen after things change
ex close issues, email people re issue change
Surprisingly well documented!
Just finished a 0.8 release
QUESTIONS AND ANSWERS
Q: If roundup emails you, and you reply, does that get tracked?
A: Roundup sets reply-to and other headers so the default behavior is yes
Q: What databases?
A: Scales up to 100k issues pretty well
Real issue is number of users
pgsql & mysql can handle as many connections as they can handle (DB the issue, not roundup)
Speaker has had about 10 concurrent users
Q: what do you use as backendybits?
A: postgresql
Q: spam going into mail gateway - is it a problem?
A: disallow anonymous email. also, could fire off spambayes and train it too.
Q: integrate with scm systems?
A: yeah, but he's never done it.
It's easy on the same machine, it can be done with email on different machines
Audience dude: there is another tracker called trac with svn integration (edgewall trac)
Speaker hasn't had a need for it and doesn't think it's "cool", so he's never done it
--------------------------------------------------------------------------
REFERENCES: {as documents / sites are referenced add them below}
http://www.mechanicalcat.net/richard/log
http://roundup.sourceforge.net/
http://projects.edgewall.com/trac/
--------------------------------------------------------------------------
QUOTES:
"Like Bugzilla, but without the 6 years of training."
--------------------------------------------------------------------------
CONTRIBUTORS: {add your name, e-mail address and URL below}
Bob Kuehne <rpk@blue-newt.com> <http://www.blue-newt.com>
Jonathan Blocksom <blocksom@gollygee.com>
--------------------------------------------------------------------------
E-MAIL BOUNCEBACK: {add your e-mail address separated by commas }
--------------------------------------------------------------------------
NOTES ON / KEY TO THIS TEMPLATE:
A headline (like a field in a database) will be CAPITALISED
This differentiates from the text that follows
A variable that you can change will be surrounded by _underscores_
Spaces in variables are also replaced with under_scores
This allows people to select the whole variable with a simple double-click
A tool-tip is lower case and surrounded by {curly brackets / parentheses}
These supply helpful contextual information.
--------------------------------------------------------------------------
Copyright shared between all the participants unless otherwise stated...