AMO:Meeting Notes: Difference between revisions

Jump to navigation Jump to search
(September 14 meeting)
Line 31: Line 31:
** Schedule is suffering
** Schedule is suffering
** need mockups asap
** need mockups asap
*** '''everything we're getting from RC we've already got, in the zip from last week''' (shaver)
** not much room for slipping, Firefox is going to be released October sometime, aiming for concurrent release.
** not much room for slipping, Firefox is going to be released October sometime, aiming for concurrent release.
*** Any slip we do have will probably result in less QA/testing and a lower-quality product
*** Any slip we do have will probably result in less QA/testing and a lower-quality product
*** '''we should prefer to slip number of features rather than quality; it's easier to recover from the former than the latter'''; example: slip localization of dev tools rather than test coverage for dev tools.  We need to discuss specific things here, though, to really be helpful.''' (shaver)


'''clouserw'''
'''clouserw'''
* Simple search done
* Simple search done
** works, needs improvement
** works, needs improvement
*** '''where is it?''' (shaver)
** currently title, then description
** currently title, then description
*** Should be title, summary, description as discussed previously
*** Should be title, summary, description as discussed previously
** no tests yet.. need to figure out how to do that, going to wait for it to be further developed before writing more.
** no tests yet.. need to figure out how to do that, going to wait for it to be further developed before writing more.
*** '''I wish I had my previous test stub :(  happy to help sketch out tests, or write them if that's helpful and viable''' (shaver, shaking his fist at the MBP gods)
* working on l10n string stuff
* working on l10n string stuff
** have some demo code which was discussed in IRC.  
** have some demo code which was discussed in IRC.  
*** ugly, but doesn't seem to be another way.  
*** ugly, but doesn't seem to be another way.  
** open to suggestions, but need to get them in quick otherwise this is going to become a coding standard.
** open to suggestions, but need to get them in quick otherwise this is going to become a coding standard.
*** '''clouserw's example is [http://micropipes.com/temp/add_step1.php here], chiefly the lead-in comment''' (shaver)




Line 54: Line 59:
* What's with the double slash?
* What's with the double slash?
** Nobody knows, ask fligtar
** Nobody knows, ask fligtar
** '''shouldn't be a problem, likely an artifact of the test goop making sure that you don't blow up if you don't have a trailing/leading slash on one of the components''' (shaver)
* shoot css queries at morgamic or clouserw, they've done plenty before
* shoot css queries at morgamic or clouserw, they've done plenty before


Line 59: Line 65:
* Got SVN and CVS access - hoorah!
* Got SVN and CVS access - hoorah!
* Learning about command line interfaces.
* Learning about command line interfaces.


= September 7 Meeting =
= September 7 Meeting =
Confirmed users
455

edits

Navigation menu