Summit2008/Sessions/Proposals: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 130: Line 130:
* How to Hear Feedback [beltzner]
* How to Hear Feedback [beltzner]
* Leveraging the Lazyweb [beltzner]
* Leveraging the Lazyweb [beltzner]
== IT ==
* Infrastructure overview
* How to build your application to best utilize IT's infrastructure
== Metrics ==
* Data - how we collect, and what to do
* What data do you need to do your job better

Revision as of 04:28, 20 June 2008

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.

Sessions 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]
  • Partnering: What the heck does it mean, anyways [kev, who will also try and rope jay into participating]
  • How to stop guessing what the community thinks—the Community Surveys project [sethb, stas]
  • What questions should we be asking with our data? [ken]
  • How user-to-user support is the gateway into Mozilla for non-developers [sumo team]
  • Firebug/Chromebug (put where you like) [johnjbarton]
  • The new and improved MDC [sheppy]
  • 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]
  • Problems people find using Firefox and how to solve them [iacchi]
  • India - starting a viable, sustainable, smoldering Mozilla movement in a zany market [Arun]
  • Reducing testcases with Lithium [jesse]
  • What's happening with the www.mozilla.org site [davidwboswell]
  • Relationships and communication with Linux distros
  • 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]

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 maintainig 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 (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]
  • How do we improve the localization process for AMO [clouserw]

Web Platform Related

  • Rich Media on the Web [vlad]
  • Malware 2.0: Security concerns about the Web as a dominant application platform [ma1]
  • Web Standards and Strategy [arun]

Mozilla Platform Related

  • Using MDC:Mercurial [bsmedberg,jorendorff]
  • XPCOMGC introduction and planning [bsmedberg]
  • Hardware Acceleration & Gecko [vlad]
  • 1.9.1 progress updates and feature culling [roc]
  • Mozilla static analysis and rewriting tools and projects [dmandelin,taras?]
  • Positioning XULRunner as a general purpose platform [mfinkle]
  • L10n implications, how can we localize our mobile browser [mic]
  • Tamarin Tracing JIT intro, how it works [jimb]
  • Performance and memory tools for the Web platform [dbaron]

Mobile Related

  • Device APIs [dougt, aza]
  • Fennec Update [christian]
  • Embedding [blizzard]
  • Zephyr: The Firefox Phone [aza]
  • Mobile UX: [aza,madhava]
  • L10n process for mobile [mic, christian]
  • Writing add-ons for mobile [mfinkle]

Messaging/MailNews/Thunderbird Related

  • Brainstorm: How to ensure quality for Thunderbird with 1 full-time staff? [davida, ???]
  • Radical ideas for making Thunderbird massively popular [davida]
  • Thunderbird 3 planning [momo staff, etc]
  • MailNews Refactoring [kairo, momo staff, etc.]
  • Next Generation Instant Messaging
  • Beyond protocols: thinking about user experiences of communication [clarkbw, davida, ?]
  • Thunderbird + Labs brainstorming (also listed under labs)
  • What should we do about SUMO/Thunderbird/Mozillazine/etc.? [davida, dtenser]
  • ..

Labs

(DRAFT)

  • Thinking About Web Services, Context and the Role of the Browser [cbeard]
  • Weave [thunder]
  • Snowl [myk]
  • 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

Marketing/PR Related

  • Guerrilla marketing brainstorming session [polvi (& William)]
  • Discussion on growing Mozilla in Asia (focus on Asia ex-China, ex-Japan) [gen]
  • Behind the smoke and mirrors: Mozilla PR case studies - better title tbd [melissa & nicole]
  • 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)
  • Mozilla in Europe - the impact of Fx 3 and initiatives for strong 2H08 growth[Jane]
  • Europe - lessons in open source, community and culture [Gandalf/Jane]
  • Open Source Marketing - engaging the community and spreading Firefox in ways that are consistent with Mozilla values [jslater, mary, alix, rolnitzky, others]
  • Firefox in China - Firefox 3.0 and beyond [Jack]
  • Thunderbird marketing - how should we do it? [davida]

L10n Related

  • Localizing Firefox 3: Analysis of good and not so. "Nach dem Spiel ist vor dem Spiel." [Axel, l10n-drivers]
  • Expanding and better supporting international communities [Seth&Mic&Gandalf]
  • 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 ]
  • How can we better scale across all our products in more languages including emerging markets like Asia, Africa, etc. [Mic, Chofmann, Axel]
  • The world of l10n through the eyes of a small translation team [erdal]
  • moz2po - using them for Mozilla localisation including some that you might not be familiar with. Help shape the next development phase of the tools which will specifically address Mozilla requirements (dwayne/friedel)

Security

  • Fuzzing [jesse]
  • keeping an eye on malware trends. metrics, investigations, partnerships with scanning vendors (chofmann, dtenser, dveditz)

Product & User Experience Design

  • History & Future: Imagining the web browser of 2015 [faaborg, wei]
  • What are people doing with web browsers [wei]
  • The Mozilla Design process [beltzner]
  • Design Demos [beltzner]
  • How to Hear Feedback [beltzner]
  • Leveraging the Lazyweb [beltzner]

IT

  • Infrastructure overview
  • How to build your application to best utilize IT's infrastructure

Metrics

  • Data - how we collect, and what to do
  • What data do you need to do your job better