Summit2008/Sessions/Proposals

From MozillaWiki
Jump to: navigation, search

2008 Firefox Summit Session Overview

The Firefox 2008 Summit will include three full days of sessions. All Firefox 2008 Summit attendees are invited to propose and lead sessions.

Session is the generic term covering "presentations," "tutorials," "BoFs," etc.

Please only propose a session that you intend to lead. If you'd like someone else to run a session, talk with or email them directly to discuss.

Please create a new wiki page for your proposal that includes headers for Session Title, Session Leaders, Summary, and Agenda.

Please let us know if you think there is a benefit from having an open session to include people who are not attending the summit. We will do our best to accommodate, but we may not be able to.

General Proposals

Link your Summit session proposals here. Put them in the general tracks listed in the TOC if that makes sense

  • Managing/working with remote people [mrz, would be interested in a round-table discussion]
  • Customizing Distributions: What, Why, and How (and what's planned) [kev] (withdrawn)
  • Partnering: What the heck does it mean, anyways [kev, who will also try and rope jay into participating; gen also happy to help here] (withdrawn)
  • How to stop guessing what the community thinks—the Community Surveys project [sethb, stas]
  • How user-to-user support is the gateway into Mozilla for non-developers [sumo team]
  • Firebug and Chromebug [johnjbarton]
  • The new and improved MDC [sheppy]
  • Problems people find using Firefox and how to solve them [iacchi] (projector)
  • What's happening with the www.mozilla.org site [davidwboswell]
  • Relationships and communication with Linux distros [caillon]
  • Keeping multiple balls in the air: Juggling BOF [melissa and dietrich]
  • Why I Didn't Write a Test: Stuff that's hard to test, and what we could do to fix it [ted]
  • Sharing tests: cross browser tests project [syp] (projector)
  • Light of Firefox [Dr.Kakehi]

Add-ons Related

  • Ways to increase add-on adoption & discoverability (lifestyle themes/add-ons, favorite-ing, recommender, international reach, news feed) [basil]
  • Add-Ons Management in Firefox (Add-Ons Mgr, add-on locale packs, languages, dictionaries, plugins, dependency, updates) [mossop]
  • AMO Features & Roadmap (site improvements, role of sandbox, new ideas) [basil, clouserw, morgamic]
  • Add-on Metrics & Stats
  • AMO Editorial Process (streamlining editorial work, policy needs, recruiting, etc...) [basil]
  • Catering to Add-on Developers (authoring and publishing process, docs, platform services, Fx API changes, newsletter, authoring tools, AMO API's) [Mfinkle?]
  • Extension lifecycle: How to get from the idea to the extension (short), finding testers for first development versions, stabilizing and maintaining code, submission to AMO and how AMO editors make public and review it, conditions for hosting on AMO, getting the extension localized for broader international acceptance, how to keep up to date with AMO, Mozilla products and your extension [Archaeopteryx]
  • AMO L10n processes using Verbatim (roadmap, current challenges, ideas for improvements) [clouserw, mic, etc.]
  • Mozdev and the wider developer community. Deeper ties with AMO, added value, and more [kinger,davidwboswell,ericjung]

Web Platform Related

Mozilla Platform Related

  • Using MDC:Mercurial [bsmedberg,jorendorff] Large (projector)
  • XPCOMGC introduction and planning [bsmedberg] Medium (projector)
  • Hardware Acceleration & Gecko [vlad] Large (projector)
  • 1.9.1 progress updates and feature culling [roc] Medium* (projector)
  • Mozilla static analysis and rewriting tools and projects [dmandelin,taras] Medium
  • Positioning XULRunner as a general purpose platform [mfinkle] Medium
  • Tamarin Tracing JIT intro, how it works [jimb] Medium
  • DTrace [alfred.peng, sayrer] Medium (projector)
  • Priorities for code cleanup and improvement projects [roc] Medium
  • Layout meeting [roc,dbaron] Small
  • Wrappers in XPConnect [mrbkap] Small

Mobile Related

  • Device APIs [blassey, dougt] Mid Size Round Table (projector)
  • Fennec: Mobile Firefox [christian]- Larger Room
    • A presentation of where Fennec is now and where it is heading followed by a demo.
    • Need projector for slides and mobile phone projector
  • Embedding: [blizzard,mfinkle,dcamp] Mid size (white board)
  • Zephyr: The Firefox Phone [aza] (possibly combined w/ below)
  • Mobile UX: [aza,madhava] Mid Size (projector)
  • L10n process for mobile [mic, christian]- discussion Larger Room (white board)
  • Writing add-ons for mobile [mfinkle] Mid Size (Projector)

comm-central (Messaging/MailNews/Calendar/Thunderbird/SeaMonkey Related)

  • Brainstorm: How to ensure quality for Thunderbird with 1 full-time staff? [davida, nth10sd (Gary)]
    • This is also worth discussion for Calendar (2 full-time developers, 1 full time QA, part time UX)
    • size: 30-60 people
    • equipment: whiteboards, projector & screens
    • style: free thinking, open brainstorming, inspirational
    • timing: anytime
  • Radical ideas for making Thunderbird massively popular [davida]
    • size: 30-60 people
    • equipment: whiteboards, projector & screens
    • style: free thinking, open brainstorming, inspirational
    • timing: anytime
  • Thunderbird 3 planning [momo staff, etc]
    • size: 30-60 people
    • equipment: whiteboards, projector & screens
    • style: free thinking, open brainstorming, inspirational
    • timing: anytime
  • MailNews Refactoring [KaiRo, momo staff, etc.]
    • size: 30-60 people
    • equipment: whiteboards, projector & screens
    • style: free thinking, open brainstorming, inspirational
    • timing: after the Hg session
  • Next Generation Instant Messaging
    • size: 30-60 people
    • equipment: whiteboards, projector & screens
    • style: free thinking, open brainstorming, inspirational
    • timing: anytime
  • Beyond protocols: thinking about user experiences of communication [clarkbw, davida, ?]
    • size: 30-60 people
    • equipment: whiteboards, projector & screens
    • style: free thinking, open brainstorming, inspirational
    • timing: anytime
  • Thunderbird + Labs brainstorming (also listed under labs)
    • size: 30-60 people
    • equipment: whiteboards, projector & screens
    • style: free thinking, open brainstorming, inspirational
    • timing: anytime
  • What should we do about SUMO/Thunderbird/Mozillazine/etc.? [davida, dtenser]
    • size: 30-60 people
    • equipment: whiteboards, projector & screens
    • style: free thinking, open brainstorming, inspirational
    • timing: anytime
  • Plans for the move of Thunderbird/SeaMonkey/MailNews to Mercurial incl. Calendar's role in the future repository world [sipaq, KaiRo, ...]
    • size: 30-60 people
    • equipment: whiteboards, projector & screens
    • style: free thinking, open brainstorming, inspirational
    • timing: anytime
  • Raising developer interest and general interest in the calendar products [sipaq, daniel]
    • size: 30-60 people
    • equipment: whiteboards, projector & screens
    • style: free thinking, open brainstorming, inspirational
    • timing: anytime
  • Improving calendar community communication [sipaq]
    • size: 30-60 people
    • equipment: whiteboards, projector & screens
    • style: free thinking, open brainstorming, inspirational
    • timing: anytime
  • Calendar/TB3 integration plans
    • size: 30-60 people
    • equipment: whiteboards, projector & screens
    • style: free thinking, open brainstorming, inspirational
    • timing: anytime
  • Extensibility of Sunbird/Lightning [philipp]
    • size: 30-60 people
    • equipment: whiteboards, projector & screens
    • style: free thinking, open brainstorming, inspirational
    • timing: anytime
    • On the next day, the team could hold a talk discussing the top 10 ideas and how much of it is possible and how much is needed (optional)
  • SeaMonkey 2 planning/status [KaiRo]
    • size: 10-20 people
    • equipment: whiteboards, projector & screens
    • style: BoF, free thinking, open brainstorming, inspirational
    • timing: Tuesday?

Labs

(DRAFT)

  • Thinking About Web Services, Context and the Role of the Browser [cbeard]
  • Weave [thunder]
  • Snowl - an experiment around messaging in the browser [myk]
    • size: 25-50
    • style: demonstration & discussion
    • equipment: projector & screen
    • timing: any time after the main labs presentation
  • Ubiquity [aza]
  • Mixing desktop & browser and easing extension development pains [atul, aza]
  • Prism [mfinkle]
  • Lifecycle of a Labs Project []
  • Open Innovation at Scale []
  • Brainstorming Session []
  • JavaScript Tricks used in Labs Prototypes [thunder]
  • Thunderbird + Labs brainstorming (also listed under messaging)

Mozilla Mission and Identity

I'd like to have a series of sessions relating to Mozilla identity, mission and relationship to other open source and "open" projects. I'm thinking of the following; comments, suggestions welcome. Other session leaders very welcome as well; it's helpful to me to participate without leading sometimes.

Marketing/PR Related

  • Guerrilla marketing brainstorming session [polvi (& William)] Medium Working Session
  • Developing Mozilla in Asia (Asia ex-China, ex-Japan) [gen] Medium Working Session
  • Mozilla PR case studies [melissa & nicole] Medium Presentation (projector)
  • The Firefox brand: what it means and how to use it [jslater] (additional note: this might work well in a trademark/partnerships/logo track with some sessions that Harvey and Kev are developing) Medium Presentation (projector)
  • Mozilla in Europe - the impact of Fx 3 and initiatives for strong 2H08 growth[Jane] Medium Presentation (projector)
  • Europe - lessons in open source, community and culture [Gandalf/Jane] Large Presentation (projector)
  • Open Source Marketing - engaging the community and spreading Firefox in ways that are consistent with Mozilla values [jslater, mary, alix, rolnitzky, others] Large Presentation (projector)
  • Firefox in China - Firefox 3.0 and beyond [Jack] Medium Presentation (projector)
  • Thunderbird marketing - how should we do it? [davida] Medium Working Session
  • State of Spreadfirefox: what's working today, what should v3 look like? [alix] Medium Working Session
  • Firefox 3 spreading in Japan - [Shigeru] Presentation Medium
  • Plan about the new issue handling site for end-user in Japan - [himorin]
    • size : 20 to 30 or so (i think)
    • equipment : projector + screen and whiteboard
    • style : free thinking and open discussion after a short presentation of current state
    • timing : anytime
    • host : shimono (me), masayuki (+ some other Mozilla Japan staffs)
  • Foxkeh more global/official [shigeru, kaori] Presentation Meium

L10n Related

  • Localizing Firefox 3: Analysis of good and not so. "Nach dem Spiel ist vor dem Spiel." [Axel/Mic/L10n-drivers]
    • size: 50-100 people
    • equipment: whiteboards, projector & screens
    • style: free thinking, open brainstorming, inspirational
    • timing: 60 to 90 minutes
  • Expanding and better supporting international communities - community portal ideas [Seth/Mic/Gandalf]
    • size: 50-100 people
    • equipment: whiteboards, projector & screens
    • style: free thinking, open brainstorming, inspirational
    • timing: 60 to 90 minutes
  • Discussion on targeted community development and localization. How do we do a better job of recruiting, and bringing critical localizations and communities into the mix in upcoming releases? [chofmann/sethb]
    • size: 50-100 people
    • equipment: projector & screens
    • style: presentation followed by discussion
    • timing: 30-60 minutes
  • How can we scale better across all our products in more languages including emerging markets like Asia, Africa, etc. [Mic/Chofmann/Axel]
    • size: 50-100 people
    • equipment: whiteboards, projector & screens
    • style: free thinking, open brainstorming, inspirational
    • timing: 60 to 90 minutes
  • Problems of small translation teams with the l10n process. What can be done to make translation easier and more effective? [erdal]
    • size: 50-100 people
    • equipment: projector & screen
    • style: small presentation, discussion/brainstorming
    • timing: 60-90 minutes
  • moz2po and the rest of the Translate Toolkit - How to use them for Mozilla localisation, and some features that you might not be familiar with. Come and help to shape the next development phase of the tools which will specifically address Mozilla requirements (dwayne/friedel)
    • size: +-70
    • equipment: projector
    • style: presentation, discussion
    • timing: 60-90 minutes
  • Narro - Find out how you can speed up the localization process, increase the translation quality, make translations open to anyone and use Narro for translating almost anything [Alexandru Szasz aka alexxed]
    • size: 50 people
    • equipment: projector
    • style: presentation, discussion
    • timing: 60 minutes
  • Localizing SUMO - What should be the localization policy of SUMO? How do we get coverage for more locales for product help and prioritize knowledge base articles for translation? Do we want to ensure tier 1 locales always have all prioritized articles translated, or do we want it to be community-driven? [djst/mconnor]
    • size: 25-50 people
    • equipment: whiteboards
    • style: discussion
    • timing: 60 minutes
  • India - starting a viable, sustainable, smoldering Mozilla movement in a zany market. What are the opportunities for webtools and for l10n? [arun / sethb]
    • size: 15-20 people
    • equipment: whiteboards
    • style: discussion
    • timing: 60 minutes
  • QA on translation - Presentation of the pt-PT and french automated QA system - discussion of how to use QA and related translation memories. (Philippe and João Miguel Neves)
    • size: +-70
    • equipment: projector, computer, internet access
    • style: presentation, discussion
    • timing: 40 minutes
  • Anloc (pronounced Unlock) - adding 10 African languages to Firefox. An introductions to the Firefox localisation component of the global Anloc project. Discussion on how to help, support and mentor African Firefox localisers that will grow the African language community and sustain their localisation efforts. (Dwayne)
    • size: 15-20 people
    • equipment: whiteboard
    • style: discussion
    • timing: 60 minutes

Security

  • keeping an eye on malware trends. metrics, investigations, partnerships with scanning vendors (chofmann, dtenser, dveditz)
  • Updates around NSS and SSL. Planning for better handling of mixed security content. [kaie]
  • Manual penetration testing and how to practice good security techniques [pvnick]

Firefox, Product Development & User Experience Design

  • Firefox 3 Post Mortem [beltzner]
    • size: 50-100 people
    • equipment: projector & screens (will do laptop notetaking)
    • style: open discussion, roundtable
    • timing: early in the week
  • The Mozilla Design Process & How to Listen to Feedback [beltzner]
    • size: 50-100 people
    • equipment: projector & screens
    • style: presentation & discussion
    • timing: doesn't matter
  • Design Demos [faaborg, boriss]
    • size: 100+ people
    • equipment: projector & screens
    • style: demonstration & discussion
    • timing: end of day
  • Life After Awesome: How can we further improve the location bar? Where else should we apply the awesome-sauce of adaptive learning and multivariate scoring? [dietrich]
    • size: 25-50 people
    • equipment: whiteboards / easel pads
    • style: discussion & brainstorm
    • timing: doesn't matter
  • Make with the Pretty: BOF/Tutorial for visual design at Mozilla making icons, mockups, graphics [faaborg, boriss, shorlander?, tango team?]
    • size: 0-50 people
    • equipment: projector & screens
    • style: tutorial & discussion
    • timing: anytime

IT

  • Infrastructure overview Medium Projectors [Justin, MRZ]
  • How to build your application to best utilize IT's infrastructure Medium [Jeremy, MRZ]

Metrics

  • What data do you need to be able to improve your contribution to Mozilla? [deinspanjer/ken]
    • size: 25-50
    • equipment:
    • style: collaboration/round table
    • timing: after the metrics first talk
  • What questions should we be asking with our data? [ken]
    • size: 25-50
    • equipment:
    • style: brainstorm
    • timing: after the metrics first talk

QA


Accessibility

Webdev

  • MozillaID - community identity and single sign on. [laura]
    • size: 10-20 people
    • equipment: whiteboards, projector & screen
    • style: discussion
    • timing: 60 minutes