I don&#39;t think we need to overcomplicate that piece.  The validation website links to reports on the lava dashboard, and should provide some grouping of the data by teams, so that teams can have their own &quot;weather report&quot; sort of page, or link to the things they care about.  If needs be, we can create a separate project for this and store the pages in bzr.<br>

<br>-Paul Larson<br><br><div class="gmail_quote">On Wed, May 25, 2011 at 11:35 AM, Zygmunt Krynicki <span dir="ltr">&lt;<a href="mailto:zygmunt.krynicki@linaro.org">zygmunt.krynicki@linaro.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">

Hi guys.<br>
<br>
After looking hard at those blueprints and our discussions during UDS I&#39;m getting this impression that the line between the two is blurred.<br>
<br>
It would significantly to frame the problem help if we could determine the architecture of &quot;validation website&quot; and how it differs from &quot;lava&quot; (especially after we did lava-server), where it ends up being (which project?) and so on.<br>


<br>
Best regards<br><font color="#888888">
ZK<br>
</font></blockquote></div><br>