<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><p style="color: rgb(51, 51, 51); font-family: 'Lucida Grande', Verdana, Arial, sans-serif; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 16px; orphans: 2; text-align: justify; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">Squeak Oversight Board minutes – 01/17/12</p><p style="color: rgb(51, 51, 51); font-family: 'Lucida Grande', Verdana, Arial, sans-serif; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 16px; orphans: 2; text-align: justify; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">Attending: Chris Muller, Colin Putney, Levente Uzonyi, Chris Cunnington</p><ul style="margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; list-style-type: none; list-style-position: initial; list-style-image: initial; padding-left: 10px; text-indent: -10px; color: rgb(51, 51, 51); font-family: 'Lucida Grande', Verdana, Arial, sans-serif; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 16px; orphans: 2; text-align: justify; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><li style="margin-top: 7px; margin-right: 0px; margin-bottom: 8px; margin-left: 10px; ">-- it was agreed that was nice to see Eliot exploring the SqueakCore image, as we hope this is a direction the community will take up</li><li style="margin-top: 7px; margin-right: 0px; margin-bottom: 8px; margin-left: 10px; ">-- a long conversation was had about how to distribute the next version of OmniBrowser, as existing tools don’t seem quite right</li><li style="margin-top: 7px; margin-right: 0px; margin-bottom: 8px; margin-left: 10px; ">-- a long Installer script could be written, but that meant every version would have its own, and managing them would be a nuisance</li><li style="margin-top: 7px; margin-right: 0px; margin-bottom: 8px; margin-left: 10px; ">-- Metacello was seen as good, but that it would be better if the metadata/dependency info could be accessible; so you could ask questions of the metadata</li><li style="margin-top: 7px; margin-right: 0px; margin-bottom: 8px; margin-left: 10px; ">-- the difference between the needs of users and developers was raised</li><li style="margin-top: 7px; margin-right: 0px; margin-bottom: 8px; margin-left: 10px; ">-- the next OmniBrowser will have around 30 packages to co-ordinate and likely more</li><li style="margin-top: 7px; margin-right: 0px; margin-bottom: 8px; margin-left: 10px; ">-- Colin’s working on a DSL and tool to manage the task for his own personal use: a tool that reads a spec and creates an Installer script</li><li style="margin-top: 7px; margin-right: 0px; margin-bottom: 8px; margin-left: 10px; ">-- Levente suggested a tool to read a Metacello configuration to make a spec to feed into Colin’s tool and then produce an Installer script</li><li style="margin-top: 7px; margin-right: 0px; margin-bottom: 8px; margin-left: 10px; ">-- it was mentioned that a build server factors into these problems and could assist the process</li></ul><div><br></div></body></html>