canmove, Confirmed users
2,081
edits
Contribute/Thunderbird: Difference between revisions
m
→NOTE TO PEOPLE REACHING THIS PAGE: reorder text
m (→NOTE TO PEOPLE REACHING THIS PAGE: reorder text) |
|||
| (9 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
[[Category:Contribute]] | |||
[[Category:Thunderbird]] | |||
=NOTE TO PEOPLE REACHING THIS PAGE= | |||
If you would like to help with Thunderbird, visit [[Thunderbird:Home#Contributing]]. | |||
To make a financial contribution to Thunderbird, please visit [https://donate.mozilla.org/thunderbird/about/ Donate to Thunderbird]. | |||
This rest of this page's content is from the now defunct Mozilla staff team working on Thunderbird, yet seems to rate high in web searches looking for ways to contribute to Thunderbird. | |||
=Steward= | =Steward= | ||
| Line 8: | Line 19: | ||
A: | A: | ||
* (Usul/QA) Yes. Sometimes it's a bit more complicated to figure out when they are active or not, but identifying is easy. It's around 8 persons. | |||
* (jenzed/Doc) Somewhat. On the support site, I am notified of all changes and can therefore theoretically track contributions and contributors. On the developer site (MDN), software limitations mean that I can't get notifications regarding changes to | |||
* (roland/support kb on [https://support.mozillamessaging.com/ support.mozillamessaging.com] aka "SuMoMo"and [http://getsatisfaction.com/mozilla_messaging/ Thunderbird support forum at get satisfaction]) Yes. I will attempt to identify all contributors on GS and SuMoMo and keep an up to date list starting in Q1 2012. [http://blog.mozilla.com/roland/2011/12/19/support-contributors-please-add-yorself-to-the-mozillians-directory/ I have already asked Thunderbird support contributors to sign up for the Mozillians directory]. | |||
Suggestion: Use the [http://www.mozillians.org mozillians.org contributor directory] to help. Communicate through your team's channels and encourage people to sign up and group themselves with a common team tag. If you assign a group tag to all contributors on your project, the [https://metrics.mozilla.com/pentaho/content/pentaho-cdf-dd/Render?solution=metrics2&path=mozillians&file=mozillians.wcdf Mozillians dashboard] will track the size of that group and will also allow you to easily export the contact information for group members. You can export these contacts to ensure all your contributors are signed up. | Suggestion: Use the [http://www.mozillians.org mozillians.org contributor directory] to help. Communicate through your team's channels and encourage people to sign up and group themselves with a common team tag. If you assign a group tag to all contributors on your project, the [https://metrics.mozilla.com/pentaho/content/pentaho-cdf-dd/Render?solution=metrics2&path=mozillians&file=mozillians.wcdf Mozillians dashboard] will track the size of that group and will also allow you to easily export the contact information for group members. You can export these contacts to ensure all your contributors are signed up. | ||
| Line 35: | Line 47: | ||
A: | A: | ||
* For contribution inquiries: Variable. There is a clear contribution path for docs and support (and I think QA - LUDO?). The contribution path for development is not as clear; we have some information on getting into add-on development, but it's almost hopeless for a new contributor to get involved in TB core development. (jenzed TODO: revisit developer contribution path) | * For contribution inquiries: Variable. There is a clear contribution path for docs and support (and I think QA - LUDO?). The contribution path for development is not as clear; we have some information on getting into add-on development, but it's almost hopeless for a new contributor to get involved in TB core development. (jenzed TODO: revisit developer contribution path). | ||
* For support, in Q1 I am going to ping people on Get Satisfaction who have had a good support experience with a list of five to thirty minute tasks to see if they would like to help others as they have been helped. - ROLAND | |||
Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people. | Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people. | ||
| Line 48: | Line 61: | ||
* Developer docs: I (jenzed) try to track contributions on MDN but as I said above there are software limitations that make it hard to track Thunderbird activity. | * Developer docs: I (jenzed) try to track contributions on MDN but as I said above there are software limitations that make it hard to track Thunderbird activity. | ||
* Inquiries: I (jenzed) track the number of responses to inquiries I make. I don't think this is a valuable metric, though, as there is no way to tell how many people go on to become contributors. | * Inquiries: I (jenzed) track the number of responses to inquiries I make. I don't think this is a valuable metric, though, as there is no way to tell how many people go on to become contributors. | ||
* Support on GS - For Q12012, I am going to see if we can increase the number of GS contributors (where contributor means a person who has helped solve 1 support topic) by one person per month. - ROLAND | |||
Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today. We'll work on implementing dashboards when we know what data we want. | Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today. We'll work on implementing dashboards when we know what data we want. | ||