SourceForge bugwatch updates are broken

Bug #605783 reported by Graham Binns on 2010-07-15
114
This bug affects 21 people
Affects Status Importance Assigned to Milestone
Launchpad itself
High
Unassigned

Bug Description

The current, much outdated SourceForge bugwatch functionality is horribly broken, since it depends on screen-scraping the SF bugs page and SF's templates have changed since it was implemented.

The SourceForge ExternalBugTracker should be updated to use an API or XML dump, whatever's available from SourceForge.

David Graf (davidagraf) wrote :

Hello Graham.

What is that status of this problem? The SourceForge bugwatch would be very useful for the project I am working for.

Regards,
David

Deryck Hodge (deryck) wrote :

Hi, David.

I'll reply for Graham, since I'm the one charged with getting bugs team work scheduled. I imagine you're not the only one who one find this useful and we very much need to get this fixed. Unfortunately, we won't have time to get to this anytime soon. I imagine it will be at least until December or early next year before we can look at this again.

Cheers,
deryck

David Graf (davidagraf) wrote :

Hello Deryck

What a pity. We work together with a team that is hosting its bugs on sourceforge. And sometimes, we are fixing bugs from them. But with two bug trackers, it is sometimes hart to keep the overview. A working bugwatcher would be very helpful!

Can we speed up the fixing process by contributing something?

Regards,
David

Deryck Hodge (deryck) wrote :

Yes, we would gladly welcome a contribution here! Probably the easiest way forward is for the person who is interested in doing the coding to discuss this with Graham on IRC. He's gmb on Freenode. He could point someone in the right direction and likely save much wasted time.

Andrey Bondarenko (abone) wrote :

I've checked SF site. There is an unmaintained and weakly documented API (http://sourceforge.net/apps/trac/sourceforge/wiki/API). But It does not provide ways to update single bug status, only all the bugs for project/tracker. I don't see any way to get tracker-id for given bug-id without screen scrapping. So updating screen scraping code may be simpler.

Gavin Panella (allenap) wrote :

Fwiw, I agree with Andrey.

Logan Rosen (logan) wrote :

SourceForge now has a REST API that might be able to extract enough information from bugs for Launchpad to interpret - http://sourceforge.net/p/forge/documentation/API%20-%20Beta/. Could this work?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers