2018 SL UG updates #3/3: Web User Group

Grumpity and Alexa Linden host the Web User Group meetings on alternate Fridays at Alexa’s barn.

The following notes are taken from the Web User Group meeting held on Friday, December 19th, 2017. These meetings are generally held on alternate Fridays, and chaired by Alexa and Grumpity Linden at Alexa’s barn. The focus is the Lab’s web properties, which include the Second Life website (including the blogs, Destination Guide, Maps, Search, the Knowledge base, etc.), Place Pages, Landing Pages (and join flow for sign-ups), the Marketplace, and so on and the Lab’s own website at lindenlab.com.

Not all of these topics will be discussed at every meeting, however, the intention within the group is to gain feedback on the web properties, pain points, etc., and as such is very much led by comments and input from those attending. Along with this are two points of note:

  • Specific bugs within any web property  – be it Marketplace, forums, Place Pages or anything else), or any specific feature request for a web property should be made via the Second Life JIRA.
  • Alex Linden provides routine updates on the Lab’s SL-facing web properties as and when appropriate, which can be found in the Second Life Web thread.
  • Note that the SL forums are not covered by the Web User Group, as the management of functionality of the forums falls under the remit of the Support Team.

Lindens in the Web Team

A number of Lindens attend the Web User Group meetings in addition to Grumpity and Alexa (who are part of the Second Life Product team). While they may not be present at every meeting, Lindens staff directly involved in supporting the SL web services include:

  • Spidey Linden: QA Lead for SL Web and Marketplace.
  • Shrike Linden:  a QA tester on the Second Life web team.
  • Nazz Linden: a web developer who has thus far primarily worked on secondlife.com and the Place Pages.
  • Natty Linden: a web developer with a focus on the Marketplace.
  • Sherbert Linden: a web developer working on various SL web properties.

Support Portal Migration

Some people have reported that their support ticket histories are no longer intact. This may be a result of the ongoing migration of data from the old support system to the new system (see here and here for more).  If there are specific tickets raised prior to the start of 2017 people need to view, a new support ticket, including details of the ticket which needs to be viewed, should be raised, and the support team should be able to access the old ticket and provide any information on it.

360-Snapshot Viewer

Currently a project viewer (version 5.1.0.506743 at the time of writing), this is still in the process of being updated to offer higher resolution 360-degree images taken in Second Life, and for the uploading of 360 images to Place Pages (as well as the other viewer snapshot upload options).

Feature Requests

Feature requests are suggestions forwarded to the Lab on ideas and improvements which might be added / made to Second Life. They are raised via the Second Life JIRA:

  • Go to the SL JIRA – you may have to log-in.
  • Once logged-in to your Dashboard, click ob Create Issue (top right of the window).
  • A pop-up Create Issue form is displayed.
  • Click on the right of the Issue Type box on the form to display a drop-down, and select New Feature Request.
  • When filing a feature request, give as much information as clearly and concisely as possible: what the feature request is, what it is for, why it should be considered beneficial, what it might help improve, how it might work, etc., – as these things apply.
  • If you are requesting a UI change to the viewer, and can include images of proposed changes or new floaters / panels the feature would require, be sure to attach them.
Filing a Feature Request via JIRA – click for full size, if required

In 2017, 383 feature requests were filed via JIRA. Of these, 167 (roughly 43%) were accepted by Linden Lab for transfer into their internal JIRA system. It’s not clear how many of the accepted items were eventually actioned, but the figures nevertheless show that feature requests are triaged and some are taken for current or future consideration and possible implementation at a later date.

 

 

Advertisements

Have any thoughts?

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.