- Koha-devel - lists.koha-community.org

Koha 3.8 release schedule & perltidy process
by Paul Poulain 12 Mar '12

12 Mar '12

Hello koha-devel, I just updated the 3.8 release process with the schedule/planning of the release: http://wiki.koha-community.org/wiki/Roadmap_to_3.8 Here it is: March, 23th (1 month before the release) = feature freeze. April, 6th = strong feature freeze, string freeze April 20th = starting release process, everything frozen April 23th = release of Koha 3.8.0 IMPORTANT = perltidy process In january IRC meeting we spoke of perltidy thing. We have a coding guideline rule that says code must be perltidied. However, all the existing code is not perltidied, and it's hard to mix perltidied and non perltidied code. Thus, we have investigated the idea of doing a "perltidy big-bang" just when releasing 3.8.0, for all the code. Pro: * the code will be perltidied, the coding guideline will be applicable * all perltidy being made at the same time, it will be easier to read the git log. (One of the argument against perltidying is that it's a problem for reading git history) * doing that for a release is better for future bugfixes means that patches will apply on 3.8 as well as on master. Cons: * patches that are waiting may become "does not apply" because of the perltidy thing * patches submitted to fix bugs in 3.8 may not apply on 3.6 easily, that will add more work for 3.6 releases. All in one, our conclusion was that the best solution is to do that during a release process. So I plan do it during 3.8 release. (I have a (small ?) question about that : do you think I should make only one huge commit with perltidy ? one for each directory ? one for each file ?) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

13 19

Re: [Koha-devel] Koha 3.8 release schedule & perltidy process -- more time?
by savitra sirohi 10 Mar '12

10 Mar '12

Hi Paul, we have been caught off-guard by this schedule. We have a lot of stuff to submit but March 23rd is too little time. If we have 2 more weeks, we can get good stuff included. Possible? Thanks, Savitra Sirohi Nucsoft OSS Labs http://www.osslabs.biz On Thu, Mar 8, 2012 at 6:29 PM, Paul Poulain <paul.poulain(a)biblibre.com>wrote: > Hello koha-devel, > > I just updated the 3.8 release process with the schedule/planning of the > release: http://wiki.koha-community.org/wiki/Roadmap_to_3.8 > > Here it is: > March, 23th (1 month before the release) = feature freeze. > April, 6th = strong feature freeze, string freeze > April 20th = starting release process, everything frozen > April 23th = release of Koha 3.8.0 > > IMPORTANT = perltidy process > > In january IRC meeting we spoke of perltidy thing. We have a coding > guideline rule that says code must be perltidied. However, all the > existing code is not perltidied, and it's hard to mix perltidied and non > perltidied code. > Thus, we have investigated the idea of doing a "perltidy big-bang" just > when releasing 3.8.0, for all the code. > > Pro: > * the code will be perltidied, the coding guideline will be applicable > * all perltidy being made at the same time, it will be easier to read > the git log. (One of the argument against perltidying is that it's a > problem for reading git history) > * doing that for a release is better for future bugfixes means that > patches will apply on 3.8 as well as on master. > > Cons: > * patches that are waiting may become "does not apply" because of the > perltidy thing > * patches submitted to fix bugs in 3.8 may not apply on 3.6 easily, that > will add more work for 3.6 releases. > > All in one, our conclusion was that the best solution is to do that > during a release process. > So I plan do it during 3.8 release. > > (I have a (small ?) question about that : do you think I should make > only one huge commit with perltidy ? one for each directory ? one for > each file ?) > > -- > Paul POULAIN > http://www.biblibre.com > Expert en Logiciels Libres pour l'info-doc > Tel : (33) 4 91 81 35 08 > _______________________________________________ > Koha-devel mailing list > Koha-devel(a)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/ > -- Thanks, Savitra Sirohi Nucsoft OSS Labs Professional Support for Open Source Software Ph: +91 89718 06111 Web: http://www.osslabs.biz

2 2

Mobile friendly OPAC
by Marc Boivin 09 Mar '12

09 Mar '12

Hi all, We've been working a mobile friendly OPAC, you can find it here https://dev3.koha.sys-tech.net/ (please be gently it's a development server, very little resources). I did not want to post it on en general list, because the server can't handle much. To test it, either use a mobile device or, in a modern browser, shrink the width of your window till around 700 pixels. What we've done, using CSS Media Queries, is: * Remove as much noise as possible to focus on simple search and record consulting. * Simplified the advance research, only reachable if there is no search results * Reformatted opac-detail Next thing on our list is user login, we hope to have it done by the end of next week. We would like to give this feature back to the community. But first I'd like to get input on what would be nice, what's missing, what you generally think of the idea. TIA, Marc Marc Boivin Chargé de projet Web 418 520-0739, poste 169 marc.boivin(a)libeo.com Libéo / Web et applications libres 6700, boulevard Pierre-Bertrand, bureau 209 Québec (Québec) G2J 0B4 S. F. : 1 877 969-8324 Téléc. : 418 520-4554 www.libeo.com Aimez-nous sur Facebook : www.facebook.com/libeocom

1 0

Rebasing Solr devs at Hackfest
by Claire Hernandez 09 Mar '12

09 Mar '12

Hello, Just to say I'm eager to do things for Solr integration in Koha community version during Hackfest in Marseille in 10 days! There are 5 full days, I am not alone so we can start something usefull. I would like to know who is interested to test things, give feedback to move forward this week (and after). I already have some names ;) Feel free to write me to explain your vision (or encourage us :), give tips, offer help etc.! Thanks! Claire.

1 0

Fwd: [LIS-Forum] Mysore University Koha OPAC on Mobile
by SANDEEP BHAVSAR 09 Mar '12

09 Mar '12

---------- Forwarded message ---------- From: Ishwar Goudar <goudarishwar(a)googlemail.com> Date: Thu, Mar 8, 2012 at 7:39 PM Subject: [LIS-Forum] Mysore University OPAC on Mobile To: lis-forum(a)ncsi.iisc.ernet.in, francis(a)ncsi.iisc.ernet.in Dear Professionals, I am happy inform you all that our University Library Web OPAC has gone the * mobile way*. We have adopted open source library automation system KOHA for all our house keeping activities including OPAC and the same has been made available in cloud hosting environment. Anybody can access our OPAC on *Mobile* at site http://mopac.mysore-univ.org/ To see what it looks like in a mobile phone, please use following site on your desktop/laptop: http://iphonetester.com/?url=http://mopac.mysore-univ.org/ Apple claims to have sold record number of Smart-phones smashing the the record of PC sales. The same has been the fate with Laptops and notebooks. ( http://www.digitaltrends.com/mobile/smartphone-sales-exceed-those-of-pcs-fo… ) Internet access through Mobile has become the order of the day. This being the case, I strongly feel that all of us should go the mobile way for our OPACs. Our patrons can use their mobile for reserving, renewing the documents and all related activities. We are working towards using Mobile SMSs for overdue reminders, informing the availability of reserved documents, documents purchased against requests, broadcasting important library related messages, etc. The automation model we have adopted is *-* Centralised database, decentralised inputting/ housekeeping activities and Universal access to OPAC. Once completed the OPAC will have > 10 Lakh records of documents available in colleges, institutes, PG Centres and various departments, which are directly under the control of Mysore University. We acknowledge OSS Labs, Bangalore for having given quality, timely and cost effective service to us in this matter. Probably ours is the first university library to go mobile way for OPAC (?). Please have a look at it and give your feedback, enabling us to improve the service. Regards, Dr. I.R.N. Goudar Visiting professor and Library Adviser University of Mysore -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

2 1

Fwd: Re: Some changes to saved queries
by Paul Poulain 09 Mar '12

09 Mar '12

fwding the discussion I just had with Ian, as I think what we wrote can be usefull -------- Message original -------- Sujet: Re: [Koha-devel] Some changes to saved queries Date : Fri, 9 Mar 2012 07:49:58 -0500 De : Ian Walls <koha.sekjal(a)gmail.com> Pour : Paul Poulain <paul.poulain(a)biblibre.com> I would agree a default chronological sort for these reports would be the best. It doesn't affect how I do my QA, and can provide some valuable extra info to everyone. ++ Ian On Mar 9, 2012 6:28 AM, "Paul Poulain" <paul.poulain(a)biblibre.com <mailto:paul.poulain@biblibre.com>> wrote: Le 09/03/2012 12:24, Ian Walls wrote: > For my end, I don't always QA in the order the report gives. Some > patches are much quicker to evaluate than others, and the blocks of time > I have to do QA are of varying lengths and intensities. So, I pick the > combination of bug reports that look like they'd fit into the time I have. > > Not the most systematic approach, but effective. I know, I understand and I agree. One could also say that a "BLO" bug must be QAed before an ENH. My main concern here is that everybody is aware that there are some patches that are waiting for a long period. If you look at the 10 patches that need signoff for more than 2 months, most of them are quite tricky (and probably boring). But at least we know that they're waiting. Otherwise, they're lost in the middle of other patches ! PS: and i'm just asking for the DEFAULT order, that you can change in 1 clic. I don't request a rule saying "one MUST signoff/QA/..." in last change date order (even if I think it would not be a silly rule, it's not an applicable one for our community) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

1 0

Some changes to saved queries
by Paul Poulain 09 Mar '12

09 Mar '12

Hello all (and 1st of all chris_c) I'd like to have a different sort order for "passed QA" query: I push usually from oldest to newest QAed patch, so, could you please update the "passed QA" query to sort by last changed ? Same thing for signed-off = I think it's better to QA things from oldest to newest. And I'd also like to have the same sort order for "needs signoff". This way, old bugs needing attention will appear first. I think that will encourage ppl to test them. All of those queries are "owned" by you chris_c, so you're the one who can do something about that ! -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

1 0

Retrieving 10-digit ISBNs in a report
by Cab Vinton 08 Mar '12

08 Mar '12

Hi, All -- For the purposes of creating a web-based carousel of book covers of our recent acquisitions, I'd like to run a report that generates a list of ISBNs of items added between 2 dates. Amazon & therefore Koha rely on 10-digit ISBNs for book cover retrieval. However, when I run a report using biblioitems.isbn, this is the output I get. Many truncated ISBNs, presumably because the max length = 30 restriction. 9780425243244 (pbk.) | 0425243 9780307718099 | 0307718093 0804840288 | 9780804840286 (tr 9780811876377 : | 0811876373 : 1569244677 9781400064588 (acidfree paper) 9780061429255 | 0061429252 9781451661064 (hardcover) | 14 Is there a way to run a report that outputs only the 10 digit ISBNs? Many thanks, Cab Vinton, Director Sanbornton Public Library Sanbornton, NH

2 4

Google Apps integration
by Pratik Malhotra 08 Mar '12

08 Mar '12

Hello all, I am looking for someone who can do some development in Koha for me. My users should be able to login koha using their google apps email ids. Please let me know if anybody is interested. Thanks Pratik

8 9

Bugs with patch& follow-up
by Paul Poulain 08 Mar '12

08 Mar '12

Hello all, Short version: if you have a bug that has more than 1 patch, PLEASE, keep the in the apply order Long version: As you all know (I hope!), i've developed a system to test patches online. When you're a librarian, it's easy to try a patch in a few clics. However, if a bug has more than one patch attached, the system will work only if they are correctly ordered: the follow-up *must* be after the initial patch, because the system is automatic, not very intelligent, so can't detect it's a follow-up if it appears first. Stéphane Delaye wanted to test a bug this morning, and it failed because of this. I showed him how to reorder patches by downloading/reuploading patches, but it's better to keep them in the right order. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

1 0