new jira category: SCRIPT

https://jira.secondlife.com/browse/WEB-153

There are well over 100 (possibly over 200) script/language related bugs/feature requests scattered in each of the other categories, with many dozens of duplicate suggestions/bug reports. jira should have a separate category for these with sub-categories related to the main LSL categories listed on the LSL wiki. This will make it easier to track old bugs/feature requests and avoid duplicates.

The correct category for scripts is in SVC (Second Life Service). It would be nice for some sub-categories, but I think that's a perfectly good place to put them.

All very well, but there are currently TWO sub-categories for scripts:

SVC=> Scripting
VWR=>Scripting

and many dozens of bug-fixes and feature requests for scripting appear in MISC.


Put scripting in its own category at the top with SVC, VWR, WEB and MISC and let the gods (Linden) decide what they are related to. Right now, there are duplicate requests in all three so you have to hunt in 3 different places for scripting-related bugs and features in order to avoid duplicates and in order to vote.

Since scripting is such an important issue, it should be factored into its own category, even though it overlaps with everything else.

For example, SVC=scripting is the largest category in SVC anyway. It makes no sense to have 3 different places to target scripting-related issues in jira when it is such a huge category. Give SCRIPT its own top-level category and create sub-categories. This will allow both the users and the LIndens to submit and track the scripting issues more effectively.

I realize it is hard to get people excited about a bug-fix for how to categorize bugs, but this is a biggie. You can't find duplicates without a LOT of work if the bug/feature is found in 3 different categories. And there are a LOT of duplicates of both bug reports for LSL and of suggestions for extending the language in some way. If all the duplicate suggestions for language suggestions were counted as votes, some language extensions might have 10 or more votes in them, which might put them amongst the top-10 most wanted features.


https://jira.secondlife.com/browse/WEB-153

SVC-Scripts is for actual changes to scripting, new functions etc.
VWR-Scripts I don't see why they added (I don't remember seeing it) but it would presumably only be relevant for the actual script-tools. e.g if you want it to allow block-indenting or something.

The whole purpose of categories is to describe what actual project something is relevant to. A new script function is only relevant to the service/server code since that's where they run and operate.

No, the whole purpose of categories in jira is to help the submitter find a logical place to put them. If you were to consolidate all scripting related issues in a top-level SCRIPT category, it would be larger than the rest of SVC and it would be obvious to bug-reporters/suggesters where it would go.

Internally, LL can track it how they want, but jira is supposed to be the place to SUBMIT bugs/reature-requests and it should make it as easy as possible to do so.

Having a single sub-category in SVC that is (or would be if anyone knew about it) larger than the rest of SVC shows a flaw in their category design.

But scripting is a major part of the service they offer, all it really shows is that people using the Jira are more interested in new features or bugs with scripts rather than teleporting (which isn't an especially broad category) and so-on.

If you look at the JIRA, the thing is organised into projects, and the categories within that allow you to decide what your issue has an actual, real effect on. It's a very good way of organising it as it makes it a lot easier for the Lindens to know where they should be looking for things to work on/fix as they will be assigned to these various projects, and in tasks covering one or more of the categories within them.

Yes scripting is a big category, but it is in the project to which it belongs, and if 90% of that project's issues happen to be scripting related then that just means that that's what we (the Jira uses) believe that project should focus on.

Just like how a lot of bugs now could be about Windlight, we don't need a separate Windlight project, just perhaps a sub-category of graphics to keep it in. Currently we do have a special version for it, but Windlight could be we with us for another 20 versions or more (for example) so it's not version specific, as it's going to become a feature of the graphics.

But when we submit 200 bugs/suggestions in a sub-category, and only 100 bugs/suggestions i all other sub-categories combined, this is a clue that the sub-category should have its own top-level access, even if the LINDENS process it as part of SVC

No it isn't. We don't /have/ sub-categories, all we have are categories within specific projects/applications. Some categories are always going to be larger than others, the proportion is irrelevant. Making scripting into a project just results in us having 100% of a project as scripting issues, while currently have a more useful figure of (if your numbers are correct) 66% of the service having script issues. It shows quite nicely that full two-thirds of the community interests in the servers are scripting related, and while that does not mean they should focus two-thirds of their service project group(s) on it (as there are issues the community wants fixed but don't know a lot about, such as load-balancing, network specifics etc.), it does show them where more work is needed.

This is a user issue, not one for LInden's internal assessment. If LL wants to lump all scripting issues under SVC internally, fine, but USERS obviously are having a hard time figuring out where to put suggestions/bug-fixes about scripting or they wouldn't put so many into MISC.