MozillaWiki - User contributions [en]

QA/Automation/Team

2014-09-17T21:35:06Z

Xabolcs: /* Contributors */ Szabolcs' interests

== Team ==
<onlyinclude>
The [https://mozillians.org/en-US/group/firefox-automation/ Firefox Automation team] is a group of passionate and open minded people working on automation for Firefox. We are spread around the world, but we have one collective goal to empower automation even more in the Mozilla project. If you want to get in contact with one of us please check the table below for more information.

=== The Core Team ===
{| class="wikitable fullwidth-table"
| style="background:#EFEFEF; width:20%" | '''Name'''
| style="background:#EFEFEF; width:20%" | '''IRC nickname'''
| style="background:#EFEFEF; width:60%" | '''Project Assignments'''
|-
| [https://mozillians.org/u/whimboo/ Henrik Skupin]
| :whimboo
| Team Lead - Everything related to test automation for Firefox Desktop
|-
| [https://mozillians.org/u/AndreeaMatei/ Andreea Matei]
| :AndreeaMatei
|
|-
| [https://mozillians.org/u/andrei.eftimie/ Andrei Eftimie]
| :andrei.eftimie
|
|-
| [https://mozillians.org/u/cosmin.malutan/ Cosmin Malutan]
| :cosmin.malutan
|
|-
| [https://mozillians.org/u/daniel.gherasim/ Daniel Gherasim]
| :daniel.gherasim
|
|-
| [https://mozillians.org/u/mihaelav/ Mihaela Velimiroviciu]
| :mihaelav
|
|}

=== Contributors ===
{| class="wikitable fullwidth-table"
| style="background:#EFEFEF; width:20%" | '''Name'''
| style="background:#EFEFEF; width:20%" | '''IRC nickname'''
| style="background:#EFEFEF; width:60%" | '''Interests'''
|-
| [https://mozillians.org/u/xabolcs/ Szabolcs Hubai]
| :xabolcs
| likes Nightly Tester Tools and Memchaser; knows JavaScript, want to know Python
|}

</onlyinclude>

QA/Automation/Team

2014-09-17T21:23:01Z

Xabolcs: /* Contributors */ Henrik asked me if I would like to add myself to the team. Now I'm here.

== Team ==
<onlyinclude>
The [https://mozillians.org/en-US/group/firefox-automation/ Firefox Automation team] is a group of passionate and open minded people working on automation for Firefox. We are spread around the world, but we have one collective goal to empower automation even more in the Mozilla project. If you want to get in contact with one of us please check the table below for more information.

=== The Core Team ===
{| class="wikitable fullwidth-table"
| style="background:#EFEFEF; width:20%" | '''Name'''
| style="background:#EFEFEF; width:20%" | '''IRC nickname'''
| style="background:#EFEFEF; width:60%" | '''Project Assignments'''
|-
| [https://mozillians.org/u/whimboo/ Henrik Skupin]
| :whimboo
| Team Lead - Everything related to test automation for Firefox Desktop
|-
| [https://mozillians.org/u/AndreeaMatei/ Andreea Matei]
| :AndreeaMatei
|
|-
| [https://mozillians.org/u/andrei.eftimie/ Andrei Eftimie]
| :andrei.eftimie
|
|-
| [https://mozillians.org/u/cosmin.malutan/ Cosmin Malutan]
| :cosmin.malutan
|
|-
| [https://mozillians.org/u/daniel.gherasim/ Daniel Gherasim]
| :daniel.gherasim
|
|-
| [https://mozillians.org/u/mihaelav/ Mihaela Velimiroviciu]
| :mihaelav
|
|}

=== Contributors ===
{| class="wikitable fullwidth-table"
| style="background:#EFEFEF; width:20%" | '''Name'''
| style="background:#EFEFEF; width:20%" | '''IRC nickname'''
| style="background:#EFEFEF; width:60%" | '''Project Assignments'''
|-
| [https://mozillians.org/u/xabolcs/ Szabolcs Hubai]
|
|
|}

</onlyinclude>

QA/Automation/Projects/Addons/NightlyTesterTools

2013-08-18T13:42:54Z

Xabolcs: /* Overview */ Autodetector AMO link

==Overview==

{| style="width: 100%; margin-bottom: 2em" |
| style="width: 25%" |
| style="width: 75%" |
|- valign="top"
| '''Name:'''
| Nightly Tester Tools (NTT)
|- valign="top"
| '''Leads:'''
| [mailto:hskupin@mozilla.com Henrik Skupin], [mailto:dhunt@mozilla.com Dave Hunt]
|- valign="top"
| '''Team Assistance:'''
| Tony Mechelynck, Szabolcs Hubai
|- valign="top"
| '''addons.mozilla.org:'''
| https://addons.mozilla.org/addon/nightly-tester-tools
|- valign="top"
| '''Issues:'''
| https://github.com/mozilla/nightlytt/issues
|- valign="top"
| '''Repository:'''
| https://github.com/mozilla/nightlytt
|- valign="top"
| '''Etherpad:'''
| https://etherpad.mozilla.org/qas-addons-ntt
|}

== Summary ==
[https://addons.mozilla.org/en-US/firefox/addon/6543/ Nightly Tester Tools] is an extension that is a collection of useful tools for users of Firefox nightly builds. It was previously owned by Dave Townsend, but now is maintained by the [http://wiki.mozilla.org/Auto-tools Automation and Tools team]. They're leading an effort to revive Nightly Tester Tools and make it even better.

Nightly Tester Tools features the ability to disable add-on compatibility checks, crucial for nightly testers.

Contact us on IRC via [irc://irc.mozilla.org/automation #automation].

==Development==

See https://github.com/mozilla/nightlytt/blob/master/README.md for how to get Nightly Tester Tools for desktop setup.

* Desktop Nightly Tester Tools' code lives on a [http://github.com/mozilla/nightlytt Github repo]
* Mobile Nightly Tester Tools' code lives on a [https://github.com/sammybahamas/mobi_nightlytt Github repo]

==Settings==
If you know where this extension's settings are documented, please fill it in here.

AFAIK, there is no Preferences UI for this extension in the addons manager, its settings [http://kb.mozillazine.org/Editing_configuration#Modifying_preferences must be set] directly in about:config (or in the Thunderbird Config Editor). They start with '''nightly.''' and IIUC you shouldn't change '''nightly.currChangeset''' and '''nightly.prevChangeset''' — these two are for data which the extension needs to remember from one session to the next; the others are its preferences. — [[User:Tonymec|Tonymec]] 15:47, 10 November 2011 (PST)

The following describes the known settings, but the table is not complete. If you know anything that's missing, please fill it in; if there is an error, please correct it.

* '''Note:''' In the first column, we have added a space after each dot. This is intentional; these spaces are not part of the name, they are only there to allow line-breaking in the "name" cells if necessary.

{| border=4
! Name
! Type
! Values
|-
| '''nightly. currChangeset'''
| String
|
|-
| '''nightly. disableCheckCompatibility'''
| Boolean
| true: Force add-on compatibility false (default): Opposite of the above.
|-
| '''nightly. idtitle'''
| Boolean
| true (default): Use the custom title set by '''nightly. templates. title''' false: Opposite of the above.
|-
| '''nightly. prevChangeset'''
| String
|
|-
| '''nightly. templates. buildid'''
| String
| Template for the string inserted by "Tools → Nightly Tester Tools → Copy Build ID to Clipboard" or "Tools → Nightly Tester Tools → Insert Build ID into Textbox". Default: ${UserAgent} ID:${AppBuildID}${Flags} CSet: ${Changeset}
|-
| '''nightly. templates. title'''
| String
| Template for the window title. Default: ${DefaultTitle} (Build ${AppBuildID}) '''Note:''' Used only if '''nightly. idtitle''' is on (which is the default).
|}

==Variables==
The following are for use when customizing '''nightly.templates.buildid''' and '''nightly.templates.title''' — they will be replaced at run-time by the appropriate string.
{| border=4 width=100%
! width=10% | Name
! width=10% | Value
! width=50% | Example
! width=30% | Explanation
|-
| ${DefaultTitle}
| Default Application Title
| MozillaWiki - SeaMonkey
|  
|-
| ${TabTitle}
| Current Tab's Title
| MozillaWiki
| As set by the <tt><title></tt> of the current page
|-
| ${AppId}
| Application Identifier
| {92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}
| GUID of the current application
|-
| ${Vendor}
| Application Vendor
| Mozilla
|  
|-
| ${Name}
| Application Name
| SeaMonkey
|  
|-
| ${Version}
| Application Version
| 2.20a1
|  
|-
| ${AppBuildID}
| Application Build Identifier
| 20130421003001
| Datestamp, YYYYMMDDhhmmss
|-
| ${Changeset}
| Built from that changeset
| 1637ab8d5a01
| With SeaMonkey or Thunderbird it is the '''comm-central''' (or comm-aurora, comm-beta, comm-release) changeset.
|-
| ''${PlatformChangeset}''
| ''XUL platform changeset''
| ''0d50cb959c46''
| ''Changeset for mozilla-central (or mozilla-aurora, mozilla-beta, mozilla-release). For Firefox, but not for Thunderbird or SeaMonkey, it is the same as ${Changeset} above.''
|-
| ''${GeckoChangeset}''
| ''Gecko changeset''
| ''0d50cb959c46''
| ''Same as ${PlatformChangeset}. Deprecated.''
|-
| ${PlatformBuildID}
| XUL Platform Build Identifier
| 20130421003001
| Same as ${AppBuildID} AFAICT
|-
| ${PlatformVersion}
| XUL Platform Version
| 23.0a1
| With SeaMonkey it is '''not''' the same as ${Version}.
|-
| ${GeckoVersion}
| Gecko Version
| 23.0a1
| Same as ${PlatformVersion}. ''Deprecated.''
|-
| ${BrandName}
| Application Brand Name
| SeaMonkey
| I '''think''' that for Firefox-Nightly or Thunderbird-Daily it is other than ${Name}
|-
| ${UserAgent}
| User Agent String
| Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 SeaMonkey/2.20a1
| As can be seen near the bottom of Help→About
|-
| ${Locale}
| Current locale
| en-US
|  
|-
| ${OS}
| Compilation OS
| Linux
|  
|-
| ${Processor}
| Compilation Processor
| x86_64
| ix86 means 32-bit Intel
|-
| ${Compiler}
| Compiler
| gcc3
|  
|-
| ${Toolkit}
| Graphics Toolkit
| cairo
|  
|-
| ${Profile}
| Current Profile
| default
|  
|}
* The variables described ''in italics'' are not yet supported by Nightly Tester Tools 3.5; they are slated to appear in a future release. They are more subject to change than the rest: what appears above is what is currently planned for the next release.
* The variables marked ''Deprecated'' are, well, deprecated. They may disappear at some indeterminate future time.
* The first two depend on the page you are browsing; I showed what appeared on this wiki's [[Main Page]].
* Many of these depend on your current browser or mailer version: I showed what appeared in the version of SeaMonkey with which I updated this table.
* All of these can be seen in the <tt>Tools → Nightly Tester Tools → Customize Titlebar</tt> dialog… if it is present in the current version of NTT on the current application.

==Ideas==
If you'd like to propose ideas on how to make the extension better, feel free to file a bug within [https://github.com/mozilla/nightlytt/issues/new this handy form]!

We also have a [https://github.com/mozilla/nightlytt/issues list of things to do] already filed that you can look through.

SeaMonkey/AddonCompat

2013-08-07T06:59:11Z

Xabolcs: About Startup doesn't need install.rdf addition since 0.1.8

= SeaMonkey Add-on Compatibility Tracking =

<div style="border: 2px dashed #DAA520; background-color: #FFD700; padding: 1em; margin: 1em 0;">
Starting with SeaMonkey 2.7, all add-ons that are declared compatible with at least SeaMonkey 2.1 will work out of the box ("compatible-by-default"), i.e. you do not need to install additional add-ons or change preferences to make these work. Add-ons with binary components (like Lightning and Enigmail) and special add-ons (themes, dictionaries etc.) are exceptions to the rule.
</div>

== Recent Changes to This Page ==
Please list any major changes here (latest first, max. three visible entries, max. one entry per day and contributor)

* 2012-04-07 [[User:jhatlak|InvisibleSmiley]] Moved Context Highlight to External Sources now that it is has been made compatible
* 2012-02-15 [[User:jhatlak|InvisibleSmiley]] Removed QuoteColors warning regarding MailNews status bar breakage now that a fixed version is available
* 2012-02-15 [[User:jhatlak|InvisibleSmiley]] UrlParams available from External Sources



== General Notes ==
* This Wiki replaces [https://wiki.mozilla.org/SeaMonkey/2.1/AddonCompat SeaMonkey/2.1/AddonCompat] in an attempt to make the information relevant without being tied to a specific SeaMonkey version.
* Since this is a Wiki page, anyone with an account can modify it. If you have need an add-on being checked, please add it to the Discussion page instead of this one. Thanks!
* For each add-on, only the basic functionality has been checked.
* Please don't make the below a table. The goal is to have this as short and easily editable as possible.
* "AMO" means [https://addons.mozilla.org/ addons.mozilla.org]. "xsidebar site" includes: [http://xsidebar.mozdev.org/modified.html modified] / [http://xsidebar.mozdev.org/modifiedmisc.html modifiedmisc] / [http://xsidebar.mozdev.org/modifiedmailnews.html modifiedmailnews]
* Please do not add very seldom-used add-ons, themes, dictionaries etc.
* Please double-check your findings before adding to any of the below lists.
* When adding add-ons, please check for versions in this order:
*# AMO (including experimental ones)
*# external sources (versions that work without modifications)
*# AMO versions that only need a compatibility override
*# other versions that only need a compatibility override
*# any versions that need SeaMonkey added to install.rdf
* Some add-ons might be listed as compatible at AMO but not feature compatibility in the install.rdf of the XPI file. For such add-ons, AMO sends a compatibility override signal to SeaMonkey's add-ons back-end. Affected add-ons can only be installed if either an Internet connection exists or the {{addon|add-on-compatibility-reporter|Add-on Compatibility Reporter}} add-on is installed and enabled. However, add-ons that include neither SeaMonkey nor Toolkit in their install.rdf at all cannot be installed either way ({{bug|680845}}) and need to be listed under "Needs Addition to install.rdf".

== Add-ons available from AMO, by SeaMonkey release version ==
'''Notes:'''
# Please list the highest supported full release. '''Examples:''' 2.6a2 → 2.5, 2.8a1 → 2.7.
# Please list only names (except experimental versions), since versions may change.
# If an add-on listed in this section is compatible with a previous version of SeaMonkey, you can enable it after installing the {{addon|add-on-compatibility-reporter|Add-on Compatibility Reporter}} (ACR) add-on. ''(Then be sure to check that it actually works!)''

=== 2.7 and later ===
* {{addon|about-add-ons|About Add-ons}}
* {{addon|about-startup|About Startup}} (AMO says "Compatible with SeaMonkey 2.10 and later)
* {{addon|adblock-plus|Adblock Plus}}
* {{addon|add-on-compatibility-reporter|Add-on Compatibility Reporter}}
* {{addon|addressbooks-synchronizer|Addressbooks Synchronizer}}
* {{addon|bbcodextra|BBCodeXtra}}
* {{addon|chatzilla|ChatZilla}}
* {{addon|checkplaces|CheckPlaces}}
* {{addon|classicish-addon-manager|Classicish Addon Manager}}
* {{addon|classic-firefox-theme-for-seam|Classic Firefox theme for SeaMonkey}}
* {{addon|console%C2%B2|Console²}}
* {{addon|dom-inspector-6622|DOM Inspector}}
* {{addon|downthemall|DownThemAll!}}
* {{addon|earlyblue|EarlyBlue}}
* {{addon|elemhidehelper|Element Hiding Helper for Adblock Plus}}
* {{addon|enigmail|Enigmail}} ''contains binary components''
* {{addon|event-spy|Event Spy}}
* {{addon|extension-options-menu|Extension Options Menu}}
* {{addon|find-preferences|Find Preferences}}
* {{addon|fireshot|FireShot}}
* {{addon|flagfox|Flagfox}}
* {{addon|flashgot|FlashGot}}
* {{addon|folderpane-tools|Folderpane Tools}}
* {{addon|forecastfox-weather|Forecastfox Weather}}
* {{addon|form-history-control|Form History Control}}
* {{addon|foxyproxy-standard|FoxyProxy Standard}}
* {{addon|366225|Highlighted Text To File}}
* {{addon|ie-tab-plus|IE Tab +}}
* {{addon|ie-view|IE View}}
* {{addon|inspectorwidget|Inspector Widget}}
* {{addon|javascript-debugger|JavaScript Debugger (Venkman)}}
* {{addon|download-manager|Jökulsárlón Download Manager}}
* {{addon|launchy|Launchy}}
* {{addon|lcarstrek|LCARStrek}}
* {{addon|lightning|Lightning}} ''contains binary components''
* {{addon|linky|Linky}}
* {{addon|nightly-tester-tools|Nightly Tester Tools}}
* {{addon|noscript|NoScript}}
* {{addon|nostalgy|Nostalgy}}
* {{addon|open-with|Open With}}
* {{addon|opendownload-10902|OpenDownload²}}
* {{addon|prefbar|PrefBar}}
* {{addon|quickfolders-tabbed-folders|QuickFolders (Tabbed Folders)}}
* {{addon|quick-locale-switcher|Quick Locale Switcher}}
* {{addon|quickpasswords|QuickPasswords}}
* {{addon|quotecollapse|QuoteCollapse}}
* {{addon|saved-password-editor|Saved Password Editor}}
* {{addon|session-manager|Session Manager}}
* {{addon|showip|ShowIP}}
* {{addon|slim-add-ons-manager|Slim Add-on Manager}}
* {{addon|smoothwheel|SmoothWheel}}
* {{addon|speed-dial|Speed Dial}}
* {{addon|sqlite-manager|SQLite Manager}}
* {{addon|stylish|Stylish}}
* {{addon|tabs-menu|Tabs Menu}}

=== 2.6 (+ 2.7 and later) ===
* {{addon|295715|Flexible Identity}}
* {{addon|preserve-download-modification|Preserve Download Modification Timestamp}}
* {{addon|restartless-restart|Restartless Restart}}
* {{addon|tinderstatus|Tinderstatus}}
* {{addon|toggle-word-wrap|Toggle Word Wrap}}
* {{addon|video-downloadhelper|Video DownloadHelper}}

=== 2.5 (+ 2.7 and later) ===
* {{addon|bugmail|Bugmail}}
** Does not work on BMO emails if the URL at top of the bugmail includes an #anchor to a comment.
* {{addon|colorfultabs|ColorfulTabs}}
* {{addon|mnenhy|Mnenhy}}
* {{addon|provider-for-google-calendar|Provider for Google Calendar}}
* {{addon|reminderfox|ReminderFox}}
* {{addon|scriptish|Scriptish}}
* {{addon|user-agent-switcher|User Agent Switcher}}
* {{addon|web-developer|Web Developer}}

=== 2.4 (+ 2.7 and later) ===
* {{addon|charpick|Character Palette}}
* {{addon|display-mail-user-agent|Display Mail User Agent}}
* {{addon|inforss|InfoRSS}}
* {{addon|its-all-text|It's All Text!}}
* {{addon|key-manager|Key Manager}}
* {{addon|mailnews-status-icons|MailNews Status Icons}}

=== 2.3 (+ 2.7 and later) ===
* {{addon|betterprivacy|BetterPrivacy}}
* {{addon|dictionary-switcher|Dictionary Switcher}}
* {{addon|flashresizer|FlashResizer}}
* {{addon|mailbox-alert|Mailbox Alert}}
* {{addon|open-in-browser|Open in Browser}}

=== 2.2 (+ 2.7 and later) ===
* {{addon|autopager|AutoPager}}
* {{addon|folderflags|FolderFlags}}

=== 2.1 (+ 2.7 and later) ===
* {{addon|abctajpu|abctajpu}} (AMO says "Compatible with SeaMonkey 2.0 and later")
* {{addon|cookiesafe-ff-4-compatible|CookieSafe (FF 4 compatible)}}
* {{addon|colorzilla|ColorZilla}}
* {{addon|custom-buttons|Custom Buttons}}
* {{addon|filtaquilla|FiltaQuilla}}
* {{addon|live-http-headers|Live HTTP Headers}}
* {{addon|show-password-on-input|Show Password On Input}}

AMO add-ons below this line do not benefit from compatible-by-default (SM 2.7 and later).
<hr style="color:red">

=== 2.0x ===
* {{addon|duplicate-tab|Duplicate Tab}}
* {{addon|duplicate-this-tab|Duplicate This Tab}}
* {{addon|ie-tab-plus-ff-36|IE Tab Plus (FF 3.6+)}}
* {{addon|image-zoom|Image Zoom}}
* {{addon|password-exporter|Password Exporter}}
* {{addon|reloadevery|ReloadEvery}}
* {{addon|show-my-password|Show My Password}}
* {{addon|tab-clicking-options|Tab Clicking Options}}
* {{addon|textplain|text/plain}}
* {{addon|theme-font-size-changer|Theme Font & Size Changer}}

=== Earlier, works with compatibility override (or with ACR) ===
* {{addon|display-mailing-list-header|Display Mailing List Header}}

== External Sources ==
Please list name, version and source (plus extra info). Please check AMO for experimental versions before adding to this list. Note that starting with SM 2.8, add-ons are compatible by default, i.e. any add-on that is at least compatible with SM 2.1 or Toolkit 2.0 is compatible unless it explicitly opts out of compatible-by-default through either its install.rdf or AMO entry. The following list assumes this new compatibility checking which will soon be the default. For earlier version of SeaMonkey, you might need to install the {{addon|add-on-compatibility-reporter|Add-on Compatibility Reporter}} add-on before installing any of these add-ons.

* [http://xsidebar.mozdev.org/modifiedmisc.html#saveasimage Abduction! (Save As Image)] 2.026
* [http://xsidebar.mozdev.org/modifiedmisc.html#autofillforms Autofill Forms] 0.9.5.2
* [http://xsidebar.mozdev.org/modifiedmisc.html#contexthighlight Context Highlight] 0.3.1
* [http://xsidebar.mozdev.org/modifiedmisc.html#copyurlplus Copy URL +] 1.3.2
* [http://xsidebar.mozdev.org/modifiedmisc.html#dictionarysearch DictionarySearch] 3.6.1
* [http://xsidebar.mozdev.org/modifiedmailnews.html#displaymua Display Mail User Agent] 1.6.5
* [http://xsidebar.mozdev.org/modifiedmisc.html#downloadstatusbar Download Statusbar] 0.9.7.2
* [http://xsidebar.mozdev.org/modifiedmisc.html#executejs Execute JS] 0.2.4
* [http://xsidebar.mozdev.org/modifiedmisc.html#faviconpicker2 Favicon Picker 2] 0.6.1.14
* [http://xsidebar.mozdev.org/modifiedmisc.html#favloc FavLoc] 1.2.1
* [http://getfirebug.com/releases/firebug/?C=M;O=D Firebug] 1.9.x
* [http://xsidebar.mozdev.org/modifiedmisc.html#fireftp FireFTP] 1.99.5
* [http://flashblock.mozdev.org/ Flashblock] 1.3.18
* [http://xsidebar.mozdev.org/modifiedmisc.html#greasemonkey Greasemonkey] 0.9.13.1
* [http://users.skynet.be/mgueury/mozilla/download_090.html HTML Validator] 0.9.5.1
* [http://xsidebar.mozdev.org/modifiedmailnews.html#importexporttools ImportExportTools] 2.2
* [http://mozilla.doslash.org/infolister/ InfoLister] 0.10.4a3
* [http://xsidebar.mozdev.org/modifiedmisc.html#inspectorwidget InspectorWidget] 3.01.20100211
* [http://mozilla.dorando.at/readme.html keyconfig] 20110522
* [http://www.mousegestures.org/dev/nightly/ Mouse Gestures Redox] 3.2pre
* [http://xsidebar.mozdev.org/modifiedmisc.html#measureit MeasureIt] 0.3.9
* [http://xsidebar.mozdev.org/modifiedmisc.html#passwordexporter Password Exporter] 1.2.1
* [http://xsidebar.mozdev.org/modifiedmailnews.html#quickmenumc QuickMenuMC] 0.9.2.2
* [http://xsidebar.mozdev.org/modifiedmailnews.html#quotecolors Quote Colors] 0.3
* [http://xsidebar.mozdev.org/modifiedmisc.html#removecookies Remove Cookie(s) for Site] 0.52
* [http://removedupes.mozdev.org/installation.html Remove Duplicate Messages (Alternate)] 0.3.7
* [http://titobouzout.github.com/seamonkey-tab-multiple-handler/ SeaMonkey "Tab Multiple Handler"] 0.110817.3
* [http://tom-cat.com/mozilla/extensions.html SeaTabX] 1.1.3
* [http://xsidebar.mozdev.org/modifiedmisc.html#securelogin Secure Login] 0.9.9pre
* [http://xsidebar.mozdev.org/modifiedmailnews.html#selectaddressbooktext Select Address Book Text] 1.5
* [http://xsidebar.mozdev.org/modifiedmisc.html#showanchors Show Anchors] 2.1 ''Context menu transparent''
* [http://xsidebar.mozdev.org/modifiedmailnews.html#tagdialog Tag Dialog] 1.0.3 ''Shortcut "I" clashes with Mark/Flag''
* [http://xsidebar.mozdev.org/modified.html#urlparams UrlParams] 3.0.3
* [http://xsidebar.mozdev.org/modifiedmisc.html#vacuumplacesimproved Vacuum Places Improved] 1.1

=== Add-ons with Binary Components ===
The below provide pages specifically for users of trunk, Aurora and Beta versions.

* [https://developer.mozilla.org/en/Calendar/Calendar_Versions Lightning] (and Provider for Google Calendar)
* [http://enigmail.mozdev.org/download/nightly.php.html Enigmail]

=== Needs Compatibility Override ===
Please list name, version and source (plus extra info). Add-ons under this category are declared compatible with an older SeaMonkey version like 2.0 but should still work with newer versions.

* [http://xsidebar.mozdev.org/modifiedmisc.html#fullerscreen Fullerscreen] 2.3.3
* [http://xsidebar.mozdev.org/modified.html#mozimage mozImage] 1.4.5
* [http://www.go-mono.com/moonlight/download.aspx Novell Moonlight] ''version?''
* [http://xsidebar.mozdev.org/modifiedmailnews.html#signature Signature] 0.4.0.4.200610221528

=== TODO ===
The following need to be checked and either sorted into the above or the below lists.

* [http://getfirebug.com/releases/chromebug/?C=M;O=D Chromebug] 1.8.0a2 ''Requires Firebug''
* [http://tom-cat.com/mozilla/seamonkey.html Mostly Crystal theme]
* [http://mozilla-themes.schellen.net/ Pinball theme] 2.2.1

== Needs Addition to install.rdf ==
Please list name, version and source (plus extra info). See [https://developer.mozilla.org/En/Extensions_support_in_SeaMonkey_2 Extensions support in SeaMonkey 2] for an install.rdf modification example.
* {{addon|back-to-top|Back to Top}} 6.0.1
* {{addon|bugzilla-helper|Bugzilla Helper}} 0.4.3
* {{addon|dominant-color|Dominant Color}} 2 ''restartless''
* {{addon|extension-developer|Extension Developer}} 0.3.0.20100706
* {{addon|firecookie|Firecookie}} 1.2.1 ''Requires Firebug''
* {{addon|google-redesigned|Google Redesigned}} 0.7
* [http://www.juergen-ernst.de/addons/replytolist.html Reply to Mailing List] 0.4.2 ''Tested with SM 2.7a1''
* {{addon|sendvia|SendVia}} 1.0.1
* {{addon|signature-switch|Signature Switch}} 1.6.7
* [http://glandium.org/blog/?p=2180 Tab Stats] 0.0.2

== Not Yet Working (or Not Anymore) ==
Please list name and reason.
* BetterPrivacy 1.68 ''Developer has dropped all SeaMonkey support''
* Duplicate Contact Manager ''stopped working''
* MailNews Sync ''needs adaptations to new add-on module handling and/or Sync changes; abandoned by author''
* Menu Editor ''?''
* Orbit 3+1 theme ''maintainer time constraints''
* xSidebar ''maintainer time constraints''
* Remove It Permanently ''stopped working''

== Obsolete ==
Please list only names.
* Bookmark Indicator
* Firefox Sync
* Flat Bookmark Editing
* NoSquint
* Resizeable Textareas
* Tab Scroll Wheel
* Tabs Open Relative

SeaMonkey/StatusMeetings/2013-04-02

2013-06-17T20:22:50Z

Xabolcs: /* Nominees */ typo

[[SeaMonkey/StatusMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} -2 week}}|« last meeting]] | [[SeaMonkey:StatusMeetings|index]] | [[SeaMonkey/StatusMeetings/{{#time: Y-m-d | {{SUBPAGENAME}} +2 week}}|next meeting »]]

'''SeaMonkey Meeting Details'''

* Time: [http://www.timeanddate.com/worldclock/fixedtime.html?day=2&month=4&year=2013&hour=12&min=0&sec=0&p1=0 2 April, 2013, 12:00 UTC]
** (8am Eastern, 1pm UK, 2pm Central Europe, 8pm Hong Kong)
* Location: [irc://irc.mozilla.org/seamonkey #seamonkey IRC channel]
* Further Read: [[SeaMonkey/StatusMeetings/Basics|Basics]]

== Agenda ==
* Who's taking minutes? -> '''mcsmurf'''
* Nominees for Friends of the Fish Tank:
** Neil for tireless patch reviewing
** xabolcs for working on Bug 848265 (ChatZilla)

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

'''NEW'''
* Need to reward the nominees of the freinds of the fish tank from this year!

'''OPEN'''
* —

'''CLOSED'''
* —

=== Status of the SeaMonkey Buildbot Master and Tree ===

* Tinderbox is going to be EOLed. We need to move the SeaMonkey tinderboxpushlog off. See:
** {{Bug|843356}} [Tracking bug] remove SeaMonkey dependency on tinderbox.mozilla.org.
** Mostly done now, just a few loose ends.
* Intermittent issue with Mac OSX64 Debug Leak log comprehension. Issue tracked in {{bug|774844}}. Also see possibly related Thunderbird {{Bug|806492}}..
* Two remaining machines on Parallels are the buildmaster (cb-seamonkey-linuxmaster-01) and Linux64 (cb-seamonkey-linux64-01). These need to be migrated to ESX. Specifically:
** sea-vm-linux64-1 will replace cb-seamonkey-linux64-01 (and is ready to go)
** sea-master1 will replace the current buildmaster.
* {{Bug|740633}} set up seamonkey HPs in scl3. Hardware installed and iLO configured. CentOS 6.3 installed.
** Awaiting puppetmaster fully prepared to instantiate as Linux Mock-Based slaves
* sea-puppet (one of said hp machines) is ready to be configured as a puppet master ({{Bug|827079}}), needs audit of the manifests and settings creation.
* comm-* will be building out of mozilla-* eventually. Jcrammer is working on this.
==== Fixed Stuff Since Last Meeting ====

* SeaMonkey BuildAPI is now setup and running internally, investigating if it can be externally accessed.
* Windows platform builds were broken by ({{bug|842341}}). {{Bug|842445}} migrated our Win builders to use pymake by default.

=== Release Train ===
* SeaMonkey 2.17 Beta 4 shipped March 28.
* SeaMonkey 2.17 will ship later today April 2.
* SeaMonkey 2.18beta1 will build/ship this week, likely ship Friday April 5.

==== Too many betas: ====
* mcsmurf/IanN think that we can reduce the number to three or four. Mail has been sent to seamonkey-members to discuss this.
* Ewong says there is normally 1 beta per week.
* Callek to drive this conversation to a final outcome until today.
** Callek still hasn't done this yet, he should be <s>nudged</s> punished :-) .
* New number of betas: Best idea is probably beta 1,3,maybe 5,6 (compared to the previous number six betas per release cycle)

=== Extensions Compatibility Tracking ===
* See [[SeaMonkey/StatusMeetings/Basics|Basics]] page. Please only list current changes here.
* [[SeaMonkey/AddonCompat|Addon Compatibility Listings]]
* There are now Lightning versions for both SM 2.16.x (Lightning 2.1b1) and SM 2.17 betas (Lightning 2.2b1) available on AMO.
* Shipped extensions (DOMI, CZ, Venkman) compatibility:
** Extensions are now compatible by default thus mitigating the issue. Although some people still disable c-b-d and run into issues.
* Our build team (Callek, ewong, Serge) needs to automate DOMI branch selection rather than having to tweak the client.py every 6 weeks. {{Bug|763506}}
** In the past Serge often pushed this forward for us. But with Serge on a sabbatical, Ewong thinks he should talk to Callek in getting this automated.
** For 2.16, compatibility bumps were done as outlined in {{Bug|808426}}.
* There was some discussion about what ChatZilla version will be shipped in SeaMonkey 2.18
** SeaMonkey tries to ship the current release branch of an extension (like CZ) on Aurora branch date
** Shipping non-released versions will break update check with AMO
** SeaMonkey 2.18 will ship ChatZilla 0.9.90

=== 2.x (Last, Current, Next) ===
* [From last meeting:] There is a problem with the metrics server, so no current data is available

** Some people cannot upgrade due to system requirements (OS version, processor capabilities etc.). This even more applies to 2.10 which dropped support for Win2k and WinXP without SP2, and 2.14 dropping Mac OS X 10.5 support.
** We now have a webpage for latest builds available for "Legacy Platforms" like PPC ({{Bug|759315}})
* See [[SeaMonkey/StatusMeetings/Basics|Basics]] page for the usual reminders.

==== 2.16 ====
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey216&type0-0-0=equals&value0-0-0=%2B open tracking] (0)
[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey216&type0-0-0=equals&value0-0-0=%3F tracking requests] (4)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.16 targeted] (0)
[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&resolution=FIXED&field0-0-0=target_milestone&field0-1-0=cf_status_seamonkey216&field0-2-0=target_milestone&field0-3-0=cf_status_seamonkey215&field0-4-0=cf_status_seamonkey214&field0-5-0=cf_status_seamonkey213&field0-6-0=cf_status_seamonkey212&field0-7-0=cf_status_seamonkey211&field0-8-0=cf_status_seamonkey210&field0-9-0=cf_status_seamonkey29&field0-10-0=cf_status_seamonkey28&field0-11-0=cf_status_seamonkey27&field0-12-0=cf_status_seamonkey26&field0-13-0=cf_status_seamonkey25&field0-14-0=cf_status_seamonkey24&field0-15-0=cf_status_seamonkey23&field0-16-0=cf_status_seamonkey22&field0-17-0=cf_status_seamonkey21&type0-0-0=regexp&type0-1-0=equals&type0-2-0=notregexp&type0-3-0=notsubstring&type0-4-0=notsubstring&type0-5-0=notsubstring&type0-6-0=notsubstring&type0-7-0=notsubstring&type0-8-0=notsubstring&type0-9-0=notsubstring&type0-10-0=notsubstring&type0-11-0=notsubstring&type0-12-0=notsubstring&type0-13-0=notsubstring&type0-14-0=notsubstring&type0-15-0=notsubstring&type0-16-0=notsubstring&type0-17-0=notsubstring&value0-0-0=^(seamonkey2.16|seamonkey2.17|seamonkey2.18)$&value0-1-0=fixed&value0-2-0=^(seamonkey2.15|seamonkey2.14|seamonkey2.13|seamonkey2.12|seamonkey2.11|seamonkey2.10|seamonkey2.9|seamonkey2.8|seamonkey2.7|seamonkey2.6|seamonkey2.5|seamonkey2.4|seamonkey2.3|seamonkey2.2|seamonkey2.1|seamonkey2.0)$&value0-3-0=fixed&value0-4-0=fixed&value0-5-0=fixed&value0-6-0=fixed&value0-7-0=fixed&value0-8-0=fixed&value0-9-0=fixed&value0-10-0=fixed&value0-11-0=fixed&value0-12-0=fixed&value0-13-0=fixed&value0-14-0=fixed&value0-15-0=fixed&value0-16-0=fixed&value0-17-0=fixed fixed] (5)

* [http://www.seamonkey-project.org/releases/seamonkey2.16/ SeaMonkey 2.16 Release Notes]

==== 2.Next ====
* Current breakages:
** Nothing significant at the moment.

* Mozilla-central bugs that affect us:
** '''Note:''' Please file bugs if you notice any landing on mozilla-central that might break us. Please don't depend on Ratty noticing such landings.
** {{Bug|769764}} move proxy resolution to separate thread and remove sync api. Tracked in:
*** MailNews {{Bug|791645}} Rewrite calls to synchronous nsIProtocolProxyService::DeprecatedBlockingResolve with Async code before DeprecatedBlockingResolve disappears as well.
** {{Bug|737615}} Remove use of synchronous cache API from unit tests. Tracked in:
*** {{Bug|804972}} Remove synchronous calls to nsICacheSession::openCacheEntry in SeaMonkey tests.
*** Mcsmurf says this is almost fixed but there was a test failure. He will close this bug and open a new one for the failure.
** {{Bug|793634}} Force builds to be compatible with gtk 2.18/glib 2.22. Tracked in:
*** {{Bug|795354}} Migrate SeaMonkey Linux builders to CentOS 6.
*** {{Bug|794772}} Port |Bug 713802 - Build with GIO support (and drop GnomeVFS)|. This is dependent on {{Bug|795354}}.
** {{Bug|795144}} default --disable-gnomeui icon theme support
*** porting bug needed for the two configure.in changesets? Changes could be folded into {{Bug|794772}} above.
*** ''IanN says he will look into these issues. Ewong is also working on bug 794772''.
** {{Bug|834457}} Remove deprecated synchronous APIs from Places. Tracked in:
*** {{Bug|834498}} Remove usage of setPageTitle and isVisited from Seamonkey's tests. Mcsmurf is making good progress.
** {{Bug|839034}} move markPageAsXXX methods to nsINavHistoryService. Tracked in:
*** {{Bug|845895}} Fix markPageAsXXX usage in Seamonkey.

=== Feature List, Planning ===
Private Browsing is now mostly complete. However parts of it have been uplifted to 2.18, so we have some options:
* Uplift all the patches from 2.19/2.20 to 2.18
* Remove UI for Private Browsing from 2.18 and decide whether to leave it in for 2.19 in six weeks
* Remove UI for Private Browsing from 2.18 and uplift any remaining patches from 2.20 (e.g. {{bug|856406}}) to 2.19
Also we need to figure out if we want a new about:privatebrowsing page which someone will have to write.
Also I don't know whether we have any help content yet.

[http://dev.seamonkey.at/#bugstats Bug statistics] for the last two (full) weeks: 26 new, 22 fixed, 21 triaged.
* Medium triaging effort.

[https://bugzilla.mozilla.org/chart.cgi?category=-All-&subcategory=-All-&name=1183&label0=SM-with-review%3F-requests&line0=1928&label1=SM-with-superreview%3F-requests&line1=1929&gt=1&labelgt=Grand+Total&datefrom=2009-07-15&dateto=&action-wrap=Chart+This+List Open reviews/flags]:
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&namedcmd=SeaMonkey%20%282%29%20/%20-All-%20/%20SM-with-review%3F-requests&series_id=1928&remaction=runseries 25 review]
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&namedcmd=SeaMonkey%20%282%29%20/%20-All-%20/%20SM-with-superreview%3F-requests&series_id=1929&remaction=runseries 8 super-review]
[https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=ui-review%3F 1 ui-review]
[https://bugzilla.mozilla.org/buglist.cgi?product=SeaMonkey&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=feedback%3F 8 feedback]

* {{Bug|847546}} Support Retina Display (HiDPI) on SeaMokney on MacOS X.
** Ratty thinks we will need 2x PNGs as well as other changes. See Core Tracking {{Bug|785330}} for supporting HiDPI mode (Retina Display) on Mac OS X.
* See [[SeaMonkey/StatusMeetings/FeatureList|Feature List]] page for major wanted/needed features.
** Ratty suggests featuring one or more bugs from that page at each meeting.
* Featured ''helpwanted'' bugs:
** '''{{bug|677484}} Individual SeaMonkey components are not properly handled by the Windows 7 taskbar.

===Good First Bugs===

* '''Note:''' The GFB list is open to all including our regular contributors.
* Ratty is working on an updated GFB list, suggestions welcome.
* New GFBs recently added:
* Currently there are 24 GFBs open, 2 are being actively worked on. {{Bug|735333}} needs some help getting this running on the try-server. Mcsmurf is assisting.
* [https://bugzilla.mozilla.org/buglist.cgi?list_id=4423240;status_whiteboard_type=anywordssubstr;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;product=SeaMonkey;status_whiteboard=mentor;query_format=advanced List of Open mentored bugs].
** Ratty notes that there are 23 bugs that are GFBs but without the <tt>mentor</tt> keyword. These need to be audited to see if they are really suitable as GFBs.
* In the last two weeks since the previous meeting:
** {{Bug|735333}} Use Services.prefs instead of preferences-service / gPrefService, in SeaMonkey code. Mcsmurf will check in the Services.prefs patches soon. IanN says that once this is done, it's worth asking people who use trunk to give those areas a good test, because we have regressed before with Services.jsm landings.
*** Mcsmurf did some testing on this, but need to check how to "discover" JS bugs, as they don't generate TEST-UNEXPECTED-FAIL in the log.
** {{Bug|752331}} Atul had to give up on this bug due to illness. Ratty will leave this open for the time being.
* Mentors of stalled bugs should try to communicate with the assignees and if they can't work on them any more to unassign/free up those bugs.

=== 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).

==== Aqualon ====
==== Callek ====
Fixed:
* {{Bug|848222}} Use treestatus for SeaMonkey tree closures.
* {{Bug|852841}} Add SeaMonkey 2.17 Beta 3 to bouncer.
* {{Bug|854290}} Update SeaMonkey website for 2.17 Beta 3.
* {{Bug|855164}} Add SeaMonkey 2.17 Beta 4 to bouncer.
* {{Bug|855967}} Update SeaMonkey website for 2.17 Beta 4.
* {{Bug|855997}} Add SeaMonkey 2.17 to bouncer.
Working on:
* {{Bug|740633}} set up seamonkey HPs in scl3.
* {{Bug|817383}} SeaMonkey needs new (public) GPG key, in order to support signing releases properly.
* {{Bug|827079}} Setup SeaMonkey PuppetMaster.
* {{Bug|827178}} Update stage.m.o cron to match recent changes with ffxbld cron.
* {{Bug|845844}} Deploy updated tbpl to tbpl.drapostles.org.

==== crussell ====
* crussell has been working on https://hg.mozilla.org/users/sevenspade_gmail.com/sepsis/ again (a webconsole)
** See http://www.youtube.com/watch?v=FB2VZLm0sOQ for demo

==== ewong ====
*'''Fixed''':
**{{bug|624432}} - Port |Bug 337964 - changing account during message composing doesn't apply signing prefs from new account| to SeaMonkey
**{{bug|846752}} - Port Bug 713846 (unified log handling) to SeaMonkey Buildbot, utilize statusDB
**{{bug|847257}} - Update Help for changes from Bug 624432.
**{{bug|856953}} - SeaMonkey-beta must have enable_pymake set.

*'''Review''':
**{{bug|739056}} - Port |Bug 715099 - Convert nsProfileMigrator to JS so we can use JS modules on migration| to SeaMonkey

*'''Working On''':
**{{bug|633937}} - Port {{bug|562048}} to suite.
**{{bug|813844}} - Port confvars.sh changes from Bug 718067 and package.manifest.in changes from Bug 808219 (Firefox Health Reporter service)
**{{bug|834690}} - Port |Bug 569342 - Find bar should not be enabled in about:addons| to SeaMonkey
**{{bug|834691}} - Port |Bug 632233| to SeaMonkey (XULBrowserWindow.onLocationChange looks for a "disablefastfind" attribute in all content documents before ruling them out)
**{{bug|837649}} - [Tracking Bug] Stop OSX 10.5 support for SeaMonkey project
**{{bug|837650}} - Stop support for OSX 10.5 in suite/ tree

==== IanN ====
* Some testing, reviewing and commenting.
* Fixed:
* Checked in pending review:
** {{Bug|689253}} Add en-GB locale to Firefox for Android
** {{Bug|851973}} Update en-GB for Gecko 21
* Waiting for review:
** {{Bug|808835}} Add l10n.ini file for Chatzilla
** {{Bug|837408}} Add en-GB locale to gaia
** {{Bug|786316}} Save As Template should correctly manage multiple selections
* Fixing review comments before checkin:
** {{Bug|757230}} When using add button for permissions in Data Manager set a displayHost
** {{Bug|798147}} Switch to correct pref pane if pref window already open
** {{Bug|778534}} Use image instead of html:img in instant messaging
* Reviewed and waiting for feedback from mobile peer:
* Working on:
** Various SM Council documents.
** {{Bug|606683}} Allow customization of toolbar in Composer and MailNews Composition
** {{Bug|639690}} [META] Re-arrange code between editor and editorOverlay
** {{Bug|773979}} [META] Switch to new drag and drop api in SeaMonkey
** {{Bug|657234}} Move pasteQuote and pasteNoFormatting into contentAreaContextOverlay
** File/Folder selection in windows.
* To Do:
** {{Bug|639395}} Get cmd_fontSize to reflect current state of selected content / content at caret.
** Prefs-in-a-tab.
** Create FAQ for Friends of the Fish Tank.
** Help get composer standalone builds working with --enable-tests.

==== InvisibleSmiley ====
* Fixed:
** {{Bug|852261}} Update SeaMonkey website for 2.17 Beta 2

==== KaiRo ====
==== mcsmurf ====
* Fixed {{Bug|856587}} [SeaMonkey] test_contextmenu.html | checking item #4 (---) name - got context-openlinkinprivatewindow, expected ---
* Worked on {{Bug|834498}} Remove usage of setPageTitle and isVisited from Seamonkey's tests
* Fixed {{Bug|856208}} Stop using global-history;2 in SeaMonkey code
* Fixed {{Bug|827235}} Add plugin-hang-ui@BIN_SUFFIX@ to SeaMonkey package manifest
* Took care of SeaMonkey Facebook page

==== Misak ====
==== Mnyromyr ====
==== MReimer ====
==== Neil ====
Fixed:
* {{Bug|831993}} convert nsISupportsArray m_serversToGetNewMailFor variable from nsPop3IncomingServer.cpp to something better.
Fixed, needs uplift:
* {{Bug|846763}} Browser Feed Preview is broken due to xbl_scopes.
Fixed, possibly should uplift:
* {{Bug|853268}} No icons for security notifications.
Fixed, may need uplift:
* {{Bug|856406}} Tabbed browser should use favicon sevice in a privacy-aware way.
Previously fixed, but may need uplift:
* {{Bug|844497}} Open Location dialog should not save state when opened in a private window.
* {{Bug|849440}} Private downloads don't update.
* {{Bug|851304}} nsContextMenu.js save as handler creates a channel without regard for privacy status.
Working on:
* {{Bug|838888}} Web Console sidebar.
Waiting for review:
* {{Bug|839891}} Implement optional taskbar preview-per-tab.
* {{Bug|854867}} Click-to-play no longer respects per-site permissions.
* {{Bug|856571}} Move accesskey for Error Console's filter box back (Toolkit).
* {{Bug|855631}} Get New Messages for all accounts does not work.

==== Ratty ====
Fixed:
* {{Bug|852496}} [Lightning/SeaMonkey] The image for the delete button in the Event/Task Edit Dialog is messed up.
*
Working on:
* {{Bug|849525}} Clean up mailnews/subscribe.{js|xul}
* {{Bug|852499}} Port {{Bug|835730}} (Properly tear down components when the profile is being shut down) to SeaMonkey.
* {{Bug|856322}} Private Browsing changes for browser feed preview.
Other:
* Did some reviews.
* Bug triage and Bug discussions.
* Usual end user support and PR in newsgroups and [http://forums.mozillazine.org/ Mozillazine].

==== Ricardo ====
====rsx11m====
Fixed:
* {{bug|847182}} Extend Glossary with new Privacy & Security terms
* {{bug|849359}} Print button is misaligned in the Composer and Message Composition toolbars with the Modern theme
* {{bug|852809}} Explain what happens when Safe Browsing blocks a website
* {{bug|855684}} Use opacity rather than hard-coded colors for signature display
Working on:
* {{bug|856454}} Add ability to customise new mail alert information
Other:
* End-user information and discussion on [http://forums.mozillazine.org/viewforum.php?f=51 MozillaZine]

==== sgautherie ====
==== Stanimir ====
==== stefanh ====
==== Tobin ====
==== tonymec ====
* VERIFIED
** {{Bug|840003}} Icons for special IMAP folder (Inbox, trash, ...) are not shown when folder is shared
*** Tested by reporter on 2.19a1 trunk, ported to 2.18a2 aurora, not ported to 2.17 beta due to imminent merge.


''(move to "feature list, planning" above?)'' 
In Sm 2.19a1, creating a new permission for a hostname which doesn't have any yet is unobvious and tedious:
# Open the Data Manager.
# Select * '''(not the concerned hostname)''' in the left pane. ←
# Select the 'Permissions' tab.
# Click <nowiki>[ Add ]</nowiki> at bottom.
# Fill in the desired hostname.
# Select the desired permission.
# Unselect the '''<nowiki>[x]</nowiki> Default''' checkbox.
# Change the permission value. ←
# If desired, set the value back to what it seemed to be before.
* If you leave the '''* Permissions''' tab before step 8, no permission will be set. ←
* If you leave it at step 8, it may be set incorrectly.
* Steps marked ← are those I (tonymec) regard as unobvious.
* Example: Try allowing cookies for host "oxforddictionaries.com" if you don't yet have any permissions for that site.

''(move to "Extension Compatibility Tracking" above?)'' 
Since almost a year, all <tt>SEAMONKEY</tt>''something'' tags in the ChatZilla repository have been applied to branches where no code changes are made (the only file modified in those branches is <tt>.hgtags</tt> and sometimes <tt>install.rdf</tt>). This sounds seriously wrong to me: it would mean that SeaMonkey versions other than Trunk are now being shipped with a built-in ChatZilla whose growth was arrested on 24 April 2012 ([http://hg.mozilla.org/chatzilla/rev/c4510807bd9d the <tt>default</tt> branch ancestor] to branches [http://hg.mozilla.org/chatzilla/rev/e25c0b12b768 <tt>SEA_12_RELBRANCH</tt>] and later), and in particular that releases 0.9.89 and 0.9.90 of ChatZilla were judged good enough for AMO but not for SeaMonkey. — Or are those <tt>SEAMONKEY</tt>''something'' tags actually unused, in favour of the <tt>CHATZILLA</tt>''something'' tags which are on the <tt>default</tt> branch of the repository? 
On further thought, these built-in versions of cZ should be updated to the latest version available at AMO the first time SeaMonkey checks for updates.

=== Any other business? ===
* Basic Private Browsing support has been turned on and most things should work but some edge cases have probably been missed. Testing would be appreciated! Please file bugs as blocking the meta {{bug|460895}}.
* The next Bug Day: Tonymec says either some time after Easter holiday, or during the holiday, depending what we decide. Easter holiday in Belgium is 1-14 April this year. Exact date TBD.
** Need serious discussion about exactly what bug days should change, what they are for, etc.
* '''Test failures'''
** qawanted, especially on Linux and MacOSX specific issues: reproducing and reporting would already help.
** Serge says that on Linux and MacOSX, he just needs someone to actually run the tests and report what they see (screen, console, etc). For example, there is a Mac test about Ctrl+W not working. This should be so trivial.
** Tonymec suggests that any enthusiastic user, even non-technical, should be able to do some testing (litmus?) and not be scared by technical language and such.
** IanN suggests reaching out to the user community using the newsgroups and forums.
** Ratty to liaise with Serge when he gets back on doing a write up how the community can help us with this.

MozCampEU2012/DesigningUsableSecurity

2012-08-05T21:40:17Z

Xabolcs: Would like to attend here

Title of Session:
Designing usable security - Is it Secure if it's Unusable?

Facilitator(s):
Tanvi Vyas

Are you paid or volunteer staff?:
Paid staff

Area of Contribution (Team Name):
Security Engineering

How are you currently involved with the community?:
I mentor a contributor as part of a Google Summer of Code project. I've attended various security conferences, encouraging people to contribute or apply to Mozilla.

Location of Work (where do you reside?):
Mountain View, CA

Talk Length (please choose between 30, 60, 90, 120 minutes):
60 minutes

Summary:
Security warnings are often ignored by users and frowned upon by user experience designers. Can we help users make informed choices about security issues without getting in their way? Let's discuss methods to inform users about security threats without using annoying modal dialogs and without asking users to make complicated decisions.

This will consist of a 20 minute talk followed by 40 minute workshop and Q&A

How your session furthers the MozCamp Goals (https://wiki.mozilla.org/MozCampEU2012/Tracks):
This session will help spawn ideas on how Firefox can secure our users while providing a good User Experience for them. The case studies will focus on existing firefox desktop and mobile open issues.

Expected Outcome or Deliverable:
Proposals for Security UI from the community that will help form a methodology that we can base usable security decisions on in the future.

Desired Audience Type or Skill-set:
All Skill Levels welcome - Anyone who has ever used a browser.

Equipment Needs (Video projector already included):
In addition to the included Video Projector, we will need a few mics for the case studies and Q&A

--------------------------------------------------------------------

To Be Completed by the Audience-

(If you would like) Submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

Place your name here if you would like to attend this talk:
* [https://wiki.mozilla.org/MozCampEU2012/hack-core-security-code Kai Engert]
* Nils Maier
* Paolo Amadini
* Oskar Ivanić
* Szabolcs Hubai
* <put your name here>

MozCampEU2012/mozilla-for-mr-and-mrs-average

2012-08-05T21:25:18Z

Xabolcs: Would like to attend

== Session ==
Title of Session (should also be the title of your Wiki page): Mozilla for Mr and Mrs Average.

Facilitator(s): Claire Corgnou

Are you paid or volunteer staff?: Volunteer

Area of Contribution (Team Name): Mozilla FR / BonjourMozilla

How are you currently involved with the community? 
I'm volunteer in Mozilla project as a Mozilla FR volunteer (localization, documentation, event organizer, community manager), as a Remo member, and as BonjourMozilla redactor.

Location of Work (where do you reside?): Paris | France

Talk Length (please choose between 30, 60, 90, 120 minutes): 30 minutes

Summary: 
I will present a talk about FLOSS and the Average Jane and Joe. I want to convince "geeks" (Mozilla volunteers) that they should make some efforts to welcome "normal people", because geeks need Average Jane or Joe to understand what the public really wants or needs. It's the only way to really open the Web!
So, of course, I will explain what geeks can do to attract "normal people", in order to attract more into Mozilla community.

How your session furthers the MozCamp Goals (https://wiki.mozilla.org/MozCampEU2012/Tracks): 
The aim of this session is to upgrade community building skills by explain how to speak to non-technical persons.

Expected Outcome or Deliverable: Sharing best practices and experiences on "evangelization" to Mr and Mrs Average and how to explain Mozilla project to this kind of persons.

Desired Audience Type or Skill-set: Nothing - this session is open to everyone, but you'll need your sense of humor!

Equipment Needs (Video projector already included):
<ul>
<li>a white wall</li>
<li>a micro</li>
</ul>

== To Be Completed by the Audience ==

(If you would like) Submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

Place your name here if you would like to attend this talk:
* Julia Buchner
* Jérémie Patonnier
* John99
* Oskar Ivanić
* Szabolcs Hubai
* <put your name here>

MozCampEU2012/mozIT-and-you

2012-08-05T20:56:48Z

Xabolcs: /* Audience */

== Overview of Session ==

'''Title of Session:''' Mozilla IT and YOU: past, present and future

'''Facilitators:'''
* Dumitru Gherman
* Brian Hourigan (side-kick)

'''Are you paid or volunteer staff?:''' Paid

'''Area of Contribution (Team Name):''' IT/Infrastructure

'''How are you currently involved with the community?:'''
Last year at MozCamp EU, Justin Dow and I had a session entitled "How can Mozilla IT be your IT". After its success, Mozilla IT started to help communities by providing them virtual private servers (VPS). We realized that most of the community members need guidance setting up those servers, securing them and running the services. I wrote a [http://blog.mozilla.org/it/2012/06/07/a-guide-for-community-sysadmins-linux-systems-administration-101/ blog post in June], addressing those concerns and providing insights to the community on how Mozilla IT manages the servers. Brian Hourigan had a great contribution in writing this blog post.
I am also [https://wiki.mozilla.org/Romania/Active_members#Active_members involved in the Romanian community], being responsible of the system that runs www.mozilla.ro.

'''Location of Work (where do you reside?):''' Mountain View, CA, USA

'''Talk Length:''' 60 min

'''Summary:'''
2/3 of the session will cover some topics from [http://blog.mozilla.org/it/2012/06/07/a-guide-for-community-sysadmins-linux-systems-administration-101/ the blog post], in an open discussion with the auditorium. At the end we'll talk about new exciting ideas that will help communities run the web applications and other services, and open new doors to engaging contributors in IT.

'''How your session furthers the MozCamp Goals:'''
This is a great follow-up after last year's MozCamp IT's session, and it is a way to hear directly from the communities how we did this past year with the tools we provided and how we can do better.

'''Expected Outcome or Deliverable:'''
Instilling systems administration best practices, sharing experiences and ideas with community sysadmins, finding out how can we help more.

'''Desired Audience Type or Skill-set:''' Preferably people who are in charge maintaining community servers, but anyone who is curious about systems security and what IT does "behind the scenes".

'''Equipment Needs (Video projector already included):''' None

== Audience ==

If you would like, submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

* <insert question here>

Place your name here if you would like to attend this talk:

* Paolo Amadini
* Alex Lakatos
* Ioana Chiorean
* Szabolcs Hubai
* <insert name here>

MozCampEU2012/mozIT-and-you

2012-08-05T20:56:09Z

Xabolcs: Would like to attend here

MozCampEU2012/moz-summer-of-code-experience

2012-08-05T20:54:05Z

Xabolcs: Would like to attend here

== Overview of Session ==

Title of Session (should also be the title of your Wiki page): Experience from hosting Mozilla Summer Of Code parties, why you should host one next time and what to do better

Facilitator(s): Julian Viereck

Are you paid or volunteer staff?: Paid

Area of Contribution (Team Name): Mozilla Labs / PDF.JS Project

How are you currently involved with the community?: Working on PDF.JS / presenting the project on conferences (meetups) / co-host of the Mozilla Summer Of Code Party in Ch-Zurich 2012

Location of Work (where do you reside?): Switzerland | Germany

Talk Length (please choose between 30, 60, 90, 120 minutes): 60

Summary: Have you hosted a Summer of Code Party? Then tell us your experience! Wasn't it awesome? If not, how can we make it better? If it was awesome, how can we make it even more awesome? If you haven't hosted a meeting, why? You missed a lot of fun --- come by and tell us!

How your session furthers the MozCamp Goals (https://wiki.mozilla.org/MozCampEU2012/Tracks): The Mozilla Summer Of Code was a centric event of educating people how to use the web, how to change it and have fun doing this. Also, it was a event where people came together from different places and shared a common interest - and that from all over the world at the same time! Continue this kind of events is centric to achieve the Mozilla Mission. Therefore, it's good to review the past events and make sure more people get empowered/motivated to do an event on their own next time.

Expected Outcome or Deliverable: new hosts for next summer of code parties; "better" summer of code parties based on best practices exchanged in this session; interconnect hosts to make aware this was a world wide event and maybe have some "call other people at the other side of the world" action during the next summer of code party?

Desired Audience Type or Skill-set: Nothing - open to everyone!

Equipment Needs (Video projector already included): Small cards to write down things like "what did you like", "what was awesome"; pin-walls to pin them; pens to write on the cards; chairs to sit in a circle.

== Audience ==

If you would like, submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

* <insert question here>

Place your name here if you would like to attend this talk:

* Michelle Thorne
* Oskar Ivanić
* Szabolcs Hubai
* <put your name here>

MozCampEU2012/Governance Workshop

2012-08-05T20:46:18Z

Xabolcs: Would like to attend here

== Overview of Session ==

Title of Session: Governance Workshop

Facilitator(s): Gervase Markham, Rubén Martín (nukeador), Mitchell Baker if available.

Are you paid or volunteer staff?: Gerv is paid, Rubén is a volunteer, Mitchell is paid.

Area of Contribution: Gerv: officially Legal and Business Affairs, but with a broad brief. Rubén: Mozilla Hispano. Mitchell: Chief Lizard Wrangler.

How are you currently involved with the community?: Gerv does legal, licensing, community, security and other stuff, and is responsible for dealing with governance issues day-to-day; Rubén is part of the Mozilla Hispano leadership team and is a shrewd observer of our community, most recently in the area of employee/volunteer relationships; Mitchell needs no introduction.

Location of Work: Gerv is in Sheffield, UK; Rubén is in Valladolid, Spain; Mitchell is in Mountain View, USA.

Talk Length: 60-90 minutes (depending on whether we split this into multiple sessions or not)

Summary: Workshop and discussion session on project governance issues, including but not limited to the Code of Conduct, and the relationship between employees/MoCo and volunteers. (This could be multiple sessions; this is an initial proposal to see what people think.) This will involve structured discussion and small group work.

How your session furthers the MozCamp Goals (https://wiki.mozilla.org/MozCampEU2012/Tracks): Grow Mozilla requires the existing community to be happy and healthy, and requires our governance arrangements to be conducive to attracting new community members from every background. Regular reviews of our governance arrangements and discussion with the community are are therefore very important, and MozCampEU is a very convenient opportunity to do that. Governance issues can involve strong feelings, and face-to-face interaction is often far more productive than online discussion.

Expected Outcome or Deliverable: increased community understanding of and happiness with the Code of Conduct; also possibly a set of proposed changes or clarifications to be considered. Greater understanding by Recruitment, Contributor Engagement and Mozilla management of volunteer feeling about the volunteer/employee relationship. Notes on other governance issues people are having problems with, for the governance team to investigate.

Desired Audience Type or Skill-set: Core volunteer and paid Mozillians from every part of the project. All welcome.

Equipment Needs: Nothing additional required at the moment; a flip chart and markers might well be useful.

== Audience ==

(If you would like) Submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:
* Thunderbird has now been declared non-strategic by Mozilla, and yet as a product has a strong following. To me that means that perhaps the surviving community-based product team may need to propose various governance issues that differ from the strategic products on issues such as monetization, underlying cultural values, and definition of purpose. In what areas is Mozilla likely to be flexible, and where are the hard lines with a product that has in some ways not found a successful home within the existing Mozilla culture? :rkent
* It may be interesting to see if Flash 11.3 issues are discussed. Apparently Adobe are able to influence information we publish in KB articles, and therfore proposed suggestions for workarounds to Firefox issues.(John99)

Place your name here if you would like to attend this talk:
* Burak Yiğit Kaya
* Mark Capella :capella
* Gavin Sharp
* Nils Maier
* Julia Buchner
* Kent James :rkent
* John99
* Blake Winton
* Oskar Ivanić
* [[User:Henx|Henrik Mitsch]]
* Szabolcs Hubai
* <put your name here>

MozCampEU2012/hack-core-security-code

2012-08-05T20:40:54Z

Xabolcs: Would like to attend here

=HowTo hack our core security code (C/C++ programming)=

== Overview of Session ==

'''Facilitator:''' Kai Engert (:kaie)

'''Are you paid or volunteer staff?:''' Red Hat employee, my main priority is contributing to Mozilla security.

'''Area of Contribution:''' Core Web Security (SSL, NSS), Security UI (padlock, certificate management), E-Mail Encryption (S/MIME)

'''How are you currently involved with the community?:''' Fixing bugs since 2001

'''Location of Work (where do you reside?):''' Frankfurt, Germany

'''Workshop Length:''' 60-90 min

'''Summary:'''
We need more C programmers interested in enhancing our core security code, in particular related to SSL/TLS. If you want to help, where do you start? ... This isn't a presentation, it's rather a workshop. Let's explore the code, let's look at examples, ask your background questions. You could read [http://kuix.de/fosdem2012/ my talk from Fosdem 2012] to understand the high level motivation for improving our security code further. If there's interest, we can also go through lists of important bugs that need attention, and find something that you would be interested to fix.

'''How your session furthers the MozCamp Goals''': TBD

'''Expected Outcome or Deliverable:''' Find people who are willing to fix bugs and implement enhancements in our security code.

'''Desired Audience Type or Skill-set:''' C/C++ programmer, interest in security.

'''Equipment Needs (Video projector already included):''' none

== Audience ==

If you would like, submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

* <insert question here>

Place your name here if you would like to attend this talk:

* Burak Yiğit Kaya (tentative)
* Mark Capella :capella
* Nils Maier
* Jonathan Protzenko
* Szabolcs Hubai
* <put your name here>

MozCampEU2012/Thunderbird Community Working session

2012-08-05T20:39:46Z

Xabolcs: Would like to attend here

'''Title of Session (should also be the title of your Wiki page)''': Thunderbird - Technical forum

'''Facilitator(s)''': Mark Banner

'''Are you paid or volunteer staff?''': Paid

'''Area of Contribution (Team Name)''': Thunderbird

'''How are you currently involved with the community?''': Thunderbird Development Lead

'''Location of Work (where do you reside?)''': UK

'''Talk Length (please choose between 30, 60, 90, 120 minutes)''': 60 minutes

'''Summary''': Following new governance presentation by JB, give the opportunity to all interested contributors to get organized and get insights from the Thunderbird staff members. Session will be hosted by Lead Engineer Mark Banner.

'''How your session furthers the MozCamp Goals (https://wiki.mozilla.org/MozCampEU2012/Tracks)''': This is in the Grow Mozilla community sesssion. We need to foster energy around Thunderbird and keep community involved and this will be the way to get first hand information from Thunderbird engineering team.

'''Expected Outcome or Deliverable''': Organised sub-groups of contributors who will work at solving some specific features or technical issues.

'''Desired Audience Type or Skill-set''': Thunderbird enthusiasts

'''Equipment Needs (Video projector already included)''': 1 paperboard

--------------------------------------------------------------------

To Be Completed by the Audience-

(If you would like) Submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

Place your name here if you would like to attend this talk:

* [https://wiki.mozilla.org/MozCampEU2012/IrvingReid Irving Reid]
* Philipp Kewisch
* [https://wiki.mozilla.org/MozCampEU2012/hack-core-security-code Kai Engert]
* Kent James
* Blake Winton
* Magnus Melin
* Szabolcs Hubai
* <put your name here>

MozCampEU2012/New-Skies-For-Thunderbird

2012-08-05T20:36:09Z

Xabolcs: Would like to attend here

'''Title of Session''': New Skies for Thunderbird

'''Facilitator(s)''': Jb Piacentino

'''Are you paid or volunteer staff?''': Paid

'''Area of Contribution (Team Name)''': Thunderbird

'''How are you currently involved with the community?''': I am working on giving Thunderbird as much kinetic energy so it can reach Escape Velocity

'''Location of Work (where do you reside?)''': Paris

'''Talk Length (please choose between 30, 60, 90, 120 minutes)''': 60

'''Summary''': Thunderbird is preparing for a change in governance and in release model. The volunteers and paid staff are working together in defining how we will keep Thunderbird flying. This session will present up-to-date results and summary of these conversations: Main community objectives, Organization and governance, What does Mozilla do/What do volunteers do, Key upcoming contributions, How you can help...

'''How your session furthers the MozCamp Goals (https://wiki.mozilla.org/MozCampEU2012/Tracks)''': This is a community building session. It is also a catch-up and call to action session for those who have missed the ongoing conversation.

'''Expected Outcome or Deliverable''': Up to date information on the plan or record and a irrepressible appetite to contribute

'''Desired Audience Type or Skill-set''': Anyone interested in Thunderbird's future

'''Equipment Needs (Video projector already included)''': Thunder Feathers

--------------------------------------------------------------------

To Be Completed by the Audience-

(If you would like) Submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

Place your name here if you would like to attend this talk:

* [https://wiki.mozilla.org/MozCampEU2012/IrvingReid Irving Reid]
* Serge Gautherie
* Philipp Kewisch
* [https://wiki.mozilla.org/MozCampEU2012/hack-core-security-code Kai Engert]
* Paolo Amadini
* Kent James
* Blake Winton
* Magnus Melin
* [[User:Henx|Henrik Mitsch]]
* Szabolcs Hubai
* <put your name here>

MozCampEU2012/SUMO L10n Organization and Tools

2012-08-05T20:32:43Z

Xabolcs: Would like to attend here

Title of Session (should also be the title of your Wiki page): SUMO L10n Organization and tools

Facilitator: Rosana Ardila

Are you paid or volunteer staff?: staff

Area of Contribution (Team Name): SUMO

How are you currently involved with the community?: Community Manager

Location of Work (where do you reside?): Berlin

Talk Length (please choose between 30, 60, 90, 120 minutes): 60

Summary: This workshop will be split in 2 parts:
1) The first part will aim to introduce a better organization of locales and find new ways of collaboration. The locale leaders an localizers will discuss how we can organize the work better, define other roles, work with the SUMO Reps and what can be done by the English KB team to facilitate their work.

2) The second part aims to define the contributor requirements for the localization tools on SUMO. The tools will be reworked to fit better the new release cycle and we want to listen to the feedback of the users to redesign them.

How your session furthers the MozCamp Goals (https://wiki.mozilla.org/MozCampEU2012/Tracks): It aims to help provide better Firefox Desktop, B2G and Mobile support ensuring that our help documentation is localized.

Expected Outcome or Deliverable:
1) An organization structure for the L10n SUMO community
2) The requirements and feedback from the SUMO l10n community to pass it on to the development team.

Desired Audience Type or Skill-set: SUMO Locale leaders, localizers, (SUMO) Reps and any Mozillian interested in SUMO

Equipment Needs (Video projector already included): White board

--------------------------------------------------------------------

To Be Completed by the Audience-

(If you would like) Submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

Place your name here if you would like to attend this talk:

* [[User:Coce|Coce]] 10:43, 30 July 2012 (PDT)
* Ziggy Maes
* Ibrahima SARR
* Szabolcs Hubai
* <put your name here>

MozCampEU2012/Implementing-A-WebApi-in-JS

2012-08-05T20:21:43Z

Xabolcs: Would like to attend here

'''Title of Session''': Implementing a webApi in JS

'''Facilitator(s)''':Gregor Wagner

'''Are you paid or volunteer staff?''':
paid

'''Area of Contribution (Team Name)''':
B2G

'''How are you currently involved with the community?''':Work for Mozilla, working with many people from Europe.

'''Location of Work (where do you reside?)''':
San Francisco

'''Talk Length (please choose between 30, 60, 90, 120 minutes)''':
30, 60

'''Summary''':
Many WebApis are implemented in JS. I implemented 2 APIs (contacts and settings) in JS and will share my experiences. I will talk about writing an interface, connecting it to the navigator object and how we deal with separate processes. B2G is currently running apps in separate processes and we have solutions in JS that allow us to communicate between processes.

'''How your session furthers the MozCamp Goals (https://wiki.mozilla.org/MozCampEU2012/Tracks)''':
It is a good start for people that want to contribute to B2G in the near future.

'''Expected Outcome or Deliverable''':
Attendees should be able to write a quick prototype of their custom WebApi for the browser or the B2G phone.

'''Desired Audience Type or Skill-set''':
Basic JS knowledge.

'''Equipment Needs (Video projector already included)''':

--------------------------------------------------------------------

'''To Be Completed by the Audience-'''

'''(If you would like) Submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:'''

'''Place your name here if you would like to attend this talk:'''

* Philipp Kewisch (what is the difference to the [[https://wiki.mozilla.org/MozCampEU2012/how-to-create-new-web-apis other webapi session]])?
* Jérémie Patonnier
* Szabolcs Hubai
* <put your name here>

MozCampEU2012/Make Sure Your Code Works

2012-08-05T20:18:06Z

Xabolcs: Would like to attend here

'''Make Sure Your Code Works, How to Craft Automated Tests for B2G''':

'''Facilitator(s)''': Henrik Skupin, Rob Wood

'''Are you paid or volunteer staff?''': Paid

'''Area of Contribution (Team Name)''': Automation and Tools

'''How are you currently involved with the community?''': We help extend the automated tests for B2G and Firefox Desktop. We would like to expose this kind of work to the community for a number of reasons:
1. It would enable community contributors to be full fledged developers (every patch they write will need to have an automated test with it, so this is a necessary skill for contribution to Mozilla)
2. Writing automated tests is an excellent, simple way for people with fledgling technology skills to get involved, and get the first series of successes under their belt so that they are prepared for deeper involvement at Mozilla in general. Several of our core developers today began as volunteers writing automated tests.

'''Location of Work (where do you reside?)''': Dresden Germany and Toronto Canada

'''Talk Length (please choose between 30, 60, 90, 120 minutes)''': 90/120 minutes (we can tailor it to fit either slot)

'''Summary''': We would want to give the participants a hands-on demo and allow them to write their own tests. Our goal at the end of the session would be to have each participant write a test and have those patches ready to land at the end of the session.

'''How your session furthers the MozCamp Goals (https://wiki.mozilla.org/MozCampEU2012/Tracks)''': Writing automated tests is one of the very best avenues for new developers to get involved with the Mozilla code base. It provides a simple environment where they can get up to speed quickly and make real contributions in a matter of hours rather than spending days to understand a complex problem and then craft a complex solution. Writing automated tests can be a gateway to further involvement with the Mozilla project, and by writing automated tests participants in the session are actively making the B2G offering better during their session. This gives them a concrete task they can accomplish and it will plant the seed for further future involvement once they return home.

'''Expected Outcome or Deliverable''': We expect each person to write an automated test by the end of the session. We will have a set of tests that need to be written already defined, we'll do a show case on how to write one of them, and we will then help the participants in a 1:1 basis to write their tests. By the end of the session we aim to have all the tests written.

'''Desired Audience Type or Skill-set''': New developers and technically curious folks. Some JavaScript or other programming experience is nice. The tests will be written in JavaScript, so the more JS you know, the better. But the tests we will be writing will be quite elementary so a deep understanding is not required.

'''Equipment Needs (Video projector already included)''': The included projector. A whiteboard or a giant post-it note for drawing diagrams would be useful.

--------------------------------------------------------------------

To Be Completed by the Audience-

(If you would like) Submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

Place your name here if you would like to attend this talk:

* Philipp Kewisch
* Toni Hermoso
* Paolo Amadini
* Szabolcs Hubai
* <put your name here>

MozCampEU2012/State-Of-Firefox-OS

2012-08-05T20:16:45Z

Xabolcs: Would like to attend here

MozCamp EU Proposal

Title of Session: State of Firefox OS

Facilitator(s): Vivien Nicolas && Mounir Lamouri

Are you paid or volunteer staff?: Paid

Area of Contribution (Team Name): B2G/Gaia && Web API

How are you currently involved with the community?: Members of the French community, In love with the Senegalese and Tunisian communities, .... Work with contributors all over the world.

Location of Work (where do you reside?): France.

Talk Length (please choose between 30, 60, 90, 120 minutes): 60 minutes.

Summary: Firefox OS is a huge project. It is composed of technicals bits as well as strategic bits and it is very complicated to follow everything that happens from the external (and sometimes from the internal too!).

A log of the presentation will be dedicate to the things that has been done on the technical side since last august and how it looks like today.

I would like to give some place to explain the stategy and what are our partnerships? What will be shipped in Brazil? ....

Basically Mounir and I have presented B2G last year at the same MozCamp and I would like to present what has been achieved during this year.

How your session furthers the MozCamp Goals (https://wiki.mozilla.org/MozCampEU2012/Tracks): B2G and Apps.

It gives an overview of the project. What difficulties are encountered. How we are changing the web. What will happens. Lots of information there.

Expected Outcome or Deliverable: Inform/Involve people about the project.

Desired Audience Type or Skill-set: From developers to localizers. No special skills are needed even if there will be some more technicals parts when it comes to APIs.

To Be Completed by the Audience-

(If you would like) Submit a Question for the Speaker(s) or indicate what information you hope to gain by attending this talk here:

Place your name here if you would like to attend this talk:

* Philipp Kewisch
* Serge Gautherie
* Matthias Versen
* Ziggy Maes
* [https://wiki.mozilla.org/MozCampEU2012/hack-core-security-code Kai Engert]
* Paolo Amadini
* Julia Buchner
* Blake Winton
* Michael Kohler :mkohler
* [[User:KaiRo|Robert Kaiser]]
* Anas Husseini
* [[User:Henx|Henrik Mitsch]]
* Szabolcs Hubai
* <put your name here>

MozCampEU2012/Introducing ical.js for Apps and the Web

2012-08-05T20:09:55Z

Xabolcs: Would like to attend here

== Overview of Session ==

'''Title of Session''': Introducing ical.js for Apps and the Web

'''Facilitator(s)''': Philpp Kewisch (:Fallen)

'''Are you paid or volunteer staff?''': Volunteer

'''Area of Contribution''': Mozilla Calendar Project / Lightning

'''How are you currently involved with the community?''': Project lead for the Mozilla Calendar Project

'''Location of Work''': Hamburg, Germany

'''Talk Length''': 30-45 minutes

'''Summary''':
: There are quite a few simple parsers for the ICAL format (rfc5545) on the net, but I have seen none that are full featured parsers. As part of my work for the Mozilla Calendar Project, I have been working on a Javascript implementation to replace the C++ libical used in our product, Lightning. The library was designed with cross-browser compatibility in mind and I hope it turns out to be a portal that can lure new community members. Key feature of this library include being able to calculate occurrences from a recurrence rule and timezone support.

: In this talk I will give you a quick overview of the functionality, show how it can be used on a website or in a HTML5 app, and tell you whats left to do until I can stick this behind a sleek website and tell the rest of the world about it.

: If you would like to take a look beforehand, check out the [https://github.com/kewisch/ical.js repository on github]. Please keep in mind, the library is in an early state so there are some quite some rough edges, but I see a lot of potential in bringing this library forward.

'''How your session furthers the MozCamp Goals''':
: This library can be quite an enrichment for B2G + Apps, as it allows more advanced parsing of calendar data, which in turn allows to visualize raw calendar data more easily.

'''Expected Outcome or Deliverable''':
* Gather ideas how this library could be used on the web
* Attract new contributors to get this library ready for prime time

'''Desired Audience Type or Skill-set''':
* HTML5 App and Web Developers
* People interested in Calendaring and how it can be visualized on the web
* Basic Javascript knowledge is helpful

'''Equipment Needs (Video projector already included)''':
* Possibly a Flipchart

== Audience ==

If you would like, submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

* <insert question here>

Place your name here if you would like to attend this talk:

* Burak Yiğit Kaya
* Paolo Amadini
* Blake Winton
* Magnus Melin
* Szabolcs Hubai
* <put your name here>

MozCampEU2012/Javascript-optimizations-for-your-Apps

2012-08-05T20:07:40Z

Xabolcs: Would like to attend here

== Session ==
Title of Session (should also be the title of your Wiki page): Javascript optimizations for your Apps

Facilitator(s): Nicolas B. Pierron

Are you paid or volunteer staff?: Paid

Area of Contribution (Team Name): Javascript Engine Team

How are you currently involved with the community?: IRC mozilla/freenode (pierron)

Location of Work (where do you reside?): Mountain View, CA

Talk Length (please choose between 30, 60, 90, 120 minutes): 60 minutes

Summary: 
Understanding the Javascript Engine optimizations can improve the battery life and the performances of your application/game. This talk will explain the keys concepts behind SpiderMonkey (Gecko's JS Engine) optimizations.

How your session furthers the MozCamp Goals (https://wiki.mozilla.org/MozCampEU2012/Tracks): 
Javascript is one of unknown of the performance equation. Makes sure developers avoid common mistakes which may slowdown their applications.

Expected Outcome or Deliverable: Empowering developers to create awesome Games or Apps for B2G.

Desired Audience Type or Skill-set: Javascript Developers.

Equipment Needs (Video projector already included): None.

== To Be Completed by the Audience ==

(If you would like) Submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

Place your name here if you would like to attend this talk:
* Philipp Kewisch
* Burak Yiğit Kaya
* Nils Maier
* Blake Winton
* [[User:KaiRo|Robert Kaiser]]
* Anas Husseini
* Szabolcs Hubai
* <put your name here>

MozCampEU2012/How to Debug Memory Leaks in Addons and Websites

2012-08-05T19:58:23Z

Xabolcs: Would like to attend here

'''Title''': How to Debug Memory Leaks in Addons and Websites

'''Facilitator(s)''': Kyle Huey

'''Are you paid or volunteer staff?''': Paid

'''Area of Contribution (Team Name)''': DOM team

'''How are you currently involved with the community?''': Far too many ways to count

'''Location of Work (where do you reside?)''': SF

'''Talk Length (please choose between 30, 60, 90, 120 minutes)''': 90

'''Summary''': Come to an interactive workshop with one of the principal engineers on the [[Performance/MemShrink|MemShrink]] project and learn how to use tools with Firefox to debug memory leaks in addons and webpages. We're also looking for feedback on how to make these tools more user-friendly and available to a wider audience.

'''How your session furthers the MozCamp Goals (https://wiki.mozilla.org/MozCampEU2012/Tracks)''': Will equip participants with the tools necessary to produce excellent experiences (in terms of memory usage) on Firefox and other Gecko platforms.

'''Expected Outcome or Deliverable''': Participants walk away able to debug memory leaks in web pages as well as MemShrink engineers.

'''Desired Audience Type or Skill-set''': Seasoned web or addon developers, core Firefox hackers

'''Equipment Needs (Video projector already included)''': Internet access for myself and attendees

--------------------------------------------------------------------

To Be Completed by the Audience-

(If you would like) Submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

Place your name here if you would like to attend this talk:

* Philipp Kewisch
* Serge Gautherie
* [https://wiki.mozilla.org/MozCampEU2012/hack-core-security-code Kai Engert]
* Nils Maier
* Paolo Amadini
* Szabolcs Hubai
* <put your name here>

MozCampEU2012/How to User Test Your App

2012-08-05T19:56:57Z

Xabolcs: Would like to attend here

How to User Test Your App

Facilitator(s): Jennifer Morrow

Are you paid or volunteer staff?: paid

Area of Contribution (Team Name): User Experience, Product

How are you currently involved with the community?: I design the user experience of Mozilla products - especially Firefox on desktop and mobile

Location of Work (where do you reside?): San Francisco, California

Talk Length (please choose between 30, 60, 90, 120 minutes): 60 minutes

Summary:

So you've got an idea for an app. You can code. Maybe you have a prototype. But how do you know anyone will want to use it?

This talk and workshop will show how to conquer the user experience and testing challenges that app developers will face in an increasingly competitive apps marketplace. We'll learn about and then try out various tricks of the trade, including:

     - How to conduct a think-aloud user test on an app

     - How to make the most out of user feedback from beta testing

     - Principles of user experience on mobile devices

     - How to adapt a desktop product or website into an app format

     - Determining who your users are, what their metrics of success are, and how to test for the right metrics

How your session furthers the MozCamp Goals (https://wiki.mozilla.org/MozCampEU2012/Tracks):

- Focuses on testing of apps

- Is interactive: participants will try several different user testing methods during the session

Expected Outcome or Deliverable:

- Every app developer with a working prototype should leave with actionable user feedback on how to improve the user experience of their app

- App developers without prototypes will learn how to create a fantastic user experience for their apps

Desired Audience Type or Skill-set: App developers, app marketers, and app testers. Any skill level

Equipment Needs (Video projector already included): Projector, whiteboards or paper stands, paper for drawing/sketching, markers, post-it notes
<hr />

To Be Completed by the Audience-

(If you would like) Submit a Question for the Speaker(s) or indicate what information you hope to gain by attending this talk here:

Place your name here if you would like to attend this talk:

Paolo Amadini
Szabolcs Hubai

MozCampEU2012/From Code to Features

2012-08-05T19:45:15Z

Xabolcs: Would like to attend here

'''Title of Session''': From Code to Features: Scale Up Your Contributions and Be Happy

'''Facilitator''': Paolo Amadini

'''Are you paid or volunteer staff?''': Paid

'''Area of Contribution''': Firefox Team

'''How are you currently involved with the community?''': I'm a developer who helps in improving Firefox. Among other things I work on the [[User:P.A./Panel-based Download Manager|Downloads Panel]], and in my free time I also maintain the [https://addons.mozilla.org/addon/mozilla-archive-format/ Mozilla Archive Format] add-on.

'''Location of Work''': Italy

'''Talk Length''': 30 minutes

'''Summary''': Even when you're already involved in coding, it's not always easy to organize your work and coordinate with others, especially when you start contributing to larger features. Reviewers ask you for perfect code, while designers tend to experiment with different solutions frequently. Responding to user feedback and questions requires more and more of your limited time. How can you handle this efficiently?

This session builds upon the successful talk on Feature Pages and coordination strategies held at [https://archive.fosdem.org/2012/schedule/event/how_i_added_a_feature_to_firefox.html FOSDEM], adding more practical details and resources that can be helpful to people who are already involved with Mozilla.

'''How your session furthers the [[MozCampEU2012/Tracks|MozCamp Goals]]''':

Working happily and efficiently on larger features is fundamental to scale up coding contributions in Mozilla. The aim of this session is to provide some practical advice that can be applied to many products and situations.

'''Expected Outcome or Deliverable''':

* Raise awareness about Feature Pages and coordination strategies.
* Allow more people to go from fixing individual bugs to building larger features.
* Possibly, work with the audience actively to build high-quality Feature Pages.

'''Desired Audience Type or Skill-set''':

* Developers who work on larger features or want to work on one.
* People who are just curious about our design and coordination practices.

'''Equipment Needs (Video projector already included)''': No additional needs

== To Be Completed by the Audience ==

Submit a Question for the Speaker or indicate what information you hope to gain by attending this talk here:

* <insert question here>

Place your name here if you would like to attend this talk:

* [https://wiki.mozilla.org/MozCampEU2012/hack-core-security-code Kai Engert]
* Nils Maier
* Szabolcs Hubai
* <insert your name here>

MozCampEU2012/GraphicsContributions

2012-08-05T19:39:50Z

Xabolcs: Would like to attend here

== Overview of Session ==

'''Title of Session (should also be the title of your Wiki page)''':
Platform Graphics Contributions

'''Facilitator(s)''':
Bas Schouten

'''Are you paid or volunteer staff?''':
Paid

'''Area of Contribution (Team Name)''':
Platform/Graphics

'''How are you currently involved with the community?''':
Limited, only through the rare reviews and contributions we receive in graphics.

'''Location of Work (where do you reside?)''':
Netherlands

'''Talk Length (please choose between 30, 60, 90, 120 minutes)''':
60 minutes

'''Summary''':
An introduction into the active migration going on in the graphics Platform Code. And how community members can help make a contribution to the bulk of work that needs to be done here.

'''How your session furthers the MozCamp Goals (https://wiki.mozilla.org/MozCampEU2012/Tracks)''':
The planned migration should offer improved performance and responsiveness across all important platforms.

'''Expected Outcome or Deliverable''':
Increased community contributions related to graphics in the core gecko code base.

'''Desired Audience Type or Skill-set''':
Basic C++ skills

'''Equipment Needs (Video projector already included)''':
None, perhaps some workplaces if a more workshop oriented session is desired.

== Audience ==

If you would like, submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

* <put your question here>

Place your name here if you would like to attend this talk:

* Szabolcs Hubai
* <put your name here>

MozCampEU2012/FirefoxDesktop:IntroducingSocialAPI

2012-08-05T19:32:23Z

Xabolcs: Would like to attend here

'''Title of Session''': Introducing the Firefox Social API

'''Facilitator(s)''': Jared Wein, Gavin Sharp

'''Are you paid or volunteer staff?''': Paid

'''Area of Contribution (Team Name)''': Firefox team

'''How are you currently involved with the community?''':
* Jared: Mentored 25 bugs with over 12 contributors and have worked with a semester long student-project for a new version of the Firefox preferences.
* Gavin: Firefox module owner, have been involved with l10n and development community since 2004.

'''Location of Work (where do you reside?)''': Mountain View

'''Talk Length (please choose between 30, 60, 90, 120 minutes)''': 60 minutes

'''Summary''': This will be 1/3 talk and 2/3 workshop. The first 20 minutes will be spent going over the new Social API and what capabilities that it offers developers. Then 40 minutes will be spent as a hands-on workshop where attendees will write a simple SocialAPI worker that will interact with an example social network. This will function similar to a tutorial but attendees will be encouraged to explore and be creative.

'''How your session furthers the MozCamp Goals (https://wiki.mozilla.org/MozCampEU2012/Tracks)''': The SocialAPI is one of our tools for increasing the growth of Firefox desktop usage, and teaching developers and the community about the new SocialAPI, as well as how to build with it can grow its adoption and further grow Firefox' adoption.

'''Expected Outcome or Deliverable''': Increased understanding of the new SocialAPI and a room full of evangelists who can help defend any potential privacy-related criticism that may come about from the new API.

'''Desired Audience Type or Skill-set''': Web developers and technology enthusiasts, also helps if they are interested in social networks :)

'''Equipment Needs (Video projector already included)''': wifi or ethernet connection for attendees

--------------------------------------------------------------------

To Be Completed by the Audience-

(If you would like) Submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

Place your name here if you would like to attend this talk:
* Axel Hecht
* Mark Capella :capella
* Paolo Amadini
* Magnus Melin
* Oskar Ivanić
* [[User:KaiRo|Robert Kaiser]]
* [[User:Henx|Henrik Mitsch]]
* Szabolcs Hubai
* <insert name here>

MozCampEU2012/Schedule/Desktopandmobile/hands-on-profiling

2012-08-05T19:30:10Z

Xabolcs: Would like to attend here

Title of Session (should also be the title of your Wiki page): Hands-on Profiling: Scratch Your Own Itch

Facilitator(s): Josh Matthews, ???

Are you paid or volunteer staff?: Paid

Area of Contribution (Team Name): Platform engineer

How are you currently involved with the community?: Coding steward (answer tons of emails from contributors and potential contributors every month), write lots of code for Firefox internals

Location of Work (where do you reside?): Toronto

Talk Length (please choose between 30, 60, 90, 120 minutes): 60 min

Summary: We'll teach how to use the built-in desktop Firefox profiling tools by using them to identify the causes behind performance problems that session attendees are having. We'll discuss how to interpret the results, and how to make use of these tools to aid in fixing performance problems that are reported in Bugzilla.

How your session furthers the MozCamp Goals (https://wiki.mozilla.org/MozCampEU2012/Tracks):
* Teaches more people how easy and effective profiling desktop Firefox can be
* Identifies causes behind performance problems that can be demonstrated in-person, thereby helping improve Firefox

Expected Outcome or Deliverable:
* Enlarge pool of contributors able to perform (and thereby teach) deeper technical analysis of problems they encounter
* Identify some problems in desktop Firefox, furthering the process by which they can be fixed

Desired Audience Type or Skill-set:
* People with reproducible performance stutters, lags, etc. in Firefox
* People who want to learn how to contribute to fixing bugs without needing to write code
* Triagers who want to further investigate problems they can reproduce

Equipment Needs (Video projector already included):
* Power outlets, internet connection

--------------------------------------------------------------------

To Be Completed by the Audience-

(If you would like) Submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

Place your name here if you would like to attend this talk:
* Philipp Kewisch
* [https://wiki.mozilla.org/MozCampEU2012/hack-core-security-code Kai Engert]
* stripTM
* Paolo Amadini
* John99
* Szabolcs Hubai
* <insert name here>

MozCampEU2012/Schedule/Desktopandmobile/Firefox-L10n-Under-Rapid-Release

2012-08-05T19:28:55Z

Xabolcs: Would like to attend here

'''Title of Session (should also be the title of your Wiki page)''':Firefox localization under the rapid release cycle

'''Facilitator(s)''':Axel Hecht, Jeff Beatty

'''Are you paid or volunteer staff?''': Paid

'''Area of Contribution (Team Name)''': Localization

'''How are you currently involved with the community?''': Helping l10n communities who have fallen behind in the rapid release cycle.

'''Location of Work (where do you reside?)''': Utah, USA; Berlin, Germany

'''Talk Length (please choose between 30, 60, 90, 120 minutes)''': 30

'''Summary''': The Firefox rapid release cycle moves so very quickly. When it was implemented, the localization team also implemented a way for localizers to easily stay on track with their localized versions of the famous browser. With contributor turnover, some of these practices have been lost, resulting in some L10n teams falling behind in the process. Through hands-on experience, this workshop will re-introduce best practices for localizing under the rapid release cycle to help L10n teams keep their localized builds up-to-date.

'''How your session furthers the MozCamp Goals (https://wiki.mozilla.org/MozCampEU2012/Tracks)''': Keeping localized European Firefox builds up-to-date with the rapid release cycle will help spread usership of Firefox desktop throughout Europe by providing a solid L10n-related UX.

'''Expected Outcome or Deliverable''': Locale Aurora repos being filled with localized strings, pushing them toward being up-to-date.

'''Desired Audience Type or Skill-set''': Anyone working on Firefox (desktop or mobile) localization

'''Equipment Needs (Video projector already included)''':

--------------------------------------------------------------------

To Be Completed by the Audience-

(If you would like) Submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

Place your name here if you would like to attend this talk:

* [[User:Coce|Coce]] 10:30, 30 July 2012 (PDT)
* Paolo Amadini
* [[User:KaiRo|Robert Kaiser]]
* Anas Husseini
* Szabolcs Hubai
* <insert name here>

MozCampEU2012/Schedule/Desktopandmobile/All-About-Performance

2012-08-05T19:27:28Z

Xabolcs: Would like to attend here

Title of Session (should also be the title of your Wiki page): All About Performance

Facilitator(s): Taras Glek,
Vladan Djeric, Benoit Girard

Are you paid or volunteer staff?:staff

Area of Contribution (Team Name): Performance

How are you currently involved with the community?:
* We work on improving Firefox performance
* Do outreach(via blogs, talks) about dealing with problematic areas of Firefox or the web.

Location of Work (where do you reside?): Portland, Toronto

Talk Length (please choose between 30, 60, 90, 120 minutes): 60

Summary: We are part of the Performance team at Mozilla. Our primary focus is project [[Performance/Snappy]]. This talk will cover:
* How to diagnose and understand a performance problem by using a profiler, built-in telemetry collection, chromehangs reporting, [http://arewesnappyyet.com/ Telemetry web interface], etc.
* Performance problems we have encountered, areas that we are working on improving and areas for new contributors.
* Situations when Firefox performance is impacted by system configuration, how to detect that and correct your configuration.

How your session furthers the MozCamp Goals (https://wiki.mozilla.org/MozCampEU2012/Tracks):
Increasing awareness of available performance tools within Firefox, how to help make Firefox faster.

Expected Outcome or Deliverable: Faster Firefox

Desired Audience Type or Skill-set: Anyone who wants to learn to diagnose performance issues, looking to start contributing to making Firefox faster or to simply wants to learn how to optimize own system to run Firefox faster.

Equipment Needs (Video projector already included):

--------------------------------------------------------------------

To Be Completed by the Audience-

(If you would like) Submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:
* Electrolysis project, Super-Snappy?

Place your name here if you would like to attend this talk:

* Philipp Kewisch
* Matthias Versen
* Nils Maier
* stripTM
* Paolo Amadini
* Oskar Ivanić
* Szabolcs Hubai
* <insert name here>

MozCampEU2012/Schedule/Desktopandmobile/Build and Release

2012-08-05T19:25:02Z

Xabolcs: Would like to attend here

== Overview of Session ==

'''Title of Session:''' Mozilla Build and Release

'''Presenter:''' John Hopkins

'''Are you paid or volunteer staff?:''' Paid

'''Area of Contribution:''' Release Engineering

'''How are you currently involved with the community?:''' Work for Mozilla

'''Location of Work (where do you reside?):''' Ontario, Canada

'''Talk Length:''' 60 min

'''Summary:'''
This session will give an overview of the Mozilla build and release process for Firefox Desktop, Firefox Mobile, and B2G.

'''How your session furthers the MozCamp Goals''': Spread knowledge about Mozilla build/release activities.

'''Expected Outcome or Deliverable:''' Increased awareness, discussion of ways to contribute.

'''Desired Audience Type or Skill-set:''' Beginner. Diagrams, no code.

'''Equipment Needs (Video projector already included):''' None

== Audience ==

If you would like, submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

* <insert question here>

Place your name here if you would like to attend this talk:

* Philipp Kewisch
* Kent James
* Michael Kohler :mkohler
* [[User:KaiRo|Robert Kaiser]]
* Szabolcs Hubai
* <insert name here>

MozCampEU2012/FirefoxDesktop:WriteCode

2012-08-05T19:22:52Z

Xabolcs: Would like to attend

== Overview of Session ==

'''Title of Session:''' Brainstorming: Write code for Firefox

'''Facilitator:''' Paul Rouget

'''Are you paid or volunteer staff?:''' Paid

'''Area of Contribution:''' Firefox Team

'''How are you currently involved with the community?:''' Work for Mozilla

'''Location of Work (where do you reside?):''' France

'''Talk Length:''' 60 min

'''Summary:'''
This session will show the different steps you need to go through to write code for Firefox Desktop.

'''How your session furthers the MozCamp Goals''': TBD

'''Expected Outcome or Deliverable:''' Gather new potential contributors for our main product, Firefox.

'''Desired Audience Type or Skill-set:''' Beginner/Intermediate

'''Equipment Needs (Video projector already included):''' TBD

== Audience ==

If you would like, submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

* <insert question here>

Place your name here if you would like to attend this talk:

* Burak Yiğit Kaya
* Ziggy Maes
* stripTM
* Paolo Amadini
* Majda Nafissa Rahal
* Szabolcs Hubai
* <insert name here>

MozCampEU2012/Release-Management

2012-08-05T19:19:35Z

Xabolcs: Would like to attend here

==Title of Session==

'''Here Come the Trains: Releasing Mozilla Products, Growing the Mozilla Community'''

==Facilitators==
* Alex Keybl - Release Management, paid staff, MV office
* Bhavana Bajaj - Release Management, paid staff, MV office

==Talk Length==
60 minutes (45 min talk with 15 min Q&A)

==Summary==
* A short intro about the role of release management in the product
* Channels, rapid releases, versioning, frequency of updates, and other FAQ (basically an overview)
* Problems unique to shipping Firefox, with anecdotal evidence. Also unique solutions to those problems in the future
** Scalability of multiple releases, esp. w/r/t community - Firefox, Firefox ESR, Firefox for Android, and Firefox OS
** Investigating issues while maintaining user privacy
** 3rd party add-ons/plugins
* Where we need contributions and how to get involved (applies to Firefox Desktop/Mobile as well as B2G):
** Install desktop/mobile on devices, rate mobile Firefox in Google Play store
** Input feedback triage
** Crash-kill
** QA testing
** SUMO
** L10N
*** The importance of using test channels: Beta/Aurora

===How your session furthers the [https://wiki.mozilla.org/MozCampEU2012/Tracks MozCamp Goals]===
Addresses and encourages growth, helping out with mobile & desktop org goals, and providing understanding for much needed participation in improving quality of B2G.

===Expected Outcome or Deliverable===
A better understanding of release management & rapid release process. Also a clear path for people with a variety of skill sets on how to help be contribute to improving the quality of products Mozilla releases before, during, and after releases are shipped.

===Desired Audience Type or Skill-set===
* Experienced contributors
* Localizers
* SUMO/QA current contributors or people who want to get started in these areas
* First time contributors
* People interested in Firefox Desktop/Mobile and B2G dev/testing
* Anyone looking to learn more about the rapid release process

===Equipment Needs (Video projector already included)===
n/a

--------------------------------------------------------------------

To Be Completed by the Audience-

(If you would like) Submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

Place your name here if you would like to attend this talk:
* [https://wiki.mozilla.org/MozCampEU2012/hack-core-security-code Kai Engert]
* Paolo Amadini
* Oskar Ivanić
* [[User:KaiRo|Robert Kaiser]]
* [[User:Henx|Henrik Mitsch]]
* Szabolcs Hubai
* <insert name here>

MozCampEU2012/Pocket Sized Add-ons: Extension development for Firefox Mobile

2012-08-05T19:15:04Z

Xabolcs: Would like to attend here

'''Title of Session (should also be the title of your Wiki page):'''
''Pocket Sized Add-ons: Extension development for Firefox Mobile''

'''Facilitator(s):''' Kris Maglione, Margaret Leibovic

'''Are you paid or volunteer staff?:''' Paid

'''Area of Contribution (Team Name):'''
* Kris: Add-ons
* Margaret: Firefox Mobile Front-End Development

'''How are you currently involved with the community?:'''
* Kris: I review add-ons submitted to AMO, provide extension development support on IRC (26 hours a day or so, I'm given to understand), and develop several add-ons, including several related to add-on development.
* Margaret: I'm active on IRC and in Bugzilla, helping contributors report bugs and write patches.

'''Location of Work (where do you reside?):'''
* Kris: Central Florida (soon Portland, OR)
* Margaret: San Francisco

'''Talk Length (please choose between 30, 60, 90, 120 minutes):'''
Flexible: 60-90 minutes. Longer would give us more time to interact
with developers during the hacking session after the presentation.

'''Summary:'''

There will be a presentation divided into three components, followed
by a hack session. The relative length and weight of each section
will vary based on the composition and interests of the audience.
We'll have material arranged so that each section may range anywhere
from 5 to 15 minutes, with a maximum of 30 minutes in the case of
the final section.

<ol>
<li>

We will explore the possibilities for add-ons on Mobile, how they
differ from desktop add-ons, and how the limitations of the form
factor make it all the more ripe for add-on development.


This section of the presentation is meant to inspire developers and users
alike, and to generate ideas and interest in future mobile add-on development.
We'll provide key examples of popular desktop add-ons that will translate well
to mobile, those that won't, what kind of UX changes the translation would
require for success, and ideas for add-ons specific to mobile form factors with
no precedent on desktop.

</li>
<li>

We'll explore the similarities and differences in user interface
and architecture between mobile and desktop add-ons. Particular
attention will be paid to the differences in user interface
metaphors, and how to develop to the strengths of the mobile
platform rather than attempting to carry over metaphors common to
desktop. We'll also cover how the architecture and initialization
differ between current desktop add-on modalities and native mobile
add-ons.


This section of the talk will not be highly technical, but will
be primarily aimed at explaining the broad differences in
architecture and user interaction models. It may be suitable for
some non-technical users who are interested in UI and UX design.

</li>
<li>

This section of the presentation will go into technical details
of mobile add-on development, and will include a walkthrough
development of a simple, restartless add-on.


The walkthrough will be available as a Github repo developed by
Kris as part of a project by the add-ons team to provide a
basic, well designed starting point for mobile add-on
development, and will include a small library of utilities to
simplify startup, cleanup, and interaction with windows.


The following will be covered:

<ul>
<li>
We'll start by discussing and demonstrating the process of remotely
installing and debugging add-ons onto a phone from the desktop.
Kris's experience in providing support to extension developers
suggests that this is one of the major hurdles to development, so
particular attention will be paid to this point.
</li>
<li>
We'll put together a trivial bootstrapped extension
with a Hello World inline option panel, and a bootstrap.js file
which simply prints a message to the remote debugger on the desktop.
</li>
<li>
Using the library mentioned above, we'll load ourselves
into the browser window, provide some basic interaction via
NativeWindow, and load a simple content script to modify a web page.
</li>
</ul>

Some mention at this point will be given to Jetpack. However,
since Jetpack functionality on mobile is currently minimal, we'd
rather focus on how easy things can be as they are rather than how
much easier they'll be in the future.

</li>
</ol>

Finally, we'll open up to audience questions before we start the hack
session, during which we'll visit with the participants and offer any
support they need. We're hoping to encourage participants to come up
with an idea for a simple add-on and to work in groups to realize
it. We'll provide coaching and a list of suggestions for anyone who
has trouble here.

'''How your session furthers the MozCamp Goals (https://wiki.mozilla.org/MozCampEU2012/Tracks)''':

Firefox's success was built, in large part, on the success of its
add-ons. The browser on its own is great, but the ability of people
to extend it to make it into exactly what they need has been
unmatched in the browser world. To date, Firefox Mobile has failed
to generate the same kind of interest by add-on developers, and the
Mobile add-on ecosystem is sparse, to say the least, compared to
what we have on Desktop.

We hope to help jump start interest in add-on development for Mobile,
and give people the kind of information and skills necessary to
produce effective and appealing add-ons without hassle.

'''Expected Outcome or Deliverable:'''

We expect participants to leave inspired by the near limitless
potential of mobile add-ons to enhance their daily lives. We expect
most to leave having created a functional mobile add-on,
and with the resources and drive to continue developing and
promoting add-ons for Mobile.

'''Desired Audience Type or Skill-set:'''

Audience members should be interested in developing add-ons, and
familiarity with JavaScript would be useful. Experience building
add-ons for desktop would be a bonus!

'''Equipment Needs (Video projector already included):'''

Most audience members will be expected to bring their own Android
phones or tablets, laptops, and USB cables, but ideally we should
have some spares of the above for participants who want to attend
but don't have such equipment on hand. However, attendees will not
require any equipment during the presentation before the hack
session, and should be able to share thereafter.

One or both facilitators will bring spare phones or tablets in case
they are needed.

== To Be Completed by the Audience ==

'''(If you would like) Submit a Question for the Speaker(s) or indicate what information you hope to gain by attending this talk here:'''

'''List your ideas mobile add-ons here (can be anything you'd like to see someone make):'''

'''Place your name here if you would like to attend this talk:'''
* Giorgio Maone
* Burak Yiğit Kaya
* Jeff Griffiths
* Toni Hermoso
* stripTM
* [https://wiki.mozilla.org/MozCampEU2012/hack-core-security-code Kai Engert]
* Nils Maier
* Paolo Amadini
* Blake Winton
* Brian King
* Anas Husseini
* Szabolcs Hubai
* <insert name here>

MozCampEU2012/Add-ons-Back-On-Top

2012-08-05T19:13:24Z

Xabolcs: Would like to attend here

= Add-ons back on top! =

== Participation Proposal ==

'''Facilitator(s)''': Jeff Griffiths

'''Are you paid or volunteer staff?''': paid

'''Area of Contribution (Team Name)''': Jetpack

'''How are you currently involved with the community?''': Contributor Steward for Add-ons, Product Manager for Jetpack

'''Location of Work (where do you reside?)''': Vancouver BC ( will be in Europe in the Mozcamp timeframe )

'''Talk Length (please choose between 30, 60, 90, 120 minutes)''': 30

'''Summary''':

Upcoming UX changes in Firefox will not only restore but dramatically enhance the place of add-ons in the Firefo Desktop UI. In this session I'll showcase where we're headed with this project and showcase how add-ons can easily leverage the new UI features via Jetpack or restartless add-ons. No XUL necessary!

Reference [http://people.mozilla.com/~shorlander/files/addons-in-toolbar-i01/addons-in-toolbar.html Mockups]

'''How your session furthers the MozCamp Goals (https://wiki.mozilla.org/MozCampEU2012/Tracks)''':

''Add-ons are a key reason why users choose Firefox, and we're working hard to make sure that add-ons in Firefox are a great experience and continue to be a compelling reason to choose Firefox and drive desktop growth.''

'''Expected Outcome or Deliverable''':

Interest in the add-on developer community in leveraging these new features.

'''Desired Audience Type or Skill-set''': previous add-on/web development would be great.

'''Equipment Needs (Video projector already included)''': n/a

== Audience Participation ==

Submit a question for the speaker(s) or indicate what information you hope to gain by attending this talk here:
*

Place your name here if you would like to attend this talk:
* Giorgio Maone
* Burak Yiğit Kaya
* Sofien Chaabouni (Chaasof)
* Ziggy Maes
* stripTM
* [https://wiki.mozilla.org/MozCampEU2012/hack-core-security-code Kai Engert]
* Nils Maier
* Paolo Amadini
* Blake Winton
* Szabolcs Hubai
* <insert name here>

MozCampEU2012/Firefox Stability Programs

2012-08-05T19:11:09Z

Xabolcs: Would like to attend here

== Overview of Session ==

'''Title of Session:''' Firefox Stability Programs
'''Subtitle:''' How we use crash statistics, telemetry, and other measures to improve the stability of Firefox and 3rd-party software

'''Facilitator(s):'''
* Benjamin Smedberg (bsmedberg)
* [[User:KaiRo|Robert Kaiser]] (kairo)

'''Are you paid or volunteer staff?:''' Paid

'''Area of Contribution:'''
* bsmedberg: Plugin and Stability and Such
* kairo: Crashkill and crash statistics

'''How are you currently involved with the community?:'''
* bsmedberg: Module owner of XPCOM and embedding, peers of build config, bootstrap and profile management, and RDF, former l10n coordinator and engineer
* kairo: Crashkill program manager, German localizer, former SeaMonkey project manager.

'''Location of Work (where do you reside?):'''
* bsmedberg: Pennsylvania, US
* kairo: Austria, Europe

'''Talk Length:''' 60 minutes

'''Summary:'''
We use metrics from crashes and telemetry, as well as support, feedback, and external sources, to measure the stability of the Firefox product. This talk will explain the various elements of the stability/crashkill program:
* how crash statistics provide an overall picture of stability;
* how engineers use specific crash information to fix bugs;
* how Mozilla provides feedback to other vendors such as plugin and extension authors about problems with their products
* how features such as Telemetry are being used to provide additional stability metrics on jank and hangs;
* how new features such as the metrics data ping may provide additional statistical information on stability.
* how volunteer contributors can help with stability efforts in both engineering and reporting/statistical roles

'''How your session furthers the MozCamp Goals''':
* Educate community leaders in the EU community about how the stability programs work and discuss with them stability programs and other technical barriers to ongoing product adoption.
* Build the volunteer engineering and metrics community around crash and stability.

'''Expected Outcome or Deliverable:'''
* General education and community understanding
* Recruit at least one new volunteer to aid with stability engineering, and one new volunteer to aid with stability metrics.

'''Desired Audience Type or Skill-set:'''
This talk will be directed toward a moderately technical audience who may or may not have coding skill or statistical knowledge.

'''Equipment Needs (Video projector already included): '''
No additional equipment needed

== To Be Completed by the Audience ==

If you would like, submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

* <insert question here>

Place your name here if you would like to attend this talk:

* Matthias Versen
* Paolo Amadini
* Michael Kohler :mkohler
* Szabolcs Hubai
* <insert name here>