Register project from source package should include homepage URL
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Launchpad itself |
High
|
Unassigned | ||
Bug Description
A lot of Debian packages have the "Homepage" field set, which contains the upstream project homepage URL.
Now that the upstream project registration from a source package works, it should be possible to use this URL to automatically fill in the project homepage URL.
Related branches
- Tim Penhey (community): Approve on 2010-08-30
- Steve Kowalik (community): Approve (code*) on 2010-08-27
- Stuart Bishop: Approve (db) on 2010-08-23
- Robert Collins (community): Approve (db) on 2010-08-22
-
Diff: 269 lines (+80/-10)13 files modifieddatabase/schema/comments.sql (+2/-0)
database/schema/patch-2208-05-0.sql (+11/-0)
lib/lp/registry/interfaces/distroseries.py (+4/-1)
lib/lp/registry/model/distroseries.py (+3/-2)
lib/lp/soyuz/interfaces/binarypackagebuild.py (+1/-1)
lib/lp/soyuz/interfaces/binarypackagerelease.py (+7/-0)
lib/lp/soyuz/interfaces/sourcepackagerelease.py (+8/-0)
lib/lp/soyuz/model/binarypackagebuild.py (+2/-2)
lib/lp/soyuz/model/binarypackagerelease.py (+1/-0)
lib/lp/soyuz/model/sourcepackagerelease.py (+1/-0)
lib/lp/soyuz/tests/test_binarypackagerelease.py (+16/-0)
lib/lp/soyuz/tests/test_sourcepackagerelease.py (+16/-0)
lib/lp/testing/factory.py (+8/-4)
- Jeroen T. Vermeulen (community): Approve (code) on 2010-08-25
-
Diff: 296 lines (+52/-26)6 files modifiedlib/lp/archiveuploader/dscfile.py (+2/-0)
lib/lp/archiveuploader/nascentuploadfile.py (+14/-14)
lib/lp/archiveuploader/tests/test_nascentuploadfile.py (+29/-7)
lib/lp/registry/browser/product.py (+3/-1)
lib/lp/registry/stories/product/xx-product-add.txt (+2/-2)
lib/lp/soyuz/tests/test_publishing.py (+2/-2)
- Māris Fogels (community): Approve on 2010-11-24
-
Diff: 266 lines (+74/-93)3 files modifiedlib/lp/registry/browser/sourcepackage.py (+6/-0)
lib/lp/registry/browser/tests/test_sourcepackage_views.py (+61/-66)
lib/lp/registry/stories/packaging/xx-sourcepackage-packaging.txt (+7/-27)
| Jelmer Vernooij (jelmer) wrote : | #1 |
| Jelmer Vernooij (jelmer) wrote : | #2 |
I've linked a branch that adds the homepage field to the initial project registration.
| Changed in launchpad-registry: | |
| status: | New → Triaged |
| Curtis Hovey (sinzui) wrote : | #3 |
We removed the homepage field from registration last year because users thought this information was rarely relavent to registering their project. I am not certain we want to add it back for all registrations, but it is useful when registering from a source package or bug.
I'll wait to see your proposal. I too hate having to visit the Change details page to set one more piece of information.
| Jelmer Vernooij (jelmer) wrote : | #4 |
Perhaps it would make sense to just show that field if a default value has been provided (such as by the registration from source package link). On the other hand I think putting extra magic in might make things confusing for users (a field being present in some situations but missing in others).
Another alternative would be to have a hidden field for the homepage and simply always use the URL that was present in the source package. Rethinking this, I think this is perhaps the best option if re-adding the homepage field is considered a bad idea. In almost all situations the value of the sourcepackage homepage will be correct, and if it isn't the user can always go to the details page to fix it.
What do you think?
| Curtis Hovey (sinzui) wrote : | #5 |
We often change the field_names attr to a property that decides whether to include the homepage it based on the registration condition.
I think adding the homepage to the registration form *is* an improvement, and we could restore it to the field names rgiht now. It was removed last year with several other links to external sties. The project page does not prompt the maintainer to provide links to external sties, but we intended to add an ajax overlay that allows the maintainer to add the links easilly to the project page. We have not commitments to do overlay now, so maintainers do not know about the external links fields.
So in summary. Lets add the field back. I do not expect users to complain about one more field.
Fixed in db-stable r9719 <http://
| Changed in launchpad-registry: | |
| milestone: | none → 10.09 |
| tags: | added: qa-needstesting |
| Changed in launchpad-registry: | |
| status: | Triaged → Fix Committed |
| Launchpad QA Bot (lpqabot) wrote : | #7 |
Fixed in db-stable r9738 <http://
| Jelmer Vernooij (jelmer) wrote : | #8 |
This hasn't actually been fixed yet - the two branches that have landed re-introduce the homepage field and make launchpad store the homepage field from packages.
| Changed in launchpad-registry: | |
| status: | Fix Committed → Triaged |
| Changed in launchpad-registry: | |
| importance: | Undecided → High |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in launchpad-registry: | |
| milestone: | 10.09 → 10.10 |
| Changed in launchpad-registry: | |
| milestone: | 10.10 → 10.11 |
| Changed in launchpad-registry: | |
| milestone: | 10.11 → 10.12 |
| tags: | added: bridging-the-gap |
| Changed in launchpad-registry: | |
| assignee: | Jelmer Vernooij (jelmer) → Curtis Hovey (sinzui) |
| status: | Triaged → In Progress |
| Launchpad QA Bot (lpqabot) wrote : | #9 |
Fixed in stable r11971 <http://
| tags: |
added: qa-needstesting removed: qa-ok |
| Changed in launchpad-registry: | |
| status: | In Progress → Fix Committed |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in launchpad-registry: | |
| status: | Fix Committed → Fix Released |
| Changed in launchpad: | |
| assignee: | Curtis Hovey (sinzui) → nobody |
As this is one of my itches, I'll have a look at it.