<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi all,<br>
<br>
I still think that the community web site should be vendor-independent.<br>
<blockquote type="cite">
<pre wrap="">4. RECOMMEDATION FOR THIS MOMENT.
Until there is a consensus in favour of a particular presentation or set
of presentations, the pay for support page should reverted to the previous
presentation which was certainly not ideal but allowed people to do their
work without being bothered excessively about how it was presented.</pre>
</blockquote>
Agree. On the other hand, a description of the company, contact and
web site info should be enough on this page. Maybe we could add a logo.<br>
Each company has a lot of room on their respective websites to write
their contributions.<br>
<br>
User interested by support usually goes on vendor's web site of their
geographical location. I don't beleive they are doing a choice only at
looking at Koha's web site.<br>
<br>
I like the model used by Moodle: <a class="moz-txt-link-freetext" href="http://moodle.com/support/">http://moodle.com/support/</a><br>
<br>
Eric<br>
<br>
<br>
Each vendor should be able to edit its company informations without
having to send an email to the web site admin.<br>
<br>
Thomas Dukleth wrote:
<blockquote
cite="mid:33433.173.52.140.37.1242153904.squirrel@mail.highspeedrails.com"
type="cite">
<pre wrap="">Reply inline:
On Tue, May 12, 2009 4:50 pm, Joshua Ferraro wrote:
[...]
1. SUPPORT COMPANIES FOR WHICH SIGNIFICANT CONTRIBUTIONS ARE
UNDER-REPRESENTED.
</pre>
<blockquote type="cite">
<pre wrap="">Can you please list some specific examples of support vendors on that
page who's contributions are under-represented? That would really help
because we could add those contributions directly to the page.
</pre>
</blockquote>
<pre wrap=""><!---->
I only know of significant contributions in the parts of the code which I
have studied and taken a particular interest. Contributions of LibLime,
BibLibre, and Tamil are certainly under-represented. I suspect that at
least half of the companies listed under pay for support are
under-represented for significant contributions.
2. NO SMALL FIXES ADEQUATE.
The absence of information in the current presentation is not helpful in
distinguishing expertise. However, the abundance of information which
would be necessary to fairly distinguish one company from another for
contributions would transform a support companies directory into a
features list. Such information should be moved to an attribution
document.
A reasonably constrained set of annotations specified according to an
agreed formal set of rules and supplied or calculated from value lists
wherever possible should be substituted for the current presentation of
contributions from support companies.
An attribution document should be developed to give everyone due
attribution for significant contributions.
3. DEVELOPMENT GOALS.
Ideally, we should all hope for a Koha development community which would
become so rich and vibrant that even the most major contributor would have
not even contributed 1% of the code base. The current presentation of
information in the pay for support page is not the way to encourage the
development of such a rich and vibrant Koha community.
4. RECOMMEDATION FOR THIS MOMENT.
Until there is a consensus in favour of a particular presentation or set
of presentations, the pay for support page should reverted to the previous
presentation which was certainly not ideal but allowed people to do their
work without being bothered excessively about how it was presented.
5. MORE IMPORTANT PROBLEMS.
Major navigation and browser compatibility issues should be receiving more
attention at this time. They have not been receiving the attention they
deserve because of the divisive instance on going live with a new website
which has not been properly tested and for which some important content
has no consensus.
The top navigation links are not even readable in Internet Explorer which
is still the majority web browser in the world and one which many
libraries force upon patron and librarian terminals alike. Who would be
choosing Koha when they cannot even navigate the Koha website? What
impression of Koha does the failure of the website to function properly
give to most potential visitors?
[...]
Thomas Dukleth
Agogme
109 E 9th Street, 3D
New York, NY 10003
USA
<a class="moz-txt-link-freetext" href="http://www.agogme.com">http://www.agogme.com</a>
212-674-3783
_______________________________________________
Koha mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Koha@lists.katipo.co.nz">Koha@lists.katipo.co.nz</a>
<a class="moz-txt-link-freetext" href="http://lists.katipo.co.nz/mailman/listinfo/koha">http://lists.katipo.co.nz/mailman/listinfo/koha</a>
</pre>
</blockquote>
</body>
</html>