How frequently to run zebra rebuild and what switches
Hello everyone, Looking for some advice and recommendations. For a fairly small library running Koha 3.12.00.000 from the Debian squeeze packages, how often should the zebra_rebuild.pl script be executed and with exactly which switches? Right now I run it at 7:30 AM each morning with "-run-as-root -b -r -v" (yes, I run it as ROOT). The reason I ask is that by doing it this way, when the Librarian enters new holdings they don't show up until the next morning.can I run it more frequently, and if so what are people's recommendations on how often? I don't want the burden the server as the rebuild seems to be somewhat resource intensive and for at least the final part of the rebuild we get a "no results found" message when searching so I don't want to rebuild too frequently. Suggestions? THANKS, as always! Steve
Hello Steven,
Looking for some advice and recommendations. For a fairly small library
running Koha 3.12.00.000 from the Debian squeeze packages, how often should the zebra_rebuild.pl script be executed and with exactly which switches? Right now I run it at 7:30 AM each morning with "-run-as-root -b -r -v"
I am quite surprised you need to do that since you say you installed from Debian packages. All the installations I have done through the Debian packages always have the zebra incremental indexing properly set in cron and it is usually set to run every 5 minutes. You can check your cron settings to make sure that this is properly set and enabled to run regularly. I don't think you need to run it manually. That is as per my own experience. Cheers Olugbenga Adara
Thanks for the reply, but I'm 99% sure it was NOT there by default. Can someone tell me what the "default" crontab entry for rebuild_zebra.pl is, and maybe what ALL of the default crontab entries are/should be? Now I'm concerned I'm missing more than just the rebuild_zebra one. Steve -----Original Message----- From: Olugbenga Adara [mailto:gbengaadara@yahoo.com] Sent: Tuesday, August 20, 2013 2:50 PM To: Steven Nickerson; koha@lists.katipo.co.nz Subject: Re: [Koha] How frequently to run zebra rebuild and what switches Hello Steven,
Looking for some advice and recommendations. For a fairly small library
running Koha 3.12.00.000 from the Debian squeeze packages, how often should the zebra_rebuild.pl script be executed and with exactly which switches? Right now I run it at 7:30 AM each morning with "-run-as-root -b -r -v"
I am quite surprised you need to do that since you say you installed from Debian packages. All the installations I have done through the Debian packages always have the zebra incremental indexing properly set in cron and it is usually set to run every 5 minutes. You can check your cron settings to make sure that this is properly set and enabled to run regularly. I don't think you need to run it manually. That is as per my own experience. Cheers Olugbenga Adara
Steven, The packages are set up to install the following cron jobs: /etc/cron.d/koha-common => http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=debian/koha-common... /etc/cron.daily/koha-common => http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=debian/koha-common... /etc/cron.hourly/koha-common => http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=debian/koha-common... Regards, Jared On Tue, Aug 20, 2013 at 3:02 PM, Steven Nickerson <snicker1@maine.rr.com>wrote:
Thanks for the reply, but I'm 99% sure it was NOT there by default. Can someone tell me what the "default" crontab entry for rebuild_zebra.pl is, and maybe what ALL of the default crontab entries are/should be? Now I'm concerned I'm missing more than just the rebuild_zebra one.
Steve
-----Original Message----- From: Olugbenga Adara [mailto:gbengaadara@yahoo.com] Sent: Tuesday, August 20, 2013 2:50 PM To: Steven Nickerson; koha@lists.katipo.co.nz Subject: Re: [Koha] How frequently to run zebra rebuild and what switches
Hello Steven,
Looking for some advice and recommendations. For a fairly small library
running Koha 3.12.00.000 from the Debian squeeze packages, how often should the zebra_rebuild.pl script be executed and with exactly which switches? Right now I run it at 7:30 AM each morning with "-run-as-root -b -r -v"
I am quite surprised you need to do that since you say you installed from Debian packages. All the installations I have done through the Debian packages always have the zebra incremental indexing properly set in cron and it is usually set to run every 5 minutes. You can check your cron settings to make sure that this is properly set and enabled to run regularly.
I don't think you need to run it manually. That is as per my own experience.
Cheers
Olugbenga Adara
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins@cpbibliography.com (web) http://www.cpbibliography.com/
* Steven Nickerson (snicker1@maine.rr.com) wrote:
Thanks for the reply, but I'm 99% sure it was NOT there by default. Can someone tell me what the "default" crontab entry for rebuild_zebra.pl is, and maybe what ALL of the default crontab entries are/should be? Now I'm concerned I'm missing more than just the rebuild_zebra one.
If it wasn't set up by default, im 100% sure you didn't install via the packages. Because the packages put koha-common in /etc/cron.d that does the indexing. The fact you have reindexed as root will have mucked up all sorts of permissions, including breaking this cron job. Chris -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand
Thanks Chris! It turns out I actually do have /etc/cron.d/koha-common and didn't even realize it was there (running as ROOT, as well as /etc/cron.daily/koha-common and /etc/cron.hourly/koha-common). I added the other entry to the ROOT crontab file "manually". If this is the entry in the /etc/cron.d/koha-common file is this all that I need for the zebra rebuild? If a librarian adds a new holding, it should appear in search results within 5 minutes with this cron entry, right? */5 * * * * root test -x /usr/sbin/koha-rebuild-zebra && koha-rebuild-zebra $(koha-list --enabled) As Paul mentioned, there are certain tasks/admin functions that seem to require a complete rebuild and not just an "incremental" one...does the /etc/cron.d/koha-common take care of doing that periodically? Or should I leave my complete zebra rebuild in the ROOT crontab as I have it now, perhaps? THANKS! Steve -----Original Message----- From: Chris Cormack [mailto:chrisc@catalyst.net.nz] Sent: Tuesday, August 20, 2013 3:17 PM To: Steven Nickerson Cc: 'Olugbenga Adara'; koha@lists.katipo.co.nz Subject: Re: [Koha] How frequently to run zebra rebuild and what switches * Steven Nickerson (snicker1@maine.rr.com) wrote:
Thanks for the reply, but I'm 99% sure it was NOT there by default. Can someone tell me what the "default" crontab entry for rebuild_zebra.pl is, and maybe what ALL of the default crontab entries are/should be? Now I'm concerned I'm missing more than just the rebuild_zebra one.
If it wasn't set up by default, im 100% sure you didn't install via the packages. Because the packages put koha-common in /etc/cron.d that does the indexing. The fact you have reindexed as root will have mucked up all sorts of permissions, including breaking this cron job. Chris -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand
* Steven Nickerson (snicker1@maine.rr.com) wrote:
Thanks Chris! It turns out I actually do have /etc/cron.d/koha-common and didn't even realize it was there (running as ROOT, as well as /etc/cron.daily/koha-common and /etc/cron.hourly/koha-common). I added the other entry to the ROOT crontab file "manually". If this is the entry in the /etc/cron.d/koha-common file is this all that I need for the zebra rebuild? If a librarian adds a new holding, it should appear in search results within 5 minutes with this cron entry, right? */5 * * * * root test -x /usr/sbin/koha-rebuild-zebra && koha-rebuild-zebra $(koha-list --enabled)
That is very different to running rebuild_zebra.pl as root. You are running koha-rebuild-zebra as root. Which does sudo -u "$name-koha" -H \ env PERL5LIB=/usr/share/koha/lib \ KOHA_CONF="/etc/koha/sites/$name/koha-conf.xml" \ /usr/share/koha/bin/migration_tools/rebuild_zebra.pl $@ That is, it is running rebuild_zeba.pl as the user who was created when you ran koha-create. You said "Right now I run it at 7:30 AM each morning with "-run-as-root -b -r -v" (yes, I run it as ROOT). " Which means the cron job wont be able to run as it wont have the rights to write to the files it needs to, because root owns them. This is why your things arent changing every 5 minutes Chris
As Paul mentioned, there are certain tasks/admin functions that seem to require a complete rebuild and not just an "incremental" one...does the /etc/cron.d/koha-common take care of doing that periodically? Or should I leave my complete zebra rebuild in the ROOT crontab as I have it now, perhaps?
THANKS! Steve
-----Original Message----- From: Chris Cormack [mailto:chrisc@catalyst.net.nz] Sent: Tuesday, August 20, 2013 3:17 PM To: Steven Nickerson Cc: 'Olugbenga Adara'; koha@lists.katipo.co.nz Subject: Re: [Koha] How frequently to run zebra rebuild and what switches
* Steven Nickerson (snicker1@maine.rr.com) wrote:
Thanks for the reply, but I'm 99% sure it was NOT there by default. Can someone tell me what the "default" crontab entry for rebuild_zebra.pl is, and maybe what ALL of the default crontab entries are/should be? Now I'm concerned I'm missing more than just the rebuild_zebra one.
If it wasn't set up by default, im 100% sure you didn't install via the packages.
Because the packages put koha-common in /etc/cron.d that does the indexing.
The fact you have reindexed as root will have mucked up all sorts of permissions, including breaking this cron job.
Chris
-- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand
-- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand
About crons, maybe this will help: http://wiki.lib.sun.ac.za/index.php/KOHA#Setup_Zebra On 20 August 2013 20:49, Olugbenga Adara <gbengaadara@yahoo.com> wrote:
Hello Steven,
Looking for some advice and recommendations. For a fairly small library
running Koha 3.12.00.000 from the Debian squeeze packages, how often should the zebra_rebuild.pl script be executed and with exactly which switches? Right now I run it at 7:30 AM each morning with "-run-as-root -b -r -v"
I am quite surprised you need to do that since you say you installed from Debian packages. All the installations I have done through the Debian packages always have the zebra incremental indexing properly set in cron and it is usually set to run every 5 minutes. You can check your cron settings to make sure that this is properly set and enabled to run regularly.
I don't think you need to run it manually. That is as per my own experience.
Cheers
Olugbenga Adara
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- *Hilton Gibson* Ubuntu Linux Systems Administrator JS Gericke Library Room 1025D Stellenbosch University Private Bag X5036 Stellenbosch 7599 South Africa Tel: +27 21 808 4100 | Cell: +27 84 646 4758 http://library.sun.ac.za http://za.linkedin.com/in/hiltongibson http://staff.lib.sun.ac.za/~hgibson/docs/cv/cv.html
On 21 August 2013 19:14, Hilton Gibson <hilton.gibson@gmail.com> wrote:
About crons, maybe this will help: http://wiki.lib.sun.ac.za/index.php/KOHA#Setup_Zebra
Only if you are running not using the .deb packages. If you did install with the packages, following that will make a mess Chris
On 20 August 2013 20:49, Olugbenga Adara <gbengaadara@yahoo.com> wrote:
Hello Steven,
Looking for some advice and recommendations. For a fairly small library
running Koha 3.12.00.000 from the Debian squeeze packages, how often should the zebra_rebuild.pl script be executed and with exactly which switches? Right now I run it at 7:30 AM each morning with "-run-as-root -b -r -v"
I am quite surprised you need to do that since you say you installed from Debian packages. All the installations I have done through the Debian packages always have the zebra incremental indexing properly set in cron and it is usually set to run every 5 minutes. You can check your cron settings to make sure that this is properly set and enabled to run regularly.
I don't think you need to run it manually. That is as per my own experience.
Cheers
Olugbenga Adara
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- *Hilton Gibson* Ubuntu Linux Systems Administrator JS Gericke Library Room 1025D Stellenbosch University Private Bag X5036 Stellenbosch 7599 South Africa
Tel: +27 21 808 4100 | Cell: +27 84 646 4758 http://library.sun.ac.za http://za.linkedin.com/in/hiltongibson http://staff.lib.sun.ac.za/~hgibson/docs/cv/cv.html _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Yes. Please see: http://wiki.lib.sun.ac.za/index.php/KOHA#Preparation On 21 August 2013 09:25, Chris Cormack <chris@bigballofwax.co.nz> wrote:
On 21 August 2013 19:14, Hilton Gibson <hilton.gibson@gmail.com> wrote:
About crons, maybe this will help: http://wiki.lib.sun.ac.za/index.php/KOHA#Setup_Zebra
Only if you are running not using the .deb packages. If you did install with the packages, following that will make a mess
Chris
On 20 August 2013 20:49, Olugbenga Adara <gbengaadara@yahoo.com> wrote:
Hello Steven,
Looking for some advice and recommendations. For a fairly small library
running Koha 3.12.00.000 from the Debian squeeze packages, how often should the zebra_rebuild.pl script be executed and with exactly which switches? Right now I run it at 7:30 AM each morning with "-run-as-root -b -r -v"
I am quite surprised you need to do that since you say you installed from Debian packages. All the installations I have done through the Debian packages always have the zebra incremental indexing properly set in cron and it is usually set to run every 5 minutes. You can check your cron settings to make sure that this is properly set and enabled to run regularly.
I don't think you need to run it manually. That is as per my own experience.
Cheers
Olugbenga Adara
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- *Hilton Gibson* Ubuntu Linux Systems Administrator JS Gericke Library Room 1025D Stellenbosch University Private Bag X5036 Stellenbosch 7599 South Africa
Tel: +27 21 808 4100 | Cell: +27 84 646 4758 http://library.sun.ac.za http://za.linkedin.com/in/hiltongibson http://staff.lib.sun.ac.za/~hgibson/docs/cv/cv.html _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- *Hilton Gibson* Ubuntu Linux Systems Administrator JS Gericke Library Room 1025D Stellenbosch University Private Bag X5036 Stellenbosch 7599 South Africa Tel: +27 21 808 4100 | Cell: +27 84 646 4758 http://library.sun.ac.za http://za.linkedin.com/in/hiltongibson http://staff.lib.sun.ac.za/~hgibson/docs/cv/cv.html
Greetings, As of Koha 3.4.x debian packages were available. That's just over 2 years ago. Koha has progressed so much further. Tarballs are not the recommended installation method for debian-based versions of linux (e.g. Ubuntu). Much nicer and more current installation instructions are available here: http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages No matter how boldly or coloured you make the text, people won't read. And this will only cause confusion and problems. Just my unsolicited commentary on the provision of a really bad set of instructions on how to set Koha up. GPML, Mark Tompsett
What if you want to deviate from what the "packages" installation does? In the open source world, it has been my experience that a "tarball" installation is always preferred, since it allows you install anywhere, not just Debian. On 21 August 2013 22:30, Mark Tompsett <mtompset@hotmail.com> wrote:
Greetings,
As of Koha 3.4.x debian packages were available. That's just over 2 years ago. Koha has progressed so much further. Tarballs are not the recommended installation method for debian-based versions of linux (e.g. Ubuntu). Much nicer and more current installation instructions are available here: http://wiki.koha-community.**org/wiki/Koha_on_ubuntu_-_**packages<http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages>
No matter how boldly or coloured you make the text, people won't read. And this will only cause confusion and problems.
Just my unsolicited commentary on the provision of a really bad set of instructions on how to set Koha up.
GPML, Mark Tompsett
-- *Hilton Gibson* Ubuntu Linux Systems Administrator JS Gericke Library Room 1025D Stellenbosch University Private Bag X5036 Stellenbosch 7599 South Africa Tel: +27 21 808 4100 | Cell: +27 84 646 4758 http://library.sun.ac.za http://za.linkedin.com/in/hiltongibson http://staff.lib.sun.ac.za/~hgibson/docs/cv/cv.html
On 22 August 2013 19:04, Hilton Gibson <hilton.gibson@gmail.com> wrote:
What if you want to deviate from what the "packages" installation does? In the open source world, it has been my experience that a "tarball" installation is always preferred, since it allows you install anywhere, not just Debian.
I must have spent the last 20 years in another open source world then. In my experience, using a packaged system for your distro is almost always preferred because it is much much much easier to upgrade. Also you were writing instructions for ubuntu, a debian based distro, which the packages work fine for, and even adding the repository as an apt source. You are of course free to install any way you want, but we are also free to tell people that using the packages is a better idea if you can. Since they configure all the cron jobs, back ups, allow multiple sites on one machine, and many many more things. Chris
On 22 August 2013 09:04, Hilton Gibson <hilton.gibson@gmail.com> wrote:
What if you want to deviate from what the "packages" installation does? In the open source world, it has been my experience that a "tarball" installation is always preferred, since it allows you install anywhere, not just Debian.
"There is more than one way to do it", sure. And documentation is always welcome. But why not put it on the official Koha wiki, where it will receive (at least some degree of) peer review, improvements from the whole community and a lasting home? Having instructions created by individuals littered all over the web quickly leads to stale information, people following wrong or outdated instructions and in the end getting a bad impression of Koha. So maybe you could copy your wiki page over to the official wiki, link to it from your wiki, and we can all collaborate to ensure it has maximum usefullness? Best regards, Magnus Enger libriotech.no PS: The correct name is "Koha", not "KOHA". ;-)
Hi Magnus This depends, do you intend to have an "original tarball" installation wiki page? If so, will there be one for each stable version of Koha and a version for each upgrade? Cheers hg On 22 August 2013 09:42, Magnus Enger <magnus@enger.priv.no> wrote:
On 22 August 2013 09:04, Hilton Gibson <hilton.gibson@gmail.com> wrote:
What if you want to deviate from what the "packages" installation does? In the open source world, it has been my experience that a "tarball" installation is always preferred, since it allows you install anywhere, not just Debian.
"There is more than one way to do it", sure. And documentation is always welcome. But why not put it on the official Koha wiki, where it will receive (at least some degree of) peer review, improvements from the whole community and a lasting home?
Having instructions created by individuals littered all over the web quickly leads to stale information, people following wrong or outdated instructions and in the end getting a bad impression of Koha. So maybe you could copy your wiki page over to the official wiki, link to it from your wiki, and we can all collaborate to ensure it has maximum usefullness?
Best regards, Magnus Enger libriotech.no
PS: The correct name is "Koha", not "KOHA". ;-) _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- *Hilton Gibson* Ubuntu Linux Systems Administrator JS Gericke Library Room 1025D Stellenbosch University Private Bag X5036 Stellenbosch 7599 South Africa Tel: +27 21 808 4100 | Cell: +27 84 646 4758 http://library.sun.ac.za http://za.linkedin.com/in/hiltongibson http://staff.lib.sun.ac.za/~hgibson/docs/cv/cv.html
On 22 August 2013 10:15, Hilton Gibson <hilton.gibson@gmail.com> wrote:
Hi Magnus
This depends, do you intend to have an "original tarball" installation wiki page? If so, will there be one for each stable version of Koha and a version for each upgrade?
All of this depends on who wants to contribute what to the wiki. Personally, I run packages on Debian, so I intend to contribute to the documentation for that. If you want to create and maintain the pages you mention I am sure there is room for it on the official wiki. (The majority of contributors to the wiki might want to add a note of caution to those pages, saying that packages is the preferred mode of intallation though :-) Best regards, Magnus Enger libriotech.no
Greetings, There are tarball instructions on the Wiki for Ubuntu already. However, in an effort to get people to not go backwards, I am not providing the link. http://wiki.koha-community.org/ is where the Koha wiki is. As Chris has pointed out, upgrading is so much easier with packages. This was the biggest selling point for me, because nothing says easy like: $ sudo apt-get update $ sudo apt-get install koha-common -- This will upgrade koha-common, and other related dependencies. This won't work for the dependencies if you've CPAN'd several of the libraries, but that's another lesson which goes to emphasize that installing from source, when you can install from packages, means installing from source indefinitely, which is time consuming! As Magnus has pointed out, littering the internet with stale instructions is bad in general, because it can cause people to get the wrong impression of Koha,when the real problem is poor, unreviewed documentation. Magnus wrote:
PS: The correct name is "Koha", not "KOHA". ;-)
Yes. Koha is a word, not an acronym. This is why KOHA is wrong, unless you are attempting to shout the awesomeness of it. ;) GPML, Mark Tompsett
Yes. Koha is a word, not an acronym. This is why KOHA is wrong, unless you are attempting to shout the awesomeness of it. ;)
Nope - it is just best practice to ensure that users know of the product. By the way - why is there a koha-community and a koha out there. Very confusing. On 22 August 2013 14:58, Mark Tompsett <mtompset@hotmail.com> wrote:
Greetings,
There are tarball instructions on the Wiki for Ubuntu already.
However, in an effort to get people to not go backwards, I am not providing the link. http://wiki.koha-community.**org/ <http://wiki.koha-community.org/> is where the Koha wiki is.
As Chris has pointed out, upgrading is so much easier with packages. This was the biggest selling point for me, because nothing says easy like: $ sudo apt-get update $ sudo apt-get install koha-common -- This will upgrade koha-common, and other related dependencies. This won't work for the dependencies if you've CPAN'd several of the libraries, but that's another lesson which goes to emphasize that installing from source, when you can install from packages, means installing from source indefinitely, which is time consuming!
As Magnus has pointed out, littering the internet with stale instructions is bad in general, because it can cause people to get the wrong impression of Koha,when the real problem is poor, unreviewed documentation.
Magnus wrote:
PS: The correct name is "Koha", not "KOHA". ;-)
Yes. Koha is a word, not an acronym. This is why KOHA is wrong, unless you are attempting to shout the awesomeness of it. ;)
GPML, Mark Tompsett
-- *Hilton Gibson* Ubuntu Linux Systems Administrator JS Gericke Library Room 1025D Stellenbosch University Private Bag X5036 Stellenbosch 7599 South Africa Tel: +27 21 808 4100 | Cell: +27 84 646 4758 http://library.sun.ac.za http://za.linkedin.com/in/hiltongibson http://staff.lib.sun.ac.za/~hgibson/docs/cv/cv.html
Hilton Gibson schrieb am 22.08.2013
Yes. Koha is a word, not an acronym. This is why KOHA is wrong, unless you are attempting to shout the awesomeness of it. ;)
Nope - it is just best practice to ensure that users know of the product.
Wrong, because…
By the way - why is there a koha-community and a koha out there. Very confusing.
…that is part of the problem. There is Koha. Koha is a community product, the official website is koha-community.org. Koha is free and open source software. This is the official mailing list for Koha. And there is a non-free, non-friendly fork of a company called liblime, now owned by PTFS. They were part of the community up to some point and then decided it would be best for them to leave the free software world behind. They took the domain koha.org with them, pretending to do still do "Koha" and at some point also started using "KOHA". They have other names for their products too, but when you speak of KOHA, people that have been around here for some time think of that fork. And they do not think good things about it. I won't go into more detail here. The fork is no community product, there is no support available for it apart from paying that company (as far as I know) and they diverted from Koha years ago. So if you talk about the FOSS community product, please use Koha, not KOHA, because that is the most confusing thing about it. -- Mirko
On Thu, Aug 22, 2013 at 4:04 AM, Hilton Gibson <hilton.gibson@gmail.com> wrote:
What if you want to deviate from what the "packages" installation does? In the open source world, it has been my experience that a "tarball" installation is always preferred, since it allows you install anywhere,
not
just Debian.
I agree with that point of view, but as I expressed before, we (the community) prefer people contributing to an up to date and peer-reviewed community wiki. We even have a wiki page for the same purpose you created your own. But you skip that part of the answers you receive... Preventing several documentation pages has historical reasons, mostly explained by Mark: in a few months instructions will be deprecated and people might reach them and get confused and frustrated. We've been there many times. As some people has replied, you should better contribute to the official wiki [1]. Regarding koha.org vs. koha-community.org there is some literature on the subject [2]. Regards To+ [1] I have to confess my first impression was that your email posting your own wiki was just a SEO trick, but tried to be polite anyway. [2] http://diligentroom.wordpress.com/2011/11/22/the-exemplar-of-stupid-koha-vs-...
From the story of the trademark hijack, I can understand the grievance all my feel at what seems to be my intrusion. I apologise for any erroneous
Hi to all those who have replied and apologies for cross-posting. Please see: http://bit.ly/goodir That documentation is being actively used to install and setup DSpace world wide. The DSpace developers have "official" documentation and there is no animosity about anybody else having documentation as far as I know. In addition, please see: http://www.journals.ac.za for OJS and OCS. Same here, the PKP developers have no objections to this documentation. perceptions created. An old Roman adage goes, divide and conquer, or as Paul Maritz said, Embrace, Extend, Extinguish. These attacks are to be expected in our dysfunctional software world at the moment. Just thinking, would it have been too much trouble to trademark a new name and then carry on as usual? Regards Hilton PS: It normal procedure for me to create docs for things I install and setup. Linux is so stable, that I forget exactly how I did it months later ;-) On 22 August 2013 16:06, Tomas Cohen Arazi <tomascohen@gmail.com> wrote:
On Thu, Aug 22, 2013 at 4:04 AM, Hilton Gibson <hilton.gibson@gmail.com> wrote:
What if you want to deviate from what the "packages" installation does? In the open source world, it has been my experience that a "tarball" installation is always preferred, since it allows you install anywhere,
not
just Debian.
I agree with that point of view, but as I expressed before, we (the community) prefer people contributing to an up to date and peer-reviewed community wiki. We even have a wiki page for the same purpose you created your own. But you skip that part of the answers you receive...
Preventing several documentation pages has historical reasons, mostly explained by Mark: in a few months instructions will be deprecated and people might reach them and get confused and frustrated. We've been there many times. As some people has replied, you should better contribute to the official wiki [1].
Regarding koha.org vs. koha-community.org there is some literature on the subject [2].
Regards To+
[1] I have to confess my first impression was that your email posting your own wiki was just a SEO trick, but tried to be polite anyway. [2] http://diligentroom.wordpress.com/2011/11/22/the-exemplar-of-stupid-koha-vs-...
-- *Hilton Gibson* Ubuntu Linux Systems Administrator JS Gericke Library Room 1025D Stellenbosch University Private Bag X5036 Stellenbosch 7599 South Africa Tel: +27 21 808 4100 | Cell: +27 84 646 4758 http://library.sun.ac.za http://za.linkedin.com/in/hiltongibson http://staff.lib.sun.ac.za/~hgibson/docs/cv/cv.html
On 22/08/13 15:21, Hilton Gibson wrote:
Just thinking, would it have been too much trouble to trademark a new name and then carry on as usual?
This was discussed around http://koha.1045719.n5.nabble.com/Foundation-conversation-td3213032i30.html#... http://koha.1045719.n5.nabble.com/Koha-demo-links-on-koha-org-td3060269.html and will always remain as a last-resort option, but I think there was a strong feeling similar to "why should we give in to terrorists?" among some of the koha community. Personally, I feel it seems utterly inappropriate to abandon this Maori word to trade mark law. It makes as little sense as the recent attempt of "Red Bull" to claim the word "Red" as a trade mark in England and force the Redwell Brewery near me to change their name (I think you'll find the details if you search for "Red Bully" or "#RedBully") which also failed. There's also the simple fact that LibLime only registered the name as a trade mark many years after many other companies had already built it up in commerce, including social enterprises like software.coop and BibLibre, and only one of those had sold their claim to LibLime (which was in turn bought by PTFS). The co-op didn't register the name as a trade mark locally because we get some rights simply from use and we also want to collaborate freely with other GOOD players, which I feel the increasing criminalisation of trade marks hinders. Hope that explains, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op http://koha-community.org supporter, web and library systems developer. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire (including development) at http://www.software.coop/
participants (12)
-
Chris Cormack -
Chris Cormack -
Hilton Gibson -
Jared Camins-Esakov -
Magnus Enger -
Marcel de Rooy -
Mark Tompsett -
Mirko -
MJ Ray -
Olugbenga Adara -
Steven Nickerson -
Tomas Cohen Arazi