On Fri, May 8, 2009 at 4:04 PM, Eric Bégin <span dir="ltr"><<a href="mailto:Eric.Begin@inlibro.com">Eric.Begin@inlibro.com</a>></span> wrote:<br><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 bgcolor="#ffffff" text="#000000">
Hi, <br>
<br>
First, I want to raise my hat to LibLime team for the new website.<br>
<br>
<br>
I also want to thanks Thomas for the time he spent to analyse the new
site and for bringing those worth to discuss points.<br>
<br>
Here is, briefly, my comments.<br>
<br>
1. LOCALISATION<br>
If we do not make the French (France) link point to <a href="http://koha-fr.org" target="_blank">koha-fr.org</a>, I
strongly recommand to remove it until the french version of the site is
almost completed.</div></blockquote><div>Unfortunately, that link is there strictly to allow changing the language of the website from English to French, and any other translation that is added will show up as a link just like the French/English ones. So disabling the language would remove the possibility of translation, that's just how Plone works AFAIK.<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 bgcolor="#ffffff" text="#000000"><br>
<br>
3. DEMONSTRATION<br>
I'm aware that the demo site are maintained by LL team, however, since
this is a demo for the community, wouldn't be faire to remove any
reference to LL in the demo site?<br>
This includes the username/password, logo and name. As Thomas
mentionned, it would also be nice if the URLs were using the same
approach as the koha-fr site, I means <a href="mailto:something@koha.org" target="_blank">something@koha.org</a><br>
By the way, I just tried the demo site and here what I noted:<br>
- can not log on the intranet using liblime/liblime at the moment (both
public and academic)</div></blockquote><div>The liblime user was deleted by someone who logged into the academic demo as the liblime user ... These demos refresh on a daily basis so the problem would have resolved itself by morning, but in any event, its fixed now. The public demo appears to be working fine.<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 bgcolor="#ffffff" text="#000000"><br>
- there is a 404 when we click Catalogue in the public demo</div></blockquote><div>Yep, that's a broken link, but its otherwise fine.<br><br>BTW: nothing has changed with this Plone site with respect to how we demonstrate Koha ... LibLime has been faithfully providing stable, public, free, demos for the community for years. So that's nothing new and I'm not sure how it relates to the website update.<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 bgcolor="#ffffff" text="#000000"><div class="im"><br>
<br>
3.2 PAY FOR SUPPORT<br>
</div><blockquote type="cite"><span>Support
companies are listed by the date they joined the Koha community. </span></blockquote>
I really don't want to remove any credits to LibLime or BibLibre. You
guys are doing awesome job. However, I'm a bit confused about the
contribution part.<br>
<br>
As far as I can tell, a contribution should be something that the
company as paid or provide the ressource to do something. Features
developped for and paid by a client shouldn't be considered as a
contribution.</div></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div bgcolor="#ffffff" text="#000000"><br>
<br>
Has contributed over 55% of the entire Koha
codebase, including the integration of Koha and Zebra<br>
Has contributed over 35% of the entire Koha codebase<br>
Was the developpment payed by a client? If so, the client should be
credited for the integrations/development, not LibLime... does it make
sense?</div></blockquote><div>Well, I can't speak for BibLibre, but LibLime does not get paid by clients to contribute back to the Koha community. We don't get paid to maintain those contributions. We don't get paid by clients to write and maintain the free documentation we've maintained for the community, and we don't get paid by clients to hold time-consuming official Koha positions such as Release Manager, Translation Manager and Documentation Manager. LibLime pays those expenses ourselves at considerable cost to us. <br>
<br>Many of the Koha vendors listed on the support page do not contribute 100% of the code they write for customers to the community, and we've learned over the past fwew years that in some cases this is due to them not being paid for that effort, and in other cases, its a deliberate attempt to proprietize components of the services they offer.<br>
<br>LibLime has, from our inception in 2005, contributed back 100% of the code we've created because we believe in the community process and we strive to set an example for other support organizations.<br><br>Listing notable contributions by vendors on the support page where applicable is additional incentive for vendors to get more actively involved in contribution. Its important that libraries selecting support options know the roles that their support provider is playing in the community.<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 bgcolor="#ffffff" text="#000000"><br>
<br>
In March 2007, LibLime acquired the Koha division of Katipo
Communications, Ltd., the original developers of Koha 1.0.<br>
Not really a contribution... This is marketing stuff and shoud stay on
LibLime website.</div></blockquote><div>That is not meant to be a marketing statement, but rather an explanation of LibLime's listing having been grandfathered from Katipo's Koha Division, which could be confusing to first-time visitors.<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><br>
<blockquote type="cite">the koha-manage group decided to...</blockquote>
What are the factor making for someone to be in the Koha-manage group?
There is no mention of such a group on <a href="http://koha.org" target="_blank">koha.org</a>.<br>
<br>
My main point here is that the Koha.org website should be as
vendor-independant as possible. I really think that the Alphabetical
order is the best way to reach that goal. </div></blockquote><div>I respectfully disagree. Listing by date joined is the most vendor-independent and community-focused. Another fair option would be to list in order of contributions, most to least. This community is, after all, a meritocracy :).<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 bgcolor="#ffffff" text="#000000"><br>
<br>
Here some broken links that I found on the new (now current) web site.<br>
<br>
<a href="http://www.koha.org" target="_blank">www.koha.org</a> (with www) bring a Zope Quick Start Page...<br>
In the footer: LibLime Link<br>
Support » Free Support » Koha Mailing List<br>
Documentation » Reference Manual » Koha 3.0 or Koha 3.2 » All content
on one page... It takes a long time to load and after a while, it
request to log on our Google Account...</div></blockquote><div>Very helpful, thanks we'll try to locate and fix these asap.<br><br>Cheers,<br>Josh </div></div><br>-- <br>Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE<br>
CEO migration, training, maintenance, support<br>LibLime Featuring Koha Open-Source ILS<br><a href="mailto:jmf@liblime.com">jmf@liblime.com</a> |Full Demos at <a href="http://liblime.com/koha">http://liblime.com/koha</a> |1(888)KohaILS<br>