MozillaWiki

SeaMonkey/StatusMeetings/2015-02-17: Difference between revisions

Page Discussion

SeaMonkey/StatusMeetings/2015-02-17 (view source)

Revision as of 13:48, 17 March 2015

843 bytes added ,  17 March 2015
→‎Feature List, Planning
(My cat is sad because I didn't pick any Smiths or Leonard Cohen for this top ten)
 
(5 intermediate revisions by 2 users not shown)
Line 61: Line 61:
* See [[SeaMonkey/StatusMeetings/Basics|Basics]] page. Please only list current changes here.
* See [[SeaMonkey/StatusMeetings/Basics|Basics]] page. Please only list current changes here.
* [[SeaMonkey/AddonCompat|Addon Compatibility Listings]]
* [[SeaMonkey/AddonCompat|Addon Compatibility Listings]]
* '''AMO and addon-signing. All addons will have to be signed, uploaded to AMO then reviewed by AMO editors including extensions not hosted on AMO. Otherwise they'll be disabled'''. Discussion in [https://groups.google.com/forum/#!forum/mozilla.addons.user-experience mozilla.addons.user-experience]
* '''AMO and addon-signing. All addons will have to be signed, uploaded to AMO then reviewed by AMO editors including extensions not hosted on AMO. Otherwise they'll be disabled'''. '''TL;DR: SeaMonkey and Thunderbird will not implement mandatory extension signing'''. Discussion in [https://groups.google.com/forum/#!forum/mozilla.addons.user-experience mozilla.addons.user-experience]
** Tracking bugs:  {{bug|1047239}}, {{bug|1070152}}, {{bug|1070153}}; Wiki: [[AMO/SigningService]]  
** Tracking bugs:  {{bug|1047239}}, {{bug|1070152}}, {{bug|1070153}}; Wiki: [[AMO/SigningService]]  
** [Ratty] According to jorgev there will be some sort of build time switch. SeaMonkey users will be disproportionately affected as they use orphaned extensions or modified Firefox/Thunderbird extensions via the ''xSidebar Project'' or the ''Firefox & Thunderbird Add-on Converter for SeaMonkey''. We should disable this check in our releases.
** [Ratty] According to jorgev there will be some sort of build time switch. SeaMonkey users will be disproportionately affected as they use orphaned extensions or modified Firefox/Thunderbird extensions via the ''xSidebar Project'' or the ''Firefox & Thunderbird Add-on Converter for SeaMonkey''. We should disable this check in our releases.
Line 67: Line 67:
** Lemon Juice started a MozillaZine thread in the SeaMonkey Builds forum which by now migrated into the general Extension Dev forum (73 replies). [http://forums.mozillazine.org/viewtopic.php?f=19&t=2907359]
** Lemon Juice started a MozillaZine thread in the SeaMonkey Builds forum which by now migrated into the general Extension Dev forum (73 replies). [http://forums.mozillazine.org/viewtopic.php?f=19&t=2907359]
* '''Firefox & Thunderbird Add-on Converter for SeaMonkey''' [http://addonconverter.fotokraina.com/ http://addonconverter.fotokraina.com/]<br>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.
* '''Firefox & Thunderbird Add-on Converter for SeaMonkey''' [http://addonconverter.fotokraina.com/ http://addonconverter.fotokraina.com/]<br>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.
** !This item should be moved to somewhere more permanent and discoverable! Ratty proposed a link on the front page of [http://www.seamonkey-project.org/ http://www.seamonkey-project.org/] posibly near the "Add-ons" navigation item. Also ask Lemon Juice to put his list of successful conversions somewhere on his site.
** Ratty filed {{Bug|1130390}} to add a link on [http://www.seamonkey-project.org/ seamonkey-projects.org] to the Firefox & Thunderbird Add-on Converter for SeaMonkey.
* Lightning 3.7b1 builds for SM 2.32 release have been released on AMO, en-US only, using old tinderbox builds [http://forums.mozillazine.org/viewtopic.php?f=46&t=2905997].
* Lightning 3.8b1 builds are available for SeaMonkey 2.33.
* The Thunderbird team is planning to ship Lightning with Thunderbird. IanN thinks we will want to ship lightning too. We should coordinate with Thunderbird.
* The Thunderbird team is planning to ship Lightning with Thunderbird. IanN thinks we will want to ship lightning too. We should coordinate with Thunderbird. Related bugs:
** {{Bug|1130854}} Package Lightning with Thunderbird for c-c and c-a builds.
** {{Bug|1113183}} Integrate Lightning Into Thunderbird by Default.
** {{Bug|1130852}} Add opt-in dialog to promote Calendar integration [Thunderbird].
* Proposed replacement for Venkman for shipping with SeaMonkey: [https://addons.mozilla.org/seamonkey/addon/tiny-javascript-debugger/  Tiny JavaScript Debugger]. TinyJSD is a JavaScript debugger for privileged code running Mozilla products like Firefox, Thunderbird, SeaMonkey. It serves to debug the application as well as extensions written in JavaScript.
* Proposed replacement for Venkman for shipping with SeaMonkey: [https://addons.mozilla.org/seamonkey/addon/tiny-javascript-debugger/  Tiny JavaScript Debugger]. TinyJSD is a JavaScript debugger for privileged code running Mozilla products like Firefox, Thunderbird, SeaMonkey. It serves to debug the application as well as extensions written in JavaScript.
** Consensus is that we should ship TJSD as a replacement for Venkman. The next step is to contact the author.
** IanN filed {{Bug|1133723}} Investigate options for replacing Venkman with the TinyJSDebugger.
* Our build team needs to automate DOMI branch selection rather than having to tweak the client.py every 6 weeks. {{Bug|763506}}
* Our build team needs to automate DOMI branch selection rather than having to tweak the client.py every 6 weeks. {{Bug|763506}}


=== 2.x (Last, Current, Next) ===
=== 2.x (Last, Current, Next) ===
* SeaMonkey Statistics can be viewed at [https://dataviz.mozilla.org/t/public/views/SeamonkeyADI/VersionChannelADI?:embed=y#1 https://dataviz.mozilla.org] Across all channels we have an approximate ADU of 120k.
* SeaMonkey Statistics can be viewed at [https://dataviz.mozilla.org/t/public/views/SeamonkeyADI/VersionChannelADI?:embed=y#1 https://dataviz.mozilla.org] Across all channels we have an approximate ADU of 120k.
** Ratty suggests embedding these graphs somewhere on [http://www.seamonkey-project.org/ seamonkey-projects.org] or [https://dev.seamonkey.at/ https://dev.seamonkey.at]
** {{Bug|1133728}} Look at embedding dataviz information into the SeaMonkey website.
<!--* 2.16 had ~X ADU by Tuesday 12th March and has had ~Y downloads so far.
<!--* 2.16 had ~X ADU by Tuesday 12th March and has had ~Y downloads so far.
** Of the released versions, as of Tuesday 12th March, we have A% on 2.0, B% on 2.1-2.3, C% on 2.4-2.6, D% on 2.7-2.9, E% on 2.10-2.12, F% on 2.13, G% on 2.14, H% on 2.15 and I% on 2.16.-->
** Of the released versions, as of Tuesday 12th March, we have A% on 2.0, B% on 2.1-2.3, C% on 2.4-2.6, D% on 2.7-2.9, E% on 2.10-2.12, F% on 2.13, G% on 2.14, H% on 2.15 and I% on 2.16.-->
Line 113: Line 118:
*** {{Bug|998807}} Sync account creation or device pairing fails with exception in BrowserIDManager.
*** {{Bug|998807}} Sync account creation or device pairing fails with exception in BrowserIDManager.
*** {{Bug|1003434}} Add support for about:sync-progress.
*** {{Bug|1003434}} Add support for about:sync-progress.
*** '''Update''' SeaMonkey won't be allowed to use the Firefox Sync 1.5 servers. Need to look into the possibility of hosting our own servers on a community machine or VPS.
** A lot of these bugs are due to mozilla-central switching from synchronous APIs to Asynchronous APIs.
** A lot of these bugs are due to mozilla-central switching from synchronous APIs to Asynchronous APIs.
** {{Bug|566746}} (asyncFormHistory) Form history should use asynchronous storage API. Tracked in:
** {{Bug|566746}} (asyncFormHistory) Form history should use asynchronous storage API. Tracked in:
Line 136: Line 142:
* See [[SeaMonkey/StatusMeetings/FeatureList|Feature List]] page for major wanted/needed features.
* See [[SeaMonkey/StatusMeetings/FeatureList|Feature List]] page for major wanted/needed features.
*'''TODO:''' We will need to update our Sync UI code due to the new Sync API. Also we need to check if we are allowed to create FX accounts from our UI Since the new Sync accounts are FX accounts.[IanN] I'm sure I saw a question about FX accounts and branding. Callek was going to ask about being able to use Firefox accounts.
*'''TODO:''' We will need to update our Sync UI code due to the new Sync API. Also we need to check if we are allowed to create FX accounts from our UI Since the new Sync accounts are FX accounts.[IanN] I'm sure I saw a question about FX accounts and branding. Callek was going to ask about being able to use Firefox accounts.
(Note: SeaMonkey cannot use FxA. If and when they allow 'other' projects to use FxA, we can't use it.)


=== Roundtable - Personal Status Updates ===
=== Roundtable - Personal Status Updates ===
Line 178: Line 185:
==== Mnyromyr ====
==== Mnyromyr ====
==== Neil ====
==== Neil ====
Working on:
* {{Bug|1133582}} Warning box in about:config doesn't display properly in Modern any more.
* {{Bug|1133380}} about:privatebrowsing doesn't display properly in Classic any more.
Still waiting for review:
* {{Bug|970993}} Aero Peek rendering issues.
==== Px ====
==== Px ====
==== Ratty ====
==== Ratty ====
Ewong
Confirmed users
2,078

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/1056439...1062435"