Webdev/GetInvolved/developer.mozilla.org: Difference between revisions
(Update who to contact, Bugzilla product name) |
(Update Getting Started with current triage process) |
||
Line 9: | Line 9: | ||
We use Docker for development and deployment. Docker works reasonable well for backend development on a macOS or Linux environment. There are additional steps required for front-end development. No staff developers use Windows, and you will need previous Docker experience on Windows to get a development environment working. | We use Docker for development and deployment. Docker works reasonable well for backend development on a macOS or Linux environment. There are additional steps required for front-end development. No staff developers use Windows, and you will need previous Docker experience on Windows to get a development environment working. | ||
Staff developers are currently focused on tuning MDN for AWS and reducing existing technical debt. | We're triaging incoming bugs and legacy bugs (oldest first), and marking good first bugs by adding a mentor. We also annotate with a Level of Difficulty (<code>[lod:]</code>) and a Point system (<code>points:</code>). Smaller numbers generally mean easier issues. See the [https://docs.google.com/document/d/1h3R5v60ZXaRG4pFI5Ia2Woov-39Swda6Z5Jxp0F4GDI/edit?usp=sharing MDN Triage Process] for details. | ||
Staff developers are currently focused on tuning MDN for AWS and reducing existing technical debt. MDN has a mature codebase, and there's not much new development, which means there aren't a lot of good first bugs. We're not aware of other Mozilla projects that are in a better position for new contributors. | |||
Here's how to contribute to Kuma: | Here's how to contribute to Kuma: |
Latest revision as of 19:09, 20 February 2018
Get Involved: developer.mozilla.org (MDN)
Description
The MDN web docs is Mozilla's technical resource for web developers - containing documentation for open web technologies.
Getting Started
We use Docker for development and deployment. Docker works reasonable well for backend development on a macOS or Linux environment. There are additional steps required for front-end development. No staff developers use Windows, and you will need previous Docker experience on Windows to get a development environment working.
We're triaging incoming bugs and legacy bugs (oldest first), and marking good first bugs by adding a mentor. We also annotate with a Level of Difficulty ([lod:]
) and a Point system (points:
). Smaller numbers generally mean easier issues. See the MDN Triage Process for details.
Staff developers are currently focused on tuning MDN for AWS and reducing existing technical debt. MDN has a mature codebase, and there's not much new development, which means there aren't a lot of good first bugs. We're not aware of other Mozilla projects that are in a better position for new contributors.
Here's how to contribute to Kuma:
- Fork us on GitHub
- Read our contribution guidelines
- Install locally
- Check out the mentored bugs or contact a developer below
Contacts
- Who:
- John Whitlock @jwhitlock (jwhitlock)
- Ryan Johnson (rjohnson)
- Schalk Neethling (espressive)
- IRC: #mdndev
Mentored Bugs
These bugs are good for your first contribution to MDN code. Each bug has a mentor assigned who can help you get started.
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
PatchWelcome Bugs
These bugs are good for more advanced contributions to MDN code that will make a big impact on the site. The bug may or may not have a mentor, and it may take more work than a simple mentored bug.
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);