112
edits
Thunderbird/July2012AndBeyond: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 39: | Line 39: | ||
It also struck me that I forgot to mention that having a Thunderbird<->Gaia email sync ought to be a major goal. | It also struck me that I forgot to mention that having a Thunderbird<->Gaia email sync ought to be a major goal. | ||
eric Moore | eric Moore - | ||
The proposal doesn't address several issues such as who will maintain the ISP database, and what happens to account provisioning (is anybody left authorized to sign contracts with new email providers?). | The proposal doesn't address several issues such as | ||
- who will maintain the ISP database, and what happens to account provisioning (is anybody left authorized to sign contracts with new email providers?). | |||
I don't see the need for security patches every six weeks for a email client. People can still safely use 2.0.0.24 if they apply common sense. The security advisories seem to deliberately inflate the impact of potential problems. I'd argue that a new release every 6 weeks actually contributes to stability problems, especially if there is no longer a QA lead. | I don't see the need for security patches every six weeks for a email client. People can still safely use 2.0.0.24 if they apply common sense. The security advisories seem to deliberately inflate the impact of potential problems. I'd argue that a new release every 6 weeks actually contributes to stability problems, especially if there is no longer a QA lead. | ||
=> Mark banner : The ISP database has at least one community member already doing reviews for new entries, I believe the reviews can be done by almost anyone with a knowledge of the APIs, but I'm sure Ben can correct me if I'm wrong. | |||
SeaMonkey is a community effort hosted by and under the legal protection of the Mozilla Foundation, with the SeaMonkey Council providing the project leadership. SeaMonkey would seem a better model than maintaining the status quo with a fraction of the existing resources. | For the server part of the ISP database, that's within Mozilla. If the GSoC student completes the work on the new ISPDB application, then that could be hosted somewhere and the ISP database run from there. | ||
Eric Moore Cont-d: SeaMonkey is a community effort hosted by and under the legal protection of the Mozilla Foundation, with the SeaMonkey Council providing the project leadership. SeaMonkey would seem a better model than maintaining the status quo with a fraction of the existing resources. | |||
Most of the Thunderbird module owners seem to be Mozilla employees. Its not clear why that would change anytime soon. I'm worried that the project will continue to pay the political cost of being a Mozilla project (many decisions dictated by what Firefox does or Mozilla's roadmaps) while losing most of its resources. That doesn't seem viable. | Most of the Thunderbird module owners seem to be Mozilla employees. Its not clear why that would change anytime soon. I'm worried that the project will continue to pay the political cost of being a Mozilla project (many decisions dictated by what Firefox does or Mozilla's roadmaps) while losing most of its resources. That doesn't seem viable. | ||
It would help if a few features developed over a long time that are near completion such as maildir support were finished and there was some sort of explicit exit criteria to have a smooth handoff rather than development ending as soon as a new governance model was established. That doesn't necessarily require more investment by Mozilla, it might be done by prioritizing what needs to get done before the transition. | It would help if a few features developed over a long time that are near completion such as maildir support were finished and there was some sort of explicit exit criteria to have a smooth handoff rather than development ending as soon as a new governance model was established. That doesn't necessarily require more investment by Mozilla, it might be done by prioritizing what needs to get done before the transition. | ||
https://wiki.mozilla.org/Features/Thunderbird | https://wiki.mozilla.org/Features/Thunderbird | ||
| Line 57: | Line 60: | ||
Users want a product that is under active development and has a future, even if they don't really care about the new features or get annoyed by some of the changes. I suspect many users will interpret the re-focusing of efforts as Mozilla abandoning Thunderbird, and will look for alternative email clients since they don't perceive the community as providing enough development. I think there would have been a much better reaction if Mozilla had announced they were reducing staffing levels (there were only two full time employees for a good while) but would continue new development at a slower pace. | Users want a product that is under active development and has a future, even if they don't really care about the new features or get annoyed by some of the changes. I suspect many users will interpret the re-focusing of efforts as Mozilla abandoning Thunderbird, and will look for alternative email clients since they don't perceive the community as providing enough development. I think there would have been a much better reaction if Mozilla had announced they were reducing staffing levels (there were only two full time employees for a good while) but would continue new development at a slower pace. | ||
Ludo: Yes it would be nice to have and probably have a sort of roadmap so people who want to participate might get ideas on what needs to be worked on. | |||