Proposing a feature

This page contains instructions about how to use the Issue Tracker to propose features or enhancements to the Imprudence Viewer software, Kokua Viewer software, or any part of our website. Separate instructions are available for reporting a bug.

What is a feature proposal?
A feature proposal is a proposal, suggestion, or request to change the intended look or behavior of our software (the Imprudence Viewer, Kokua Viewer, or our website). For the purposes of the issue tracker, the term "feature" includes new features (tools or abilities of the software) as well as improvements, enhancements, and changes to existing features.

If the software is behaving contrary to how we intended it, telling us so that we can fix the software to match our intentions is considered a bug report, not a feature proposal.

Search for existing proposals
Before you file a new feature proposal, please check to make sure that someone hasn't already proposed the same thing. If it has already been proposed, you should not file a new proposal. Instead, update the existing issue to add a comment, attach a file, or change the issue properties to provide additional information or ideas.

You can browse the lists of current issues (i.e. both bug reports and feature proposals) here:


 * List of current Imprudence Viewer issues
 * List of current Kokua Viewer issues
 * List of current Website issues

You can search for existing issues by typing search terms into the Search box at the top right hand side of the issues tracker page, then pressing the Enter key.

Create a new issue
Before you can create a new issue, you must register for the issue tracker and sign in.

There are three "projects" on our issue tracker. It is important to create the new issue in the correct project:


 * Create a new Imprudence Viewer issue - for issues related the Imprudence Viewer software
 * Create a new Kokua Viewer issue - for issues related the Kokua Viewer software
 * Create a new Website issue - for issues related to any part of our website, including the blog, forums, wiki, issue tracker, mailing lists, etc.

The form has many issue properties to fill out. These details help us understand the bug so we can fix it. So, it is important that you fill them out correctly, and provide an appropriate amount of detail.

Note: depending on your issue tracker account permissions, you might not be able to see or set some of these properties.

(To be written...)

Description
(To be written...)

Category
The list of available categories for a feature proposal varies depending on which issue tracker project you are reporting for:

Imprudence Viewer project

 * Avatar: Proposals related to avatar rendering, customization, etc.
 * Building (Prims): Proposals related to inworld building, the prim building/editing interface, etc.
 * Camera: Proposals related to the 3D camera, camera controls, etc.
 * Chat/IM: Proposals related to chat, group chat, IMs, etc.
 * Compiling: Proposals related to compiling the Imprudence Viewer itself.
 * Draft: Proposals that are still works in progress or need more feedback, and don't fit into a more specific category.
 * Debugging: Proposals related to debugging the viewer code.
 * Economy: Proposals related to money, shopping, land sales/purchases, etc.
 * Import/Export: Proposals related to the Content Backup features.
 * Improvement: Proposals related to improving existing features, that don't fit into a more specific category.
 * Inventory: Proposals related to the inventory UI, inventory loss, giving or receiving inventory, etc.
 * Inworld Audio: Proposals related to inworld sound effects (not streams or voice chat).
 * Linux: Proposals that only affect Linux, and don't fit into a more specific category.
 * Localization: Proposals related to localization and translation of the viewer.
 * Login/logout: Proposals related to logging in or out of the viewer.
 * Mac: Proposals that only affect Mac, and don't fit into a more specific category.
 * Meta-Issue: This category is used for organizing groups of other issues.
 * Optimization: Proposals related to optimizing the viewer's performance.
 * Other Stuff: Proposals that don't fit into a more specific category.
 * Rendering: Proposals related to rendering, that don't fit into a more specific category.
 * Restrained Love: Proposals related to the Restrained Love/RLVa feature.
 * Scripting: Proposals related to inworld scripting and the script editor.
 * Source code: Proposals related to the Imprudence Viewer source code.
 * Spellchecking: Proposals related to the Spellchecking feature.
 * Streaming Audio/Video: Proposals related to streaming audio/video.
 * Teleport History: Proposals related to the Teleport History feature.
 * Teleporting: Proposals related to teleporting to another sim or another location in the same sim.
 * UI: Proposals related to the viewer UI, that don't fit into a more specific category.
 * Viewer Skinning: Proposals related to viewer skinning (creating the UI and UI skins).
 * Windows: Proposals that only affect Windows (operating system), and don't fit into a more specific category.

Kokua Viewer project

 * Compiling: Proposals related to compiling the Kokua Viewer itself.
 * Meta Issue: This category is used for organizing groups of other issues.
 * QA: Proposals related to Quality Assurance.
 * User Interface: Proposals related to the viewer UI, that don't fit into a more specific category.

(More categories for this project will be added in the future.)

Website project

 * App Support: Proposals related to web resources used by the viewer (login screen news bar, client tag list, default grids list, etc.)
 * Blog: Proposals related to the blog (blog.kokuaviewer.org).
 * Forums: Proposals related to the forums (forums.kokuaviewer.org).
 * Git Repositories: Proposals related to our Git repositories at GitHub.
 * Issue Tracker: Proposals related to the issue tracker (redmine.kokuaviewer.org).
 * Other/General: Proposals that don't fit into a more specific category.
 * Wiki: Proposals related to the wiki (wiki.kokuaviewer.org).