gmane.education.libraries.koha.devel

Official Koha Newsletter: Volume 3, Issue 5: May 2012

Daniel Grobani — 2012-05-24T22:36:26

Official Koha Newsletter: Volume 3, Issue 5: May 2012

[Below is the text of the newsletter. For active links and a more
readable format, please visit
http://koha-community.org/koha-newsletter-volume-3-issue-5-may-2012]

Official Koha Newsletter (ISSN 2153-8328)
Volume 3, Issue 5: May 2012

Edited by Daniel Grobani, Koha Community Newsletter Editor.

Please submit news items to danielg.koha-Re5JQEeQqe9fmgfxC/sS/w< at >public.gmane.org

Table of Contents

    Koha Development
        Koha 3.8.1 Released
        Koha 3.6.5 Release Imminent
        Koha Statistics
        Database Schema Documentation Updated
    Koha Community
        New Koha Libraries
        Community Gossip
    Past Koha Events
        May General IRC Meeting
        New Zealand Koha User Group Day 2012
    Upcoming Koha Events
        June General IRC Meeting
        KohaCon12
        KohaCon13

Koha Development

Koha 3.8.1 Released
by Chris Cormack

The Koha release team is happy to announce the release of Koha 3.8.1.
This is a stable release and contains bugfixes as well as updated
translations.

Koha 3.8.1 can be downloaded here. Release notes are here.

Installation instructions can be found here or in the INSTALL files
that come in the tarball.

Koha 3.6.5 Release Imminent

As we go to press on 24 May 2012, Koha 3.6.5 is scheduled to be released today.

Koha Statistics

Chris Cormack, statistician par excellence, has posted bug statistics
for April and statistics for Koha 3.8.1.

Database Schema Documentation Updated

Koha’s database schema documentation has been updated.

Koha Community

New Koha Libraries

    Gerard Cottet Library at Salus University (via ByWater Solutions)
    Lane Library at Ripon College (via ByWater Solutions)
    North Central Regional Library (via ByWater Solutions)

Community Gossip

Lenora Oftedahl reports: “The StreamNet Library successfully upgraded
from 3.0 to 3.6. In addition to our upgrade, we also successfully
installed the Koha software on the same server as our WordPress CMS.
The two programs are peacefully co-existing through the creative use
of subdomains. You can visit our website at our new domain,
http://www.streamnetlibrary.org. If other users would like assistance
or have suggestions, please feel free to contact Lenora at
oftl-/jyUCfb61qK4UlQgPVntAg< at >public.gmane.org

Lee Miller of the Butte-Silver Bow Public Library in Montana reports
that her library is co-hosting KohaCon12 and that she’ll be presenting
at the conference on the use of open source software in Montana
libraries and the use of new applications and discovery tools.

Equinox Software is looking to hire a support specialist to provide
technical support for Koha and Evergreen.

Shire of Derby West Kimberley has become the first local government
area in Australia to choose Koha to support the delivery of its public
library services. More information is here.

Past Koha Events

May General IRC Meeting

The May general IRC meeting was held on 2 May 2012.

More info, including the agenda and links to the minutes, is here.

New Zealand Koha User Group Day 2012

Current and prospective Koha users got together at the New Zealand
Treasury on 15 May 2012 for the second New Zealand Koha users group
meeting. Chris Cormack reported on the meeting here.

Upcoming Koha Events

June General IRC Meeting

The June general IRC meeting will be held on Wednesday, 13 June 2012.

More info is here.

KohaCon12

KohaCon12 is nearly upon us! It will be held in Edinburgh, Scotland,
UK, 5-7 June 2012. A hackfest will be held 9-11 June 2012.

This is a free conference for everyone interested in the Koha library
system. There is no registration fee, but attendees are asked to
pre-register.

The conference schedule has been posted here.

The organizers continue to seek sponsors to help defray the cost of
the conference. Sponsors so far include Tamil, PTFS Europe, Catalyst,
Libriotech, Projektlink Konsult, The Galecia Group, C & P Bibliography
Services, CALYX Information Essentials, and KohaAloha. Information on
sponsorship is here.

More details on the conference can be found here.

KohaCon13

Bidding is now open for hosting of KohaCon13. Proposals can be viewed
and added on this page of the Koha community wiki.
_______________________________________________
Koha-devel mailing list
Koha-devel-yy2XUMoudrGBeeJdjao7tfCrwMbev77B< at >public.gmane.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

DateTime::Format::MySQL

Chris Nighswonger — 2012-05-24T13:50:33

Hi all,

The QOTD work recently committed to master adds DateTime::Format::MySQL as
a core dependency thereby extending DateTime objects to handle proper
formatting of datetime strings for MySQL.

While Koha::DateUtils will parse ISO formatted datetime strings, the POD
notes that the module is intended to be a temporary aid
to demystify DateTime foo while we are transitioning fully to DateTime:

"Koha has historically only used dates not datetimes and been content to
40
handle these as strings. It also has confused formatting with actual dates
41
this is a temporary module for wrappers to hide the complexity of
switch to DateTime"

There are similar DateTime::Format::<db> plugins for Pg, Oracle, and
friends which may be implemented in Koha as support for those db's is added.

Basically DateTime::Format::MySQL will parse a correctly MySQL formatted
datetime and return a DateTime object for your morphing pleasure.

It will also format a DateTime object and return a MySQL datetime string.

Read more here: http://tinyurl.com/br49o38

By moving away form a custom DateTime formatting module we reduce long
term maintenance costs and issues as well as moving a step closer to
dropping the temporary Koha::DateUtils.

Kind Regards,
Chris
_______________________________________________
Koha-devel mailing list
Koha-devel-yy2XUMoudrGBeeJdjao7tfCrwMbev77B< at >public.gmane.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: Print page - Firefox, etc

Owen Leonard — 2012-05-23T00:32:15

I don't know if this is the best way, but the most basic way is
probably to grab the updated file from the git web interface:

http://git.koha-community.org/gitweb/

I navigated to the 3.6.4 branch and found the most recent version of
the file in question, the staff client print stylesheet:

http://git.koha-community.org/gitweb/?p=koha-small.git;a=blob_plain;f=koha-tmpl/intranet-tmpl/prog/en/css/print.css;hb=441b98cea41ed7d99354195b79d5b4f44b194913

If you replace your file with that one it should be the functional
equivalent of reverting that commit.

  -- Owen

Re: Print page - Firefox, etc

Paul — 2012-05-23T00:15:52

[snip]

Thanks - what's the best way on a *production* server to revert the patch 
and install the better fix?

I must admit to not fully understanding how git (or whatever is most 
appropriate) is setup, and after a look at bug 6291, there appear to be 
quite a few elements touched.  In my sandbox, I once tried (unsuccessfully) 
to have two parallel but different versions of Koha so do not really want 
to try that on the production box.

Best - Paul



---
Maritime heritage and history, preservation and conservation,
research and education through the written word and the arts.
<http://UltraMarine.ca>, <http://AandC.org> and <http://MarDoc.ca>

_______________________________________________
Koha-devel mailing list
Koha-devel-yy2XUMoudrGBeeJdjao7tfCrwMbev77B< at >public.gmane.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: KOCT pushed on contrib repo

Chris Cormack — 2012-05-22T21:11:58

Awesome! Thank you

Chris
_______________________________________________
Koha-devel mailing list
Koha-devel-yy2XUMoudrGBeeJdjao7tfCrwMbev77B< at >public.gmane.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

KOCT pushed on contrib repo

Paul Poulain — 2012-05-22T21:07:21

Hello,

I just pushed a few minuts ago a patch with KOCT on the contrib repository
(http://git.koha-community.org/gitweb/?p=contrib/global.git;a=summary)

Re: Print page - Firefox, etc

Owen Leonard — 2012-05-22T18:01:32

Probably, in that your description matches exactly the PDF attached to
the bug ;)

However, I can't reproduce the problem in master so this may already
have been fixed. Tested in Firefox 12, Chrome 19, Opera 11, and IE 9
on Windows 7.

Judging from the description and the timeline of Koha 3.6.1 I'm
guessing the bug is caused by my first fix for Bug 6291 which was
subsequently reverted in favor of a better fix.

  -- Owen

Print page - Firefox, etc

Paul — 2012-05-22T15:49:56

Our cataloguers are having a local problem that I was unaware of. This is 
probably Koha bug 7199 which appears to be a tad inactive; I'd be happy to 
assist, but have no knowledge whatsoever of how browsers render 
CSS|templates for printing.

Trying to "print page" after a staff screen listing such as 
<http://koha-admin/cgi-bin/koha/catalogue/search.pl?q=lambert%2C+andrew> 
(the page itself is perfect) gives an oddball output with the "Results" and 
"Location" columns squeezed down to very narrow columns on the right hand 
side of the page. The "check box" column (normally very narrow) expands to 
well over 50% of page width.

This happens (for us at least) in Firefox (v. 12.0), Chrome (build 16.0), 
Safari (5.1) and MSIE (6.0 - we don't have anything more recent in our Win 
machine.)

A quick review of "equivalent" OPAC search pages (rather than staff-admin) 
shows no problems.

Koha 3.06.01.000, on Linux 2.6.38, Perl 5.010001, Apache 2.2.17, mysql Ver 
14.14 Distrib 5.1.54, for debian-linux-gnu

Thanks - Paul

_______________________________________________
Koha-devel mailing list
Koha-devel-yy2XUMoudrGBeeJdjao7tfCrwMbev77B< at >public.gmane.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: Proposed QA Enhancements

Ian Walls — 2012-05-22T15:44:23

For my part, I tend to review patches textual to see if they make sense as
a changeset.  If I cannot tell from reading what this patch does, I'll
either apply and test, or ask for clarification.  Generally, both of those
actions take more effort than reading on Bugzilla, and thus take longer.

I agree that it would be preferable to have the actual QA signoff on the
patch itself when it gets through QA, so that our git signoff stats are
more accurate.  That does add the additional overhead of pulling down and
applying each patch, then amending the commit and firing back up to BZ...
not complicated, but additional steps.  Hence why I haven't been doing it
reliably.

Any QA rules we can put into scripts to automatically check, I'm all for,
as that can relieve some of the more tedious work of checking spacing and
variable name declarations, and let QA look more in-depth about the patch's
implementation.  I know we've got a few such tests... anyone who is willing
to write more goes in my Nice Person book.

My new job is starting to ramp up further, and I'm finding myself doing
less QA than I expected.  I'll try to rectify that, but if the community
feels I'm not doing the job as it needs to be done, I do hope folks will
speak up and help us find a remedy to the situation.

Cheers,


-Ian

On Tue, May 22, 2012 at 11:02 AM, Marcel de Rooy
<M.de.Rooy-QifR6MnrAH5Dtxw8gMNZkQ< at >public.gmane.org>wrote:

_______________________________________________
Koha-devel mailing list
Koha-devel-yy2XUMoudrGBeeJdjao7tfCrwMbev77B< at >public.gmane.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: Proposed QA Enhancements

Marcel de Rooy — 2012-05-22T15:02:31

Just a quick response on first glance: The numbers in this discussion are imo far from accurate. As for me, I mostly QA without signing off, just to spare time. In most cases I did apply and test (at least some functionality, in other cases much more). I would not recommend doing QA in Bugzilla only, perhaps with the exception of very small things. 
Adding the rule that QA must do an additional signoff too will put more work (better testing etc.) on the QA team, and will result in more delay. If a QA member does not trust a patch, why not ask for a second signoff (older idea..)? 

________________________________________
Van: koha-devel-bounces-yy2XUMoudrGBeeJdjao7tfCrwMbev77B< at >public.gmane.org [koha-devel-bounces< at >lists.koha-community.org] namens Chris Cormack [chrisc-6STWZtX7tXAqAMOr+u8IRA< at >public.gmane.org]
Verzonden: dinsdag 22 mei 2012 10:51
To: Paul Poulain
Cc: koha-devel-yy2XUMoudrGBeeJdjao7tfCrwMbev77B< at >public.gmane.org
Onderwerp: Re: [Koha-devel] Proposed QA Enhancements

* Paul Poulain (paul.poulain-zkl4Dl7PsEhWk0Htik3J/w< at >public.gmane.org) wrote:

That's what Chris N was asking for, that a sign off is added when the
patch is tested, it must have been applied and tested, so why not sign
off and attach it back on the bug at the same time as changing the bug
status.

I'm not sure we want to get into a who does more for Koha contest, nor
do I think that was the point of this email.

I do think there are too many patches missing getting 2 independent
sign offs, and that is what we need to fix.

Chris

--
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-053, Manners St, Wellington 6142, New Zealand
_______________________________________________
Koha-devel mailing list
Koha-devel-yy2XUMoudrGBeeJdjao7tfCrwMbev77B< at >public.gmane.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
_______________________________________________
Koha-devel mailing list
Koha-devel-yy2XUMoudrGBeeJdjao7tfCrwMbev77B< at >public.gmane.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Multi-Lingual SQL & User Defined Parameters

Massoud Alshareef — 2012-05-16T06:03:11

Hello,

I have asked a question about two years ago about when we can have Koha
support of Multi-Lingual SQL files (used for marc21/Auth fields description
in the Staff client) and Multi-Lingual users defined parameters (used for
describing items/ libraries & groups/ locations/ patrons categories/ etc),
and the answer from Koha development then was that it is
under consideration but not in the development pipelines yet, as it will
require some re-structuring in Koha system databases and controls. That
means, Koha will remain a single language in these areas.

With Koha 3.6 release, I noticed the inclusion of "Spanish translation for
SQL files" in the INTERNATIONALIZATION enhancement section. Does this mean
that Spanish Koha, or any non-English Koha, now has both Spanish and
English SQL files, where Koha users can switch between more than one
language when, for instance, editing marc records in the staff client ?

Koha Preferences description used to be in SQL files, which means a single
language prefers, and then moved into PO files format with 3.2 release (I
think) and thus Preferences became multi-lingual since then.

Thank you Koha development for elaborating on the issue of having a fully
bilingual Koha.

BTW, Arabic Koha 3.8 is now on the fast-lanes translation speed to be
completed within 3-4 weeks.
See Arabic Koha 3.8 OPAC demo site on
http://176.34.184.60/cgi-bin/koha/opac-search.pl?q=%D8%B9%D9%84%D9%85

Thanks
Massoud M. AlShareef,

The world of achievement has always belonged to the optimist!

KnowledgeWare Technologies
(P.O. Box 230-312)
Riyadh 11321, Saudi Arabia
Cel: +966 505 307 267
massoud-UTyHMNcGeSdWk0Htik3J/w< at >public.gmane.org
_______________________________________________
Koha-devel mailing list
Koha-devel-yy2XUMoudrGBeeJdjao7tfCrwMbev77B< at >public.gmane.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: Proposed QA Enhancements

Chris Cormack — 2012-05-22T08:51:15

That's what Chris N was asking for, that a sign off is added when the
patch is tested, it must have been applied and tested, so why not sign
off and attach it back on the bug at the same time as changing the bug
status.

I'm not sure we want to get into a who does more for Koha contest, nor
do I think that was the point of this email.

I do think there are too many patches missing getting 2 independent
sign offs, and that is what we need to fix.

Chris

Re: Proposed QA Enhancements

Paul Poulain — 2012-05-22T08:40:22

Le 21/05/2012 19:38, Chris Nighswonger a écrit :
Something I made during the 3.8 release was to add many things to the
coding guidelines. My preference goes to QA rules that are clearly
defined and explained. That will help QAing a lot, and "anyone" with a
good Koha experience, and some time to dedicate should/could do it.

I agree that we *must* have a functional AND a technical review of every
patch, the 2 steps are different.

Most QA is done in bugzilla only: when a patch is QAed, it's not
signed-off & git bz attach most of the time.
(that's also why your numbers below are meaningless : Ian has not made
only 25 QA or joubu 5 ! OTOH, when I, as RM, push a patch, I always add
my signature, that can be as RM or QA)

As I just wrote, I don't do the majority of QA, (even if I agree I do a lot)

As I've said previously, as RM, I dedicate more than half of my time to
this task.
I think that we could have someone dedicated full time to QA and someone
dedicated full time to sign-off. And until we won't... we will face this
kind of trouble. Our workflow is good, but require a large effort we
collectively fail to "pay" until now.

[ off-topic: BibLibre dedicate a lot of resources to Koha (see
statistics on chris_c blog. A lot being "self-sponsored") and can't
dedicate more. I think everybody should ask himself seriously "What did
I do for Koha last week, what will I do next week ?" ]

+1 (and it's already done that way in fact : as member of the QA team, I
always order by date when I QA, and start by the oldest patches. I've
suggested to change the default order to date, but the idea has not been
approved)

Re: Koha 3.8.1 released

Chris Nighswonger — 2012-05-21T22:27:32

Huzza!

On Mon, May 21, 2012 at 5:32 PM, Chris Cormack <chris-BI0SDMbrYt0bf4OJjhDl03TaI6DYlTYJ< at >public.gmane.org>wrote:

_______________________________________________
Koha-devel mailing list
Koha-devel-yy2XUMoudrGBeeJdjao7tfCrwMbev77B< at >public.gmane.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Koha 3.8.1 released

Chris Cormack — 2012-05-21T21:32:25

The Koha release team is happy to announce the release of Koha 3.8.1

This is a stable release and contains bugfixes as well as updated translations.

You can download it at

http://download.koha-community.org/

Go forth, download, and enjoy :)


RELEASE NOTES FOR KOHA 3.8.1
21 May 2012
========================================================================

Koha is the first free and open source software library automation package
(ILS). Development is sponsored by libraries of varying types and sizes,
volunteers, and support companies from around the world.
The website for the Koha project is

    http://koha-community.org/

Koha 3.8.1 can be downloaded from:

    http://download.koha-community.org/koha-3.08.01.tar.gz

Installation instructions can be found:

   in the INSTALL files that come in the tarball

Koha 3.8.1 is a bugfix/maintenance release.

Highlights of 3.8.1
======================

7924criticalFix handling of command line arguments in koha-remove
7998critical3.8 UI cleanup, tweaks to new styles
8035criticalbibs with comments show an error in opac
8072criticalreports wizard dies
8077criticaloverdues with fines won't run
3969majorBudget Search Doesn't Work
7984majorFix the upload_local_cover_images permission
8002majorCan't add patron attribute type in newer installation
8027majorWrong order for parameters in Z39.50 SQL INSERT


Bugs fixed in 3.8.1
======================

2399normalAll status fields in the item edit interface offer two
blank/null entries per dropdown instead of one
3413normalrepeatable tickbox not sticking 1st time round
6335normalBranch not set consistently in all SIP transactions
7604normalLink on basket group name for closed basket groups is broken
7722normalInsidious problem with searching
7820normalMissing packages from install_misc/debian.packages
7842normalInconsistencies in Notices interface
7982normalTypo in moremember-receipt.tt
8020normalPrepare debian packages for 3.8 release
8022normalPermissions test doesn't check all languages
8025normalPatron attribute not selected if value is zero
8045normalProblems on Due date when checking in
8084normalSuspend Until not set on by suspend button
5345enhancementDataTables in Koha
5549enhancementHourly Loans
7178enhancementImprove order item creation
7213enhancementDocument /svc/ HTTP API and provide example command-line client
7647enhancementCheckout History Sort
7849enhancementInstant Fine Calculation at Checkin
7870enhancementReplace itemnumber by barcode in links of patron
modification log
7903enhancementadd an ordernumber column in orders history table
7990enhancementbad html attribute into aqplan.tt : styl= insted of style=
8001enhancementAdd some styling to the tags to allow them to be distinctive


System requirements
======================

    Changes since 3.6:

    * No new system requirements


Documentation
======================

As of Koha 3.2, the Koha manual is now maintained in DocBook.  The
home page for Koha documentation is

    http://koha-community.org/documentation/

As of the date of these release notes, only the English version of the
Koha manual is available:

    http://manual.koha-community.org/3.8/en/

The Git repository for the Koha manual can be found at

    http://git.koha-community.org/gitweb/?p=kohadocs.git;a=summary

Translations
======================

Complete or near-complete translations of the OPAC and staff
interface are available in this release for the following languages:

the following languages:
  * French (100%)
  * Spanish (100%)
  * German (100%)
  * Chinese -Taiwan- (97%, OPAC 100%)
  * Italian (86%, OPAC 100%)
  * Danish (81%)
  * Portuguese (79%)
  * French -canada- (76%)
  * English -nz- (76%)
  * Greek (74%)
  * Norwegian (73%)

Partial translations are available for various other languages.

The Koha team welcomes additional translations; please see

    http://wiki.koha-community.org/wiki/Translating_Koha

for information about translating Koha, and join the koha-translate
list to volunteer:

    http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-translate

The most up-to-date translations can be found at:

    http://translate.koha-community.org/

Release Team
======================

The release team for Koha 3.8 is

  Release Manager:       Paul Poulain <paul.poulain< at >biblibre.com>
  Documentation Manager: Nicole C Engard <nengard< at >gmail.com>
  Translation Manager:   Frédéric Demians <frederic< at >tamil.fr>
  QA Manager:            Ian Walls <koha.sekjal< at >gmail.com>
  QA team:               Marcel de Rooy <M.de.Rooy< at >rijksmuseum.nl>,
  Jonathan Druart <jonathan.druart< at >biblibre.com>
  Bug Wranglers:         Katrin Fischer, Magnus Enger

  Release Maintainer (3.4.x): Chris Nighswonger <cnighswonger< at >foundations.edu>
  Release Maintainer (3.6.x): Jared Camins-Esakov <jcamins< at >cpbibliography.com>
  Release Maintainer (3.8.x): Chris Cormack <chrisc< at >catalyst.net.nz>


Credits
======================

We thank the following individuals who contributed patches to
Koha 3.8.1.

     2Jared Camins-Esakov
     3Colin Campbell
     8Chris Cormack
     2Stéphane Delaune
     7Jonathan Druart
     4Magnus Enger
     6Katrin Fischer
     4Kyle M Hall
     2Srdjan Jankovic
     4Owen Leonard
     1Julian Maurice
     1Chris Nighswonger
     1Dobrica Pavlinusic
     4Paul Poulain
     2Liz Rea
     2Marcel de Rooy
     3Adrien Saurat
     3Robin Sheat
     2Lyon3 Team
     2Ian Walls


We regret any omissions.  If a contributor has been inadvertantly missed,
please send a patch against these release notes to
koha-patches< at >lists.koha-community.org.

Revision control notes
======================

The Koha project uses Git for version control.  The current development
version of Koha can be retrieved by checking out the master branch of

    git://git.koha-community.org/koha.git

The branch for Koha 3.8.x (i.e., this version of Koha and future bugfix
releases) is 3.8.x.

The next major feature release of Koha will be Koha 3.10.0.

Bugs and feature requests
======================

Bug reports and feature requests can be filed at the Koha bug
tracker at

    http://bugs.koha-community.org/


Ehara taku toa i te toa takitahi, engari he toa takitini
_______________________________________________
Koha-devel mailing list
Koha-devel< at >lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: Proposed QA Enhancements

Galen Charlton — 2012-05-21T17:52:22

Hi,

On May 21, 2012, at 1:38 PM, Chris Nighswonger wrote:

+1 -- this seems like a obvious procedure documentation fix, hopefully one that just more clearly describes existing practice.

[snip]

These go hand-in-hand.  I agree that reducing the QA burden the RM is a good thing, but in order for that to happen, I think one question that needs an answer first is how do we increase the size of the QA team?  Or to phrase it more broadly, what can we do to encourage more people to do QA, whether or not the current QA structure is used as is or changed?

Regards,

Galen
--
Galen Charlton
Director of Support and Implementation
Equinox Software, Inc. / The Open Source Experts
email:  gmc-DI3WXjSZzk1VtazZjgo0Tw< at >public.gmane.org
direct: +1 770-709-5581
cell:   +1 404-984-4366
skype:  gmcharlt
web:    http://www.esilibrary.com/
Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org

_______________________________________________
Koha-devel mailing list
Koha-devel-yy2XUMoudrGBeeJdjao7tfCrwMbev77B< at >public.gmane.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Proposed QA Enhancements

Chris Nighswonger — 2012-05-21T17:38:58

I am making two proposals that will help "tighten" up our QA procedures a
bit in order to facilitate clarity and transparency in our patch
submission/acceptance workflow. Currently the workflow is described in the
wiki here:

http://wiki.koha-community.org/wiki/Bug-enhancement-patch_Workflow#Steps

1. I propose that we modify step 5 to read:

"The patch is checked and signed-off by the QA team member. Then the bug
status is set to Passed QA"

This will ensure that we have clarity that the patch was, indeed, touched
by a member of the QA team, as well as increasing the accuracy of QA stats
in git.

2. I propose that the RM be the QA of last resort. At present the stats
show that the RM is doing the majority of the QA'ing. "Last resort" is a
condition evoked by all members of the current QA team acknowledging that
no one among them has the time, etc. to do QA on a particular patch the RM
feels needs to be pushed OR by a bug remaining in the "Signed Off" status
beyond a fixed time period of four weeks. This mechanism would address
concerns of bug stagnation by allowing ample time for QA members to at
least glance at a bug and determine of they do or do not have time to give
to that bug as well as having a catch mechanism for bugs falling through
w/o notice.

Here are some statistics on sign-offs by the currently listed QA team for
commits between the 3.6.0 and 3.8.0 tags:

NOTE: 100% of our patches have the minimum required 1 sign-off by any
community member

Total commits: 1086

Sign-offs by QA Team members:

Marcel de Rooy - 43
Jonathan Druart - 5
Paul Poulain - 538
Ian Walls - 25

Total commits w/sign-off by a QA team member: 611 OR 56.3%
Total commits w/sign-off by RM: 538 OR 49.5%
Total commits w/sign-off by non-RM QA member: 73 OR 6.7%

These figures reasonably agree with the stats posted here:
http://blog.bigballofwax.co.nz/2012/04/24/statistics-for-koha-3-8-0/

You may reproduce them on your local git repo master branch by using
variations of the following:

git log --grep="^Signed-off-by: <regexp>" --no-merges --oneline
52c666edce42..5c32a9f811d | wc -l

Lets have some discussion on the two proposals above, and I'll put them on
the agenda for the next IRC meeting to be voted on.

Kind Regards,
Chris
_______________________________________________
Koha-devel mailing list
Koha-devel-yy2XUMoudrGBeeJdjao7tfCrwMbev77B< at >public.gmane.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: Public IP for Koha

Paul Poulain — 2012-05-21T16:26:33

Le 21/05/2012 18:17, Fridolyn SOMERS a écrit :
Agreed, but you can also achieve that by using a virtual host configured
to listen only on your staff interface (you need a static IP for your
library though). that's how we do for most of our hosted customers afaik.

Re: Public IP for Koha

Fridolyn SOMERS — 2012-05-21T16:17:08

Hie,

Personnaly, I strongly recommand not to use a public access on intranet.

Can't you set up a VPN between your 4 branches libs ?
It is the most secured network solution.
Less secured solution is a reverse-proxy.

Best regards,

On Mon, May 21, 2012 at 4:16 PM, Tim O'brien <obtim123-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

Re: Public IP for Koha

Tim O'brien — 2012-05-21T14:16:09

Hi,
I manage  to intall koha 3.6. My institution has four branch libraries and
i wanted to use public IP so that the other three branches can access the
system. I am thinking of using public IP for these purpose. Kindly advice
me: the risks and if there are better options.
Regards,
O'brien
_______________________________________________
Koha-devel mailing list
Koha-devel-yy2XUMoudrGBeeJdjao7tfCrwMbev77B< at >public.gmane.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: Koha Calendar

Galen Charlton — 2012-05-16T18:57:58

Hi Elliott,

On May 16, 2012, at 12:00 PM, Elliott Davis wrote:

The table special_holidays itself currently just sets closed days, but just using a date field rather than year/month/day seems reasonable.  I'm less sure about using a timestamp field; if we extend special_holidays to cover not just closures but alternative opening and closing times, I think it might be better to use two time fields to set the opening and closing times, e.g.

special_holidays:
  the_date date
  open_time time
  close_time time
  is_open_at_all boolean

Regards,

Galen
--
Galen Charlton
Director of Support and Implementation
Equinox Software, Inc. / The Open Source Experts
email:  gmc-DI3WXjSZzk1VtazZjgo0Tw< at >public.gmane.org
direct: +1 770-709-5581
cell:   +1 404-984-4366
skype:  gmcharlt
web:    http://www.esilibrary.com/
Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org

_______________________________________________
Koha-devel mailing list
Koha-devel-yy2XUMoudrGBeeJdjao7tfCrwMbev77B< at >public.gmane.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/