Confirmed users
139
edits
Line 10: | Line 10: | ||
It can be difficult to know how to recognize contributors, particularly when you've been working with someone for months or years. Repeating the same form of recognition over and over loses its impact over time. This toolkit will help demystify some of the things that Mozilla uses for recognition as well as inspire new forms of culturally and individually appropriate recognition. | It can be difficult to know how to recognize contributors, particularly when you've been working with someone for months or years. Repeating the same form of recognition over and over loses its impact over time. This toolkit will help demystify some of the things that Mozilla uses for recognition as well as inspire new forms of culturally and individually appropriate recognition. | ||
Another way to know is to use Mozillians. There is a new function on Mozillians that will allow you to see how contributors like to be recognized. Please refer to the function when recognizing in conjunction with this toolkit. | Another way to know is to use Mozillians. There is a new function on Mozillians that will allow you to see how contributors like to be recognized. Please refer to the function when recognizing in conjunction with this toolkit. (This function is currently in production and we will update with a link to screen shots when it's completed.) | ||
You should always check in with people to make sure that they want to be publicly recognized. Best practices should be built within teams and communities revolving around the needs of your individual contributors. | You should always check in with people to make sure that they want to be publicly recognized. Best practices should be built within teams and communities revolving around the needs of your individual contributors. |