Labs/Ubiquity/Meetings/2009-03-18 Weekly Meeting: Difference between revisions
Jump to navigation
Jump to search
(New page: == Details == === Time === [http://www.timeanddate.com/worldclock/fixedtime.html?day=18&month=3&year=2009&hour=17&min=0&sec=0&p1=224 5:00pm Pacific time] === Location === * IRC channel...) |
Indolering (talk | contribs) m (→Notes) |
||
| (5 intermediate revisions by 4 users not shown) | |||
| Line 15: | Line 15: | ||
== Agenda == | == Agenda == | ||
* | * Talk about [[Labs/Ubiquity/Secure_Coding_Practices]] | ||
* Get 0.1.7 out | |||
* Zack's [http://help.indolering.com/wikipedia.html documentation prototype] | |||
* Fern's work on Herd | |||
== Attendees == | == Attendees == | ||
# | # Aza | ||
# Atul | |||
# Blair | |||
# Fern | |||
# Cers | |||
# Zach | |||
== Notes == | == Notes == | ||
* | * Placed the way Ubiquity worked so that the pblock of commands (i.e., the preview area) now live in content space via an iframe. This solves a major security issue where results from XHRs could potentially include system privileged code. | ||
* We need volunteers to help with CSS tweaks caused by the switch to using the iframe. | |||
* If you are programming a chrome://... URL, please make sure that all dynamic text place in that page that comes from 3rd-party places must be sanatized/escaped. Otherwise we create a security hole. Use Utils.escapeHtml, http://www.hurl.ws/1d72s. | |||
* Memory leaks fixed! | |||
* Lots of code changes. Would like to get out 0.1.7 tomorrow morning, but needs serious testing. | |||
* Zach/indolering produced a mockup for new documentation. It is essentially copied and restructured from the Enso work and is available here: http://help.indolering.com/wikipedia.html He will be producing more work and testing it as well. | |||
* Fern is making rapid progress on the Herd now that he has time. He has basic command submission, tagging, friends, embedding bespin and more in the pipeline for next week. | |||
Latest revision as of 01:36, 19 March 2009
Details
Time
Location
- IRC channel: #ubiquity
- Dial in:
- +1 800 707 2533 (pin 369) Conf# 201 (US Toll Free/Skype)
- +1 650 903 0800 x92 Conf# 201 (US/International)
- +1 416 848 3114 x92 Conf# 201 (Canada)
Agenda
- Talk about Labs/Ubiquity/Secure_Coding_Practices
- Get 0.1.7 out
- Zack's documentation prototype
- Fern's work on Herd
Attendees
- Aza
- Atul
- Blair
- Fern
- Cers
- Zach
Notes
- Placed the way Ubiquity worked so that the pblock of commands (i.e., the preview area) now live in content space via an iframe. This solves a major security issue where results from XHRs could potentially include system privileged code.
- We need volunteers to help with CSS tweaks caused by the switch to using the iframe.
- If you are programming a chrome://... URL, please make sure that all dynamic text place in that page that comes from 3rd-party places must be sanatized/escaped. Otherwise we create a security hole. Use Utils.escapeHtml, http://www.hurl.ws/1d72s.
- Memory leaks fixed!
- Lots of code changes. Would like to get out 0.1.7 tomorrow morning, but needs serious testing.
- Zach/indolering produced a mockup for new documentation. It is essentially copied and restructured from the Enso work and is available here: http://help.indolering.com/wikipedia.html He will be producing more work and testing it as well.
- Fern is making rapid progress on the Herd now that he has time. He has basic command submission, tagging, friends, embedding bespin and more in the pipeline for next week.