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
Greetings, What if 3.18 was 4.0 (or 5.0)? At some point we need to increment the major number, and the full drop of prog/CCSR and defaulting of Bootstrap seems like a good enough reason. GPML, Mark Tompsett
Hi, On Mon, Oct 28, 2013 at 10:41 AM, Mark Tompsett <mtompset@hotmail.com>wrote:
What if 3.18 was 4.0 (or 5.0)? At some point we need to increment the major number, and the full drop of prog/CCSR and defaulting of Bootstrap seems like a good enough reason.
What the version happens to be called does not affect the substance of the proposal. For 3.16, you can read it as "the next major release after 3.14"; for 3.18, you can read it as "the second major release after 3.14". The wording for any public announcements can be made suitably vague as to what the version number or monikers will be. At this point I am going to be dictatorial and assert that what the versions are called is off-topic for this particular email thread. If a discussion of version numbering is warranted, it should go in a separate thread. 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
On 29/10/2013 6:47 AM, "Galen Charlton" <gmc@esilibrary.com> wrote:
Hi,
On Mon, Oct 28, 2013 at 10:41 AM, Mark Tompsett <mtompset@hotmail.com>
What if 3.18 was 4.0 (or 5.0)? At some point we need to increment the
major number, and the full drop of prog/CCSR and defaulting of Bootstrap seems like a good enough reason.
What the version happens to be called does not affect the substance of
wrote: the proposal. For 3.16, you can read it as "the next major release after 3.14"; for 3.18, you can read it as "the second major release after 3.14". The wording for any public announcements can be made suitably vague as to what the version number or monikers will be.
At this point I am going to be dictatorial and assert that what the
versions are called is off-topic for this particular email thread. If a discussion of version numbering is warranted, it should go in a separate thread.
+1 Also blue. Chris
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/
On 28 October 2013 10:32, Galen Charlton <gmc@esilibrary.com> wrote:
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.
Ooops in the midst of being derailed by a version numbering question, I missed actually adding my support for the proposal So +1 for this scheme from me Chris
Am 28.10.2013 19:06, schrieb Chris Cormack:
On 28 October 2013 10:32, Galen Charlton <gmc@esilibrary.com> wrote:
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.
Ooops in the midst of being derailed by a version numbering question, I missed actually adding my support for the proposal So +1 for this scheme from me
Chris
+1 from me too Katrin
+1 from me on the timeline.
[4] The RM will assist in getting OPAC template patches in the pipeline that were written for prog updated to support Bootstrap as well.
I'm happy to help too. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org
+1 on the strategy. On Mon, Oct 28, 2013 at 11:34 AM, Owen Leonard <oleonard@myacpl.org> wrote:
+1 from me on the timeline.
[4] The RM will assist in getting OPAC template patches in the pipeline that were written for prog updated to support Bootstrap as well.
I'm happy to help too.
-- Owen
-- Web Developer Athens County Public Libraries http://www.myacpl.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 28 Oct 2013 20:26, "Doug Kingston" <dpk@randomnotes.org> wrote:
+1 on the strategy.
On Mon, Oct 28, 2013 at 11:34 AM, Owen Leonard <oleonard@myacpl.org>wrote:
+1 from me on the timeline.
[4] The RM will assist in getting OPAC template patches in the pipeline that were written for prog updated to support Bootstrap as well.
I'm happy to help too.
-- Owen
-- Web Developer Athens County Public Libraries http://www.myacpl.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/
participants (7)
-
Chris Cormack -
Doug Kingston -
Galen Charlton -
Katrin Fischer -
Mark Tompsett -
Martin Renvoize -
Owen Leonard