<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hi.<br><br></div><div>In the last week we started to use <a href="http://lively-kernel.org/trac">Lively's trac</a> again. There, we keep track of <a href="http://lively-kernel.org/trac/report/11">existing issues</a>, <a href="http://lively-kernel.org/trac/report/12">feature requests</a> and <a href="http://lively-kernel.org/trac/report/14">necessary refactorings</a>. </div><div><br></div><div>Besides trac we also use Lively itself for <a href="http://lively-kernel.org/repository/webwerkstatt/issues/">issue reports</a>. Whenever there's a bug that's description isn't absolutely trivial, it's a great help to have a small example in Lively for the issue. Such issue pages are usual Lively worlds and, therefore, can contain any morphs and texts that help to understand and reproduce issues. Examples: <a href="http://lively-kernel.org/repository/webwerkstatt/issues/111017_StaticBindingOfSuperInClosures.xhtml">http://lively-kernel.org/repository/webwerkstatt/issues/111017_StaticBindingOfSuperInClosures.xhtml</a>, <a href="http://lively-kernel.org/repository/webwerkstatt/issues/111026_CustomFormattedBinsInPartsBin.xhtml">http://lively-kernel.org/repository/webwerkstatt/issues/111026_CustomFormattedBinsInPartsBin.xhtml</a></div><br><div>We create such issue worlds from a template: <a href="http://lively-kernel.org/repository/webwerkstatt/issues/CreateIssuePage.xhtml">http://lively-kernel.org/repository/webwerkstatt/issues/CreateIssuePage.xhtml</a>.<br><br>Please feel free to contribute!<br><br>Best,<br>Lauritz</div></body></html>