Hi guys Let me reiterate it: - We need you! - 75 % of the issues on the bug tracker are simple. - BTW how did we learn stuff, by reading code and learning. I'm not smart I'm just a tedious learner I can any opportunity to learn something new. - if you spend 30 min a week, YOU CAN get an IMPACT! - if pharo is important for you then 30 min in a good investment - every single LITTLE bugs fixed and improvement is IMPORTANT - we do not want the final latest coolest superhyper cool and hyper clever fixes! - we accept little improvement - in UNSTABLE we have the right to push not 100% finish code Now think what YOU can do for pharo. Because Yes YOU can - screencast - checking tests (yesterday I moved CompiledMethodAsStringTest>>testPrint to CompiledMethodTest>>testPrint) Yeah hyper difficult - Class comments: look at the URI class comment - blogging - tweeting We should slowly change our process so that Pharo continue to evolve even if we disappear on the moon. Now I asked marcus to focus on the newcompiler and stop fixing little bugs because we want to make progress on other fronts. We want newcompiler - we want the newcompiler - we want the newcompiler and fixing it and fixing its interface. We want Helvetia hooks -We want Helvetia hooks. We want a new package object (but I do not find time to code argh). Stef