Tuesday, August 2, 2011
This cycle I’m spending some of my time on a project outside the translations world: working with the awesome Web Design Team on a portal to attract and make it easy for developers to create and publish lightweight applications for Ubuntu.
As part of this work, we’ll be doing some user research on the 10th and 11th of August at the Canonical office in London, and we are looking for app developers to interview there.
If you think you meet the following criteria or if you know of anyone who does, we’d like to hear from you! We’re looking for someone who:
- Must not be employed as an app developer, but may be employed in a technical role.
- Develops at night or on weekends – hobbyist, not professional
- Must be interested in developing apps.
- The platform does not matter.
- Must be familiar with the concept of open source development.
- The participants will receive a cash incentive of £60 on the day of the session.
- Travel expenses will not be covered
- The research is to help validate our initial concept for one our current projects – developer.ubuntu.com.
If you know of anyone, please get in touch directly with Ellen Arnold, who coordinates the recruitment of testers for this project.
Thanks a lot!
Friday, March 18, 2011
We’ve just uploaded fresh language packs in the maverick-proposed repository for testers to check before they are released to all users. These should contain all updates and fixes in translations done since the last language pack update.
I’d like to ask for your help in testing them and in providing an indication that the test has been done. You can do this very easily by following the instructions here:
The deadline for the testing is the 25th of March (in a week’s time). After that, we’ll update the language packs we’ve received feedback for into maverick-updates, so that all users can benefit from the new translations and fixes.
Remember that you’ll have to enable the maverick-proposed repository to start testing. Here’s how:
Remember that now you can subscribe to the iCal feed to stay up to date with language pack updates and better coordinate your work if you are a translator:
Notice that as commented on the translators mailing list recently, we’ve experienced
bug 731298. This bug has now been fixed, but for those of you using the language packs PPA, please remember to follow Martin Pitt‘s advice to purge and reinstall the packages for a proper fix:
Note that I can’t automatically fix packages for people who already upgraded to the broken PPA version; they will need to purge the packages (-base as well) and reinstall them.
If you are not using the language packs PPA, you shouldn’t need to worry about this.
Wednesday, February 24, 2010
This cycle we have a brand new set of localization test cases for everyone to check and make sure language support in Lucid is top notch, and we need your help!
Here’s how you can contribute; the procedure for testing is very easy, and it involves:
- Signing up – create an account at the ISO testing tracker and log in
- Running the test cases – run the localization test cases following the given steps
- Reporting – report on them (pass/fail, comments, bugs, etc.)
Step 1: Signing up
The first thing you’ll need is an account at the ISO Tracker, which will allow you to record your tests and their results.
You can do this by simply going to http://iso.qa.ubuntu.com/ and clicking on the Log in link at the top right-hand side of the page. Then choose the Create new account tab, enter your data, and that’s it!
Almost immediately you’ll receive an e-mail with instructions on how to do your first log in, which will simply involve logging in with the generated password, changing it, and then being ready to roll.
Step 2: Running the test cases
Once you’ve logged in with your shiny new account, you’ll have to choose the localization test cases you want to run. We’ve put them under the Desktop category, so you can simply click on any of the two Ubuntu Desktop categories, which will take you to them:
You can click on any of them and start testing straight away. Each one has a link to the steps to follow for this, which will guide you along your testing journey.
Although it is encouraged to run the test cases on real machines to test the real hardware, it might not be that applicable to localization, so you can also use a virtual machine. The ISO Testing wiki has got a wealth of information on testing procedures.
You should definitely check out and install Test Drive, which makes the procedure of downloading and testing the images in a virtual machine a bliss.
Step 3: Reporting
So at this point you’ve finished running a test case, and you are done with the hard part. But that wasn’t that hard, was it?
Now comes the important part in making your test useful for the testing team and developers: reporting on the outcome of the test.
You’ll see that below the test case you’ve just completed there are several fields to make this easier for you: you can say whether the test passed, failed, whether you have started it, etc. Other important fields are those where you can add comments and links to bugs related to this test case. If you’ve encountered a bug, you can file it against the Ubuntu Translations project in Launchpad.
You’ll find more information on the Testing space in the wiki.
That was it!
So these were the steps to help making Lucid also a solid release on translations.
If you need any help, would like to comment on the test cases, propose new ones, etc, simply get in touch with us and we’ll be more than happy to give a hand.
Let’s make Lucid translations rock!