Bring long descriptions to Harvest

[Abhinav Upadhyay]

I think it would be a great improvement if on selecting a particular package, along with the bug numbers, a one line topic/summary is also displayed.

For example
 Network-manager appliet
     623012 wifi signal strength is not shown accurately

It would give an idea to the user, if it is a problem in his area or if it is an interesting problem to work on, without going to launchpad.

Also, when visiting harvest after 2-3 days, it is hard to remember, which bugs I had seen earlier, so a summary would be helpful there also.

[Daniel Holbach (dholbach)]

This was discussed at UDS as part of https://launchpad.net/ubuntu/+spec/community-o-developer-initiatives and we should totally bring long descriptions to Harvest.

[Daniel Holbach (dholbach)]

The JSON import already allows a long description, as explained over here: http://daniel.holba.ch/blog/?p=838 - we just need to make sure that all data sources in harvest-data cater to this. Also do we need to update the Harvest UI to show the description if available.

[Abhinav Upadhyay (er-abhinav-upadhyay)]

Thanks for the update. Looking forward to this feature :)

[Daniel Holbach (dholbach)]

This is a list of feeds that need to be updated, because .csv does not support the long description format.

http://reports.qa.ubuntu.com/reports/launchpad-database/bitesize.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/ftbfs.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/packaging.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/unmetdeps.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/upgrade.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/resolved-upstream.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/patches.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/maintainer-script.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/branches.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/SRUs-hardy.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/SRUs-lucid.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/SRUs-maverick.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/bugpatterns-needed.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/update-testing-hardy.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/update-testing-lucid.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/update-testing-maverick.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/patch-accepted.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/patch-needswork.csv

http://gaspa.yattaweb.it/issues/reverse_nbs.csv

http://qa.ubuntuwire.com/ftbfs/oneiric.csv

http://reports.qa.ubuntu.com/reports/sponsoring/sponsoring.csv

[Daniel Holbach (dholbach)]

Brian, Michael, Andrea: can you help with updating the scripts that produce .csv output and don't show long descriptions? Instructions to "port": http://daniel.holba.ch/blog/?p=838

[Daniel Holbach (dholbach)]

Dylan: do you have an idea what we can best do with long descriptions regarding wrapping, ellipsizing, if to prefer them over short descriptions, etc.?

[Dylan McCall (dylanmccall)]

I think I prefer long descriptions, but we'll need to think about the design a little. The opportunity-summary and actions blocks still need to be there, but with a longer description they'll look really weird how they are now. Perhaps we can have those in a block to the right and the description in a block to the left, lined up using display:table-cell. If the descriptions are always particularly long, maybe we can stick them on the bottom and get away from sticking stuff on the right side. I'll see if I can figure out a wireframe for it :)

How long do you think a particularly long long description would be? Perhaps we could enforce a hard 140 character limit in the server. (I think we're doing that for notes).

[Daniel Holbach (dholbach)]

Sponsoring overview now spits up json, I updated harvest-data to this effect as well.

[Daniel Holbach (dholbach)]

Dylan: maybe we should just start playing around with it and see what looks best. Ellipsising will definitely make sense (140 sounds like a reasonable start). A bunch of opportunities already make use of json and have long_descriptions.

[Daniel Holbach (dholbach)]

Dylan: how would you feel about "just adding them" for now and then figure out what people would prefer to see? For now just showing long description instead of short description (capped at 140) could be good. Maybe we can wrap the text so it doesn't overlap with the other links and options? Obviously I'm not a CSS person. :-)

[Daniel Holbach (dholbach)]

I'd like to offer https://code.launchpad.net/~dholbach/harvest/734746/+merge/66154 as a start for implementing this together.

[Daniel Holbach (dholbach)]

Now we need to fix this in the harvest-data data sources.

[Daniel Holbach (dholbach)]

Brian: do you think we could change the script which provides the different bug lists to provide long descriptions as well (bug titles)?

[Daniel Holbach (dholbach)]

Thanks for your work on this Brian. Remaining bits now are:

http://qa.ubuntuwire.com/ftbfs/precise.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/bitesize.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/branches.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/ftbfs.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/maintainer-script.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/packaging.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/patches.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/resolved-upstream.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/SRUs-hardy.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/SRUs-lucid.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/SRUs-natty.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/SRUs-oneiric.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/unmetdeps.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/update-testing-hardy.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/update-testing-lucid.csv
http://reports.qa.ubuntu.com/reports/launchpad-database/upgrade.csv

[Brian Murray (brian-murray)]

On Mon, Apr 16, 2012 at 04:37:50PM -0000, Daniel Holbach wrote:
> Thanks for your work on this Brian. Remaining bits now are:
>
> http://reports.qa.ubuntu.com/reports/launchpad-database/bitesize.csv
> http://reports.qa.ubuntu.com/reports/launchpad-database/branches.csv
> http://reports.qa.ubuntu.com/reports/launchpad-database/ftbfs.csv
> http://reports.qa.ubuntu.com/reports/launchpad-database/maintainer-script.csv
> http://reports.qa.ubuntu.com/reports/launchpad-database/packaging.csv
> http://reports.qa.ubuntu.com/reports/launchpad-database/patches.csv
> http://reports.qa.ubuntu.com/reports/launchpad-database/resolved-upstream.csv
> http://reports.qa.ubuntu.com/reports/launchpad-database/unmetdeps.csv
> http://reports.qa.ubuntu.com/reports/launchpad-database/upgrade.csv

An RT has been submitted for the above ones.

> http://reports.qa.ubuntu.com/reports/launchpad-database/SRUs-hardy.csv
> http://reports.qa.ubuntu.com/reports/launchpad-database/SRUs-lucid.csv
> http://reports.qa.ubuntu.com/reports/launchpad-database/SRUs-natty.csv
> http://reports.qa.ubuntu.com/reports/launchpad-database/SRUs-oneiric.csv

I've done the SRUs- ones now.

--
Brian Murray
Ubuntu Bug Master

[Brian Murray (brian-murray)]

Ran across this again and wanted to make it clear that all the launchpad-database ones use json long descriptions now.

[Daniel Holbach (dholbach)]

It looks like these are still left. Are they important to us?

http://qa.ubuntuwire.com/ftbfs/precise.csv,"Build status for Ubuntu Precise"
http://reports.qa.ubuntu.com/reports/launchpad-database/update-testing-hardy.csv,"Bugs in Hardy needing SRU verification"
http://reports.qa.ubuntu.com/reports/launchpad-database/update-testing-lucid.csv,"Bugs in Lucid needing SRU verification"

[Brian Murray (brian-murray)]

I've updated the SRU verification ones. Thanks for the reminder!