Merge lp:~edwin-grubbs/launchpad/bug-490593-configure-involvement-portlet into lp:launchpad
| Status: | Merged |
|---|---|
| Approved by: | Curtis Hovey on 2010-04-09 |
| Approved revision: | no longer in the source branch. |
| Merged at revision: | not available |
| Proposed branch: | lp:~edwin-grubbs/launchpad/bug-490593-configure-involvement-portlet |
| Merge into: | lp:launchpad |
| Diff against target: |
1459 lines (+524/-182) 34 files modified
Makefile (+3/-0) lib/canonical/launchpad/icing/style-3-0.css.in (+26/-5) lib/canonical/launchpad/pagetests/standalone/xx-form-layout.txt (+2/-1) lib/lp/blueprints/browser/specificationtarget.py (+1/-1) lib/lp/bugs/stories/bug-also-affects/xx-upstream-bugtracker-links.txt (+4/-2) lib/lp/bugs/stories/bugs/xx-front-page-info.txt (+1/-1) lib/lp/bugs/stories/bugtracker/bugtrackers-index.txt (+2/-1) lib/lp/bugs/stories/bugtracker/xx-bugtracker.txt (+2/-1) lib/lp/bugs/stories/guided-filebug/xx-bug-reporting-guidelines.txt (+11/-11) lib/lp/bugs/stories/guided-filebug/xx-no-launchpadder.txt (+2/-1) lib/lp/bugs/stories/guided-filebug/xx-project-guided-filebug.txt (+1/-1) lib/lp/bugs/stories/initial-bug-contacts/10-set-upstream-bugcontact.txt (+2/-2) lib/lp/bugs/templates/bugtarget-bugs.pt (+8/-3) lib/lp/bugs/templates/bugtarget-macros-filebug.pt (+1/-1) lib/lp/code/stories/branches/xx-branch-tag-cloud.txt (+7/-5) lib/lp/code/stories/branches/xx-product-branches.txt (+12/-8) lib/lp/registry/browser/configure.zcml (+42/-0) lib/lp/registry/browser/pillar.py (+72/-4) lib/lp/registry/browser/product.py (+101/-23) lib/lp/registry/browser/productseries.py (+24/-20) lib/lp/registry/browser/tests/pillar-views.txt (+46/-14) lib/lp/registry/doc/product.txt (+6/-3) lib/lp/registry/model/product.py (+6/-2) lib/lp/registry/stories/product/xx-product-development-focus.txt (+32/-16) lib/lp/registry/stories/product/xx-product-edit.txt (+4/-2) lib/lp/registry/stories/product/xx-product-launchpad-usage.txt (+40/-17) lib/lp/registry/templates/pillar-involvement-portlet.pt (+30/-3) lib/lp/registry/templates/product-index.pt (+0/-4) lib/lp/translations/stories/productseries/xx-productseries-translations.txt (+10/-10) lib/lp/translations/stories/standalone/xx-product-translations.txt (+8/-7) lib/lp/translations/stories/translationgroups/15-product-translation-group.txt (+3/-2) lib/lp/translations/stories/translationgroups/46-test-distro-structured-permissions.txt (+1/-1) lib/lp/translations/stories/translations/55-rosetta-potemplates.txt (+2/-1) lib/lp/translations/templates/product-portlet-not-using-launchpad.pt (+12/-9) |
| To merge this branch: | bzr merge lp:~edwin-grubbs/launchpad/bug-490593-configure-involvement-portlet |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Curtis Hovey (community) | code ui | 2010-03-17 | Approve on 2010-04-09 |
|
Review via email:
|
|||
Description of the Change
Summary
-------
This branch uses the "Get Involved" portlet to encourage users to link
projects to the upstream bug tracker. In a later branch, we may open
up permissions to more than the project owner.
Implementation details
-------
Drive-by cleanups.
Makefile
lib/
Split out form elements for configuring Launchpad services into seperate
forms. The visible_
projects that don't have Bugs or Branches configured.
lib/
lib/
lib/
lib/
lib/
lib/
Added styles for a disabled version of the Get Involved links.
lib/
Fixed links that were pointing to +edit.
lib/
lib/
lib/
Fixed tests that were expecting to use +edit.
lib/
lib/
lib/
lib/
lib/
lib/
lib/
lib/
lib/
lib/
lib/
lib/
lib/
lib/
lib/
lib/
Tests
-----
./bin/test -vv -t whatever '/xx-product-
Demo and Q/A
------------
* Open http://
* Test the new forms and links for:
* Configure Launchpad Answers
* Configure Launchpad Branches
* Configure Launchpad Bugs
* Configure Launchpad Translations
* Open http://
* There should be a "Configure Launchpad Blueprints" link.
* Open http://
* If translations is disabled, there should be a
"Configure Launchpad Translations" link.
* Open http://
* If the project is not using launchpad for bug tracking,
there should be a "Configure Launchpad Bugs" link.
| Edwin Grubbs (edwin-grubbs) wrote : | # |
> Hi Edwin.
>
> I really appreciate your effort to solve this usability issue.
>
> UI/Usability
> ------------
>
> ! As the owner of thunderbird, I saw that the "Report a bug" was disabled. I
> used "Configure Launchpad bugs" and choose The Mozilla.org bug tracker and
> provided the remove project.
> * I still see "Report a bug" (This service needs configuration). This is
> wrong. I provided the real information that should satisfy other
> contributors. I expect to see the warning disappear.
Hi Curtis,
Thanks for the review.
As we discussed on Skype, I will focus on code hosting now and fix the logic for displaying the bug tracker warning in another branch.
I have not fixed any of the unit tests for these recent changes, since I want to get your input on the UI changes first. You will notice that "Configure code hosting" switches between a plus-icon and an edit-icon, since I'm re-using the original menu item for +linkbranch. The plus-icon doesn't really make sense with the "configure" verb, but I think it is worth contemplating the use of a different icon to indicate unconfigured services.
> ! As the owner of Firefox and thunderbird, I expect to see a warning that
> "Development focus branch has not been specified" which I can see in the
> Project information portlet.
> * I think this is a case where official_
> We know if the project officially uses code if the branch is neither a
> mirror or import. I expect the Involvement portlet to tell me that this
> is a problem.
> * As an anonymous user I should see a warning that the development focus is
> missing a branch in the Involvement portlet.
> * May be call for action should also be repeated on the series page since
> that is the object that is being edited.
I'm confused here, since a little further down you comment that the warning could be removed from the Project information portlet. Do you want a more noticeable warning message in the involvement portlet than a tooltip?
> ! As the user of evolution, a project that has a link to a package with
> I expect to see a warning that translation syncing should be setup.
> The owner certainly can set official/unofficial usage, but any user
> can enable series sync, and should if Ubuntu has translations for it.
> * This is a unique case were any user can set this. This information
> must be shown on the series overview for any user to act on.
> * We may want alternate configuration link or tool tips about the
> problem.
> * This is case is harder than the others because the official_
> attribute is legitimate.
We agreed to handle translations later.
> ! I think the message for all these services is wrong. We want the user
> to tell Launchpad where the service is and maybe configure it if the
> service is Launchpad's. In the bug tracker example. we need to know the
> bug tracker, and the owner wants to tell every one about the official
> tracker; no one is asking users to enable Launchpad Bugs.
I tried improving the tooltip for the warnings.
> * I noticed that as an anonymous user or no-priv that the Involve...
| Curtis Hovey (sinzui) wrote : | # |
Hi Edwin.
I have a couple suggestion and questions that I think will take a few minutes
to resolve.
Using the UI:
* "bug tracker" is two words.
* Maybe "Configure support tracking" for answers.
* We are asking users to Configure project development branch? I guess
length is the issue here.
Code:
I see these warnings:
== Pyflakes notices ==
lib/
28: 'IProductSeries' imported but unused
lib/
9: undefined name 'ProductInvolve
> === modified file 'lib/lp/
> --- lib/lp/
> +++ lib/lp/
> @@ -169,9 +169,14 @@
> bug tracking.
>
> <p tal:condition=
> - id="no-
> - <a tal:attributes=
> - bug tracking.</a>
> + id="no-malone-edit"
> + tal:define ="configure_
> + >
> + <a tal:condition=
> + tal:replace=
> + <a tal:condition="not: configure_
> + tal:attributes=
> + Enable bug tracking.</a>
Why isn't this using the context's overview menu edit link that has
permission checking for rendering.
context/
The language looks wrong. We are interested in Configuring, not enabling.
I think this is for the bugs root page which may be fine in this case.
> === modified file 'lib/lp/
> --- lib/lp/
> +++ lib/lp/
> @@ -170,7 +170,7 @@
> the 'Import your project' button is not shown.
>
> >>> admin_browser.
> - >>> admin_browser.
> + >>> admin_browser.
> >>> admin_browser.
> ... 'Code for this project is published in Bazaar branches '
> ... 'on Launchpad').click()
I do not like the use of "Launchpad" in these links. They imply the project
is setting up hosting when we are really interested in gathering project info.
I have dealt with several angry, confused users who see Launchpad masquerading
or is forking project. I think taking "Launchpad" out of the link will make
it clear we want the know where the upstream branch is.
> === modified file 'lib/lp/
> --- lib/lp/
> +++ lib/lp/
> @@ -128,6 +130,78 @@
> link for link in menuapi.
> key=attrgetter(
>
> + @cachedproperty
> + def visible_d...
| Edwin Grubbs (edwin-grubbs) wrote : | # |
Hi Curtis,
Thanks for the review. I have merged in Brad's branch and pointed
the "Configure product branch" links at +setbranch instead of
+linkbranch, and I have responded to your comments below.
-Edwin
> Hi Edwin.
>
> I have a couple suggestion and questions that I think will take a few minutes
> to resolve.
>
> Using the UI:
>
> * "bug tracker" is two words.
> * Maybe "Configure support tracking" for answers.
> * We are asking users to Configure project development branch? I guess
> length is the issue here.
Fixed.
>
> Code:
>
> I see these warnings:
>
> == Pyflakes notices ==
>
> lib/lp/
> 28: 'IProductSeries' imported but unused
>
> lib/lp/
> 9: undefined name 'ProductInvolve
>
TODO: lint
>
> > === modified file 'lib/lp/
> > --- lib/lp/
> > +++ lib/lp/
> > @@ -169,9 +169,14 @@
> > bug tracking.
> >
> > <p tal:condition=
> > - id="no-
> > - <a tal:attributes=
> > - bug tracking.</a>
> > + id="no-malone-edit"
> > + tal:define ="configure_
> context/
> > + >
> > + <a tal:condition=
> > + tal:replace=
> > + <a tal:condition="not: configure_
> > + tal:attributes=
> > + Enable bug tracking.</a>
>
> Why isn't this using the context's overview menu edit link that has
> permission checking for rendering.
>
> context/
>
> The language looks wrong. We are interested in Configuring, not enabling.
> I think this is for the bugs root page which may be fine in this case.
I was afraid of breaking a bunch more tests if I changed the name of
the link from "Enable bug tracking", not to mention that there may be
push back on the "Configure bug tracker" link later on.
> > === modified file 'lib/lp/
> > --- lib/lp/
> 14:22:42 +0000
> > +++ lib/lp/
> 16:20:16 +0000
> > @@ -170,7 +170,7 @@
> > the 'Import your project' button is not shown.
> >
> > >>> admin_browser.
> > - >>> admin_browser.
> > + >>> admin_browser.
> > >>> admin_browser.
> > ... 'Code for this project is published in Bazaar branches '
> > ... 'on Launchpad').click()
>
> I do not like the use of "Launchpad" in these links. They imply the project
> is setting up hosting when we are really interested in gathering project info.
>
> I have dealt with severa...
| Curtis Hovey (sinzui) wrote : | # |
Thanks for these revisions Edwin.
I am very aware of the ProductInvolvem

Hi Edwin.
I really appreciate your effort to solve this usability issue.
UI/Usability
------------
! As the owner of thunderbird, I saw that the "Report a bug" was disabled. I
used "Configure Launchpad bugs" and choose The Mozilla.org bug tracker and
provided the remove project.
* I still see "Report a bug" (This service needs configuration). This is
wrong. I provided the real information that should satisfy other
contributors. I expect to see the warning disappear.
! As the owner of Firefox and thunderbird, I expect to see a warning that codehosting is a bogus attribute.
"Development focus branch has not been specified" which I can see in the
Project information portlet.
* I think this is a case where official_
We know if the project officially uses code if the branch is neither a
mirror or import. I expect the Involvement portlet to tell me that this
is a problem.
* As an anonymous user I should see a warning that the development focus is
missing a branch in the Involvement portlet.
* May be call for action should also be repeated on the series page since
that is the object that is being edited.
! As the user of evolution, a project that has a link to a package with translations
I expect to see a warning that translation syncing should be setup.
The owner certainly can set official/unofficial usage, but any user
can enable series sync, and should if Ubuntu has translations for it.
* This is a unique case were any user can set this. This information
must be shown on the series overview for any user to act on.
* We may want alternate configuration link or tool tips about the
problem.
* This is case is harder than the others because the official_
attribute is legitimate.
! I think the message for all these services is wrong. We want the user
to tell Launchpad where the service is and maybe configure it if the
service is Launchpad's. In the bug tracker example. we need to know the
bug tracker, and the owner wants to tell every one about the official
tracker; no one is asking users to enable Launchpad Bugs.
* I noticed that as an anonymous user or no-priv that the Involvement portlet
has about 1em extra padding in the bottom. Oh. The markup has an empty
<ul>; this is invalid HTML.
* I Think the "Uses Launchpad for" item in the Project information portlet
may be redundant. We can discuss removing it after we are certain that this
change is all the information needed. I suspect we need to disable answers
and blueprints first since they are effectively on and it is not clear
that the involvement portlet is 100% related to official uses. Of course,
the involvement portlet is not just about official uses anymore either.
* Think the "Development focus branch has not been specified" link in
the Project information portlet may be removable if we solve the Involvement
portlet issues.
* Note to self, we may want to remove official_ translations from distros.
Only Ubuntu can use translations. I recall there was a complaint from a
user that we cannot set a distro bug tracker.
I see your configuration for the bug tracker is similar to my branch and I
...