Firefox/Input/Meeting Notes

From MozillaWiki
< Firefox‎ | Input
Jump to: navigation, search

Meeting Notes

4.2

6-14-2011

4.1 release

  • dashboard is negative

4.2 release

  • reduce differences between search and dashboard
  • elasticsearch integrated


take-aways:

  • davedash and michaelk will be working together on grouperfish on Thursday
  • grouperfish timeline is uncertain
  • webdev on work week 20th-24th
  • tofumatt not available from 7/4-7/8

4.1

5-31-2011

what's been completed:

dev

  • released 4.0 without any problems
  • currently working on 4.1 bugs

metrics

  • Found a problem with the current opinions export (bug 653532, 660859). Working with Eshwaran (new intern) on PCA, and with Xavier on rebuilding the REST service in java for better code reuse (on git branch). Got started on the Grouperfish bugs -- not done yet.

qa

  • verified bugs for 4.0 release
  • davehunt and theautomatedtester got automation working again due to

product

  • working with metrics on dashboards
  • getting help from Mossop on experimental input add-on

what we aim to do over the next week:

dev (davedash, jlongster, tofumatt, wenzel)

  • currently working on 4.1 bugs
  • code freezing by the end of this week

metrics

  • Sync up with Dave on the Grouperfish integration once he’s back.

qa

  • work on mobile dashboard quality checks

product

  • work on add-ons manager experimental extension

Flags:

  • tofumatt: mobile dashboard is coming up with bugs, will need to find tests
  • 7.0a1 and 6.0a2 aren't up on input dashboard; tofumatt will file a bug to run the php script that is most likely causing the problem

4.0

5-24-2011

what's been completed:

dev

  • jlongster: working on 4.1 bug fixes
  • davedash handed off to wenzel before goign on vacation
  • wenzel: pushed twice for work-around patches on newly pushed betas

metrics

  • working on bugzilla dashboards
  • new intern to work on grouperfish with michaelk

qa

  • unplugged the grid

product

  • work on bug lists

what we aim to do over the next week:

dev (davedash, jlongster, tofumatt, wenzel)

  • finish up mobile submission pages
  • wenzel: filling in for davedash, will do the push on thursday
  • tofumatt: finish up mobile dashboard

metrics

  • fixing remaining grouperfish bugs, then start on integration

qa

  • will give ok on quality of 4.0 release

product

  • send out graphics library analysis spreadsheet to the team
  • work on input add-on for add-on manager

Flags:

  • code frozen
  • moving from one aurora major version to major version

3.5

5-17-2011

what's been completed:

dev

  • jlongster: mobile submission pages are basically done, need to fix some small issues
    • other bugs can be finished by Friday
  • davedash: grouperfish moved out, elasticsearch

metrics

  • working on bugzilla dashboards

qa

product

  • standalone feedback button
  • talked to product team about roadmap

what we aim to do over the next week:

dev (davedash, jlongster, tofumatt)

  • work on elastic search for Input
  • finish up mobile submission pages

metrics

  • fixing remaining grouperfish bugs, then start on integration

qa

product

  • work on bug lists
  • work on input add-on for add-on manager

flags

  • james and davedash have a lot of stuff on his plate right now; we'll be awkward dancing over the next month or so

5-10-2011

what's been completed:

dev

  • code froze 3.5

metrics

  • grouperfish isn't working right yet
  • worse is in august

qa

  • signed off on 3.5

product

  • presenting to product team today
  • worked on add-on for Input

what we aim to do over the next week:

dev (davedash, jlongster)

  • looking into elastic search for Input

metrics

  • At Google IO and have other projects to work on

qa

  • mbrandt not available
  • not expecting much

product

  • work on bug list for 4.0
  • finalize any work needing to be done with

5-3-2011

what's been completed:

dev

  • working with michaelk on standing up grouperfish
  • jlongster ready to merge for mobile submission pages
  • wenzel not available for reviews

metrics

  • standing up grouperfish
  • 100% unit tests passing
  • trying to land for 3.5

qa

  • sat down with dave to get foresight
  • refactored automation for channels, so no more surprises
  • ready for 3.5

product

  • talked to wikipedia folks
  • worked on feedback strategy
  • worked on UX for mobile submission pages with chowse

what we aim to do:

dev (davedash, jlongster)

  • code freeze for 3.5

metrics

  • debug grouperfish with davedash
  • go/no-go decision for 3.5

qa

  • mbrandt at conf, rbillings will qa for 3.5

etc.

  • work on standalone feedback button definition
  • talk about roadmap to product team

3.4

4-26-2011

What's been completed:

  • dev
    • jlongster: done with styling happy/sad/ feedback
    • davedash: done with 3.4 stuff and working on 3.5
  • mbrandt
    • file/verifying bugs
    • trying to get automation fixed
  • aakashd
    • added happy/sad to NNT Mobile
    • worked on feedback strategy for Fx/Fx Mobile

What we aim to do and when do we expect to accomplish them:

  • dev
    • jlongster
    • davedash: releasing 3.4 on 3/28; working on 3.5 bugs (code freeze on 5/6)
    1. finish grouperfish consumption
  • mbrandt
    1. fix automation for new channels process
    2. 3.4 looks good and feels comfortable with the push
  • aakashd
    1. talking to wikipedia on friday
    2. working on feedback strategy for Fx/Fx Mobile
  • Flags
    • mbrandt out 5/10-5/15
    • davedash out fridays and last week of may
    • wenzel out 5/2-5/14

3-29-2011

What's been completed:

  • fwenzel
    • released 3.3.1-3.3.4
  • davedash
    • working on consuming grouperfish
  • ryansnyder
    • working less on input
  • michaelk
    • cursing mahout; no tracebacks
  • mbrandt
    • having a testday for selenium automation
  • aakashd
    • talked to folks on NTT on nightlies

What we aim to do and when do we expect to accomplish them:

  • fwenzel
    1. release 3.3.5 with release dashboard
  • davedash
    1. finish grouperfish consumption
  • ryansnyder
    1. working no time for Input; talk to jlongster
  • michaelk
    1. offer a working prototype and get it working with dave's consumption code
  • mbrandt
    1. testing 3.4;
  • aakashd
    1. work on wiki for input 4.0 and channel changes
    2. work on constructivity meter


3-15-2011

What's been completed:

  • fwenzel
    • released 3.3 on sunday
    • visited pycon
  • davedash
    • filed IT bugs for Input-sphinx
  • code reviews
  • ryansnyder
    • worked on 3.3 bugs
  • michaelk
    • worked on grouperfish
  • mbrandt/rbillings
    • released 3.3
  • aakashd
    • wrote a SWOT for NTT on nightlies
    • talked to folks on AMO for input and api consumption
    • wrote out wiki's for 4.x

What we aim to do and when do we expect to accomplish them:

  • fwenzel
    1. assign 3.4 bugs to folks
    2. determine dev scheduling
  • davedash
    1. consume metrics data for input
    2. fixing highchart issues
  • ryansnyder
    1. work on 3.4 bugs
  • michaelk
    1. work on grouperfish
  • mbrandt/rbillings
    1. make a test plan for 3.4
    2. bug 636173 must
  • aakashd
    1. talk to legneato with wenzel
    2. start requirements gathering on 5.0

3.3

3-8-2011

What's been completed:

  • fwenzel
    • ideas themes page are done
  • string and code frozen
  • davedash
    • finished beta overlay
  • ryansnyder
    • got caught up with Fx4 stuff
  • michaelk
    • working on clustering via grouperfish
  • mbrandt/rbillings
    • seeing server errors, IT is looking into it
  • aakashd
    • finished 4.0 PRD
    1. press is open to more info from Input to send out to folks

What we aim to do and when do we expect to accomplish them:

  • fwenzel
    1. ready to release on tuesday, but might need to release earlier dur to fx4 rc1 release
  • davedash
    1. Lots of little bugs to fix
    2. if that's finished, then look into elastic search
  • ryansnyder
    1. pick up 3.4 bugs
  • michaelk
    1. GET GROUPERFISH DONE NOW KTHX
  • mbrandt/rbillings
    1. everything looks good for release
  • aakashd
    1. do initiative stuff with API
    2. have planning meeting on Input 4


Flags

  • Release may need to go out earlier due to Fx4 RC shipping on the 15th
  • will need to lessen scope on 3.4


3-1-2011

What's been completed:

  • fwenzel
    • brought up the ideas themes page
  • davedash
    • didn't have much time for Input
  • ryansnyder
    • haven't had a lot of time due to socorro
  • michaelk
  • mbrandt/rbillings
    • not much to test on Input, waiting for test data
  • aakashd

What we aim to do and when do we expect to accomplish them:

  • fwenzel
    1. fix "ideas" themes page
    2. run test data with IT
    3. triage 3.3 bugs
  • davedash
    1. work on 3.3 graph work
  • ryansnyder
    1. fix p3; possibly pick 3.4
  • michaelk
    1. work on clustering before Fx4 ships
  • mbrandt/rbillings
    1. test Input
  • aakashd
    1. add build id's to url charts
    2. finish 4.0 PRD
    3. work with metrics on clustering sync-up

3.2

2-22-2011

What's been completed:

  • fwenzel
    • release 3.1
  • davedash
    • finished 3.2 bugs
  • ryansnyder
    • knocked out 3.2 bugs
  • michaelk
  • mbrandt/rbillings
    • wrote some automated tests for Input
  • aakashd
    • started scope work for Input 4.x

What we aim to do and when do we expect to accomplish them:

  • fwenzel
    1. release input 3.2
    2. follow-up with michaelk for clustering
    3. triage 3.3
  • davedash
    1. work on all bugs for 3.3
  • ryansnyder
    1. will work on bugs assigned to me by next monday
  • michaelk
  • mbrandt/rbillings
    1. work on test failures
  • aakashd
    1. have meetings about 4.x Input stuff
    2. scope out 3.4 and 4.x work
    3. start on a PRD

3.1

2-15-2011

What's been completed:

  • fwenzel
    • good for release
    • most of 3.2 work has been completed
  • davedash
    • input 3.2
  • ryansnyder
    • worked on 3.2 and mobile submission pages
  • michaelk
    • working on clustering service
  • mbrandt/rbillings
    • qa verified 3.1, looks good
    • trying to wrap around automation for Input
  • aakashd
    • got t-shirts in and gave to folks in the office

What we aim to do and when do we expect to accomplish them:

  • fwenzel
    1. release input 3.1
    2. need to determine if 3.2
  • davedash
    1. stragglers for 3.2
  • ryansnyder
    1. finish up some 3.2 bugs, but they're low-priority
  • michaelk
    1. trying to push for big clusters for 3.3 release
  • mbrandt/rbillings
    1. look into inconsistent failures
  • aakashd
    1. send t-shirts out
    2. scope out 3.4 and 4.x work


2-1-2011

What's been completed:

  • fwenzel
    • reviewing 3.1 patches
  • davedash
    • finished release dashboard for rate
  • ryansnyder
    • mostly done with mobile submission pages
  • michaelk
    • sites theme is done on branch, now waiting
  • rebecca
    • worked on SUMO and started ramping up Matt
  • aakashd
    • did the lightning talk about input
    • talking to vendors and lee

What we aim to do and when do we expect to accomplish them:

  • fwenzel
    1. file bugs for 3.2 and 3.3
  • davedash
    1. finishing up on release dashboard
  • ryansnyder
    1. fixed 3.1 bugs
  • michaelk
    1. waiting for versioning stuff to land, then will rebase and push it
  • rebecca
    1. verify bugs and get ready for release
    2. work with matt
  • aakashd
    1. get t-shirt orders done

Flags:

3.0

1-25-2011

What's been completed:

  • fwenzel
    • assigned bugs for 3.1
    • working on channel switcher
  • davedash
    • channels framework work
    • middleware decides which channel you're in
  • ryansnyder
    • refactoring 3.1 work
    • dealing with failing tests in sandbox due to changes from 3.0 to 3.1
  • michaelk
    • QA'd export to tsv work
  • rebecca
    • verified/filed all 3.0 bugs
  • aakashd
    • did the brownbag and created a follow-up doc on use cases for input
    • talking to vendors

What we aim to do and when do we expect to accomplish them:

  • fwenzel
    1. finish channel switcher
    2. finish review requests
  • davedash
    1. finishing up on release dashboard
  • ryansnyder
    1. fixed 3.1 bugs
  • michaelk
    1. review request for broken sites on major release dashboard
    2. bugzilla work is piling up and need to work on that
  • rebecca
    1. wrap-up testing for 3.0
    2. SUMO release on Wednesday
  • aakashd
    1. get t-shirt orders done
    2. write up a mini-search plugin

Flags:


1-18-2011

What's been completed:

  • fwenzel
    • 3.0 is code and string frozen
  • davedash
    • added themes work for "All"
  • ryansnyder
    • finished 3.0 bugs
  • michaelk
    • copy ux
  • rebecca
    • verified/filed bugs
  • aakashd
    • posted a screencast of basic features on input
    • set up testday with localizers

What we aim to do and when do we expect to accomplish them:

  • fwenzel
    1. need to fix a css and rendering bug
    2. Assign bugs for 3.1
  • davedash
    1. will work on previous beta theme reports
    2. make links permanent
  • ryansnyder
    1. will look at 3.1 bugs
    2. a little bit
  • michaelk
    1. work on 3.1 bugs
  • rebecca
    • emergency training and SUMO training
    • will file and verify bugs
  • aakashd
    1. work on brownbag, 1/20
    2. have a testday on bugdays/testdays with localizers


1-11-2011

What's been completed:

  • fwenzel
    • fixing bugs with 4 left on 3.0
    • worked on 3.x roadmap
    • talked to jono about feedback add-on on beta channel
  • davedash
    • prioritized themes bugs and started work on versioning and "all" issues
  • ryansnyder
    • couple of bugs fixed
  • michaelk
    • copy ux
  • stephend
    • verifying bugs
  • rebecca
    • verifying bugs
    • figured out user agent stuff
  • aakashd
    • created a brownbag
    • sent out email to seth for triaging locale feedback

What we aim to do and when do we expect to accomplish them:

  • fwenzel
    1. work with michaelk
    2. fix assigned bugs
  • davedash
    1. work on themes work for 3.x
  • ryansnyder
    1. fix remaining bugs, 1/12
    2. unavailable until next tuesday
  • stephend
  • rebecca
    • verify 3.0 bugs
    • follow-up on a ramp-up document on how to test Input (i.e. UA stuff)
  • michaelk
    1. finish up remaining 3.0 bugs
  • aakashd
    1. work on brownbag, 1/20
    2. work on bugdays/testdays with localizers

1-4-2011

What's been completed:

What we aim to do and when do we expect to accomplish them:

  • fwenzel
    1. work with michaelk
    2. fix assigned bugs
  • davedash
  • ryansnyder
    1. fix 3-4 assigned bugs
  • stephend
  • rebecca
    • verify 3.0 bugs
  • michaelk
    1. finish sites clusters metrics job to speed things up
  • aakashd
    1. finish up input 4.0 mock-ups
    2. start work on the PRD
    3. start up education work with localizers on triaging input data into bugs

Flags:

  • bug 620845 - cannot search for recently submitted feedback
    • when its broken, its broken on staging and prod
    • reproducible only sometimes

2.1

12-07-2010

What's been completed:

  • fwenzel
    • branching for 3.0
  • davedash
    • integrated ideas and mobile device type on dashboard
  • ryansnyder
    • committed work for 2.1
  • michaelk
    • started work on 2.1 bugs
  • stephend
    • on dedicated hardware with IT for staging
    • not sure about performance testing, been cobbling...need a baseline
  • aakashd
    • look into bizdeving an open-source version of the library for AMO, Input and other projects, 12/3
    • worked with juanb and ashughes on lesson plan for localizers
    • mocked up client-side changes for major releases

What we aim to do and when do we expect to accomplish them:

  • fwenzel
    1. branching for 3.0
    2. start assigning out issues for 3.0
  • davedash
    1. fix remaining bugs for 2.1, 12/7
  • ryansnyder
    1. start work on 3.0, 12/7
  • stephend
    1. get a perf baseline, 12/9
    2. work on better coverage on automation
    3. rebecca billings for 3.0, 12/14
  • michaelk
    1. finish off 2.1 bugs, 12/7
    2. ramp-up on 3.0, 12/14
  • aakashd
    1. look into bizdeving an open-source version of the library for AMO, Input and other projects, 12/3
    2. work on getting input used by localizers, 12/9
    3. work on client-side changes to feedback add-on, 12/14

Flags:

  • un-assigned bugs for 2.1
  • Enable submissions on staging from mobile nightlies

11-30-2010

What's been completed:

  • fwenzel
    • released 2.0.1
    • got device type working
  • davedash
    • worked on incorporating suggestions onto highchart and search
  • ryansnyder
    • pushed suggestions onto staging
  • michaelk
    • started work on 2.1 bugs
  • stephend
    • started work on automation with david burns
  • aakashd
    • working on input with localizer feedback per beta
    • moar promotions in mobile firefox since people can't

What we aim to do and when do we expect to accomplish them:

  • fwenzel
    1. finished off the traceback bug for 2.1, 11/30
    2. determine a time and schedule for code freeze, 12/3
    3. start work on submission pages for 3.0
  • davedash
    1. ask IT for crons running on staging, 11/30
    2. get suggestions into search and line charts, 12/3
    3. get device type for mobile dashboard and search, 12/3
  • ryansnyder
    1. fixing p2/p3's assigned for 2.1, 12/3
  • stephend
    1. determine a more formal environment (i.e. where and when) to run qa tests on staging, 12/3
    2. continue on automation for Input
  • michaelk
    1. finish off 2.1 bugs, 12/3
  • aakashd
    1. look into bizdeving an open-source version of the library for AMO, Input and other projects, 12/3
    2. work on getting input used by localizers, 12/1

Flags:

  • chowse is done with mock-ups, going forward with stylings for 3.0
  • 3.0 vs 2.1: resourcing
  • plan for bundling highcharts and using another library in the future
  • staging
    • '1day ago': the cron runs daily at noon
    • determine a more formal environment (i.e. where and when) to run qa tests on staging

11-23-2010

What's been completed:

  • fwenzel
    • interesting push with IT, learned a lot more about release process
  • davedash
    • worked on releasing 2.0
    • reviewed ideas
  • ryansnyder
    • got ideas reviewed
  • michaelk
  • stephend
    • vish_moz is working on selenium tests; page object model is done
    • prathiba is working on manual coverage
  • aakashd
    • created blogpost
    • worked on 3.0 design work

What we aim to do and when do we expect to accomplish them:

  • fwenzel
    1. release 2.0.1, 11/23
    2. will assign remaining 2.1 bugs
  • davedash
    1. ideas integration
  • ryansnyder
    1. fixing p2/p3's assigned for 2.1
  • stephend
    1. slow on automation for input, will ask david burns to look into it
    2. check up on feedback submission issue
  • michaelk
  • aakashd
    1. talk with google user support about input, 11/30
    2. work on getting input used by localizers, 12/1

Flags:

  • look at feedback submission issue on staging
  • release 2.0.1 at 4pm today

2.0

11-16-2010

What's been completed:

  • fwenzel
    • fixed remaining small input 2.0 bugs
  • davedash
    • all-in with AMO, but helped out with some bugs for Input
  • ryansnyder
    • done with 2.1 and ready to merge after release
  • michaelk
  • stephend
    • verified bugs
    • created test run for input in litmus
    • slow on automation for input
  • aakashd
    • sent out e-mail to l10n group for input triage
    • worked with chowse on 3.0 mock-ups

What we aim to do and when do we expect to accomplish them:

  • fwenzel
    1. hash out remaining bugs
    2. code freeze pushed out to 11/11, release date 11/16
  • davedash
    1. start work on integrating ideas into graphs and search
  • ryansnyder
    1. get in ideas and fix other 2.1 issues
    2. second priority
  • stephend
    1. slow on automation for input, will ask david burns to look into it
  • michaelk
  • aakashd
    1. work on 2.0 blogpost

Flags:

  • 4pm push; Dave Dash and krupa will be available.
  • Dave will tag 2.0

11-9-2010

What's been completed:

  • fwenzel
    • fixing lots of p2's and assigning
  • davedash
    • incorporated search and high charts
  • ryansnyder
    • finished most of ideas
  • michaelk
  • stephend
    • london
  • aakashd
    • finished NTT for mobile
    • finished data challenge ideas/themes for dees

What we aim to do and when do we expect to accomplish them:

  • fwenzel
    1. hash out remaining bugs
    2. code freeze pushed out to 11/11, release date 11/16
  • davedash
    1. full-time committed to AMO
  • ryansnyder
    1. rebase to 2.1 and work on ideas
  • stephend
    1. verify everything after code freeze; litmus testcases
  • michaelk
  • aakashd
    1. work on 2.0 blogpost

11-2-2010

What's been completed:

  • fwenzel
    • graphs without data, passed down to dave to add in the data
    • minified css/js files and improved YSlow score
  • davedash
    • finished faceted search
  • ryansnyder
    • 100% on socorro and have a rollout tonight
  • michaelk
    • finished a few sites
  • stephend
    • verified bugs, wrote some litmus testcases
  • aakashd
    • finished product roadmap blogpost
    • talked to desigan about input and design challenges

What we aim to do and when do we expect to accomplish them:

  • fwenzel
    1. work on copy user agent, 11/5
    2. look at p2's, 11/5
  • davedash
    1. finish graphs, 11/2
  • ryansnyder
    1. finish ideas, 11/3
    2. file a bug on search and graph work incorporating ideas, 11/2
  • stephend
    1. in London for the week, krupa and vishal will occur on verifications and bug filing
  • michaelk
    1. fix remaining 2.0 bugs, 11/5
  • aakashd
    1. write out some data challenges, 11/5

Additional/Flags

  • Data Challenges: improve clustering both in making the connections tighter and faster

10-26-2010

What's been completed:

  • fwenzel
    • worked on graphs and assignments
  • davedash
    • worked on faceted search
  • ryansnyder
    • worked mostly on Socorro
  • michaelk
    • fixed duplicate domain and other bugs
  • stephend
    • verified CSRF issues and 1.9 release
  • aakashd
    • finished 3.0 PRD
    • set up a bunch of meetings on tuesday

What we aim to do and when do we expect to accomplish them:

  • fwenzel
    1. finish graphs, 10/29
  • davedash
    1. finish faceted search, 10/26
  • ryansnyder
    1. work on ideas, 11/3
  • stephend
    1. verified some bugs, start work on mobile stuff 10/29
  • michaelk
    1. fix remaining 2.0 bugs, 11/3
  • aakashd
    1. have a product planning meeting for 3.0
    2. post out product roadmap blogpost, 10/29
    3. work with design challenge folks, 10/29

10-19-2010

What's been completed:

  • fwenzel
    • 1.9 bugs and moving over to America
  • davedash
    • CSRF fun. Worked over the weekend
  • ryansnyder
    • Worked mostly on Socorro
  • michaelk
    • Class!
  • stephend
    • Verified CSRF issues and 1.9 release
  • aakashd
    • Finished 3.0 PRD

What we aim to do and when do we expect to accomplish them:

  • fwenzel
    1. assign out 2.0 bugs
  • davedash
    1. Work on faceted search
  • ryansnyder
    1. Work on 2.0
  • stephend
    1. Coverage is good, work on mobile coverage
  • michaelk
    1. work on multiple sites and domains
    2. get any bugs related to product
  • aakashd
    1. Create a product roadmap meeting
    2. Review finished 3.0 PRD

Notes:

  • Thanks Dave!

1.9

10-12-2010

What's been completed:

  • fwenzel
    • 1.9 bugs
  • davedash
    • Fixed themes by product
    • CSRF bug
    • staging crons
  • ryansnyder
    • feedback landing page landed
  • michaelk
    • fixed ssl, product differentiation on sites
    • can't work on differentiation
  • stephend
    • filed a bunch of bugs, verified mostly all bugs
    • wrote some litmus testcases
  • aakashd
    • Worked on 3.0 PRD
    • Talked to Dev Tools and Automation about Input on NTT

What we aim to do and when do we expect to accomplish them:

  • fwenzel
    1. scrounging for 1.9 bugs
  • davedash
    1. Work on 2.0 bugs
  • ryansnyder
    1. Pick up 2.0 bugs
  1. Talk to michaelk on 10/6/ morning about remaining 1.9 bugs
  • stephend
    1. Digure out what's going on with bug 602427, 10/14
    2. Continue verifying 1.9 bugs, 10/14
    3. Regression-test and file any bugs, 10/14
    4. Need to verify csrf bug, 10/12
  • michaelk
    1. Working on 2.0 bugs
  • aakashd
    1. Push back remaining 1.9 bugs to 2.0, 10/12
    2. Finish 3.0 PRD, 10/16
    3. Schedule a product planning meeting (10/25-10/29) about Input over the next 6-9 months, 10/25


10-05-2010

What's been completed:

  • fwenzel
    • Immigration stuff
  • davedash
    • CSRF bug, will finish this week
    • Will look into bug 601015
  • ryansnyder
    • Working on Socorro
  • stephend
    • Prathiba should be writing testcases on litmus
  • aakashd
    • Talked to chowse and horlander about Input 2.0 and 3.0 icons
    • Determine scalability of major release support

What we aim to do and when do we expect to accomplish them:

  • fwenzel
    1. COMIN' TO THE USSAAA
  • davedash
    1. I plan on tackling some of the 1.9 bugs that cropped up in the last day. I expect to have some time this or next week to dive into that.
  • ryansnyder
    1. Back on Socorro through Tuesday, at which time I'll pick up Input 1.9 tickets, 10/12
  1. Talk to michaelk on 10/6/ morning about remaining 1.9 bugs
  • stephend
    1. Circle back with Prathiba on litmus testcasea additions, 10/12
    2. Continue verifying 1.9 bugs, 10/12
    3. Regression-test and file any bugs, 10/12
  • michaelk
    1. Working on bug 600209, 10/12
  • aakashd
    • Talk to Erik Moeller from Wikipedia, 10/6
    • Get Input 2.0 & 3.0 icons and post into bugs, 10/8
    • Started work on 3.0 PRD, 10/16

Notes:

  • Stephend is unsure on how to get data on themes and sites

9-30-2010

What's been completed:

  • fwenzel
    • Working on movin' to America
  • davedash
  • ryansnyder
    • Identified 1.8 did not get pushed in its entirety yesterday
  • stephend
    • Flagged several bugs for Litmus tests (to be written by

Pratihba/Rebecca/myself)

    • Committed to 1.9/2.0
  • aakashd
    • Worked on scheduling/resourcing Input 2.0 with morgamic
    • Stephen Horlander will have the Idea Submission icons ready to go by the end of this week or early next week
    • Talked to chowse on availability on 2.0 features

What we aim to do and when do we expect to accomplish them:

  • fwenzel
    1. Will poke my nose into 1.9 bugs, 10/1
  • davedash
    1. I plan on tackling some of the 1.9 bugs that cropped up in the last day.  I expect to have some time this or next week to dive into that.
  • ryansnyder
    1. Back on Socorro through Tuesday, at which time I'll pick up Input 1.9 tickets, 10/12
  • stephend
    1. As time permits, write Litmus tests for existing features, 10/12
    2. Continue verifying 1.9 bugs, 10/12
    3. Regression-test and file any bugs, 10/12
  • michaelk
    1. Working on bug 600209, 10/12
  • aakashd
    • Start work on 3.0 PRD, 10/16
    • Make sure chowse knows he'll need to devote some time to 3.0 work this quarter, 10/1
    • Determine scalability of major release support, 10/16
    • Talk to Wikimedia, 9/30

9-28-2010

What's been completed:

  • fwenzel
  • Crunched 1.8 bugs (with Ryan)
  • tagged 1.8 for production
  • waited in vain for the push to happen this morning
  • davedash
    • Nothing - AMO has been beating me like a red-headed step child
  • ryansnyder
    • Added product / version dropdowns per #590688
  • hamilton
    • Demo'd on LDA Topic Modeling per Platform & Type
  • stephend
    • Verified FIXED 1.8 bugs
    • Filed a few bugs
  • aakashd
    • Worked on scheduling/resourcing Input 2.0 with morgamic
    • Stephen Horlander will have the Idea Submission icons ready to go by the end of this week or early next week
    • 3 Talked to chowse on availability on 2.0 features

What we aim to do and when do we expect to accomplish them:

  • fwenzel
    1. not much "actual work" for the rest of the quarter: movers are coming, approx. a bazillion forms want filled out, and your guys' embassy wants to interview me...
  • davedash
    1. Finish my AMO stuff early this week and crank on any bugs assigned to me., 9/20
  • ryansnyder
    1. Picking up bugs for 2.0 release, 9/15
  • stephend
    1. Keep trying to stay sane
    2. See above., 9/28
  • aakashd
    1. Start work on 3.0 PRD, 10/16
    2. Make sure chowse knows he'll need to devote some time to 3.0 work this quarter, 10/1
    3. Determine scalability of major release support, 10/16
    4. Talk to Wikimedia, 9/30

1.8

9-21-2010

What's been completed:

  • fwenzel
  • Crunched 1.8 bugs (with Ryan)
  • tagged 1.8 for production
  • waited in vain for the push to happen this morning
  • davedash
    • Nothing - AMO has been beating me like a red-headed step child
  • ryansnyder
    • Added product / version dropdowns per #590688
  • hamilton
    • Demo'd on LDA Topic Modeling per Platform & Type
  • stephend
    • Verified FIXED 1.8 bugs
    • Filed a few bugs
  • aakashd
    • Talked to Wikimedia Foundation. They want to learn about the design and implementation decisions made for user submission.
    • Worked on defining roadmap into Q4 and filed bugs via Mr. Alexis's webform

What we aim to do and when do we expect to accomplish them:

  • fwenzel
    1. not much "actual work" for the rest of the quarter: movers are coming, approx. a bazillion forms want filled out, and your guys' embassy wants to interview me...
  • davedash
    1. Finish my AMO stuff early this week and crank on any bugs assigned to me., 9/20
  • ryansnyder
    1. Picking up bugs for 2.0 release, 9/15
  • stephend
    1. Keep trying to stay sane
    2. See above., 9/28
  • aakashd
    1. Start on PRD for Input 3.0 designs and requirements, 10/8
    2. Push out blogpost for 1.8, 9/28


9-14-2010

What's been completed:

  • fwenzel
    • Fixed some P1 bugs (we're down to three!)
    • Fixed product-details lib to make developers' lives easier
    • PTO until Wednesday, will be back Thursday.
  • davedash
    • Worked on Admin site stuff
    • AMO has me over capacity
  • ryansnyder
    • I've been hosting family, so I've accomplished a big fat nothing since 9/9
    • Worked with Dave Dash yesterday to get my sandbox back up and running (thanks Dave)
  • michaelk
    • --
  • hamilton
    • Demo'd on LDA Topic Modeling per Platform & Type
  • stephend
    • Working my way through the resolved-fixed 1.8 bugs, now that we have

staging data, w00t w00t!

  • aakashd
    • Worked on Mobile Firefox Feedback Add-on
    • Tested Mobile dashboard, filed a few bugs on ua'ing

What we aim to do next and when we expect to accomplish them:

  • fwenzel
    1. There are a few P1s open. I'll try to assign them and fix some of them myself., 9/15
  • davedash
    1. For this coming week, I'll look at the remaining 1.x bugs or dig into 2.x, 9/16+
  • ryansnyder
    1. Currently working on #590688 in between meetings/work for Socorro week, 9/15
  • michaelk
    1. --
  • stephend
    1. Finish verifying all fixed 1.8 bugs I can, 9/16
    2. Do a round of serious testing and some more fuzzing, 9/16
  • aakashd
    1. Figure out dev estimation on 2.0, 9/16
    2. Work on blog post for 1.8, 9/16
    3. Talk to mrz, 9/21

9-9-2010

  • Fred
  • Dave
  • Ryan
    1. Mobile search came in
  • Michael
  • Hamilton
    1. Demo'd on LDA Topic Modeling per Platform & Type
  • Stephen
    1. Filed/verified bugs
    2. Some data loss
  • Aakash
    1. Was on vacation

What we aim to do next and when we expect to accomplish them:

  • Frederic:
  • Dave
  • Ryan
    1. Hands tied with family and socorro, will take small bugs if available
  • Michael
    1. Fix 1.8 bugs related to Sites, 9/16
  • Hamilton
    1. Working on LDA Topic Modeling
  • Stephen
    1. File/verify bugs
    2. Check it out with Android
  • Aakash
    1. Work on blog post for 1.8, 9/16
    2. Figure out dev estimation on 2.0, 9/14

8-31-2010

What's been completed:

  • Fred
    1. Working on Mobile Dashboard, will commit 8/31
  • Dave
  • Michael
    1. Getting fennec set up with sites
  • Andres
    1. --
  • Ryan
    1. Pushed last 1.7 bug, there was a regression
    2. Will try to pick up some 1.8
  • Stephen
    1. Filed/verified bugs
  • Aakash
    1. Setup 2.0 meeting
    2. Filed some bugs
  • 3 Created 1.7 blog post

What we aim to do next and when we expect to accomplish them:

  • Frederic:
    1. Complete UX overhaul of mobile dashboard, 9/6
  • Ryan
    1. Fix assigned 1.8 bugs, 9/6
  • Dave
  • Michael
    1. Fix 1.8 bugs related to Sites, 9/6
  • Andres
    1. --
  • Stephen
    1. file/verify bugs (swamped with other projects)
  • Aakash
    1. Talk to folks in platform meeting about Input, 8/31
    2. Hold the 2.0 planning meeting
    3. Help Stephen get set up on his mobile device, 8/31

1.7

8-26-2010

What's been completed:

  • Fred
    1. 1.7 Bugs Fixed
    2. L10n notified
  • Dave
    1. Themes up on Sites
  • Michael
    1. Fixed Sites bugs for 1.7
  • Andres
    1. --
  • Ryan
    1. Fixed last bug, need a push
  • Stephen
    1. Finishing up QA Completeness
  • Aakash
    1. Done with 2.0 PRD (on the wiki)
    2. Created 1.8 wiki

What we aim to do next and when we expect to accomplish them:

  • Frederic:
    1. Complete UX overhaul of mobile dashboard, 9/6
  • Ryan
    1. Get bug pushed by Dave
    2. File all necessary bugs needed to complete 1.8 milestone, 8/27
  • Dave
    1. Push Ryan's bug, enjoy the weekend
    2. Work on 1.8 bugs
  • Michael
    1. Fix 1.7 bugs related to Sites, 8/24
  • Andres
    1. --
  • Stephen
    1. file/verify bugs
  • Aakash
    1. Hold a planning meeting for 2.0
    2. on vacation (not available) from 9/1-9/5
    3. Work on communication effort to promote Input after 1.7, 8/31
    4. Create 1.7 release blogpost, 8/26

Additional Notes:

  • We're going to be in Firefox Proper
  • We're planning to be in Nightly Builds

8-24-2010

What's been completed:

  • Fred
    1. Fixed remaining P1/P2 bugs
    2. Need follow-up with michaelk
  • Dave
    1. Done with Themes UX Overhaul, need to have tests automated
  • Andres
    1. --
  • Ryan
    1. Fixed 1 of the bugs
  • Stephen
    1. Verified some bugs and filed some more
  • Aakash
    1. 3/4 done on 2.0 PRD
    2. Created 1.8 wiki

What we aim to do next and when we expect to accomplish them:

  • Frederic:
    1. Finish P1/P2 bugs, 8/24
  • Ryan
    1. Fix last bug and work with wenzel on committing process, 8/24
  • Dave
    1. Themes UX Overhaul, 8/24
  • Michael
    1. Fix 1.7 bugs related to Sites, 8/24
  • Andres
    1. --
  • Stephen
    1. file/verify bugs
  • Aakash
    1. Finish Input 2.0 PRD, 8/24
    2. Talk to mrz about release time
    3. Update 1.8 wiki, 8/24
    4. Work on communication effort to promote Input after 1.7, 8/31
    5. Create 1.7 release blogpost, 8/26

8-19-2010

What's been completed:

  • Fred
    1. Only 1 P1 bug left
    2. Assigned 2 bugs to Ryan
    3. Working on RTL support
  • Dave
  • Michael
    1. staging site now has sites dump coming in on a daily basis
    2. fixed P2 bugs for Sites
  • Andres
  • Ryan
    1. Been busy with Socorro, but will work on bugs today and tomorrow
  • Stephen
    1. Verified some bugs and filed some more
    2. Has some sites questions that should be answered with chowse's
    3. Got another free load test report
  • Aakash
    1. Finished 2.0 definition

What we aim to do next and when we expect to accomplish them:

  • Frederic:
    1. Finish P1/P2 bugs, 8/23
    2. Contact l10n, 8/19
  • Ryan
    1. Fix assigned bugs, 8/23
  • Dave
    1. Themes UX Overhaul, 8/23
  • Michael
    1. add (unit) tests for sites generation as soon as I find the time
    2. Fix 1.7 bugs related to Sites
  • Andres
    1. --
  • Stephen
    1. file/verify bugs
  • Aakash
    1. Finish Input 2.0 definition, 8/24
    2. Work on communication effort to promote Input after 1.7, --
    3. Create 1.7 release blogpost, 8/24

8-17-2010

What's been completed:

  • Fred
    1. Working on UX Overhaul
    2. fixed most P1 bugs
      • won't be ready for tomorrow, but we'll need a few days
  • Dave
    1. Brought up a half-done sites for the ux overhaul
  • Michael
    1. made the changes to the sites process that were needed for Bugs 587616, 587588, 586915
    2. added an IT ticket (Bug 587942) to regularly run migrations for sites on stage
  • Andres
  • Ryan
    1. Sandbox is up and running
    2. WIll pick up bugs
  • Stephen
    1. Verified some bugs
    2. Ran LoadImpact and Jmeter
      • Got some 500 errors on staging
      • Running 40 requests/sec and 300kb/sec with no issue
  • Aakash
    1. Start communication effort for Input Dashboard
    2. Filed some bugs

What we aim to do next and when we expect to accomplish them:

  • Frederic:
    1. UX overhaul
    2. Give heads up when pages are ready to be QA'd
  • Ryan
    1. Work with Fred and fix assigned bugs
  • Dave
    1. Themes UX Overhaul
  • Michael
    1. - make sure the sites production db is migrated before 1.7 goes online (please notify me when code freezes)
    2. add (unit) tests for sites generation as soon as I find the time
    3. Fix 1.7 bugs related to Sites
  • Andres
    1. --
  • Stephen
    1. file/verify bugs
    2. try to look into happy/sad load testing
  • Aakash
    1. Finish Input 2.0 definition, 8/24
    2. Work on communication effort to promote Input, --
    3. Create 1.7 release blogpost, 8/24

1.6.2

8-12-2010

What's been completed:

  • Fred
    1. Working on UX Overhaul
  • Dave
    1. Almost fully sandboxed
  • Andres
  • Stephen
    1. Verified some bugs
    2. Load testing as well
  • Aakash
    1. Finished data flow, its on the wiki now
    2. Created 1.6.2 blogpost

What we aim to do next and when we expect to accomplish them:

  • Frederic:
    1. Will release on branch by end of today
    2. Give an update on possibility of release on Wednesday, 8/16
  • Ryan
    1. Take a look at bug queries, pick up a few bugs, 8/13
    2. Fix assigned 1.7 bugs, 8/16
  • Dave
    1. Fix assigned 1.7 bugs, 8/16
  • Andres
  • Stephen
    1. vacation, vishal verifying bugs
  • Aakash
    1. Input 2.0 definition
    2. Create 1.7 release blogpost

8-10-2010

What's been completed:

  • Fred
  • Dave
    1. Hudson is up, coverage is kinda crap - 67%
    2. Individual pieces of feedback linked
  • Andres
  • Michael
    1. Sites is up
  • Stephen
    1. verify some bugs
    2. load testing as well
  • Aakash
    1. finished data flow
    2. github commits are working

What we aim to do next and when we expect to accomplish them:

  • Frederic:
    1. UX overhaul, 8/16
  • Ryan
    1. UX Overhaul, 8/16
  • Dave
    1. Take a look at 1.7 bugs, 8/12
  • Andres
  • Michael
    1. Maintain Sites, 8/12
  • Stephen
    1. vacation, vishal verifying bugs
  • Aakash
    1. Prepare 1.6.1 blogpost, 8/5
    2. input 2.0 definition

1.6.1

8-05-2010

What's been completed:

  • Fred
    1. Held UX Overhaul meeting with chowse
    2. Atom Feeds
  • Dave
    1. Worked on Hudson and removed smiley face from dashboard
  • Andres
    1. introduced us to Hamilton
  • Michael
    1. Don't have access to prod db, need help from IT
    2. need uptake with dmoore
    3. code is r+'d by fwenzel
  • Stephen
    1. load-testing being worked on
    2. random numbers for search query terms brings down
  • Aakash
    1. talked to Hamilton about things we're working on and our needs
    2. finished another rev of data flow chart
    3. sent out inquiries about 2.0 definition to triagers

What we aim to do next and when we expect to accomplish them:

  • Frederic:
    1. Wait on chowse UX Overhaul, 8/10
  • Dave
    1. Hudson for 1.7
  • Andres
    1. continue with parsing through adjectives; modeling by topic
  • Michael
    1. Sites, 8/4
  • Stephen
    1. load testing, 8/4
    2. verify bugs
  • Aakash
    1. work on data flow, 8/5
    2. work on Input 2.0 definition, 8/16
    3. Prepare 1.6.1 blogpost, 8/5
    4. figure out why my github commits to master are not working, 8/5

8-03-2010

What's been completed:

  • Fred
    1. Took a look at the designs
  • Dave
    1. Started on hudson, build is failing
  • Andres
    1. parse through adjectives; modeling by topic
  • Michael
    1. 1st review completed
    2. manual SQLs -> django to access db needs to be changed
    3. is thinking about pre-processing the data before Sites is
  • Stephen
    1. verified some bugs
  • Aakash
    1. Set up a meeting UX Overhaul
    2. Set up a meeting with Load Testing
    3. created the first draft of a data flow chart
    4. Sent out 1.6 blogpost

What we aim to do next and when we expect to accomplish them:

  • Frederic:
    1. Have meeting with chowse about UX Overhaul
    2. Start on UX Overhaul
  • Dave
    1. Fix Atom Feed, dashboard smiley face and hudson bugs, 8/4
  • Andres
    1. Sites, 8/4
    2. Introduce Hamilton to the group
    3. continue with parsing through adjectives; modeling by topic
  • Michael
    1. Sites, 8/4
  • Stephen
    1. load testing ramp-up meeting, 8/4
    2. help out with UX Overhaul
  • Aakash
    1. work on data flow, 8/5
    2. work on Input 2.0 definition, 8/16
    3. Push 1.6.1 release back (After word from mkurze), 8/3
    4. Prepare 1.6.1 blogpost

1.6

7-29-2010

What's been completed:

  • Fred
    1. Finished all remaining (and found) P1/P2 bugs
  • Dave
    1. Cluster
    2. Finished all remaining (and found) P1/P2 bugs
  • Andres
    1. Sites prototyped on a local server
    2. Met with IT for Sites set up with metrics db cluster
  • Michael
    1. Sites prototyped on a local server
    2. Met with IT for Sites set up with metrics db cluster
  • Stephen
    1. Couldn't get a hold of oremj, will meet with him next week
  • Aakash
    1. Worked on promoting out Input 1.6's and future releases
    2. Worked on new UX with chowse

What we aim to do next and when we expect to accomplish them:

  • Frederic:
    1. UX Overhaul
  • Dave
    1. 1.6.1 bugs
  • Andres
    1. Sites, 8/3
  • Michael
    1. Sites, 8/3
  • Stephen
    1. load testing ramp-up, 8/2
  • Aakash
    1. Set up a meeting UX Overhaul, 7/29
    2. Set up a meeting with Load Testing, 7/29

Additional Notes:

  • Need time on working on better code
  • Get hudson up
  • Let's not fight fires

7-27-2010

What's been completed:

  • Fred
    1. Finished Mobile
    2. URL submission on happy reports
  • Dave
    1. Cluster
  • Andres
    1. Sites prototyped on a local server
    2. Get PDF for Sites info over the past week
  • Michael
    1. Sites prototyped on a local server
  • Stephen
    1. Found Grinder, JMeter and ran them
    2. Need another sphinx node to run it against
  • Aakash
    1. Get the new Cluster/Sites buttons
    2. Worked on new UX with chowse

What we aim to do next and when we expect to accomplish them:

  • Frederic:
  • Dave
  • Andres
    1. Get PDF of Sites report, 7/29
  • Michael
    1. Get term-matching onto trends box, 7/29
  • Stephen
    1. Work on optimization of production sphinx node with oremj, 7/27
    2. QA 1.6 Changes
  • Aakash
    1. Work on UX overhaul with chowse, 7/29
    2. File a bug on removing sites buttons, 7/27

Additional Notes:

  • Are clusters and sites filtering by the product version? [aakash]
    1. There's no mixing, so we'll only get beta 2 information.

7-22-2010

What's been completed:

  • Fred
    1. got the url (m.stage.input.mozilla.com) working
    2. submission pages are up, won't be completely done by 7/23
  • Dave
    1. Finished RSS Feeds, working on Clusters
  • Andres
    1. Finished algorithm, working on UI; targeting 7/26
    2. Got python on metrics db working
  • Michael
    1. look up at Andres
  • Stephen
    1. Jmeter is a bit complicated;
  • Aakash
    1. Finished PRD 1.6 and re-uptake on Sites page

What we aim to do next and when we expect to accomplish them:

  • Frederic:
    1. Finish Mobile, 7/27
  • Dave
    1. Cluster, 7/26
  • Andres
    1. Get prototype of Sites, 7/26
  • Michael
    1. Get prototype of Sites, 7/26
  • Stephen
    1. Investigate into load testing (talk to oremj), 7/27
    2. Figure out differences between staging and production for load testing
  • Aakash
    1. UX Refresh with Chris Howse, 7/27
    2. Work with Lee Tom on new buttons, 7/27

1.5

7-20-2010

What's been completed:

  • Fred
    1. On verbatim and have 7 locales already completed
    2. fixed all P1/P2 bugs that were blockers for 1.5
  • Dave
    1. Almost done with RSS Feeds; Will go in a bit;
  • Andres
    1. Working on "Sites";
    2. Q's: How do we analyze sites? Siphon the domains and then perform cluster analysis from there.
  • Michael
    1. Last thursday/friday, worked on term-matching
    2. Setting up reporter project locally, will need Fred's help
    3. Q's: How do we write back into the tool? File an Input bug.
  • Stephen
    1. Verified all bugs and filed some bugs.
  • Aakash
    1. IT will help out in a big way
    2. PRD for 1.6 completed

What we aim to do next and when we expect to accomplish them:

  • Frederic:
    1. Work on Mobile, 7/23
  • Dave
    1. Cluster, 7/26
  • Andres
    1. Finish up pseudo code of "sites", 78/
  • Michael
    1. File Input Bug for data exchange workflow
    2. Get prototype of Sites, 7/26
  • Stephen
    1. Investigate into load testing, 7/22
  • Aakash
    1. Work through mock-ups and requirements with each feature, 7/26
    2. Figure out better triage techniques, 7/26
    3. UX Refresh with Chris Howse, 7/23

7-15-2010

What's been completed:

  • Fred
    1. Completed Translate, l10n possible/not on verbatim
  • Dave
    1. Changes haven't been made yet, got busy with AMO stuff
  • Stephen
    1. Krupa is interested, but he'll be the only person needed for this release
  • Aakash
    1. Talked to Chris Howse and he'll start on UX work next week with Input
    2. Worked with Metrics on Web Problems Page

What we aim to do next and when we expect to accomplish them:

  • Frederic:
    1. Get on verbatim 7/19;
  • Dave
    1. Complete RSS Feeds, 7/16
    2. Will try to get it in Clusters, 7/23
  • Stephen
    1. Ready to QA and got updated on bug system
  • Aakash
    1. communicate relative importance of Input to IT, 7/16

7-13-2010

Feeds:

  • Django native cache; headers get picked up by Zeus and it doesn't hit the webhead.

L10n:

  • Fred marked them as localizable and need to put them in verbatim. Will need strings separated for mobile pages.

Clusters:

  • Aakash: Get a review from Chris Howse
  • Warning Thing
  • Doing a happy/sad report by version. It's a week's worth of data.
  • Would rather prefer a week's worth of data because it's more useful and data won't get too large if we work on 3 week beta cycles.

Scheduling:

  • 7/28: Searches with Feeds, L10n of Webpages, Translation Link and Clusters Beta
  • String Freeze: 7/19
  • Code Complete 7/21
  • QA until 7/28
  • Release 7/28

1.0

6-28-2010

Things we did well?

  • Fred: requirements were very clear, mock-ups helped; execution was very much on-time;
  • Aakash: pretty much what fred said; fred's coding was beast-like in its intensity; we got help from everyone we asked

Things we didn't do well?

  • Fred: background changes a day before we launched; timeline was very short;
  • Aakash: https stuff; blogposts were confusing since beta was not out yet to use the pages; VPN set-up 1 week after requested by fred

Things that are important to work on for next rev?

  • get an idea about what marketing might want from Input early on
  • When going live, Input needs an apache reload

Overall

  • things were very good considering the timeline

6-22-2010

What's been completed:

  • Frederic
    1. All remaining bugs fixed
  • Aakash
    1. Tested Feedback Extension and identified nits to change
    2. Verified warning notification on submission pages

What we aim to do next and when we expect to accomplish them:

  • Frederic:
    1. GO LIVE!
    2. Create blog post
  • Aakash
    1. Create blog post/promotions as necessary and link Fred's stuff in it

6-21-2010

What's been completed:

  • Frederic
    1. Pretty much all bugs fixed
    2. Filed bug 573468 to go live
  • Aakash
    1. Done with Privacy Policy stuff
    2. verified fixes

What we aim to do next and when we expect to accomplish them:

  • Frederic:
    1. fix remaining bugs
    2. Try out Lee Tom's next background image if he gets it in time
  • Aakash
    1. Test out Jono's fix
    2. Verify warning notification on submission pages

6-20-2010

What's been completed:

  • Frederic
    1. Fixed a bunch of bugs over the weekend
  • Aakash
    1. talking to legal about implementation of privacy policy text on submission pages
    2. verified fixes
    3. promoted out input to a wider audience and got some testers (go kbrosnan!)

What we aim to do next and when we expect to accomplish them:

  • Frederic:
    1. fix remaining P1-P3's
    2. file bug to go live Tuesday night PST
  • Aakash
    1. hash out implementation with legal and give Fred a solution
    2. talk to Jono to comment out URL inclusion on extension side

6-16-2010

What's been completed:

  • Frederic
    1. finished all P1/P2's except 1
    2. received horlander's icons
  • Aakash
    1. finished 2nd set of mock-ups for mobile firefox
    2. verified p1 and p2 fixes

What we aim to do next and when we expect to accomplish them:

  • Frederic:
    1. fix vendor directory issue for IT to get up on staging
    2. load testing
    3. fix remaining P1's and P3's
  • Aakash
    1. test Input on staging
    2. promote out input to a wider audience (i.e. key stakeholders: qa, marketing, ux, fx-team)

6-15-2010

What's been completed:

  • Frederic
    1. finished all P1's except 1
    2. replied to horlander
  • Aakash
    1. followed-up with stephen horlander
    2. worked on implementation with mobile firefox
    3. filed a few more bugs

What we aim to do next and when we expect to accomplish them:

  • Frederic:
    1. p2 bugs and remaining p1 bug
  • Aakash
    1. test changes after p1 and p2 fixes are done
    2. look into load testing


6-14-2010

What's been completed:

  • Frederic
    1. got hosed due to late issue with the weave team
  • Aakash
    1. sent graphics via e-mail
    2. extension created by jono and we're testing that side
    3. all bugs triaged

What we aim to do next and when we expect to accomplish them:

  • Frederic:
    1. p1 bugs
    2. reply back to horlander about smiley icon sizes on submission pages & sentiment box
  • Aakash
    1. test changes after p1 fixes are done
    2. look into load testing

6-10-2010

What's been completed:

  • Frederic
    1. completed beta page
    2. wrote unit tests
    3. did not file bug since app is changing quite a bit
  • Aakash
    1. gave list of user agents
    2. got VPN access and tested/filed bugs
    3. created bugzilla component
    4. gave mock-up for download page

What we aim to do next and when we expect to accomplish them:

  • Frederic
    1. fixing P1/P2's
    2. file a bug to staging when all P1/P2s are fixed
  • Aakash
    1. follow up horlander
    2. lee tom for icons and graphics
    3. work on layout of search results
    4. file/triage bugs as needed

6-08-2010

What's been completed:

  • Frederic:
    1. Search is working, pop-down for URLs, menu box options
  • Aakash:
    1. Got Lee Tom to work on Dashboard and Thank You page graphics and Horlander to work on platform-specific icons
    2. Jono is going to incorporate button implementation with Feedback
    3. Metrics and TP will give info on riak implementation once its completed

What we aim to do next and when we expect to accomplish them:

  • Frederic:
    1. create intermediary page to download beta (6/9)
    2. write unit test to make sure all cases are covered to send users to the download page
    3. file a bug on putting dashboard and submission pages to staging for input-stage.mozilla.com, input.stage.mozilla.com/happy input-stage.mozilla.com/sad (6/9)
  • Aakash
    1. make a list of user agents 6/8
    2. get VPN access 6/8
    3. give text for download page 6/8
    4. get info on uservoice/survey api implementation with mktg on fx betas 6/10

6-01-2010

What's been completed:

What we aim to do next and when we expect to accomplish them:

  • Fred (by Thursday 6/3):
    1. get search working
    2. pop-down for URLs when clicked ( go to page only when hyperlink clicked)
    3. implement in menu box options
  • Aakash (by Thursday 6/3):
    1. get some designer love for happy/sad faces, dashboard header and follow-up buttons on thank you page
    2. start looking into client side
    3. getting info from metrics on implementation help for riak on rev 2

Additional Notes?

  • Aakash: get set up with VPN for future demos

5-27-2010

Status Update:

  • Fwenzel
    • completed = forms (post positive and negative feedback), completed-ish user agent parser,
    • questions = app that searches with riak?, interval on dashboard is? (1 day, 1 week, 1 month)
  • aakashd
    • getting info from metrics on implementation help for riak on rev 2

Next Steps:

  • fwenzel = making django app/dashboard (late next week)
  • aakashd = looking at list of swear words (mid-5/27)