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

Google Summer of Koha
by Joshua M. Ferraro 16 Mar '07

16 Mar '07

Hi all, Just a heads up to the Koha community that LibLime was selected as a mentor for the Google Summer of Code program. We've got a few ideas defined already, but are certainly open to additional suggestions: http://wiki.liblime.com/doku.php?id=googlesummerofcodeideas So if you've got a neat koha-related project that's doable in a three month period by a student or group of students, let us know. And of course, if you happen to be a student, we'd love to have you involved. You can select from one of the ideas above, or come up with something completely new ... More info about the program and the application process is available at the Google Summer of Code site: http://code.google.com/soc The deadline is fast approaching so get those applications in. Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS

2 2

Status of Savannah
by Joshua M. Ferraro 16 Mar '07

16 Mar '07

Hi gang, I'll get back into the version control discussion shortly, just wanted to post a note saying where we're at with the recovery of Savannah. I was able to re-commit everything to the HEAD branch. However, if you have a working copy newer than Sunday March 10th, you may want to check out a fresh copy and diff your changes into the fresh copy to avoid conflicts. If you have any questions about this, let me know. Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS

1 0

Version Control
by Kyle Hall 16 Mar '07

16 Mar '07

Hello All, On the topic of version control. I think everybody is in agreement that we need a backup system, no matter if koha stays at savannah, moves to google, or goes somewhere else. We at the CCFLS are offering to put up a VCS mirror. I assume that it is possible to do a nightly sync of the main vcs to our backup vcs, please correct me if I'm wrong. Thoughts? Opinions? Kyle -- IT Tech Crawford County Federated Library System

1 0

Re: [Koha-devel] [URGENT] Move away from Savannah/CVS
by Simon Mitchell 16 Mar '07

16 Mar '07

Ruby has moved to SVN http://www.ruby-lang.org/en/ I sure that koha will move to ruby one day, so why not move to SVN as a first step. ;-)

2 1

Savannah back up
by Joshua M. Ferraro 15 Mar '07

15 Mar '07

Hi gang, Just a quick note to say that savannah is back up. The first thing Chris and I did was to nab the whole repository, history, etc. and I've set up a cron job to do a nightly rsync. In case you want to do one too, here's how to go about it: $ rsync -avzru cvs.savannah.nongnu.org::sources/koha/ ./ -a = archive (ie copu) -z = compress for transmission -r= recursive -u=update If you put that in your crontab it'll just grab diffs rather that download the whole thing every time. Next task is to merge in the change history, I'll report back when that's done. Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS

1 0

GNA vs GNU
by Joshua M. Ferraro 14 Mar '07

14 Mar '07

For what it's worth, those interested might be interested in this brief history of Savannah and Gna: http://en.wikipedia.org/wiki/Gna.org Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS

2 1

3.0 Code Audit: Web Installer
by Joshua M. Ferraro 12 Mar '07

12 Mar '07

Hi folks, Ryan and I have started a code audit of Koha 3.0 and we have the results of the first module in that audit, the new Web Installer. A few months back we decided to split installation into two types: system-level, and librarian-level. The web installer is the first example of a librarian interface to installation. It was written by Henri-Damien, so first off, I'd like to thank Henri-Damien and the French team for devoting resources to this very important component of Koha. The new Web Installer allows a systems person to download Koha, install dependencies, set up Apache, create the MySQL database, add a user with permissions, and then hand the rest of the install process over to a librarian to be completed via a web interface. This web-based installer will check the dependencies, create the table definitions and constraints, allow the user to pick frameworks and other default settings to import, upgrade the db definition using updatedatabse, etc. We have a list of items that need to be improved before we sign off on the Web Installer as ready for 3.0. These items have all been entered into bugzilla as 'blocker' bugs. There are some additional items we'd like to improve that aren't bockers but that would be nice. These are also listed in bugzilla. Here are the blocker bugs: 1298: Web installer uses platform-specific elements 1302: Web Installer should check a conf variable to determine if Koha's already been installed 1303: Before web installer is run, opac and intranet interfaces should redirect to the installer Henri-Damien has agreed to do 1302 and 1303 this week. We could use some help on 1298, any volunteers? There are also a couple of 'wish list' items: 1304: Remove system call to mysql from Web Installer. 1305: Add error checking to web installer Any takers? OK, gonna get back to the audit, let me know if you have questions or ideas. Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS

1 0

HEAD & REL_3_0
by Paul POULAIN 09 Mar '07

09 Mar '07

Hello, i spoke with joshua, who confirmed that nothing was waiting for a commit in rel_3_0 from liblime. thus, tomorrow morning, unless i've more urgent work to do, i'll move rel_3_0 to HEAD and create a rel_TG branch and declare rel_3_0 DEAD ! I'll tell you when it's done, you'll have to move from rel_3_0 to head then. (and pls commit nothing in rel_3_0 when it will have been done...) -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19

1 1

huge commit done...
by Paul POULAIN 08 Mar '07

08 Mar '07

Hello, I just commited a huge stuff. This commit, even if huge, should be harmless. it contains : - some visual improvements (repeated titles removed, 3 colors/classes in members detail like in biblio detail, some buttons moved, tools module menu completed...) - a hardcoded string in search.pl has been moved to the template to be translatable (and/or/not + Scan indexes) - some _() have been added in javascript to get the strings in translation tool - some strings have been splitted when they mean 2 different concepts that needs different words in a language other than english, even if in english there is only one (like "issues", used for issuing books & serial issues. "serial" added where needed for example) Except for search.pl removed hardcoded string, only templates are concerned by the commit. -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19

1 0

koha 3.0 and accesskey
by Paul POULAIN 08 Mar '07

08 Mar '07

Hi, In rel_3_0, Joshua has added some accesskey to the left menu. For example : Issues, has access key u. Great and useful. Except that, in french, we say "prêts", that has no u. The result in koha 3.0 french is a not nice "prêtué à" , which means nothing. I investigated to fix this problem and see only 2 ways of fixing it : - remove accesskeys from the templates when generating translated files. A feature will be missing, but at least descriptions will be correct ! - use universal accesskeys. The only "universal" accesskeys I can imagine are numbers. So a solution could be to have : 1-Issue 2-Search (member) 3- search (catalogue). That sounds more easy to remember for users, but I would like to hear english speaking ppl giving their opinion. Note : the translator tool we use can't deal with accesskey (ie : we could get the string but have no method to "link" it to the description, making impossible to know which description it refers to). So the solution to translate the accesskey can't be reached. Of course, it would have be the best one ! -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19

3 2