Good first bug - Revision history

Arai: Remove outdated download and build instructions and update the links to the latest documents

2023-05-23T23:26:58Z

Remove outdated download and build instructions and update the links to the latest documents

← Older revision		Revision as of 23:26, 23 May 2023
Line 11:		Line 11:
	There are also mentored bugs, which may be a little more difficult, but still good for beginners. Currently you can find these in Bugzilla or look for them in [https://codetribute.mozilla.org/ Codetribute].		There are also mentored bugs, which may be a little more difficult, but still good for beginners. Currently you can find these in Bugzilla or look for them in [https://codetribute.mozilla.org/ Codetribute].

	==~~But first!!~~ Set up an environment==		==Set up an environment and build==

	Download and compile Firefox. The instructions depend on your platform. Here they are:		Download and compile Firefox. The instructions depend on your platform. Here they are:

			https://firefox-source-docs.mozilla.org/setup/windows_build.html

			https://firefox-source-docs.mozilla.org/setup/macos_build.html

			https://firefox-source-docs.mozilla.org/setup/linux_build.html

			Also there's quick ref for the entire process:

	https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html		https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html
Line 19:		Line 27:
	This might take a while - perhaps a couple of hours.		This might take a while - perhaps a couple of hours.

	==~~Update to~~ the ~~latest~~ build==		==Run the local build==
	~~Before you tackle your first bug, here is a walkthrough of what you can do to set up for Firefox coding.~~

	~~Let's download the source code for Firefox.~~
	~~Run hg clone https://hg.mozilla.org/mozilla-central to get it. This is going to take a while.~~

	~~Time to build Firefox.~~
	~~Go to the new mozilla-central directory, and run ./mach build. This is going to take a very long time.~~

	Let's make sure it works!		Let's make sure it works!
	Run ./mach run ~~-P blank. If the profile manager dialog appears, create a new profile named blank and continue starting Firefox~~.		Run ./mach run.

	==Code change walkthrough: Turn your tabs green==		==Code change walkthrough: Turn your tabs green==

Emilio: DXR -> Searchfox, MDN -> FF source docs, Bugs Ahoy -> Codetribute

2021-06-23T12:53:26Z

DXR -> Searchfox, MDN -> FF source docs, Bugs Ahoy -> Codetribute

← Older revision		Revision as of 12:53, 23 June 2021
Line 3:		Line 3:
	This page will explain how to set up a development environment and start looking at the code. It has a walkthrough for you to try making a change to Firefox code on your local machine, so that you can see that change reflected in a copy of the browser.		This page will explain how to set up a development environment and start looking at the code. It has a walkthrough for you to try making a change to Firefox code on your local machine, so that you can see that change reflected in a copy of the browser.

	It may take a few hours to go through this one-time setup. Not because it's particularly hard, but because the download and build can take a while. While the build is happening, you can look at bugs in Bugzilla, or read info for developers new to Mozilla on the ~~Mozilla Developer Network.~~		It may take a few hours to go through this one-time setup. Not because it's particularly hard, but because the download and build can take a while. While the build is happening, you can look at bugs in Bugzilla, or read info for developers new to Mozilla on the [https://firefox-source-docs.mozilla.org/ docs].

	~~Build instructions for other Mozilla stuff that isn't desktop Firefox can be found here:~~

	https://~~developer~~.mozilla.org~~/en-US~~/docs~~/Developer_Guide/Build_Instructions~~

	==Good First Bugs==		==Good First Bugs==
Line 13:		Line 9:

	==Mentored Bugs==		==Mentored Bugs==
	There are also mentored bugs, which may be a little more difficult, but still good for beginners. Currently you can find these in Bugzilla or look for them in [https://~~wiki~~.mozilla.org/~~BugsAhoy Bugs Ahoy~~].		There are also mentored bugs, which may be a little more difficult, but still good for beginners. Currently you can find these in Bugzilla or look for them in [https://codetribute.mozilla.org/ Codetribute].

	==But first!! Set up an environment==		==But first!! Set up an environment==
Line 19:		Line 15:
	Download and compile Firefox. The instructions depend on your platform. Here they are:		Download and compile Firefox. The instructions depend on your platform. Here they are:

	https://~~developer~~.mozilla.org/~~en-US~~/~~docs/Simple_Firefox_build~~		https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html

	This might take a while - perhaps a couple of hours.		This might take a while - perhaps a couple of hours.

	~~If you aren't already set up as a developer, you may need to do some other things too.~~
	~~Here are the build prerequisites. There are instructions to install all the tools you will need on various operating systems in order to build Firefox.~~

	~~https://developer.mozilla.org/en-US/docs/Developer_Guide/Build_Instructions#Build_prerequisites~~

	==Update to the latest build==		==Update to the latest build==
Line 49:		Line 40:
	HINT: It might be tempting to look at searchbar.css, but that only styles the small input bar where you can quickly access major search enginges. You should look at browser.css, which contains the styling rules for the majority of the Firefox user interface.		HINT: It might be tempting to look at searchbar.css, but that only styles the small input bar where you can quickly access major search enginges. You should look at browser.css, which contains the styling rules for the majority of the Firefox user interface.

	===Use ~~DXR~~===		===Use Searchfox===

	It turns out that browser.css has a lot of rules in it. Let's narrow down the actual rule we want to change.		It turns out that browser.css has a lot of rules in it. Let's narrow down the actual rule we want to change.

	It's time to use [https://~~dxr.mozilla~~.org/ ~~DXR~~], the Mozilla Cross Reference tool. You can search for "browser.css" and take a look through the results; see if any of the files that show up look like good candidates!		It's time to use [https://searchfox.org/ Searchfox], the Mozilla Cross Reference tool. You can search for "browser.css" and take a look through the results; see if any of the files that show up look like good candidates!

	HINT: You can focus on ~~XUL and XML~~ files, which are used to define Firefox's user interface. Often, CSS files share filenames with the files that they are styling - in this case, browser.~~xul~~ looks like a good match.		HINT: You can focus on XHTML files, which are used to define Firefox's user interface. Often, CSS files share filenames with the files that they are styling - in this case, browser.xhtml looks like a good match.

	===Search for keywords===		===Search for keywords===
	browser.~~xul~~ is a pretty big file, so it's usually best to search for keywords to find relevant parts. In this case, try searching for "tab" and see if you come across anything useful (such as a class or id attribute). If you do, see whether you can find the selector in browser.css.		browser.xhtml is a pretty big file, so it's usually best to search for keywords to find relevant parts. In this case, try searching for "tab" and see if you come across anything useful (such as a class or id attribute). If you do, see whether you can find the selector in browser.css.

	HINT: In your search, you should come across a <tabs> element that represents the tabs in Firefox's interface. Everything you need can be found there, since it has a <tab> child with a class attribute that is present in browser.css.		HINT: In your search, you should come across a <tabs> element that represents the tabs in Firefox's interface. Everything you need can be found there, since it has a <tab> child with a class attribute that is present in browser.css.

Emilio: Update IRC link to point to matrix instead.

2021-06-23T12:47:45Z

Update IRC link to point to matrix instead.

← Older revision		Revision as of 12:47, 23 June 2021
Line 72:		Line 72:
	If this didn't work:		If this didn't work:

	Please visit [~~irc~~://~~irc~~.mozilla.org/introduction #introduction] on ~~irc~~.mozilla.org and explain the problem you're having.		Please visit [https://chat.mozilla.org/#/room/#introduction:mozilla.org #introduction] on chat.mozilla.org and explain the problem you're having.



	''hat tip to http://www.joshmatthews.net/trainingmontage/''		''hat tip to http://www.joshmatthews.net/trainingmontage/''

Dao at 07:40, 30 March 2017

2017-03-30T07:40:19Z

← Older revision		Revision as of 07:40, 30 March 2017
Line 10:		Line 10:

	==Good First Bugs==		==Good First Bugs==
	You can find good first bugs in bugzilla.mozilla.org, that have been tagged "good first bug" in the ~~whiteboard~~ field.		You can find good first bugs in bugzilla.mozilla.org, that have been tagged '''good-first-bug''' in the keyword field.

	==Mentored Bugs==		==Mentored Bugs==

Towkir: /* Help! */

2016-07-21T18:08:28Z

Help!

← Older revision		Revision as of 18:08, 21 July 2016
Line 69:		Line 69:
	When this is finished, run the local Firefox build and see whether your changes worked!		When this is finished, run the local Firefox build and see whether your changes worked!

	==~~Halp~~!==		==Help!==
	If this didn't work:		If this didn't work:

Timdream: MXR -> DXR

2016-07-20T06:18:06Z

MXR -> DXR

← Older revision		Revision as of 06:18, 20 July 2016
Line 49:		Line 49:
	HINT: It might be tempting to look at searchbar.css, but that only styles the small input bar where you can quickly access major search enginges. You should look at browser.css, which contains the styling rules for the majority of the Firefox user interface.		HINT: It might be tempting to look at searchbar.css, but that only styles the small input bar where you can quickly access major search enginges. You should look at browser.css, which contains the styling rules for the majority of the Firefox user interface.

	===Use ~~MXR~~===		===Use DXR===

	It turns out that browser.css has a lot of rules in it. Let's narrow down the actual rule we want to change.		It turns out that browser.css has a lot of rules in it. Let's narrow down the actual rule we want to change.

	It's time to use ~~MXR~~, the Mozilla Cross Reference tool. You can search for "browser.css" and take a look through the results; see if any of the files that show up look like good candidates!		It's time to use [https://dxr.mozilla.org/ DXR], the Mozilla Cross Reference tool. You can search for "browser.css" and take a look through the results; see if any of the files that show up look like good candidates!

	HINT: You can focus on XUL and XML files, which are used to define Firefox's user interface. Often, CSS files share filenames with the files that they are styling - in this case, browser.xul looks like a good match.		HINT: You can focus on XUL and XML files, which are used to define Firefox's user interface. Often, CSS files share filenames with the files that they are styling - in this case, browser.xul looks like a good match.

NicolasWeb: added a link to the #introduction IRC channel

2015-02-18T19:08:53Z

added a link to the #introduction IRC channel

← Older revision		Revision as of 19:08, 18 February 2015
Line 72:		Line 72:
	If this didn't work:		If this didn't work:

	Please visit #introduction on irc.mozilla.org and explain the problem you're having.		Please visit [irc://irc.mozilla.org/introduction #introduction] on irc.mozilla.org and explain the problem you're having.



	''hat tip to http://www.joshmatthews.net/trainingmontage/''		''hat tip to http://www.joshmatthews.net/trainingmontage/''

Mw22: /* Mentored Bugs */

2014-08-21T15:00:58Z

Mentored Bugs

← Older revision		Revision as of 15:00, 21 August 2014
Line 13:		Line 13:

	==Mentored Bugs==		==Mentored Bugs==
	There are also mentored bugs, which may be a little more difficult, but still good for beginners. Currently you can find these in Bugzilla or look for them in [https://wiki.mozilla.org/BugsAhoy Bugs Ahoy]].		There are also mentored bugs, which may be a little more difficult, but still good for beginners. Currently you can find these in Bugzilla or look for them in [https://wiki.mozilla.org/BugsAhoy Bugs Ahoy].

	==But first!! Set up an environment==		==But first!! Set up an environment==

Mw22: /* Mentored Bugs */

2014-08-21T15:00:48Z

Mentored Bugs

← Older revision		Revision as of 15:00, 21 August 2014
Line 13:		Line 13:

	==Mentored Bugs==		==Mentored Bugs==
	There are also mentored bugs, which may be a little more difficult, but still good for beginners. Currently you can find these in Bugzilla or look for them in [[https://wiki.mozilla.org/BugsAhoy \| Bugs Ahoy]].		There are also mentored bugs, which may be a little more difficult, but still good for beginners. Currently you can find these in Bugzilla or look for them in [https://wiki.mozilla.org/BugsAhoy Bugs Ahoy]].

	==But first!! Set up an environment==		==But first!! Set up an environment==

Mw22: /* Mentored Bugs */

2014-08-21T15:00:30Z

Mentored Bugs

← Older revision		Revision as of 15:00, 21 August 2014
Line 13:		Line 13:

	==Mentored Bugs==		==Mentored Bugs==
	There are also mentored bugs, which may be a little more difficult, but still good for beginners. Currently you can find these in Bugzilla or look for them in [~~url=~~https://wiki.mozilla.org/BugsAhoy]Bugs Ahoy~~[/url~~].		There are also mentored bugs, which may be a little more difficult, but still good for beginners. Currently you can find these in Bugzilla or look for them in [[https://wiki.mozilla.org/BugsAhoy \| Bugs Ahoy]].

	==But first!! Set up an environment==		==But first!! Set up an environment==