PDF.js/Meeting2011-10-06

meeting notes for 2011-10-06 artur:

   since last week
       set up milestones on github for quarterly goals
       https://github.com/andreasgal/pdf.js/issues/milestones
       working on bugs with pdfjs bot, has already detected a bug
   for next week
       looking into text selection; html5 backend?

bdahl:

   since last week
       type 3 fonts first big commit
       fixing related issues
       diagnose and triage big list of PDF tests from contributor
   for next week
       trying to grab big list of prominent PDF's
       assessing important missing features
       

jviereck:

   since last week
       hacking on workers code
       following cjones's refactoring suggestions
       has been tagging issues, noted that many issues are not categorized
       thinking about problems with Web Print API
   for next week
       need to merge with other changes
       optimizing rendering speed
       

yury: <absent>

   seems to do a little bit of everything
   helped out with unicode mapping

vingtetun: <absent>

   discussion about add-ons using jetpack
           

topics:

   splitting up PDF.js source files
       git should be able to track splitting files because it tracks content
       we should set a flag day and move things quickly to avoid hurting private repo's
       we should do it at a moment when there are few open pull requests
       we should wait until jviereck's worker code is checked in
       artur will make a discussion-only pull request for his suggestions
       Q: how was ace/cloud9 broken up?
       A: in our terms, move subjects into their own files
       
   supporting jviereck's big merge
       sooner is better
       speedy review of his pull request
       should we postpone big commits?
       Q: if pull request updates driver.js, does the bot use the new driver.js?
       A: before running tests, pull upstream into your code (new reference set, etc)
   moving the github project to user mozilla
       target for week of oct 18
       
   work week (oct 18-22)
       artur and vingetun in MV with brendan
       use the work week to split up the code; move to mozilla user
       make at least one new backend prototype
       
   existing issues poorly categorized
       we should tag issues when we ourselves file them
       use bdahl's categories -- broken PDF; spec work; feature request; UI
       we want to reduce the number of tags
       artur will file an issue to propose a subset of the labels that we use
       
   web print API
       prefer not to bring all 1,000 pages of a document into memory  just to print 1 page
       
   whether to use jetpack for the add-on
       discussion postponed, not a blocker for now