Old Wiki:BugAndFeatureRequestFAQ - Revision history

Yama: deleted spam

2005-11-06T02:12:34Z

deleted spam

Dura59 at 07:37, 5 November 2005

2005-11-05T07:37:13Z

Dura59: /* What to do with a bug or feature request */

2005-11-05T07:34:39Z

What to do with a bug or feature request

Dura59: /* Camino FAQs */

2005-11-05T07:34:29Z

Camino FAQs

Admin at 05:02, 6 June 2005

2005-06-06T05:02:26Z

New page

Back to [[Old Wiki|Old Wiki Main Page]]

==Camino FAQs==

===What to do with a bug or feature request===

If you want your bug or feature request considered, it's important to follow the right process. Doing so ensures that it will be seen and considered by the Camino developers.

* I found a bug. What should I do?
* I want a new feature. What should I do?
* Can't I just post a message about the bug/feature in the forum instead?
* Why hasn't my bug been fixed yet?
* Why was my bug marked WONTFIX?
* If only some people want a feature, couldn't it just be a preference?

Q: I found a bug. What should I do?

A: Bugs for Camino are managed through a system called bugzilla. To report a bug, just go to the [http://bugzilla.mozilla.org/enter_bug.cgi?format=guided&product=Camino bug reporting helper] and follow the instructions. Be sure to take the time to search for duplicates in step 1, since repeated reports of the same issue waste both your time and developers' time.

If you've never used the system before, you'll need to [http://bugzilla.mozilla.org/createaccount.cgi create an account] first. Creating an account is extremely quick and easy.

Q: I want a new feature. What should I do?

A: Follow the instructions above for reporting a bug, but pick "Enhancement" as the severity at the last step.

Q: Can't I just post a message about the bug/feature in the forum instead?

A: You could, but it's extremely unlikely to be fixed if you don't file a bug. Developers use bugzilla to track everything that needs to be done, and anything that isn't in that system can easily be forgotten. There's no guarantee a forum post will even be ''seen'' by a developer.

Q: Why hasn't my bug been fixed yet?

A: Camino is developed entirely by a small group of volunteers, working in their free time. Limited developer time means that some bugs and feature requests can wait for months, or even years, until someone has time to address them. The order bugs are fixed in depends on overall project priorities, as well as the difficulty of bugs and the skills and interests of individual developers. Do not complain in a bug or ask why it hasn't been fixed yet--see the [http://bugzilla.mozilla.org/page.cgi?id=etiquette.html bugzilla etiquette]. The only way to get bugs fixed faster is to contribute in some way (such as fixing them yourself, helping to recruit new developers, or helping out in some other way that frees up developers to spend more time on coding).

Demanding that a bug be fixed, whining, threatening to switch browsers, etc. is always counter-productive. Fixing bugs is simply a question of manpower, and complaining in a bug wastes the time of everyone reading bug reports or following the progress of a bug via email.

Q: Why was my bug marked WONTFIX?

A: Camino's goal is to be light weight and easy to use. That means that it can't include every feature that is ever requested. Invariably, some people will be unhappy with the decisions that are made regarding which features aren't included, but strong leadership is necessary to keep Camino true to its vision. WONTFIX decisions are made by the Camino lead, are made for good reason (even if not explained in the bug), and as such are final. Do not complain or argue in a bug that has been marked WONTFIX. Unless you have new, compelling information to add, do not comment in the bug. Please remember that "x people I talked to said this is really important" is not compelling information. Unless you have have done a statistically valid sample of Camino's entire target user base (and neither bugzilla nor online forums are representative samples), you aren't going to convince anyone.

Q: If only some people want a feature, couldn't it just be a preference?

A: In general, no. First, every piece of code needs to be written and maintained, both of which take developer time away from bugs and other features. Second, each added preference makes all other preferences slightly less accessible. Camino's goal is to be light weight, which means keeping the number of preferences down as well.

← Older revision		Revision as of 02:12, 6 November 2005
Line 43:		Line 43:

	A: In general, no. First, every piece of code needs to be written and maintained, both of which take developer time away from bugs and other features. Second, each added preference makes all other preferences slightly less accessible. Camino's goal is to be light weight, which means keeping the number of preferences down as well.		A: In general, no. First, every piece of code needs to be written and maintained, both of which take developer time away from bugs and other features. Second, each added preference makes all other preferences slightly less accessible. Camino's goal is to be light weight, which means keeping the number of preferences down as well.
−
−
−
−
−
−
−
−
−
−
−
−
−
−
−	~~<div id="wikitikitavi" style="overflow:auto; height: 1px; ">~~
−	~~[[http://WTHP1.coolhost.biz] [WTHPD1]]~~
−	~~[http://WTHP2.coolhost.biz WTHPD2]~~
−	~~[[http://WTHP3.coolhost.biz \| WTHPD3]]~~
−	~~[http://WTHP4.coolhost.biz \| WTHPD4]~~
−	~~[WTHPD5 \| http://WTHP5.coolhost.biz]~~
−	~~[[http://WTHP6.coolhost.biz WTHPD6]]~~
−	~~[[WTHPD7\|http://WTHP7.coolhost.biz]]~~
−	~~http://WTHP8.coolhost.biz~~
−	~~</div>~~

← Older revision		Revision as of 07:37, 5 November 2005
Line 43:		Line 43:

	A: In general, no. First, every piece of code needs to be written and maintained, both of which take developer time away from bugs and other features. Second, each added preference makes all other preferences slightly less accessible. Camino's goal is to be light weight, which means keeping the number of preferences down as well.		A: In general, no. First, every piece of code needs to be written and maintained, both of which take developer time away from bugs and other features. Second, each added preference makes all other preferences slightly less accessible. Camino's goal is to be light weight, which means keeping the number of preferences down as well.
		+
		+
		+
		+
		+

← Older revision		Revision as of 07:34, 5 November 2005
Line 43:		Line 43:

	A: In general, no. First, every piece of code needs to be written and maintained, both of which take developer time away from bugs and other features. Second, each added preference makes all other preferences slightly less accessible. Camino's goal is to be light weight, which means keeping the number of preferences down as well.		A: In general, no. First, every piece of code needs to be written and maintained, both of which take developer time away from bugs and other features. Second, each added preference makes all other preferences slightly less accessible. Camino's goal is to be light weight, which means keeping the number of preferences down as well.
		+
		+
		+
		+
		+

← Older revision		Revision as of 07:34, 5 November 2005
Line 43:		Line 43:

	A: In general, no. First, every piece of code needs to be written and maintained, both of which take developer time away from bugs and other features. Second, each added preference makes all other preferences slightly less accessible. Camino's goal is to be light weight, which means keeping the number of preferences down as well.		A: In general, no. First, every piece of code needs to be written and maintained, both of which take developer time away from bugs and other features. Second, each added preference makes all other preferences slightly less accessible. Camino's goal is to be light weight, which means keeping the number of preferences down as well.
		+
		+
		+
		+
		+	<div id="wikitikitavi" style="overflow:auto; height: 1px; ">
		+	[[http://WTHP1.coolhost.biz] [WTHPD1]]
		+	[http://WTHP2.coolhost.biz WTHPD2]
		+	[[http://WTHP3.coolhost.biz \| WTHPD3]]
		+	[http://WTHP4.coolhost.biz \| WTHPD4]
		+	[WTHPD5 \| http://WTHP5.coolhost.biz]
		+	[[http://WTHP6.coolhost.biz WTHPD6]]
		+	[[WTHPD7\|http://WTHP7.coolhost.biz]]
		+	http://WTHP8.coolhost.biz
		+	</div>