82
edits
(5 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
==Introduction:== | ==Introduction:== | ||
This report was compiled from hundreds of comments, ideas and suggestions made to various web blogs, wikis and mailing lists, due to the recent [http://weblogs.mozillazine.org/mitchell/archives/2007/07/email_futures.html Email call to action] by Mitchell Baker. It aims to provide an overview of the information we found important, ordered by feasibility and relevance, with possible suggestions for a future road map and plan for the Thunderbird mail application and possible revenue schemes and targets. | This report was compiled from hundreds of comments, ideas and suggestions made to various web blogs, wikis and mailing lists, due to the recent [http://weblogs.mozillazine.org/mitchell/archives/2007/07/email_futures.html Email call to action] by [http://weblogs.mozillazine.org/mitchell/ Mitchell Baker]. It aims to provide an overview of the information we found important, ordered by feasibility and relevance, with possible suggestions for a future road map and plan for the Thunderbird mail application and possible revenue schemes and targets. | ||
It takes into account current limitations such as a limited team of lead developers (2) and the current focus and attention of MoCo on the Firefox browser. The report is intended to be helpful in the decision making process of an eventual organizational change. | It takes into account current limitations such as a limited team of lead developers (2) and the current focus and attention of MoCo on the Firefox browser. The report is intended to be helpful in the decision making process of an eventual organizational change and defining the future of [http://www.mozilla.com/en-US/thunderbird/ Thunderbird]. | ||
Thanks to many contributors for this collaborative work! | Thanks to many contributors for this collaborative work! | ||
Line 87: | Line 87: | ||
==Summary and Recommendations:== | ==Summary and Recommendations:== | ||
These are conclusions and recommendations of this report: | These are the conclusions and recommendations of this report: | ||
* Defining of a road map is essential to describing current and future needs. The road map should reflect the targets as seen in this report, in respect to features, revenues and higher involvement by volunteers. | * Defining of a road map is essential to describing current and future needs. The road map should reflect the targets as seen in this report, in respect to features, revenues and higher involvement by volunteers. | ||
Line 97: | Line 97: | ||
* A team should be formed for the supervision of the project and implementation of the road map. It would be responsible for the development process and contacts with software vendors. It would preform actions to increase involvement by development volunteers as outlined in the report. | * A team should be formed for the supervision of the project and implementation of the road map. It would be responsible for the development process and contacts with software vendors. It would preform actions to increase involvement by development volunteers as outlined in the report. | ||
* Form an Evangelist Team to do the marketing studies and search for revenues. The team would also take action to increase involvement by volunteers. | * Form an Evangelist Team to do the marketing studies and search for revenues. The team would also take action to increase involvement by volunteers. The team Will need support of PR and Business specialists to capitalize on there expertise. | ||
== | ==Authors:== | ||
[[User:Eddyn|Eddyn]] 05:49, 4 August 2007 (PDT)<br> | [[User:Eddyn|Eddyn]] 05:49, 4 August 2007 (PDT)<br> | ||
[[User:Killjay|Ron K.]] 12:35, 4 August 2007 (PDT)<br> | [[User:Killjay|Ron K.]] 12:35, 4 August 2007 (PDT)<br> | ||
[[User:Mohamed samy|Mohamed samy]] 17:20, 4 August 2007 (PDT) | [[User:Mohamed samy|Mohamed samy]] 17:20, 4 August 2007 (PDT) |
edits