clearly indicate to users where they should file bugs for operational issues

Bug #1140776 reported by Glyph Lefkowitz
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Twisted Website

Bug Description

Right now the only thing on the web site suggesting a way to report a problem - with Twisted, with the web site, with the software itself - is the "new ticket" link in the navbar. The fact that one should use the Twisted website for reporting issues with the Twisted website is further reinforced by the presence of the open "website" component. As per this discussion: <> we should really indicate that issues with Trac-as-deployed should be in lp:twisted-trac-integration, issues with the site itself should be reported here, and issues with buildbot should be reported in lp:twisted-buildbot-configuration.

Also, the website component should be closed so that folks don't file new bugs in it.

Revision history for this message
Richard Wall (richardw) wrote :

What's wrong with reporting operational and website issues in Trac?

I guess there good reasons. I'd be interested to hear them if you have
time to summarise.

I think it would be much more intuitive if was
the single database of all Twisted related issues.

 1. Easy for bug reporters to find
 2. Single sign on (doesn't require *another* registration)
 3. Admins can monitor all new Twisted issues in one place.
 4. I find Trac ticket reporting much simpler and more intuitive than
    Launchpad - maybe just because I'm familiar with Trac.
 5. Simple Trac markup for formatting the ticket description and

On the other hand...

 1. Trac is a single point of failure.
    * If Trac (website) dies you can still get the configuration and file
      tickets about the problem on Launchpad.
 2. Trac is slow
    * Maybe you are trying to minimise the use of Trac to reduce the
      slow down.

= Ticket #6329 =

My original trac ticket was badly constructed,
"pydoctor does not generate
twisted.names.common.ResolverBase.getHostByName api documentation
because it is in an interface base class"

I'd reported the problem in Pydoctor. I wanted to make sure that Tom
(or someone) was aware that the problem. I created a duplicate Trac
ticket and filled in the Launchpad ticket field; thinking this would
be a way of notifying Trac devs when the pydoctor problem was fixed,
at which point they could upgrade pydoctor on the buildslave.

Alternative Options:

 1. Associate the ticket with multiple projects: I just discovered
    that I can associate a Launchpad ticket with multiple projects -
    as exarkun has done in

    I've now done this for another of my tickets:

 2. Or I could have created a separate ticket eg

    "upgrade pydoctor on bot-glyph-1 to support API documentation from
    interface base classes"

Anyway, I must admit I felt cheesed off when all my tickets were
closed "invalid" last week, but...on reflection, I was aware of
twisted-buildbot-configuration on Launchpad and I could have gone
looking for it. I guess I was just being lazy.

I also remember feeling curious about the Launchpad ID field in the
Trac tickets and wanted to try it out. I know it's related to
Launchpad integration with external trackers, but is that still used
by Twisted? If not, can it be removed to avoid future confusion /

= A Custom New Ticket Page =

How about customising the Trac "New ticket" page.
The Trac project does it:

If I can have "Wiki Edit" permissions on I'll draft an Edgewall
style NewTicket page.


Revision history for this message
Glyph Lefkowitz (glyph) wrote : Re: [Bug 1140776] clearly indicate to users where they should file bugs for operational issues

On Mar 3, 2013, at 4:08 AM, Richard Wall <email address hidden> wrote:

> What's wrong with reporting operational and website issues in Trac?

Good question. If we're going to redirect people to different places for different kinds of issue, we should really say why we're doing that.

Revision history for this message
Richard Wall (richardw) wrote :

I drafted some words for inclusion on the new ticket and attachment upload pages.

Revision history for this message
Richard Wall (richardw) wrote :
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.