How to resolve a mentored developer doc request

Sometimes, when a reader finds a problem with content on MDN, they submit a Developer Documentation Request in Mozilla's Bugzilla. You can help improve MDN by fixing the problem and closing the request.

Where does this need to be done?

You can find a list of MDN bugs on BugsAhoy. All issues in Bugzilla are called "bugs", even if they are enhancement requests or ideas for new material or features. The bugs on this list are issues that have been judged to be good for first-time contributors to MDN, and have been assigned a mentor who can give you guidance and advice in resolving the issue.

What do you need to know to do the task?

You need to be familiar with the topic of the request that you select to work on. Being somewhat familiar with editing on MDN and with using Bugzilla is helpful.

What are the steps?

1. Select a request that looks interesting to you, and is within your realm of knowledge. It's OK to pick something you don't know completely, as long as you reasonably expect to learn what is needed along the way.
2. Carefully read the request to make sure that you understand what is requested. Also, notice the name or names listed in the Mentors field. A mentor is someone who has committed to helping someone like you work on the request.
3. If you haven't already done so, create an account on Bugzilla.
4. If you've decided to work on the request, assign the request to yourself: Click the "take" link next to the Assigned To field (which fills in your name and email address in the field), and then click the Save Changes button. The mentor or mentors get notified that you've taken ownership of the request.
5. Work on fulfilling the request by doing whatever is needed on MDN. Add comments to the request if you need to ask questions of the mentor. It's a good idea to ask the mentor to review your work when you're basically finished with it.
6. When you and the mentor agree that the request has been fulfilled, change the Status to RESOLVED, and the resolution to FIXED, and click Save Changes.

That's it! Congratulations on fixing a documentation bug!