Agenda

I propose Frank-Rainer Grahl who's been doing a lot of testing and bug reporting on Windows recently, mostly on own-compiled W64 builds; also some bug fixing. Any seconds? — Tonymec (talk) 10:32, 26 December 2015 (PST)

Seconded by Ratty and IanN

Action Items

(who needs to do what that hasn't been recorded in a bug)
We should assign people to the open items.

NEW

—

OPEN

Need to port Sync 1.5 to SeaMonkey - IanN has spoken briefly to ewong about options, Ratty might be able to help too.

bug 1198340 The carousel within Add-On Manager can be used for SeaMonkey specific content. TO DO: Find out what sort of format AMO needs for the carousel. Get our webdev person to create necessary content. Submit content for upload to AMO.

Unfortunately nobody knows exactly how addons.mozilla.works because there's no full time developer working on AMO. Ratty was given bug 1009759 as an example. So now we need someone who knows python+django.

There are also some upcoming changes to L10n build system in Q1 2015 (bug 1107635).

Buildmaster is up and running, and produces en-US builds, see 9/16 meeting's Friends of the Fish Tank. Builds and langpacks in 18 languages including en-US are available unofficially thanks to A.Kalla.

Extensions and Plugins Compatibility Tracking

Lightning button icons are not shown on the mail-toolbox making them invisible. Fixed in bug 1223898 but we should consider moving the CSS from suite to Lighting.

We are looking for a new place to host the Addon Compatibility Listings for the Add-on Converter in order to make it easy to maintain and to serve as the main database for the AMO browsing extension in the future. The details are in this post.

Firefox & Thunderbird Add-on Converter for SeaMonkeyhttp://addonconverter.fotokraina.com/This tool goes a little further beyond simply modifying install.rdf - it also identifies a few more other things in the code that are Firefox or Thunderbird specific and attempts to change them. Of course, not all extensions can be ported so easily to SeaMonkey since there's only so much an automated tool like that can do.

Lemon Juice continues to improve his already impressive Addon Converter. The source is now available on GitHub [1].

looking for a better(?) home for extension-converter pages, along with a way to track successful and conversion-failed add-ons, and respective integration into SeaMonkey by add-on or manager overlay [2], bug 1145026.

Rainer Bielefeld will no longer update the list of Firefox addons that have been successfully converted by the Addon Converter. -- Rrbd (talk) 09:59, 16 August 2015 (PDT)

2.40

2.Next

We have official permission to use the Firefox FxA 2.0 sync servers! We need someone to work on porting sync 2.0 over to replace legacy sync code. The finer details of how are so far unknown, but we should have a usable solution before legacy sync is turned off. See: New Firefox Sync has landed in Firefox Nightly. Tracked in:

Ratty restored about:privatebrowsing UI to before it was messed up by Project Chameleon styles [bug 1192276]. Subsequent to Chameleon, Firefox developers have again redesigned the about:privatebrowsing UI to include UI for tracking protection. We should look into picking any changes we like.

may prohibit Modern theme being shipped with or installed in SeaMonkey

removal is "decided" without any clear alternative envisioned

IanN thinks it would be useful to remind people on the newsgroups / forums that they can contribute by triaging. Tonymec will post a reminder to newsgroups / forums. See bug 1092632(Sm_tri_HowTo) Document how to triage SeaMonkey bugs.

bug 1127784 added a preference and UI to enable/disable playback of Encrypted Media Extensions, with UI seen in non-release builds only

more work appears to be needed to download necessary 3rd-party Content Decryption Modules, some UI can probably be ported from Firefox

What about declaring linux-x86_64 builds found at seamonkey-project.org and at ftp.m.o as "official" ?

On October 7 two people asked in #seamonkey at a few minutes' interval when there would be "official" 64-bit SM builds for Linux. I pointed them to the x86_64 release at the bottom of the "Other languages" release page for 2.38 and to the x86_64 2.40a2 aurora & 2.41a1 trunk builds at the bottom of the ftp.m.o nightly/latest-comm-* pages but they said these were not "official".

So — how are we going to get out of the following vicious circle? 64-bit builds are not "official" because too few users, and users don't install them (some even prefer compiling their own) because they aren't "official".

[IanN] The tagging has fixed the issue for chatzilla before 2.41 but more is needed for 2.41 and above?

[frg] Yes. The optional language xpi will not compile in 2.41 and is broken in 2.42 and up. install.rdf missing. The main xpi is fine.

[IanN] Can you spin a bug off with the steps to generate the optional language xpi for 2.41 along with any errors, similarly another one for 2.42 and up. If it ends up being the same fix, not a problem, bugs are cheap. just cc me.

[IanN] Ratty: do we need to start looking at how to overlay Chatzilla and DOMi on top of the TB's new merged (c-c + m-c) repository?

[Ratty] Not sure. I hope we can continue doing what we have been doing using nested repositories. However in the new merged repository. The comm-central client.py is replaced by the mozilla-central client.py so I don't know how this will work.

[IanN] Merging DOMi into comm-central would make SeaMonkey releases easier. We just need to sort out locale building for DOMi.

Roundtable - Personal Status Updates

Status Updates from developers - what are you working on, what's the progress, any other comments? (feel free to add yourself to the list if your name is missing and you have interesting status).

bug 1101381 Printing throws error: DEPRECATION WARNING: getWebBrowserPrint is now deprecated, and fully unsupported for multi-process browsers. Please use a frame script to get access to nsIWebBrowserPrint from content