Bug triage/UI Agenda

Next meeting: 2007-10-30, 10am PDT at Benjamin Linden's office. See Bug triage for details.

Fast Track Import

(Move bugs here that have solid repros, or valid patches that you have reviewed)

Misc Pool

• VWR-2872 - Votes: 0 - Clicking on an event link on the map popups a search with the wrong event information - marceledward edman

Feature Request

• VWR-1607 - Votes: 45 - Ability to log out back to the welcome / log in screen instead of having to quit - Davey Callisto
• VWR-1927 - Votes: 35 - Preferences: Add the ability to customize display fonts - Odysseus Fairymeadow
• VWR-2249 - Votes: 29 - Sculpted Prims (Sculpties/Sculptys) Level of Detail (LoD) Should be Able to be Set by the Client in Preferences Window - Miller Rust
• VWR-468 - Votes: 26 - Allow login as "invisible to all" from the login window - StarSong Bright
• VWR-220 - Votes: 15 - Inventory tab enhancements - Argent Stonecutter
• VWR-1066 - Votes: 12 - Save screenshots in any other image format than bitmap - Yuukie Onmura
• VWR-1163 - Votes: 12 - Friends Categories - instead of using multiple normal groups - Smiley Barry
• VWR-394 - Votes: 11 - LSL function to access the HTML floater for more capable dialogs. - Argent Stonecutter
• VWR-328 - Votes: 10 - Turn off voice dots above the user's head. - Catherine Omega

Transcript

Transcript is/will be at Bug triage/UI Agenda/Transcript

Creating An Agenda

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