It would make sense to list the libraries sponsoring Koha developments on the about page.
Should we add a new tab or list them at the bottom of "Koha team"?
Using the git log (`git log|grep "Sponsored-by"|sort -n | uniq`), I have this list: Alingsås Public Library, Sweden American Numismatic Society Arcadia Public Library Athens County Public Libraries BdP de la Meuse Briar Cliff University Brooklyn Law School Library BULAC - http://www.bulac.fr/ California College of the Arts Camden County Carnegie Stout Library CCSR ( http://www.ccsr.qc.ca ) Central Kansas Library System (CKLS), Plum Creek Library System and Washoe County Library System Cheshire Libraries Corpus Christi Public Libraries Dover FIT Goethe-Institut Halland county library Hochschule für Gesundheit (hsg), Germany Hotchkiss School KEEP SOLUTIONS Kultur i Halland - Regionbibliotek Library of the Józef Piłsudski Institute of America Los Gatos Public Library and Harrison Carmel Public Library North Central Regional Library (NCRL) Northeast Kansas Library System (NEKLS) Oslo Public Library Regionbibliotek Halland / County library of Halland Region Halland Rolling Hills Consolidated Libraries South-East Kansas Library System Sunday TV is boring SWITCH Library Consortium Talking Tech Universidad de El Salvador Universidad Empresarial Siglo 21 Universidad Nacional de Córdoba Université d'Aix-Marseille Université de Lyon 3 Université de Rennes 2 Université de St Etienne University of the Arts London Vaara-kirjastot Vanier college Ville de Victoriaville, QC VOKAL Washoe County Library System Duplicate and support companies have been removed manually. We could also split the list by release (and so a library could appear several times)?
I think adding a new tab would make sense. I think doing the list by release would get cumbersome, so my vote is for a simple alphabetical list.
Simple list, all time library sponsors/contributors.
(In reply to Owen Leonard from comment #3) > I think adding a new tab would make sense. I think doing the list by release > would get cumbersome, so my vote is for a simple alphabetical list. +1
+1
I would love to get rid of the single big list, and have per-release pages. I imagine a slider to jump from current, to previous release teams and contributors. I wanted that for 3.22 but didn't manage to do it in time.
I wonder how this relates to bug 21317. In that bug we cleared up the formatting a little.. perhaps this bug is more about updating the list to get it current?
Created attachment 80945 [details] [review] Bug 20720: Using git Sponsored-by lines to update 'about'
Created attachment 80946 [details] [review] Bug 20720: Using git Sponsored-by lines to update 'about'
Very minor: after Los Gatos Public Library (love the name btw), there is a bullet with nothing.
Created attachment 80950 [details] [review] Bug 20720: Using git Sponsored-by lines to update 'about'
Ooops, corrected now, thanks.
Created attachment 80951 [details] [review] Bug 20720: Using git Sponsored-by lines to update 'about' Signed-off-by: Caroline Cyr La Rose <caroline.cyr-la-rose@inlibro.com>
Created attachment 80952 [details] [review] Bug 20720: Using git Sponsored-by lines to update 'about' Signed-off-by: Michal Denar <black23@gmail.com>
Created attachment 80961 [details] [review] Bug 20720: Found some more sponsors to add to 'about' git log|grep -i "sponsored-by"|sort -n | uniq git log|grep -i "sponsored by"|sort -n | uniq
Found a few more so added a followup.
Created attachment 80962 [details] [review] Bug 20720: Using git Sponsored-by lines to update 'about' Signed-off-by: Michal Denar <black23@gmail.com>
Created attachment 80963 [details] [review] Bug 20720: Found some more sponsors to add to 'about' git log|grep -i "sponsored-by"|sort -n | uniq git log|grep -i "sponsored by"|sort -n | uniq Signed-off-by: Michal Denar <black23@gmail.com> Signed-off-by: Michal Denar <black23@gmail.com>
Should not we split by Koha version? And add the number of enhancements they sponsored?
(In reply to Jonathan Druart from comment #20) > Should not we split by Koha version? Oops sorry, this has been discussed already!
As it happens, I'm keen to automate this as part of the release process and then add enhancements on top of that automation. My initial plan is to convert the process from 'add lines to the template directly' to 'build a developers.yaml and sponsors.yaml' as release time and use in the template instead. This was just intended as a quick 'get us up to date' patch whilst I work on a more joined up procedure.
Created attachment 81391 [details] [review] Bug 20720: Using git Sponsored-by lines to update 'about' Signed-off-by: Michal Denar <black23@gmail.com> Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de>
Created attachment 81392 [details] [review] Bug 20720: Found some more sponsors to add to 'about' git log|grep -i "sponsored-by"|sort -n | uniq git log|grep -i "sponsored by"|sort -n | uniq Signed-off-by: Michal Denar <black23@gmail.com> Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de>
Created attachment 81393 [details] [review] Bug 20720: (QA follow-up) Some minor corrections Made some corrections to countries, spelling and changed OPUS entry.
About OPUS: I changed it back to be only the abbreviation as the full name was not the correct one. The one that was listed refers to a digital repository software that is developed and widely used in Germany. It shows up a lot in combination with Koha in searches, as a lot of presentations, thesis and other publications on Koha are published in OPUS based systems.
I think this might be a good candidate - Chris C. might be able to confirm: http://katipo.co.nz/portfolio/libraries/54-opus.html
*** Bug 20610 has been marked as a duplicate of this bug. ***
Thanks for the fixes Katrin [U+1F601]
Awesome work all! Pushed to master for 18.11
I chose to backport this to give contributing institution their dues. Pushed to 18.05.x for 18.05.06
Pushed to 17.11.x for 17.11.13 Viva our sponsors :D