mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-16 14:55:47 +00:00
c7e21b65bc
A frequent question when mentoring new contributors is what "your mozconfig file" is. By suggesting to create the file if it does not exist, we can hopefully alleviate some new contributor frustration. This change does unfortunately not take into account that the mozconfig file can be named .mozconfig or even be in a designated location defined by the MOZCONFIG environment variable, but it seems reasonable to assume that developers who already know about those alternatives will know which file to edit, and that what we should optimise for during the bootstrapping process is to get new contributors up and running quickly. |
||
|---|---|---|
| .. | ||
| devtools/migrate-l10n | ||
| docs | ||
| l10n/fluent_migrations | ||
| mach | ||
| mozboot | ||
| mozbuild | ||
| mozlint | ||
| mozrelease | ||
| mozterm | ||
| mozversioncontrol | ||
| safety | ||
| mach_commands.py | ||
| moz.build | ||
| README | ||
This directory contains common Python code. The basic rule is that if Python code is cross-module (that's "module" in the Mozilla meaning - as in "module ownership") and is MPL-compatible, it should go here. What should not go here: * Vendored python modules (use third_party/python instead) * Python that is not MPL-compatible (see other-licenses/) * Python that has good reason to remain close to its "owning" (Mozilla) module (e.g. it is only being consumed from there). Historical information can be found at https://bugzilla.mozilla.org/show_bug.cgi?id=775243 https://bugzilla.mozilla.org/show_bug.cgi?id=1346025