<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="gmail_quote"><div>Just to add another idea about the organization of the vendor listing
page - why not create a map - then it's not random and it's not alpha -
you zoom into your country and see who's there - just an idea since I
just finished teaching my mashups workshop and we talked about map
mashups :)<br></div></div></blockquote><div><br>Fantastic idea! Nicole++<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="gmail_quote">
<div> </div><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>
> The very thing we should avoid is grandfathering, meaning exempting,<br>
> anyone from the rules. Any rules worth having are rules which should be<br>
> applied equally to all.<br>
<br>
</div>As long as Liblime is the only entity with complete control over<br>
<a href="http://koha.org" target="_blank">koha.org</a>, that's not going to happen.<br></blockquote></div><div><br>The idea is that this is going to change - we're going to form a committee and work with the group we choose in the survey to control Koha assets.<br>
</div></div></blockquote><div><br>Indeed. I suppose that the proper solution to changing the listing rules is to have all listed vendors agree to all the changes to make sure they are aware and still in compliance.<br> </div>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="gmail_quote"><div>Nicole<br></div></div></blockquote><div><br> </div></div><br>