AMO:Meeting Notes: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 26: Line 26:
* We're keeping really detailed stats with the news feed which we delete after 3 months.  Perhaps we should store certain news indefinitely, like add-ons getting disabled or authors being added?
* We're keeping really detailed stats with the news feed which we delete after 3 months.  Perhaps we should store certain news indefinitely, like add-ons getting disabled or authors being added?
* [http://spreadsheets.google.com/ccc?key=0Aswo2Bn17-PrdHIzVWhDc0IycU5ZaEdySnNrSzItOXc&hl=en&invite=CKiE6swN Q4 releases]
* [http://spreadsheets.google.com/ccc?key=0Aswo2Bn17-PrdHIzVWhDc0IycU5ZaEdySnNrSzItOXc&hl=en&invite=CKiE6swN Q4 releases]
* AMO content finalization for 3.6 launch
** Customization
** First Run
** What's new
* Sports collection metrics
** http://spreadsheets.google.com/ccc?key=0Arf3nByedulrdGhGcHNyTHJTN0ZsMFd5M0U5S0NRZ1E&hl=en
* Blog naming finalization


== September 16 ==
== September 16 ==

Revision as of 17:01, 23 September 2009

AMO Project Meeting Details

Wednesdays, 10:00am Pacific, 1:00pm Eastern
1-800-707-2533 (pin 369) or 1-650-215-1282 or 1-650-903-0800
Conferencing Center: x92
Conference ID: 300

Common AMO Bugzilla Queries

September 23

  • 5.1 Status moxie
    • webdev
      • cesar working on a couple fizzypop bugs
      • status on contractor reskin?
    • content
      • case studies only remaining content
      • beta launch
  • Contributions update
    • Phase II
  • Add-on Collector update
  • We're keeping really detailed stats with the news feed which we delete after 3 months. Perhaps we should store certain news indefinitely, like add-ons getting disabled or authors being added?
  • Q4 releases
  • AMO content finalization for 3.6 launch
    • Customization
    • First Run
    • What's new
  • Sports collection metrics
  • Blog naming finalization

September 16

  • 5.1 status moxie
    • webdev
      • jbalogh working on builder
      • rdoherty patch for developer homepage r+'d
      • clouserw forums patch awaiting review by jbalogh
      • mccammos working on newsfeed backend
    • content
      • Case Studies and Getting Started left to write
      • Asked for editor review of policies
      • Asking for community review of docs today
      • logo positioning
    • Site is looking great!
  • Community Update
  • Review Process Redesign spec
  • There are a ton of "add my plugin to AMO" bugs. What do you want to do with them?
  • Add-ons blog naming

September 9

September 2

Ramones-Pleasant_Dreams-Frontal.jpg

  • 5.0.9 yay!
  • 5.1 yay!
    • Firefox string freeze is 9/14; ours is 9/17. :(
  • Giant CSVs
  • Community Update
  • AMO work week
  • Q4 release planning
5.2
Oct. 15		5.3
Nov. 5		5.4
Nov. 26
  • Personas Integration (Nick) [1]
  • Disclosure of Add-on Practices (Justin) [2]
  • Adding locales to statistics (Justin)
  • Remaining Fennec integration (Nick)
  • Download Sources in Stats Dashboard (Justin)
  • HTML/Links in Add-on Descriptions (Justin) [3]
  • Stub Entries (Justin)
  • Add-on Compatibility Reporter (Justin) [4]
  • Enhanced Localization (Nick) [5]
  • Get Satisfaction or other add-on discussion system (Nick) [6]
  • Release Channels (Nick) [7]

August 26

  • 5.0.9 Update
    • Paypal IPN?
  • 5.1 Triage this Thursday
    • Developer tools, need to come to a decision regarding launch date
    • Paypal dashboards
    • Share count widget
    • Top tag page
  • Bug 511321 - can we get it done soon?
    • QA's never been able to test related add-ons
  • Wil and I talked, and we're happy with RJ's unverified bugs - stephend
  • developer.AMO
    • Filing bugs today
    • Some bugs are higher priority to implement than others so we can start inserting content
  • Community Update
    • Add-on Meetups
      • NYC Meetup was great
      • Miami set for Sept 15
      • Chicago set for Sept 29
    • Burndown
    • 2 New Editors - Joe Emith & Alexandre Vautier
    • Geo-specific collections to be rotated in

August 19

August 12

  • 5.0.9 update
  • I think bug 501988 might be landing this time around so if you're not paying attention to that, heads up
  • Add-on Usage Stats blogged
  • Disclosure of Add-on Practices Spec
  • Compatibility Reporter Spec
  • Community Update
    • About-Addons newsletter
    • August, 2009 recommended list
    • AMO burndown on Aug 29 & 30
    • Getting feedback from editors on improving the review queue management & review process
    • NYC Add-on meetup next week - Aug 18th
      • Next 2 add-on meetup cities are Miami & Chicago
    • Geo-specific AMO front page collections management (BR,FR,UK,DE,JP,CN)
    • Extend Firefox on-going coordination & promotion

August 5

July 29

Clouseroo.png

July 22

  • 5.0.8 update moxie
  • clouserw will be at blackhat from 28th-2nd. From this far away it still seems like we can hit freeze but that may affect some of the timing. --clouserw
  • paypal tracking should be done offline via logs --clouserw
  • Bandwagon Phase II
  • Community Update:
    • 93% compatibility
    • Jetpack contest launching next Monday
    • about:add-ons newsletter
    • Geo-specific AMO collections

July 15

julio.png

July 8

855c.jpg

  • AMO 5.0.7 update moxie
  • Q3 projects
    • Bandwagon II - 5.0.9
    • developer.AMO - 5.0.10
    • Sandbox - 5.0.11
  • Community update

July 1

676874843_339d1d19ae.jpg

June 24

907017277_2f84c7816e.jpg

  • AMO 5.0.7 status
  • developer.AMO update
  • Jetpack Gallery
  • Community Update

June 17

Q3 mapping of features

June 9

Morgamic.jpg

  • AMO 5.0.7
    • bugs created
    • P1's are tagging and contributions
  • AMO 5.0.6
    • Signed, sealed, delivered, oh yeah!
    • How do we fix the issues with the collector login?
      • do we need to consider removing the ext completely if we can't fix it by EOD.
  • Community Update
    • Announcing a new editor today
    • Extend Firefox
      • Updated design completed
      • Working on updated copy
    • Personalized contact of add-on devs
    • YSlow & Pagespeed updating to 3.5

June 3

Aidan.jpg

  • AMO 5.0.6
  • Q2 Goals
  • Q3 Goals
    • Bandwagon Phase 2
    • Developer.AMO
    • Automated code audit tool
    • GetSatisfaction Pilot
    • Performance Metrics for add-ons
    • New sandbox
    • Release channels
    • Predictive dashboard for review time
    • Recruit 15 more editors (1.2/week)
    • Reduce average wait in queue to x (two?) weeks for both nominated and updates
    • Launch Jetpack Gallery
    • What else?
  • Community Update
    • Extend Firefox site redesign
    • AMO June Rotation
    • New editor - Andreas Wagner
    • Compatibility up 6% from last week
    • Burndown

May 27

3563955105 d924380919.jpg

  • add-on meet-up
  • AMO 5.0.6
    • New code freeze/release date
    • Nightly + Firebug + 5.0.6 == consistent crash (rdoherty)
      • Nightly + Firebug == flailing browser (clouserw)
  • AMO 5.0.7
    • Tagging Status
      • Would be great to get tagging in, especially if it's post 7/1
    • Contributions
      • Chris Howse has admin mocks, check with him if you want to see them
  • Community
    • Extend Firefox 3.5
    • Mini-burndown
    • Direct reach out to authors

May 20

  • AMO 5.0.6
    • Status!!!!!!
    • Progress report/what do we need from Clearleft?
    • Discuss revising the ship date for 5.0.6 and how it impacts 5.0.7
      • Impact on QA / scheduling
        • Pages ready on preview for test day on Friday?
    • Merge out existing L10n?
  • AMO 5.0.7
    • Contributions are the must-have feature for 5.0.7
    • Go over end user and chowse's admin mocks early next week to tee this up
    • Get Satisfaction integration is blocking on Get Satisfaction, the current widget integration could be considered a *light* version of what we want. I will follow up this week on what's going on with them
    • Search and Tagging
  • Add-ons meetup
    • If you're presenting, get ready
    • Will be on air.mozilla (fligtar and I got our training)
  • Community update
    • New Editor - Eylon Yogev
    • Extend Firefox 3.5
    • Mini-burndown

May 13

  • AMO 5.0.6
    • Progress report
    • Tagging design
    • Search design in progress
  • AMO 5.0.7
    • Chris Howse working on admin tools for contributions
    • 25 developers have signed up for the pilot so far
    • WebMocha starting on tagging
  • Community Update
    • Working on burn down day for editors
    • T-shirts going out hopefully this week
    • Extend Firefox
    • AMO May Rotation
    • Fx 3.5b4 compatibility mailing

May 6

  • AMO 5.0.6
    • What do we do before CL delivers code?
    • Bandwagon update
    • Don't forget L10n
  • Beyond 5.0.6
    • Need to figure out what we can do around add-on profiling
    • Contributions (aka why we have the flows we have)
    • Search design
    • Tagging design
  • SAMO
    • Should have this tested by the end of this weekend
  • Community update
    • Extend Firefox
    • AMO May Rotation
    • Fx 3.5b4 compatibility mailing
  • Welcome Chris Howse

April 22

TeAmoCorazon.jpg

  • AMO 5.0.5
    • how confident are we on the following bugs?
      • Category Page Redesign
      • Developer Agreement
  • New Home Page
  • AMO Meetup 5/26
    • Everyone encouraged to attend, book travel if you want to be there
    • Pizza + Beer + presos from us on AMO present and future
    • presentations from any add-on developers who want to show their warez
  • Ideas for new TLD
    • We're thinking of a domain for addons which is easier to remember. Post any ideas you may have here for hopefully available domains
      • fxaddons.com
      • mozaddons.com
      • foxyaddons.com
      • firefoxaddons.com (belongs to Mozilla already)
  • Bandwagon Update
    • M5 and M6 corresponding with 5.0.5 and 5.0.6
    • API bugs finished
    • ClearLeft design work coming along; Fred working on M5 bugs
    • Hoping to wrap up extension development by M5. l10n continues
    • full meeting notes
  • Community Update
    • Daniel Buchner working on a new JS framework for add-ons based on MooTools
    • Conduit discussions restarted
    • Re-prioritizing Editor reports & queue filtering for 5.0.6

April 15

  • AMO 5.0.5
  • Spec for Contributions
  • Home page concepts
  • omg, tax day
  • Are there any employees who write code who are not on amo-drivers@ ?
    • it includes webdev@ and I can't think of anyone not on it Fligtar 16:53, 15 April 2009 (UTC)
  • We're testing using bug priorities
  • Soon [tm], maybe we should give the user info pages a little design love. They are quite crowded (ex.) and the new "About Me" field adds to that. --wenzel
    • agreed. I mentioned this in bug 478088 - we're definitely getting more and more crowded there. Fligtar 16:53, 15 April 2009 (UTC)
  • Bandwagon Update
    • API extension blockers fixed yesterday
    • l10n starting today
    • hoping to wrap up extension development this week
  • Community Update

April 8

  • 5.0.4 update
  • Q2 task list
  • Bandwagon update
    • ClearLeft has begun work and will hopefully have Bandwagon pages ready in 3-4 weeks.
    • AMO 5.0.6 is dedicated to implementing the new homepage and Bandwagon designs
    • Extension localization and QA should begin this week
    • Top priorty bugs for the API and extension can be found in the Bandwagon meeting notes from this week
  • Community Update

April 1

March 25

  • 5.0.4 update
  • ClearLeft update
  • Bandwagon update
  • Community Update
    • Rey gone for rest of week; traveling to Berlin for MAOW keynote

March 18

  • 5.0.4 is fat and sassy
  • Fligtar has some bandwagon bugs (frontend work) which need to be worked into the schedule somehow.
  • clouserw is leaving at the end of the day and will return on March 28th or 29th
  • Community Update
    • about:addons newsletter sent out
    • Bugs submitted for phase 1 of editor PRD
    • Contacted authors re: upgrading to Fx 3.1b3
    • New editor: Yair Halevi (Spock)
    • Requested campus call-out from Jay

March 11

  • 5.0.3 -- push: bug 482605
  • Proposed 5.0.4 bugs finalized by EOD today
  • Community Update
  • Do we want to resurrect/re-file bug 424187 - "Increase ySlow score for all AMO pages to A"? (https://bugzilla.mozilla.org/show_bug.cgi?id=424187); we've slipped a bit -- both of the following used to be A's
    • B - Avoid CSS expressions
    • B - Minify JS
  • Anything else?

March 4

06:13 <tomeu> welcome, remora rocks ;)  
06:16 <tomeu> well, it is working very well for us
06:16 <tomeu> and the code base is the best php web app I have ever seen
06:25 <tomeu> I was very impressed by how css is used, also by that single png image containing all the backgrounds
06:26 <tomeu> we have mostly used css to hide unused stuff by now, but we should start soon to change the look to make it more similar to the sugarlabs sites

You said it, you can't unsay it! <3 :)

  • Code Freeze is March 9, Release is March 12

Feb 25

  • 5.0.3 update
  • Logo Update
  • Bandwagon Update (notes from meeting)
  • Community Update
  • Requesting comments on AMO submission stuff
    • New editor: Wind Li
    • Conduit
    • BarCamp Miami
    • Email to campuses
  • Other!

Feb 18

  • 5.0.2 launches this week (bug!)
  • 5.0.3 development starts
  • GetSatisfaction Update
  • Bandwagon Update (notes from meeting)
  • Community Update
    • Fx 3.1 Compatibility email sent
    • New editors: Wind Li (AutoPager) & Stephane Hamel (WASP)
    • Sent draft message to Jay Patel for campus recruiting
    • Still finalizing security issues w/ SurfCanyon, FireFTP & Ant.com Toolbar
    • Conduit conference call
    • Developer FAQ
    • AMO recommend rotation PRD
    • AMO Editor PRD
  • The organization of this page is confusing. Why is that stuff under 5.0.2? There should be some explanatory text about "phases" in the docs vs. AMO milestones too.
  • Other!

Feb 11

  • bugs assigned to nobody in 5.0.2 --clouserw
  • Do we allow <moz:UpdateUrl> elements in search engines?
  • 5.0.3 meeting
  • Bandwagon Update
  • Community Update
    • Feb 09 Rotation Completed
    • Added new editor Stephane Hamel
    • Expect compatibility mailing to go out this week
  • Get Satisfaction Thursday

Feb 4

  • Brown Bag Recap
  • 5.0.1 went out last week. Great work.
  • Next up is 5.0.2 (shared query)
  • Stats Update
  • Bandwagon Update
  • Q2 planning
  • Wladimir filed a pile of bugs last night. I'd like someone to take point and follow up on them. --clouserw
  • Community/Compatibility Update

Jan 28

Jan 21

  • Welcome Jeff Balogh
  • Welcome Justin Scott (again)
  • 5.0.1 status
    • Stats issues and potential resolution
    • bug 472784 (Preview is horked)
    • Developer Dash bug 473244
    • prev/next buttons bug 471706
    • alphabetized category listings bug 472164
    • Updated developer dashboard
    • Permalinks for latest versions
    • Revised category list bug 432665
    • Who takes care of (otherwise valid) add-ons with an empty GUID? bug 435075
    • Rey's request bug 455686
  • 3.1 compatibility update
  • Developer Agreement bug 436307
  • Community Update
    • Fx 3.1 compatibility email to go out this week
    • about:addons newsletter
    • More AMO blog posts up
    • T-shirts to reward editors
  • Bandwagon update

Jan 14

  • 5.0.1 status
  • Bandwagon designs, feedback
  • Bandwagon meeting later this afternoon
  • Q1 Goal review
  • Community Update

Jan 7

  • Introductions - introduce yourself to Nick, what you've worked on for AMO and what you work on outside of it
  • Pushes since Dec 19?
  • Statistics issues bug 469737
  • Sandbox issues bug 471201
  • Bandwagon designs, feedback
  • Add-Ons quarterly goals
  • Community Update
    • Audit survey
    • about:addons Newsletter
    • Email authors about Fx 3.1 compatibility

Earlier Meeting Notes

Retrieved from "https://wiki.mozilla.org/index.php?title=AMO:Meeting_Notes&oldid=170272"