[Tracker-discuss] issue tracker for Roundup (the project) itself ?

[Erik Forsberg]

On Mon, 05 Nov 2007 19:34:04 +0200
Roché Compaan <roche at upfrontsystems.co.za> wrote:

> On Mon, 2007-11-05 at 11:54 -0500, Stefan Seefeld wrote:
> > Hello,
> > 
> > in the early phase of the new-tracker-for-python.org work, we talked
> > about the possibility to host the Roundup project's own issue
> > tracker on the same machine as python.org's tracker. Is this still
> > an option ? If so, what would be the next steps ?
> 
> If it depends on us as hosts, then yes! We would love to host Roundup
> tracker :-)
> 
> The next steps would be to simply add another tracker instance and do
> the necessary configuration in Apache and Postfix. Shout if you need
> help or want us to do the initial setup.

I have some thoughts on separation of tracker instances for security
and stability reasons, but apart from that, I would also enjoy if
roundup could get its own tracker!

I'd like each tracker to run as its own user, for two main reasons:

1) Security. Breakin to one tracker due to misconfiguration or perhaps
badly written detector should not affect other trackers.

2) More important: Stability of one tracker should not be affected
because someone makes a mistake for another tracker. A 'rm -rf' in the
wrong place can cause so much wasted time. With tracker permissions
separated, we can have "per tracker admins" that don't have the ability
to destroy for example bugs.python.org.

I also see it as neccesary that all trackers run the same anti-spam
measures as bugs.python.org and the meta tracker. One tracker should
not be able to get the IP of psf.upfronthosting.co.za blacklisted. Just
as we can run a central postgresql instance, we can run a central
spambayes XMLRPC server instance.

To summarize - I think hosting a tracker for roundup itself is a great
idea, and I hope someone can do the actual schema/template/import work.
I'm willing to help with the setup of the tracker/apache/user
separation, etc, once we have a working tracker instance.

Regards,
\EF
-- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.python.org/pipermail/tracker-discuss/attachments/20071106/c272dea6/attachment.pgp