Hi
Any reason why smolt trac instance bug reporting is being restricted at https://hosted.fedoraproject.org/projects/smolt/newticket? There isn't a bugzilla component either.
Rahul
Rahul Sundaram wrote:
Hi
Any reason why smolt trac instance bug reporting is being restricted at https://hosted.fedoraproject.org/projects/smolt/newticket? There isn't a bugzilla component either.
Because all track bugs are and there is a bugzilla component for smolt.
-Mike
On Friday 08 June 2007 14:21:39 Rahul Sundaram wrote:
Any reason why smolt trac instance bug reporting is being restricted at https://hosted.fedoraproject.org/projects/smolt/newticket?
To prevent spam, and to ensure that the filer uses an address that we can get back to for feedback on potential fixes. Same reason that the wiki components don't allow anonymous edits in Trac spaces.
Jesse Keating wrote:
On Friday 08 June 2007 14:21:39 Rahul Sundaram wrote:
Any reason why smolt trac instance bug reporting is being restricted at https://hosted.fedoraproject.org/projects/smolt/newticket?
To prevent spam, and to ensure that the filer uses an address that we can get back to for feedback on potential fixes. Same reason that the wiki components don't allow anonymous edits in Trac spaces.
Shouldn't all trac projects disable this then? It doesn't currently.
Rahul
Jesse Keating wrote:
On Friday 08 June 2007 14:53:14 Rahul Sundaram wrote:
Shouldn't all trac projects disable this then? It doesn't currently.
I may have missed some when I started blocking it off. Can you tell me which ones don't block it?
https://hosted.fedoraproject.org/projects/revisor/newticket https://hosted.fedoraproject.org/projects/LHCP/newticket https://hosted.fedoraproject.org/projects/mirrormanager/newticket https://hosted.fedoraproject.org/projects/mock/newticket https://hosted.fedoraproject.org/projects/presto/newticket https://hosted.fedoraproject.org/projects/readahead/newticket https://hosted.fedoraproject.org/projects/revisor/newticket https://hosted.fedoraproject.org/projects/setroubleshoot/newticket
Rahul
On Friday 08 June 2007 17:53:55 Rahul Sundaram wrote:
https://hosted.fedoraproject.org/projects/revisor/newticket https://hosted.fedoraproject.org/projects/LHCP/newticket https://hosted.fedoraproject.org/projects/mirrormanager/newticket https://hosted.fedoraproject.org/projects/mock/newticket https://hosted.fedoraproject.org/projects/presto/newticket https://hosted.fedoraproject.org/projects/readahead/newticket https://hosted.fedoraproject.org/projects/revisor/newticket https://hosted.fedoraproject.org/projects/setroubleshoot/newticket
These should all be blocked now.
Jesse Keating wrote:
On Friday 08 June 2007 17:53:55 Rahul Sundaram wrote:
https://hosted.fedoraproject.org/projects/revisor/newticket https://hosted.fedoraproject.org/projects/LHCP/newticket https://hosted.fedoraproject.org/projects/mirrormanager/newticket https://hosted.fedoraproject.org/projects/mock/newticket https://hosted.fedoraproject.org/projects/presto/newticket https://hosted.fedoraproject.org/projects/readahead/newticket https://hosted.fedoraproject.org/projects/revisor/newticket https://hosted.fedoraproject.org/projects/setroubleshoot/newticket
These should all be blocked now.
So let me get this straight. We (kinda upstream) should have users log bugs in bugzilla, although we are using the hosted.fp.org ticketing system for the work we do? How do we get bugzilla tickets into Trac? Manually?
Kind regards,
Jeroen van Meeuwen -kanarip
On Saturday 09 June 2007 10:04:17 Jeroen van Meeuwen wrote:
Jesse Keating wrote:
On Friday 08 June 2007 17:53:55 Rahul Sundaram wrote:
https://hosted.fedoraproject.org/projects/revisor/newticket https://hosted.fedoraproject.org/projects/LHCP/newticket https://hosted.fedoraproject.org/projects/mirrormanager/newticket https://hosted.fedoraproject.org/projects/mock/newticket https://hosted.fedoraproject.org/projects/presto/newticket https://hosted.fedoraproject.org/projects/readahead/newticket https://hosted.fedoraproject.org/projects/revisor/newticket https://hosted.fedoraproject.org/projects/setroubleshoot/newticket
These should all be blocked now.
So let me get this straight. We (kinda upstream) should have users log bugs in bugzilla, although we are using the hosted.fp.org ticketing system for the work we do? How do we get bugzilla tickets into Trac? Manually?
Any user with a valid Fedora account (regardless of group) can open tickets in Trac. Just like any user with a valid bugzilla account can open bugs. Hopefully at some point it'll be very easy to get a Fedora account for stuff, or be able to use an existing OpenID for stuff. However the alternative of letting any random internet user or bot spam wikis or tickets is not good.
The way I treat Trac and bugzilla is as such.
Bugs get filed in bugzilla for a particular component in a particular release. IE this bug effects this release. If necessary, I file a ticket in Trac, the upstream, to fix the issue. Issue gets fixed in Trac, Trac ticket gets closed. Once I've rolled that fix into an update or testing update for the Fedora product then I'd alter the bugzilla ticket. Since my Trac project could potentially be used by other distributions/users I don't want to tie everything to Fedora distribution releases.
On Saturday 09 June 2007 12:21:16 Jesse Keating wrote:
Any user with a valid Fedora account (regardless of group) can open tickets in Trac. Just like any user with a valid bugzilla account can open bugs. Hopefully at some point it'll be very easy to get a Fedora account for stuff, or be able to use an existing OpenID for stuff. However the alternative of letting any random internet user or bot spam wikis or tickets is not good.
I should note that this is just the default. Admins for projects can adjust the rights of users (authed or not) via the Admin panel. New projects (and the projects I had already created) get set to non anon content generation.
infrastructure@lists.fedoraproject.org