The new Waze Wiki, aka Wazeopedia, is now live at Wazeopedia.waze.com! While this legacy wiki will remain accessible for the time being, it is no longer updated by the community. For the most up-to-date guidance, please visit your local Wazeopedia.

Please do not make any more updates to these legacy wiki pages, all future updates should be made in your country's local Wazeopedia.

Clock over a larger globe

Difference between revisions of "Bugzilla"

From waze
Jump to: navigation, search
Line 26: Line 26:
 
**Experts
 
**Experts
 
**Editor/App beta-testers
 
**Editor/App beta-testers
 +
 +
===Voting===
 +
Votes are your method to express your concerns.
 +
We deeply care about the concerns of our community, we consider the vote count, but can not always fit our development to it.
 +
There are other things we are forced to consider such as development dependencies, infrastructure issues, business development, things that are easier / harder to develop, etc.
 +
 
==Bug Submitters==
 
==Bug Submitters==
 
Bug Submitters have permission to post <u>new</u> bugs and are hand-picked by Waze.
 
Bug Submitters have permission to post <u>new</u> bugs and are hand-picked by Waze.
 +
 +
==How to be helpful==
 +
*Vote on what you think are the most pressing issues we need to address.
 +
*Comment with helpful information:
 +
**Bugs - ways to reproduce them, description of environments in which they occur, examples.
 +
**Requirements - specific use cases which are difficult to perform with the current implementation.
 +
 +
==How to be unhelpful==
 +
*Add comments with irrelevant information such as off-topic reproduction of other issues, requests, opinions, social interaction, etc. The forums are there for all these things.
 +
*Ask the experts to create new bugs that are duplicates of currently existing bugs.
 +
  
 
=Public Products=
 
=Public Products=
 
App (
 
App (

Revision as of 13:57, 3 June 2013

Bugzilla is an external bug tracking system used internally by Waze technical teams.

Waze Bugzilla is partially open to the community with different access level permissions in order to make the status of bugs and feature requests visible.

Structure

Waze Bugzilla is divided to two main classifications:

  1. Internal - accessible to Waze staff only
  2. Public - accessible to all with different permission levels

Each classification contains different products. There are two public products, each of them also having corresponding products in the internal part as well.

Permissions

View only

Everyone can access most of the public bugs in view mode with no need to login.

Comment & Vote

This permission level requires a login. A login requires submitting an application.

  • At this time, only the following will be eligible for a login:
    • Champs
    • Experts
    • Editor/App beta-testers

Voting

Votes are your method to express your concerns. We deeply care about the concerns of our community, we consider the vote count, but can not always fit our development to it. There are other things we are forced to consider such as development dependencies, infrastructure issues, business development, things that are easier / harder to develop, etc.

Bug Submitters

Bug Submitters have permission to post new bugs and are hand-picked by Waze.

How to be helpful

  • Vote on what you think are the most pressing issues we need to address.
  • Comment with helpful information:
    • Bugs - ways to reproduce them, description of environments in which they occur, examples.
    • Requirements - specific use cases which are difficult to perform with the current implementation.

How to be unhelpful

  • Add comments with irrelevant information such as off-topic reproduction of other issues, requests, opinions, social interaction, etc. The forums are there for all these things.
  • Ask the experts to create new bugs that are duplicates of currently existing bugs.


Public Products

App (