Difference between revisions of "Feature Requests"
m (Replace Jira with feedback.secondlife.com) |
|||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
Do you have suggestions for a new or enhanced feature? We're always looking for new ideas. Please let us know what you would like to see done. | Do you have suggestions for a new or enhanced feature? We're always looking for new ideas. Please let us know what you would like to see done. | ||
The best place for your feature requests to get noticed is | The best place for your feature requests to get noticed is [https://feedback.secondlife.com feedback.secondlife.com]. | ||
{{TOCright}} | {{TOCright}} | ||
| Line 26: | Line 26: | ||
* The request will introduce security issues. | * The request will introduce security issues. | ||
* Scope of work is too great. | * Scope of work is too great. | ||
== Feature Contributions == | |||
For features that can be implemented entirely (or even mostly) in the Viewer, it may be that the best way to get it done is to become (or work with) an open source contributor to make the change. See [[Feature Contributions]]. | |||
[[Category:Bug Tracker]] | [[Category:Bug Tracker]] | ||
Latest revision as of 00:53, 27 January 2024
Do you have suggestions for a new or enhanced feature? We're always looking for new ideas. Please let us know what you would like to see done.
The best place for your feature requests to get noticed is feedback.secondlife.com.
How to Write a great Feature Request
- Tell us about the specific functionality you're hoping to see. Describe both the current behavior and desired behavior in as much detail as possible.
- Provide Supporting Materials. This can be done with snapshots, videos, example code, etc. Again, the more information you provide, the better!
- What are the benefits of your Feature?
What Happens Next
Once your Feature Request has been submitted, it will join the queue for a team of Lindens to review. Please be patient... Depending on the nature of your request, it may require members of multiple teams to review.
Why wasn't my Feature Request Accepted?
Please be reassured this isn't personal! We understand, and appreciate, that you put a lot of thought into these proposals, and we consider them seriously. Some feature requests we simply cannot do. Here are some of the reasons why:
- Our internal architecture doesn't allow it.
- It will break existing content.
- It is not scalable.
- The request will introduce security issues.
- Scope of work is too great.
Feature Contributions
For features that can be implemented entirely (or even mostly) in the Viewer, it may be that the best way to get it done is to become (or work with) an open source contributor to make the change. See Feature Contributions.