This project was initiated by Richard Wallis (formerly of Talis, now
with OCLC).  I'm not sure what happened to stewardship after we
(Talis) sold the library division to Capita.  I think (but I'm not
100% sure) that Capita's Prism 3 uses Juice for extensions (at least,
that had been the plan - this article from Aspire's support pages
seems to confirm it:
http://support.talisaspire.com/entries/20118736-item-linking-api-specification).

My guess is that Capita now maintains this project, you might want to
ping Phil John (philjohn - at - capita.co.uk,
https://twitter.com/_philjohn) or Matt Machell (who, according to
Google is on this list).  Nobody currently at Talis is, to my
knowledge.

-Ross.
p.s. Jangle (another Talis-bootstrapped project) is sort of trapped in
a similar state - I'm still happy to help anybody that wants to use
it, but due to a series of unfortunate mishaps, the website fell into
a black hole, as well as the main Google Code repo (that, at least, is
on Github now - I still need to try to retrieve the website content).

On Wed, Jul 18, 2012 at 7:39 AM, Tim Spalding <[log in to unmask]> wrote:
> Does anyone keep up on the "Juice Project"? ( http://juice-project.org ).
> It's sort of an open-source framework for adding extensions to library
> OPACs, similar to what the framework behind LibraryThing for Libraries or
> Syndetics' ICE does, but open source. The UK ILS vendor Talis pushed it.
>
> I watched it and to some extent promoted it when it first came out, but I
> haven't followed it since. The site and community list looks quiescent, but
> I'm not sure. Does anyone know about it—how its doing, how many libraries
> are using it, whether any OPACs have it built in, etc.?
>
> Tim
>
> --
> Check out my library at http://www.librarything.com/profile/timspalding