[OPEN-ILS-DEV] Features and defaults and navigation (was: [Bug 1261939] Re: Add per-library TPAC pages with schema.org structured data support)

[Galen Charlton]

Hi,

On Wed, Jan 22, 2014 at 8:41 AM, Dan Scott <dan at coffeecode.net> wrote:
> As far as I know "slam dunk" criteria has never been formally applied to any
> previous changesets. Perhaps we should formalize how we make such decisions
> and apply it consistently for _all_ new features, otherwise conflict, hurt
> feelings, and wasted time may result.

Speaking in general terms, I would suggest some rules of thumb,
keeping in mind that there can always be exceptions.  It's important
to distinguish between default settings for new installations versus
default values new settings introduced by upgrades.

For new installations, I think the preference should be to enable a
new feature out of the box, unless it clearly serves only a niche need
or would require additional configuration to work at all.

For upgrades, I think we should optimize for minimizing both surprises
and the amount of mandatory configuration work that a library has to
do post-upgrade.  In other words, a library should be able to follow
the upgrade instructions and end up with a system that works much the
same, just with fewer bugs and more buttons to push.

I see your point about release notes -- it can be hard to sell a
useful feature that way -- so I think we can still have a preference
for enabling new features by default during upgrade, provided that
they don't change circulation policy or other patron-affecting
features in ways that are likely to lead to revolt.

However, I think the bar should be set pretty high for changing values
of existing settings during upgrade.  Sure, the new default may be
better, but unless a security vulnerability or the like is involved,
being too quick to change existing settings is akin to saying that
policy and configuration decisions made by the library take second
place to what the developers push out.

Regards,

Galen
-- 
Galen Charlton
Manager of Implementation
Equinox Software, Inc. / The Open Source Experts
email:  gmc at 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