Confirmed users
656
edits
Line 43: | Line 43: | ||
* Working in the open can take some getting used to, especially when you feel like everything is new. Don't be afraid to expose your weaknesses or say you don't know something. You will not encounter negative feedback for such honesty. | * Working in the open can take some getting used to, especially when you feel like everything is new. Don't be afraid to expose your weaknesses or say you don't know something. You will not encounter negative feedback for such honesty. | ||
* Expect that your work will be critiqued and often rejected. This is normal, and it happens to even the most seasoned contributors. Working in a collaborative open source project the size of Mozilla means making compromises, adjusting to meet other people's needs, and improving what you thought was good until it's great. | * Expect that your work will be critiqued and often rejected. This is normal, and it happens to even the most seasoned contributors. The reasons are technical, not personal, and they are usually something you can fix. Having to do half-a-dozen versions of a patch before getting it accepted is not uncommon, and in no way an embarrassment. Working in a collaborative open source project the size of Mozilla means making compromises, adjusting to meet other people's needs, and improving what you thought was good until it's great. | ||
* When you pick a project, speak to someone in Mozilla Education in order to let them know. This way you can get the bug assigned to you, we can remove it from the list, and make sure you are connected to the right people. | * When you pick a project, speak to someone in Mozilla Education in order to let them know. This way you can get the bug assigned to you, we can remove it from the list, and make sure you are connected to the right people. |