The idea to join forces makes sense on many levels, not only financially as the development teams would share costs of the required infrastructure, but also legally and maybe also when it comes to support and development as well.
The last information from the Thunderbird team about the split dates back to October 2016. Back then, prospective new homes were still evaluated. Also, the same could become true for add-ons as Thunderbird and SeaMonkey might join forces there as well (plus Instabird). It could mean that both teams join forces when it comes to creating the infrastructure needed to maintain, build and offer SeaMonkey and Thunderbird. We might be able to share costs by sharing on add-ons site for both or even all three comm-central applications (Instantbird]. SeaMonkey Council is looking into setting up a separate add-ons site for SeaMonkey extensions.This might fix our problem with lack of builders and our PERMA-CLOSED trees due to this lack. Rkent - Thunderbird leader - would like SeaMonkey to join Thunderbird in this move.You find the following information under planning: It was abandoned (not released) and then rewritten by Mozilla. Netscape Communicator 5 was coordinated by Mozilla.
SEAMONKEY THUNDERBIRD SCREENSHOTS CODE
It's email/news client was based on the same code that was later on used by SeaMonkey and Thunderbird. Thunderbird supports using POP and IMAP mail servers for fetching/reading new messages. Your search results are displayed in a tab so you can easily switch back and forth to your search results and other email. Thunderbird also indexes all of your emails and chat conversations to help you search even faster. SeaMonkey, another project that depends highly on Mozilla's infrastructure and code, faces similar issues. Discontinued Beonex Communicator was a sibling of Netscape Communicator. This article was written for Thunderbird but also applies to Mozilla Suite / SeaMonkey (though some menu sequences may differ). The search interface in Thunderbird contains filtering and timeline tools to pinpoint the exact email you’re looking for. Mozilla stated back then that it would support the Thunderbird team financially, with resources required for the separation, and with legal advice.Ī recent status meeting of the SeaMonkey team suggests that Thunderbird could join forces with SeaMonkey when it comes to that move. In short, cutting the ties would certainly be disruptive to Thunderbird and its development, but it would be beneficial to Mozilla and the Thunderbird team in the long run.
SEAMONKEY THUNDERBIRD SCREENSHOTS UPDATE
Thunderbird developers on the other hand had to update the email program more frequently ever since Mozilla switched to the rapid release cycle, and spent most of the resources on that, and only what remained on bug fixes and light feature enhancements. Mozilla's core reason for doing so at the time was that Firefox developers were held back because they had to make sure that nothing would be introduced during development of the browser that would render the email client Thunderbird inoperable. Mozilla announced back in December 2015 that it wants to cut the tie to Thunderbird completely.
0 kommentar(er)
