Difference between revisions of "Category:Feature Requests"

Filing Feature Requests

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 in JIRA Bug Tracker.

Implementing Feature Requests

If you are a developer looking for ways to contribute, you can find ideas on a JIRA Meta Issue VWR-1577 which is intended to collect issues that lend themselves to be solved through open source contributions. Another source of inspiration would be the JIRA report Unresolved Feature Requests .

Whenever you are planning to work on a feature, make sure you bring it up on the SLDev mailing list. By engaging with the community, you'll get a better idea about whether your feature implementation will be accepted into the main codebase, you'll get ideas about how to make it more likely that your code will be accepted, and you might find developers willing to collaborate with you on the implementation.

See also: Category:Design Discussions, Category:Bounties , LSL_Useful_Function_WishList .

Refining Feature Requests

Features are more likely to get implemented if the description of the feature is clear. For a complicated feature, a link to a specification on the wiki is a great way to help flesh out the idea. Articles in this category should be well developed and should be a secondary resource for feature requests already in JIRA. Make sure that after you create a feature request article, you add the Category:Feature Requests to the article so that it displays on this page.

Tracking New Features that you are working on

Linden Lab allows developers who have signed a contribution agreement to assign tasks in the public JIRA, so if you are working on a new feature and have signed an agreement, put it out on the JIRA and set its status to "In Progress" so others can keep track of what is being worked on. Feel free to pick up any Open requests or issues as well.

You don't automatically get permissions on the public JIRA when you sign the agreement.

• The Contrib-Agreement group in the public JIRA entitles you to certain permissions. The main permission you are granted is the power to assign a JIRA task. Please note the following about your permissions:
  • These permissions were introduced so that Open Source Contributors could assign JIRA tasks to themselves in order to show that work is in progress. Assigning an issue to yourself will inform Lindens and your peers of that work in progress or your forthcoming contribution.
  • Don't assign tasks to anyone without their consent.
  • These permissions would allow you to assign tasks to Lindens.
  • Please don't assign things directly to Lindens unless the person in question has specifically requested it.
  • To get added to the group: sign a contribution agreement, then file a request in JIRA under WEB/jira.secondlife.com to be added to the dropdown list.