Roundup Tracker - Issues

Issue 2551354

Hosting 3rd party templates on sourceforge under Roundup org
Type: rfe Severity: minor
Components: Web interface, Infrastructure Versions:
Status: new
: : ThomasAH, asavchuk, rouilj
Priority: :

Created on 2024-05-29 14:07 by rouilj, last changed 2024-06-14 05:15 by ThomasAH.

msg8083 Author: [hidden] (rouilj) Date: 2024-05-29 14:07
I have a request from a developer who implemented an updated jinja2 template for roundup
(see issue2551308).

He would like to publish the template on sourceforge under the roundup umbrella.

It looks like it's possible to do this. I have created a test mercurial (could be
git if we decide that's a better choice for 3rd party) repo at

I don't want to create/manage multiple third party repos. I am also concerned about
the security model for this. A DVCS is pretty much full access to everything.
I don't think publishing multiple tracker templates into one DVCS repo will
work. Unlike with centralized repos (SVN) we can't restrict access to a subpath
in the repo.

We also have governance issues. If a template is broken, what do we do?
It's under our namespace so we have some responsibility for it. Similar
issue for abandoned templates. Keeping our currently supplied templates up to
date is difficult enough.

New issues are cc'ed to the roundup-devel list IIRC. I'll bring this up
separately as well if needed.
msg8092 Author: [hidden] (ThomasAH) Date: 2024-06-14 05:15
I am able to add a hook to the repo on to prevent commits outside
a specified subdirectory for certain users.

But this would still leave the other aspects you mentioned, so I would
recommend applying the usual criteria for allowing push access, e.g. a
track record of being active in Roundup development instead of just
being a one-time contributor.
Date User Action Args
2024-06-14 05:15:18ThomasAHsetnosy: + ThomasAH
messages: + msg8092
2024-05-29 14:07:55rouiljcreate