2006/5/17, Kevin Smith <<a href="mailto:email@example.com">firstname.lastname@example.org</a>>:<div><span class="gmail_quote"></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I think a couple of examples of projects of a larger scale would at<br>the least allow me to better understand what it is I'm disagreeing<br>with ;)<br></blockquote></div><br>What I understand from Lucas' mail is that he would like projects like distributed monitoring of the Jabber Network (which he did propose) :
<br><a href="http://wiki.jabber.org/index.php/Summer_of_Code_2006#Federation">http://wiki.jabber.org/index.php/Summer_of_Code_2006#Federation</a><br>An other example of a project non-related to a specific client or server would be a tool to test XMPP compliancy of clients or servers.
<br>Maybe also writting a component which could be plugged on any Jabber server would enter this category.<br>So on...<br><br><br>I agree that it would be good to have some of these projects but I do not see it as a problem to have projects related to a specific client or server as long as they are innovating or original and not just day to day work on a software.
<br><br>For example, making a software (client or server) support a JEP that nobody else support would benefit a lot to the all Jabber community. However, making a software support a JEP that many other softwares already support would not benefit as much to the Jabber community and would be too software specific.
<br><br>Does everybody else agree ?<br><br>-- <br>Etienne<br>