Bug triage/Internationalization Agenda

Next meeting: not scheduled yet. See Bug triage for details.

Other Bugs

• VWR-2232 - Votes: 3 - Mac keyboard shortcuts don't respect non-QWERTY layout - Simil Miles
  • Imported
• VWR-1843 - Votes: 2 - Inappropriate default folder name for Make Outfit - Alissa Sabre
  • Imported
• VWR-1593 - Votes: 0 - Improve localisation ability of Second Life - Gudmund Shepherd
• VWR-1889 - Votes: 0 - Search in classifieds for queries with German Umlauts is not case insensitive but yields different results depending on the case of the Umlaut - Peter Stindberg
• VWR-2231 - Votes: 0 - Entire screen flashes as you type Japanese characters when in Full-screen mode on Windows - Alissa Sabre
• VWR-2204 - Votes: 0 - Geforce 8xxxM series not working with hardware check - RP Smit

Other Feature Requests

• VWR-2237 - Votes: 5 - The SL client should bundle a number of open source fonts in order to normalize the international text issues - Saijanai Kuhn
• VWR-1719 - Votes: 3 - Need for a better mechanism to add new UI translation - Alissa Sabre
• VWR-1841 - Votes: 1 - Switching of UI language requires viewer restart - Alissa Sabre
• VWR-1899 - Votes: 0 - Skin files could use ... (ellipsis) rather than ... (three full stops/periods) - Gudmund Shepherd

Pre-meeting activity

Some issues will be resolved in the course of building this agenda. Rather than deleting them from the proposed agenda, move the issue and associated discussion into the appropriate section below.

Resolved

Community members generally collaborate on the agenda for bug triage meetings. Here's how you can quickly fill in an otherwise blank agenda:

Setting up

• Go to Bug_Triage/YYYY-MM-DD where YYYY is the four digit year code, MM is the two digit month code, and DD is the day code
• Write and save {{subst:Triage Template}} as the only content of your new page. This will copy the complete markup from Template:Triage Template as a starting point for your agenda.
• Fill in the relevant time, date, and location info for the upcoming meeting. The easiest way to do this is to copy the entire block of information from an earlier meeting of the same type (RC, regular, etc...) and modify the date and time as needed.

Populating the issue listings section(s)

• Look at the results of one of these queries
  • General triage: "Viewer 2 Bug Triage" (sorted by LL ID, Created, Last Triaged):
    • https://jira.secondlife.com/secure/IssueNavigator.jspa?mode=hide&requestId=12724
  • UI triage:
    • https://jira.secondlife.com/secure/IssueNavigator.jspa?mode=hide&requestId=10470 (The selected filter with id '10470' does not exist.)

  (Note: there's no hard and fast rule that says these are the only valid queries. If you feel there's a better query one particular week, use that.)

• Save a copy of the XML version of the query
• Run this perl script on the xml file

<perl>

1. !/usr/bin/env perl

use XML::Simple;

my $bugs = XMLin($ARGV[0]);

foreach my $item (@{$bugs->{channel}->{item}}) {

 $title = $item->{title};
 $title =~ s/^\^\*\] //;
 $key = $item->{key}->{content};
 $votes = $item->{votes};
 $reporter = $item->{reporter}->{username};
 print "* $key - Votes: $votes - $title - $reporter\n";

}

</perl>

• Pick a reasonable cutoff point, and copy the output into the appropriate section of your newly created page.

• if you do not have access to a perl interpreter. There is a ported version of the script on PHP, located here: http://jirafiller.technokittydevelopment.com/ made by roberto salubrius