UpstreamImportIntoUbuntu

Summary

Describe in a few phrases the main findings of the testing. If someone read only this part of the report, what would you want them to

Findings

• As someone new to the translations world, how would I learn the correct way to translate my upstream software and have it included in the ubuntu distribution? That is, how can I take advantage of the upstream translation import feature on LP?

  • Actually this one is answered quite well in https://help.launchpad.net/Translations, so ignore this bullet point.

• perhaps add one of those inline help question marks to the "This source package is not sharing translations with an upstream project." option so people will better understand what that is for

• Link to upstream project page on https://translations.qastaging.launchpad.net/ubuntu/natty/+source/gnuhello/+edit-packaging shows the "Change" button followed by "or or" and then "Cancel" link.

• when the upstream link is updated I'm taken back to the main translation page for gnuhello. It should go back to the next step ideally to complete the 4 needed steps.
  • I realize this point will be moot once all the controls are ajaxified

• The table displayed here https://translations.qastaging.launchpad.net/ubuntu/natty/+source/gwibber have headers "language" and "status" left aligned and untranslated, need review, changed headers right aligned. The cell contents are all left aligned which makes the number under the "Changed" column looks like it belongs to the "need review" column

AJAX overlay testing

• Message box says "Translations are currently being linked by a background job. When that job has finished, translations will be shared with the upstream project."
  • So... uhh... does that mean the box goes away? Or does that mean we should refresh? How does the user figure out that this is done?

  • Starting at https://translations.qastaging.launchpad.net/ubuntu/natty/+source/gwibber/+sharing-details

  • Set up a upstream project (e.g. gwibber)
  • On "Translations are enabled on the upstream project." overlay click the submit button
    • XXX: Trying to undo this to test and I get "Sorry, an error occurred while loading the form" message when I click the edit icon next to "translations are enabled" link.
  • You get the background job message

• We can all remove the link between the Gwibber source package and the Gwibber series – is this correct? (We are all registry admins, so yes. need to be a no-priv account to verify). no-priv accounts can't see "Sharing information" in the main page: http://ubuntuone.com/p/mG1/

* XXX: Deryck to make sure that dpm & Kyle Nietzsche (kyleN) are enabled to test this

Bugs filed already

• Usage settings permission issues: Bug 758920

  • matsubara & jml get http://ubuntuone.com/p/mFA/ (this is bad, you should look at it)

  • Ursinha gets the form, but a 403 on submit. Presented with http://ubuntuone.com/p/mFL/ and when choosing Unknown, External or Not Applicable options, an error box is displayed: http://ubuntuone.com/p/mFI/.

• AJAX overlay uses a cancel button rather than a link (Usage settings & Import settings) Bug 758901

  • Guidelines say that cancel should be a link <https://dev.launchpad.net/UserInterfaceWording>

    • <beuno> the rationale was that cancelling isn't an action <beuno> so a link is more representitive of what actually happens <beuno> as well as making it harder for you to mis-click cancel <beuno> because submit and cancel are so different

* When choosing "Translations are enabled on the upstream project." (or negative equivalent) to change it, The "title" of the box is "Usage settings", which gives me no clue about what I'm changing. I mean, usage of what? Bug 758852

• Linked branch should look like lp://qastaging/gwibber/1.0, rather than ~gwibber-committers/gwibber/2.0, because we always link to branches using the former Bug 758857

• AJAX overlay says "Select productseries" in "No upstream project series has

  • been linked" <https://translations.qastaging.launchpad.net/ubuntu/natty/+source/gwibber/+sharing-details> https://bugs.launchpad.net/launchpad/+bug/758845

* http://ubuntuone.com/p/mFG/ Two messages contradicting each other at https://translations.qastaging.launchpad.net/ubuntu/natty/+source/gnuhello/+sharing-details

• XXX: https://bugs.launchpad.net/launchpad/+bug/758883 needs reproducing instructions

• In the "Automatic synchronization of translations is not enabled" option, choosing the "import template files" doesn't work and there's no feedback message telling why it didn't work. Choosing "import template files and translation files" works. This happened with the ~gwibber-committers/gwibber/2.0 upstream branch linked. Bug 758896

  • OOPS-1928QS216 unlink package association in +remove-packaging page Bug 758902

• Non-default way of showing error in https://translations.qastaging.launchpad.net/ubuntu/natty/+source/gwibber/+remove-packaging when there's no packaging link Bug 758904

  • Go to https://translations.qastaging.launchpad.net/ubuntu/natty/+source/gnuhello/+sharing-details Edit the upstream source branch. You'll get an overlay called "Select translation branch". Type in the name of the branch currently selected, hit "Enter" and then select the only branch that comes up. You will get a 412 Precondition failed error. Bug 758919

    • Should handle the 412 when setting this again, not notify on it (discard if it's the same branch?)

• There should be something on the page (spinner?) informing the action is being processed, after choosing an option in the automatic syncronization settings because there is a delay before the action takes affect Bug 758922

  • Submit button on AJAX overlays doesn't say what it's submitting, for "Import settings" and "Usage settings" Bug 758929

• When adding an upstream link right after an unlinking, it links successfully with the green glowing AJAX, but the unlinking message doesn't disappear ("Removed upstream association between something series and Natty."). This happens to all "permanent" messages. Bug 758976

Recommendations

• Short recommendation that describes the outcome, rather than the implementation detail.
• Consider things that would make testing easier.