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

Re: [Koha] Koha 2.2 release plan & translations
by Paul POULAIN 05 Oct '04

05 Oct '04

Indranil Das Gupta a écrit : >Hi Paul, >On Tue, 2004-10-05 at 15:07, Paul POULAIN wrote: ><snipped> > > >>I encourage all the translators team to work on actual CVS. I can send a >>uptodate file to translate to anyone requesting it. the opac is about >>500 lines, the librarian interface is about 3000 lines (without >>OnlineHelp for instance) >> >> >Requesting the uptodate file. I'm volunteering to translate Koha into my >mother tongue - Bangla/Bengali (BN), spoken by about 200 million people >in India and Bangladesh. > > Really great, I've stored on CVS (http://cvs.sourceforge.net/viewcvs.py/koha/koha/misc/translator/po/) 2 _en_EN.po files. get them, then rename them match your language (like fr_FR.po for french), then begin translation. note : the file may not appear immediatly, but they are here -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Koha Documentation Structure
by Stephen Hedges 04 Oct '04

04 Oct '04

I have attached a file called "koha_docs_structure" which contains an outline for all of the Koha documentation. This is _not_ the documentation itself, but a description of the structure that will be used to organize the documents. (If you have trouble with the attachment, you should be able to find this file on Sourceforge at http://cvs.sourceforge.net/viewcvs.py/koha/koha-doc/ within the next few days.) The outline contains some words in brackets <Like This> that are names for document containers. Many of these containers simply hold other containers. Only the text that is not enclosed by brackets (for example, "Description in English") refers to an actual document. The goal is to have a place for every type of Koha-related document. If you have Koha-related documents that do not seem to have a place in the structure, please let me know. If you can think of some possible Koha-related documents that do not seem to have a place in the structure, please let me know. It is not intended that we have a document that matches every document described. But it is intended that every document that gets submitted can be easily "plugged in" to this document structure. I will be retrieving existing documents, such as Nicholas Rosasco's "Koha Manual," converting them to XML, and fitting them into this structure. All documents will be stored in XML format, but you can submit documents in any format that is comfortable for you. (XML was chosen as the format for storage because it is basic and can easily be converted to many other formats using a wide variety of tools.) I will also be looking through old e-mail messages for relevant information, and may contact some e-mail writers and ask that they expand their comments into a document that can be used as part of the Koha documentation. If you would like to submit a document, please include the following statement in the document: "This document is copyrighted (c) 2004 by <your name here>. Unless otherwise stated, Koha documents are copyrighted by their respective authors. Koha-related documents may be reproduced and distributed in whole or in part, in any medium physical or electronic, as long as this copyright notice is retained on all copies. You may create a derivative work and distribute it provided that you: 1. Send your derivative work to the Koha Project for possible posting on the Internet. 2. License the derivative work with this same license, or the Linux Documentation Project License (http://www.tldp.org/manifesto.html) or the GNU General Public License (http://www.gnu.org/copyleft/gpl.html) Include a copyright notice and at least a pointer to the license used. 3. Give due credit to previous authors and major contributors. Commercial redistribution is allowed and encouraged; however, the author would like to be notified of any such distributions. Please check your local laws on copyright." OK, that's it. All comments or suggestions for improvement are welcome. --- Stephen Hedges Skemotah Solutions

3 3

RE: [Koha-devel] Koha Documentation Structure
by Anthony Youngman 04 Oct '04

04 Oct '04

Take a look at some of the O'Reilly books. I don't know how many of them are "Free" books that they have taken off the net, but there are a fair few where O'Reilly includes the source of the book and is not able to stop users copying the text. I thought DocBook was one of these but I'm not sure. If you want a "publisher friendly" licence, contact O'Reilly and ask them. As for all the documentation "being XML" and someone pointing out that XML is more a meta-format than a format, I would say that you should use DocBook for the documentation. I seem to remember hearing something about DocBook being updated recently, but it is a structured markup language, I think it does have an XML DTD, and it's pretty much the standard for Free Software documentation (the master copy, at least). The nice thing about it is that all the scripts, programs and everything are all there so that you can convert it into a help file, an html manual, a print manual, whatever. And if a publisher should decide it's worth printing, it's in a nice, convenient, STANDARD form for them to just drop into their system and run with ... Cheers, Wol -----Original Message----- From: koha-devel-admin(a)lists.sourceforge.net [mailto:koha-devel-admin@lists.sourceforge.net] On Behalf Of Joshua Ferraro Sent: 04 October 2004 15:15 To: koha-devel(a)lists.sourceforge.net Subject: Re: [Koha-devel] Koha Documentation Structure On Mon, Oct 04, 2004 at 02:39:49PM +0100, MJ Ray wrote: > froody... If you want CC, use that one ;-) Free software needs free > software manuals. However, I do think we should at least consider the possibility of a printed manual at some time in the future. So which license is likely not to prevent a publisher from signing on? Or would we self-publish? Joshua ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/koha-devel **************************************************************************** This transmission is intended for the named recipient only. It may contain private and confidential information. If this has come to you in error you must not act on anything disclosed in it, nor must you copy it, modify it, disseminate it in any way, or show it to anyone. Please e-mail the sender to inform us of the transmission error or telephone ECA International immediately and delete the e-mail from your information system. Telephone numbers for ECA International offices are: Sydney +61 (0)2 8272 5300, Hong Kong + 852 2121 2388, London +44 (0)20 7351 5000 and New York +1 212 582 2333. ****************************************************************************

1 0

[OT] announce
by Paul POULAIN 02 Oct '04

02 Oct '04

Hello Koha developpers, I'm very, very, very happy to give you this link and announce that my 3rd son is born. Official annoucement (in french) and some pictures at : http://www.paulpoulain.com/jeremie/ -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

3 2

Koha Favicon
by Russel Garlick 28 Sep '04

28 Sep '04

Hi I have made and added a Favicon to the Koha.org website. Kinda nice as it shows up in your bookmarks and stuff. If you want to grab it, it is here - http://www.koha.org/favicon.ico Cheers -- Russel Garlick Operations Manager Katipo Communications Ph 04 934 1285 Mob 027 537 1377 Web www.katipo.co.nz

1 0

OLC Annual Conference Docs
by Joshua Ferraro 28 Sep '04

28 Sep '04

Hi everyone, I've finally finished my conference handout and Koha presentation slides/notes for the OLC conference on Wednesday (http://http://www.olc.org/ann_conf.asp) and they are available on my website: Slides: http://kados.org/LibraryScience/presentations/OLC2004/koha.html (looks best in Mozilla; http://mozilla.org) Notes: http://kados.org/LibraryScience/presentations/OLC2004/koha-notes.html Handout: http://kados.org/LibraryScience/presentations/OLC2004/koha_at_a_glance.pdf (there's an html version too: http://kados.org/LibraryScience/presentations/OLC2004/koha_at_a_glance.html) There'a also a Freemind mindmap that basically contains the same general information as the handout ... but in a mindmap format: http://kados.org/LibraryScience/koha.mm http://kados.org/LibraryScience/koha.mm.html (if you don't have Freemind you can use your browser--or download http://sourceforge.net/projects/freemind) I've also put together a static Koha resources page with a few more resources listed than on the handout (due to space constraints) that I plan to point folks to for further info (since the official one isn't ready yet): http://kados.org/LibraryScience/koha.html There's still one day before the conference so if anyone has any suggestions for improving anything let me know--if you know of any resources I've not listed please drop me a note. And feel free to use and modify anything as it's all CC licensed (http://creativecommons.org/licenses/by-nc-sa/1.0/) I'm going to try to videotape the Koha presentation, our Linux Installfest and our Kohafest ... so hopefully that'll be forthcoming too. Finally, if I have time I'll spruce up the docs I've written and get them out later today ... we'll see how that goes. Joshua Ferraro

2 2

Re: [Koha] Double _items_ tags, Was: More questions for migrating to koha
by Paul POULAIN 27 Sep '04

27 Sep '04

Dana Huff a écrit : > Umm...actually the script you sent me still has the error. Here is the > corrected script with comments around the change. Dana, you're the best ;-) In fact, I use a specific bulkmarcimport when migrating french libraries. It does some specific stuff for a given library (like cleaning the XXX field, moving the YYY field, checking something...) I've fixed this bug some months ago, but I realise I never fixed the official CVS bulkmarcimport !!! I'll fix it ASAP. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Moving to Arch?
by MJ Ray 26 Sep '04

26 Sep '04

In yesterday's IRC, "CVS and Arch" was one of the last things discussed and some of the developers had to be in other places by then, so I agreed to summarise to the list and start discussion here. Please wade in with comments or questions as you see fit. Here we go! Introduction: I introduced GNU Arch http://www.gnuarch.org/ which solved the problems I had getting 2.0 under control and making tarballs from it. The move mostly consisted from making a tarball from CVS, unpacking it and then adding the files to an Archive. That's what you can get from my development page at http://www.mjr.dsl.pipex.com/ Anyone can make their own copy of the koha2 archive and publish it if they have a public file space (web, ftp or sftp for sure). That works for mirrors and for development branches. So, new developers have full revision control easily, by default, rather than needing hacks or write access to the release source tree. A release manager can merge their changes into the release tree with a simple command. Apart from merging, all operations happen on your own file space, which eliminates the wait for a central server to answer that often holds me back with CVS. Suggestion and tasks: I suggest trying to move to arch for 2.4 development if we can get it working for current developers, because it should make the lives of the release managers and new developers a lot easier. I've offered to answer questions and improve my tutorial until it's good enough. Some commented about having large amounts of CVS experience, but there didn't really any great love for CVS, more a feeling of "better the devil we know". The sticking points are likely to be users of GUI interfaces and Microsoft Windows, so I'd be very happy about offers to help with those. No other public archives for 2.0 were posted, which I think is a shame, but I guess 2.2 has all the appeal for developers now. A couple of people mentioned that they would like 2.0 commit messages to koha-cvs, so I'll try to set that up. There was a suggestion of compiling a list of benefits and drawbacks of each system, but I think that's probably already covered by http://wiki.gnuarch.org/moin.cgi/SubVersionAndCvsComparison or could be (it's a wiki). Finally, what would happen to the CVS? I'd leave it as a historical record, with some clear marking that development has moved on. You can transfer some of the history to Arch, but it's an attempt to reconstruct information that isn't really kept by CVS, so it seems more trouble than its worth. -- MJR/slef My Opinion Only and not of any group I know Creative copyleft computing - http://www.ttllp.co.uk/ http://www.thewalks.co.uk stand 13,Lynn Carnival,12 Sep

5 12

Re: [Koha-devel] Moving to Arch?
by Owen Leonard 24 Sep '04

24 Sep '04

> Yes, arch basically stores the repo as a tar.gz of sources > and a tar.gz of patchfiles and some instructions; along > with that goes some metadata like the email-style log > file. Does that mean you can't do an update on an individual file? Thanks for bearing with me, I haven't had a chance to read any of the docs yet. -- Owen

4 4

Re: [Koha-devel] Moving to Arch?
by Owen Leonard 23 Sep '04

23 Sep '04

> > So does this mean that I can't merge back into the main > > branch ... that you > > have do do that? In CVS anyone with devel privs could > > commit to the main repo ... or am I mising something? > > Either the RM or their automaton will need to do the merge. > This is a deliberate model change from CVS which both allows > more people to do more development tasks without waiting for > approval, and allows the RM to say "show me the code" before > accepting it into the final release tree, if they want. It sounds like this is quite a shift of power, if I understand correctly, from a group of trusted developers to a single director who chooses what goes in and what doesn't. Do I understand correctly? Have we had problems in the past that will be alleviated by this shift of power? -- Owen

3 2