Reading/Multimedia/Scrum notes/gi11es

Last update on: 2014-03-12

2014-03-12
 The scrum note cutoff happening for me in the middle of a work day with a lot of evening calls explains this "yesterday"/"today" imbalance.


 * Yesterday
 * In-depth review of the share & embed changeset
 * Spent a bunch of time in Mingle cleaning up the iterations and meeting cards


 * Today
 * 1-on-1 with Michael Dale about technical aspects of TMH
 * Interviewing candidate for PM position
 * Team planning meeting
 * Work on #288 (fullscreen cursor: none issue)
 * Work on #198 (image load data dashboard) if Mark hasn't finished it



2014-03-11

 * Yesterday
 * 1-on-1 with Rob
 * Design review meeting
 * Helped out with miscellaneous fixes on the Share & Embed WIP diff
 * Reviewed various UploadWizard diffs by Rillke
 * Set up my local environment for E2E tests and fixed the basic navigation one (#296)


 * Today
 * Figure out why ZNC on multimedia-alpha is so sluggish/unreliable since I came back. Maybe move it to another of our VMs?
 * Work on #288 (fullscreen cursor: none issue)
 * Work on #198 (image load data dashboard)



2014-03-04

 * Yesterday
 * Did #278 (get rid of global viewer instance) which solved issues experienced by Gergo in #178 (consolidating multilightbox and lightboxinterface)
 * Discussed jenkins gotchas with Antoine, which we'll document when I come back. The latest I ran into is that jenkins runs qunit tests on the changeset automerged to the latest master, which is a different state than you have locally when you "git review -d" the changeset. Thus, you can end up with the tests working locally but failing on jenkins, because the automerge causes changes that are incompatible on an application level. The workaround is rebasing to master when you encounter the situation, which brings you to the same state as jenkins and should make the qunit errors start happening locally.
 * Contributed to this TeamPractices discussion: https://www.mediawiki.org/wiki/Talk:Project_management_tools/Review/Options which might determine what tools the foundation uses in the future.


 * Today
 * I'm off until further notice, I'll let you know ASAP when I know I'll be able to do a work day



2014-03-03

 * Yesterday
 * Asked analytics for limn0 access, which is prerequisite to work on #198 and #54 (stats dashboards)
 * Wrote a fix for #274 (write a test to check that events are left untrapped)
 * Did #232 (check CORS double-load behavior in all browsers) and wrote a fix for the issues in IE6 and IE11


 * Today
 * Contribute to #54 and #198 if analytics gives me access
 * Fish for more "must have" cards from the current release like yesterday if the above doesn't happen



Archived
2014-02