Lab 1

Mozilla Firefox

Firefox wants 2 main types of contributions to their codebase. Fixing pet peeve, and fixing a bug. After
you’ve written your contribution, you use Phabricator to submit your code to a reviewer you select. Once
it is reviewed, you would make the changes recommended by the reviewer, and tried on their ‘try server.’
If it passed all of their automated testing, it gets merged into their main branch
(https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Introduction).

React JS

Contribution on React happens on GitHub. All changes from team members and external contributors
can send pull requests, and they have the same review process according to React’s website
(https://reactjs.org/docs/how-to-contribute.html). React apparently uses Semantic versioning, which
according to https://semver.org/ is a versioning process designed to avoid ‘dependency hell.’ All code is
to be submitted on the master branch, where it will be reviewed. Experimental and breaking changes are
gated on the master branch on a feature flag, and patch fixes are released for critical bug fixes, minor
bug fixes, and major versions.