interesting Helios/FBO news

[Casey]

Currently Borders UK has a partnership with Amazon to do their online
web-presence. They decided they wanted to strike out on their own, so
they recently had a bunch of web development shops submit demos for
the project. I just found out the winning one was based upon Helios/
FacBackOPAC. The new site is supposed to debut Spring 2008. Today, a
couple of libraries, tomorrow, the world!

[Gabriel Farrell]

Wow, that's awesome! Who's the development shop?

[Dan Chudnov]

On Nov 28, 2007, at 4:50 PM, Casey wrote:
>
> I just found out the winning one was based upon Helios/
> FacBackOPAC. The new site is supposed to debut Spring 2008. Today, a
> couple of libraries, tomorrow, the world!

That is exciting! I hope we can hear more about this soon, too.

Btw, since this codebase seems to be gaining more attention, it'd be
good to cross 't's and dot 'i's w/r/to licensing. The fbo gcode site
says it's available under the Apache 2.0 license, both in prose and
under the "License" metadata in the corner. The code itself doesn't
seem to have a LICENSE file or any kind of copyright statement, though.

This is something that shouldn't be overlooked. If the goal is to
have a clear copyright statement and license file as part of the
source code, whose copyright should it indicate?

-Dan

[Dan Scott]

Quite right, Dan, and that was pure laziness on my part.

At a minimum, all of the non-Jython files should contain copyright
statements for Casey for 2007, as well as the Apache 2 license header
that points to the LICENSE file.

We can also add copyright statements for Mike and myself to some of
the files - as well as Gabe and Dan, as the commits roll in. Or we can
maintain an AUTHORS file instead.

--
Dan Scott
Laurentian University

[Gabriel Farrell]

On Nov 28, 11:58 pm, "Dan Scott" <deni...@gmail.com> wrote:
>
> At a minimum, all of the non-Jython files should contain copyright
> statements for Casey for 2007, as well as the Apache 2 license header
> that points to the LICENSE file.
>
> We can also add copyright statements for Mike and myself to some of
> the files - as well as Gabe and Dan, as the commits roll in. Or we can
> maintain an AUTHORS file instead.
>

I'd prefer an AUTHORS file, rather than worry about whose code is
which. But seeing as the bulk of it is still Casey's work, I guess
it's mostly his decision at this point.

gsf

[Casey]

It's an outfit called Tangent Labs:

http://www.tangentlabs.co.uk/