On Tue, Jan 21, 2014 at 10:37 AM, Liam Whalen
liam.wha...@bc.libraries.coop wrote:
I do not know if there is a ticket open yet. If there is not a ticket then
open one, and I will add what I know.
Thanks Liam; I don't see an open ticket for this, but we can always
mark a bug as duplicate later
I've forwarded comments from Dan Wells on bug # 1261939 around merging a
new feature; and instead of responding in the bug (which is now closed),
I've put my thoughts below that. There's a mix of discussion around whether
new features should be on by default, as well as design how navigation in
Hello all,
Thanks, Dan, for bringing this to the list. It is a better place to have the
discussion, I think. I don’t have a lot to add beyond the original post, but
do wish to clarify a couple of my views.
As far as I know slam dunk criteria has never been formally applied to any
previous
Hi,
On Wed, Jan 22, 2014 at 8:41 AM, Dan Scott d...@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,
I am going to send four emails about my thoughts on the staff client. I have
not had time to investigate the prototype code very much yet, but I think some
of the issues I am thinking about are things that should be considered before
full development is begun regardless of the technical
Have we consulted with the libraries about what their needs are?
This is a large project that has direct impact on library staff. It would be
good to get a basic needs assessment from community libraries, so we can be
sure we are targeting our code at machines and software that will be able to
Network performance is a very important issue for Sitka. We have a number of
remote libraries with high latency Internet connections. The more we can
reduce information sent between the server and clients the better the staff
experience will be in these libraries.
I think WebSockets will
Google has a website and video that talk about best practices to be used when
developing AngularJS apps. It would be a good idea to adhere to these as much
as possible because it will ensure the new staff client can use updated
versions of the AngularJS framework with minimal to no
