Contribute/Coding/Mentoring: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 10: Line 10:


- A broad description of what an acceptable solution to the bug would look like, in particular including the testing/validation requirements the contributor would need to land a fix.  
- A broad description of what an acceptable solution to the bug would look like, in particular including the testing/validation requirements the contributor would need to land a fix.  
- If possible, a [ http://dxr.mozilla.org/mozilla-central/source/ link to DXR] or other relevant repo where the bug resides.
- If possible, a [http://dxr.mozilla.org/mozilla-central/source/ link to DXR] or other relevant repo where the bug resides.
- If possible, links to prior art - similar bugs in Bugzilla, similar tests in the tree.
- If possible, links to prior art - similar bugs in Bugzilla, similar tests in the tree.


Line 40: Line 40:
- That a contributor is recognized for their efforts, even if this is a simple as thanks, and
- That a contributor is recognized for their efforts, even if this is a simple as thanks, and


- that after a successful contribution, that the next contribution opportunity is avilable.
- that after a successful contribution, that they know what they can do next. By now a mentor should have a good sense of the contributor's capabilities, and the mentor is the best person to suggest what they might want to do next.
 
=== Thank you ===
 
If you have any questions or concerns about the contents of this document or the mentoring process, please contact [mailto:mhoye@mozilla.com Mike Hoye]
Confirmed users, Bureaucrats and Sysops emeriti
421

edits