Re: [Koha-devel] OPAC theme proposal
+1 Six month seems enough for adjusting the css anyway. El 28/10/2013 14:32, "Galen Charlton" <gmc@esilibrary.com> escribió:
Hi,
Based on the feedback received last week, here is my current proposal for
managing the OPAC themes:
[1] We ship Bootstrap as the default theme for 3.14 for new installations. [2] We announce deprecation of prog and CCSR when 3.14 is released and
[3] At the same time, we announce that prog and CCSR will be removed in 3.18. If some organization wishes to maintain either theme after then,
[4] The RM will assist in getting OPAC template patches in the pipeline
issue a recommendation that libraries start switching to Bootstrap. they can do so, but as a separate contrib. However, if you are inclined to support either theme after they've been removed ... please think carefully about the amount of work that would entail. that were written for prog updated to support Bootstrap as well.
[5] Starting with the 3.16, new OPAC patches should be targeted for Bootstrap first. During the 3.16 cycle, contributors are requested to make an effort to update the prog theme as well, particularly for new features, but this is a request, not a requirement. In other words, this means that for 3.16, libraries may need to switch to Bootstrap to take full advantage of new OPAC functionality, but the prog theme will continue to be functional. [6] During the 3.18 cycle, no patches will be pushed for prog except insofar as they may be needed to fix security issues in the maintenance releases. Before 3.18 is released, prog and CCSR will be taken out entirely.
Regards,
Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
_______________________________________________ Koha-devel mailing list Koha-devel@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/
+1 On Mon, Oct 28, 2013 at 6:17 PM, Tomas Cohen Arazi <tomascohen@gmail.com>wrote:
+1
Six month seems enough for adjusting the css anyway.
El 28/10/2013 14:32, "Galen Charlton" <gmc@esilibrary.com> escribió:
Hi,
Based on the feedback received last week, here is my current proposal
for managing the OPAC themes:
[1] We ship Bootstrap as the default theme for 3.14 for new
[2] We announce deprecation of prog and CCSR when 3.14 is released and issue a recommendation that libraries start switching to Bootstrap. [3] At the same time, we announce that prog and CCSR will be removed in 3.18. If some organization wishes to maintain either theme after then,
[4] The RM will assist in getting OPAC template patches in the pipeline
installations. they can do so, but as a separate contrib. However, if you are inclined to support either theme after they've been removed ... please think carefully about the amount of work that would entail. that were written for prog updated to support Bootstrap as well.
[5] Starting with the 3.16, new OPAC patches should be targeted for Bootstrap first. During the 3.16 cycle, contributors are requested to make an effort to update the prog theme as well, particularly for new features, but this is a request, not a requirement. In other words, this means that for 3.16, libraries may need to switch to Bootstrap to take full advantage of new OPAC functionality, but the prog theme will continue to be functional. [6] During the 3.18 cycle, no patches will be pushed for prog except insofar as they may be needed to fix security issues in the maintenance releases. Before 3.18 is released, prog and CCSR will be taken out entirely.
Regards,
Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
_______________________________________________ Koha-devel mailing list Koha-devel@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/
_______________________________________________ Koha-devel mailing list Koha-devel@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/
+1 On Mon, Oct 28, 2013 at 8:58 PM, Nicole Engard <nengard@gmail.com> wrote:
+1
On Mon, Oct 28, 2013 at 6:17 PM, Tomas Cohen Arazi <tomascohen@gmail.com>wrote:
+1
Six month seems enough for adjusting the css anyway.
El 28/10/2013 14:32, "Galen Charlton" <gmc@esilibrary.com> escribió:
Hi,
Based on the feedback received last week, here is my current proposal
for managing the OPAC themes:
[1] We ship Bootstrap as the default theme for 3.14 for new
[2] We announce deprecation of prog and CCSR when 3.14 is released and issue a recommendation that libraries start switching to Bootstrap. [3] At the same time, we announce that prog and CCSR will be removed in 3.18. If some organization wishes to maintain either theme after then,
[4] The RM will assist in getting OPAC template patches in the pipeline
installations. they can do so, but as a separate contrib. However, if you are inclined to support either theme after they've been removed ... please think carefully about the amount of work that would entail. that were written for prog updated to support Bootstrap as well.
[5] Starting with the 3.16, new OPAC patches should be targeted for Bootstrap first. During the 3.16 cycle, contributors are requested to make an effort to update the prog theme as well, particularly for new features, but this is a request, not a requirement. In other words, this means that for 3.16, libraries may need to switch to Bootstrap to take full advantage of new OPAC functionality, but the prog theme will continue to be functional. [6] During the 3.18 cycle, no patches will be pushed for prog except insofar as they may be needed to fix security issues in the maintenance releases. Before 3.18 is released, prog and CCSR will be taken out entirely.
Regards,
Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
_______________________________________________ Koha-devel mailing list Koha-devel@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/
_______________________________________________ Koha-devel mailing list Koha-devel@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/
_______________________________________________ Koha-devel mailing list Koha-devel@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/
-- Joy Nelson Director of Migrations ByWater Solutions <http://bywatersolutions.com> Support and Consulting for Open Source Software **Office: Fort Worth, TX Phone/Fax (888)900-8944 What is Koha? <http://bywatersolutions.com/what-is-koha/>
+1 http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) Mill Run Technology Solutions ( http://millruntech.com ) On Tue, Oct 29, 2013 at 10:18 AM, Joy Nelson <joy@bywatersolutions.com>wrote:
+1
On Mon, Oct 28, 2013 at 8:58 PM, Nicole Engard <nengard@gmail.com> wrote:
+1
On Mon, Oct 28, 2013 at 6:17 PM, Tomas Cohen Arazi <tomascohen@gmail.com>wrote:
+1
Six month seems enough for adjusting the css anyway.
El 28/10/2013 14:32, "Galen Charlton" <gmc@esilibrary.com> escribió:
Hi,
Based on the feedback received last week, here is my current proposal
for managing the OPAC themes:
[1] We ship Bootstrap as the default theme for 3.14 for new
[2] We announce deprecation of prog and CCSR when 3.14 is released and issue a recommendation that libraries start switching to Bootstrap. [3] At the same time, we announce that prog and CCSR will be removed in 3.18. If some organization wishes to maintain either theme after then,
[4] The RM will assist in getting OPAC template patches in the
installations. they can do so, but as a separate contrib. However, if you are inclined to support either theme after they've been removed ... please think carefully about the amount of work that would entail. pipeline that were written for prog updated to support Bootstrap as well.
[5] Starting with the 3.16, new OPAC patches should be targeted for Bootstrap first. During the 3.16 cycle, contributors are requested to make an effort to update the prog theme as well, particularly for new features, but this is a request, not a requirement. In other words, this means that for 3.16, libraries may need to switch to Bootstrap to take full advantage of new OPAC functionality, but the prog theme will continue to be functional. [6] During the 3.18 cycle, no patches will be pushed for prog except insofar as they may be needed to fix security issues in the maintenance releases. Before 3.18 is released, prog and CCSR will be taken out entirely.
Regards,
Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
_______________________________________________ Koha-devel mailing list Koha-devel@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/
_______________________________________________ Koha-devel mailing list Koha-devel@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/
_______________________________________________ Koha-devel mailing list Koha-devel@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/
-- Joy Nelson Director of Migrations
ByWater Solutions <http://bywatersolutions.com> Support and Consulting for Open Source Software **Office: Fort Worth, TX Phone/Fax (888)900-8944 What is Koha? <http://bywatersolutions.com/what-is-koha/>
_______________________________________________ Koha-devel mailing list Koha-devel@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/
+1 On Tue, Oct 29, 2013 at 2:50 PM, Kyle Hall <kyle.m.hall@gmail.com> wrote:
+1
http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) Mill Run Technology Solutions ( http://millruntech.com )
On Tue, Oct 29, 2013 at 10:18 AM, Joy Nelson <joy@bywatersolutions.com>wrote:
+1
On Mon, Oct 28, 2013 at 8:58 PM, Nicole Engard <nengard@gmail.com> wrote:
+1
On Mon, Oct 28, 2013 at 6:17 PM, Tomas Cohen Arazi <tomascohen@gmail.com
wrote:
+1
Six month seems enough for adjusting the css anyway.
El 28/10/2013 14:32, "Galen Charlton" <gmc@esilibrary.com> escribió:
Hi,
Based on the feedback received last week, here is my current proposal
for managing the OPAC themes:
[1] We ship Bootstrap as the default theme for 3.14 for new
[2] We announce deprecation of prog and CCSR when 3.14 is released and issue a recommendation that libraries start switching to Bootstrap. [3] At the same time, we announce that prog and CCSR will be removed in 3.18. If some organization wishes to maintain either theme after then,
[4] The RM will assist in getting OPAC template patches in the
installations. they can do so, but as a separate contrib. However, if you are inclined to support either theme after they've been removed ... please think carefully about the amount of work that would entail. pipeline that were written for prog updated to support Bootstrap as well.
[5] Starting with the 3.16, new OPAC patches should be targeted for Bootstrap first. During the 3.16 cycle, contributors are requested to make an effort to update the prog theme as well, particularly for new features, but this is a request, not a requirement. In other words, this means that for 3.16, libraries may need to switch to Bootstrap to take full advantage of new OPAC functionality, but the prog theme will continue to be functional. [6] During the 3.18 cycle, no patches will be pushed for prog except insofar as they may be needed to fix security issues in the maintenance releases. Before 3.18 is released, prog and CCSR will be taken out entirely.
Regards,
Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
_______________________________________________ Koha-devel mailing list Koha-devel@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/
_______________________________________________ Koha-devel mailing list Koha-devel@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/
_______________________________________________ Koha-devel mailing list Koha-devel@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/
-- Joy Nelson Director of Migrations
ByWater Solutions <http://bywatersolutions.com> Support and Consulting for Open Source Software **Office: Fort Worth, TX Phone/Fax (888)900-8944 What is Koha? <http://bywatersolutions.com/what-is-koha/>
_______________________________________________ Koha-devel mailing list Koha-devel@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/
_______________________________________________ Koha-devel mailing list Koha-devel@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/
+1 from me as well. Thanks for the coherent proposal, Galen. Liz On 30/10/13 07:53, Christopher Nighswonger wrote:
+1
On Tue, Oct 29, 2013 at 2:50 PM, Kyle Hall <kyle.m.hall@gmail.com> wrote:
+1
http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) Mill Run Technology Solutions ( http://millruntech.com )
On Tue, Oct 29, 2013 at 10:18 AM, Joy Nelson <joy@bywatersolutions.com>wrote:
+1
On Mon, Oct 28, 2013 at 8:58 PM, Nicole Engard <nengard@gmail.com> wrote:
+1
On Mon, Oct 28, 2013 at 6:17 PM, Tomas Cohen Arazi <tomascohen@gmail.com
wrote: +1
Six month seems enough for adjusting the css anyway.
El 28/10/2013 14:32, "Galen Charlton" <gmc@esilibrary.com> escribió:
Hi,
Based on the feedback received last week, here is my current proposal for managing the OPAC themes: [1] We ship Bootstrap as the default theme for 3.14 for new installations. [2] We announce deprecation of prog and CCSR when 3.14 is released and issue a recommendation that libraries start switching to Bootstrap. [3] At the same time, we announce that prog and CCSR will be removed in 3.18. If some organization wishes to maintain either theme after then, they can do so, but as a separate contrib. However, if you are inclined to support either theme after they've been removed ... please think carefully about the amount of work that would entail. [4] The RM will assist in getting OPAC template patches in the pipeline that were written for prog updated to support Bootstrap as well. [5] Starting with the 3.16, new OPAC patches should be targeted for Bootstrap first. During the 3.16 cycle, contributors are requested to make an effort to update the prog theme as well, particularly for new features, but this is a request, not a requirement. In other words, this means that for 3.16, libraries may need to switch to Bootstrap to take full advantage of new OPAC functionality, but the prog theme will continue to be functional. [6] During the 3.18 cycle, no patches will be pushed for prog except insofar as they may be needed to fix security issues in the maintenance releases. Before 3.18 is released, prog and CCSR will be taken out entirely. Regards,
Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org _______________________________________________ Koha-devel mailing list Koha-devel@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/
_______________________________________________ Koha-devel mailing list Koha-devel@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/
_______________________________________________ Koha-devel mailing list Koha-devel@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/
-- Joy Nelson Director of Migrations
ByWater Solutions <http://bywatersolutions.com> Support and Consulting for Open Source Software **Office: Fort Worth, TX Phone/Fax (888)900-8944 What is Koha? <http://bywatersolutions.com/what-is-koha/>
_______________________________________________ Koha-devel mailing list Koha-devel@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/
_______________________________________________ Koha-devel mailing list Koha-devel@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/
_______________________________________________ Koha-devel mailing list Koha-devel@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/
+1
Six month seems enough for adjusting the css anyway. +1 for this proposal. I would also add : if someone can't adjust it's css, the 3.14 will be
Le 28/10/2013 23:17, Tomas Cohen Arazi a écrit : maintained for at least 6 months, probably one year, maybe more. So anyone can stay on 3.14 if needed. -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Drupal, Piwik, Jasper
Hi, On Wed, Oct 30, 2013 at 12:43 AM, Paul Poulain <paul.poulain@biblibre.com>wrote:
+1
Six month seems enough for adjusting the css anyway. +1 for this proposal. I would also add : if someone can't adjust it's css, the 3.14 will be
Le 28/10/2013 23:17, Tomas Cohen Arazi a écrit : maintained for at least 6 months, probably one year, maybe more. So anyone can stay on 3.14 if needed.
Thanks for the feedback, everybody. I have now pushed a patch to master making Bootstrap the default OPAC theme for new installs. Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
participants (8)
-
Christopher Nighswonger -
Galen Charlton -
Joy Nelson -
Kyle Hall -
Liz Rea -
Nicole Engard -
Paul Poulain -
Tomas Cohen Arazi