I'm working with the University of Oxford on a project to enhance
resource lists they present in their learning environment - Sakai. We
have proposed using Juice to add various enhancements to the lists,
and if we did this, we would of course be contributing back the
metadefs/extensions we develop.
Our ideal outcome in Sakai would be to be able to distribute the Juice
code as part of the Sakai distribution. However, the licensing of
Juice as GPL is slightly problematic - so, the question is whether
there is any chance of dual licensing Juice under GPL and another (non-
viral) licensing regime. For example JQuery itself is licensed under
GPL and MIT License.
I'm working with the University of Oxford on a project to enhance
resource lists they present in their learning environment - Sakai. We
have proposed using Juice to add various enhancements to the lists,
and if we did this, we would of course be contributing back the
metadefs/extensions we develop.
Our ideal outcome in Sakai would be to be able to distribute the Juice
code as part of the Sakai distribution. However, the licensing of
Juice as GPL is slightly problematic - so, the question is whether
there is any chance of dual licensing Juice under GPL and another (non-
viral) licensing regime. For example JQuery itself is licensed under
GPL and MIT License.
As long as it is OS and attributable to those that produced it, I am fairly ambivalent about which actual licences we use.
What you suggest sounds fine, especially as that approach seems to be OK for JQuery.
What do others think.
It would be good if we could get to a version 1.0, with a few desirable tweaks, fixes and finished off new extensions in it, before others such as Saki started distributing it.
Regards, Richard.
On 4 Aug 2010, at 09:53, Owen wrote:
I'm working with the University of Oxford on a project to enhance resource lists they present in their learning environment - Sakai. We have proposed using Juice to add various enhancements to the lists, and if we did this, we would of course be contributing back the metadefs/extensions we develop.
Our ideal outcome in Sakai would be to be able to distribute the Juice code as part of the Sakai distribution. However, the licensing of Juice as GPL is slightly problematic - so, the question is whether there is any chance of dual licensing Juice under GPL and another (non- viral) licensing regime. For example JQuery itself is licensed under GPL and MIT License.
Is there any possibility of doing this?
Thanks,
Owen
-- You received this message because you are subscribed to the Google Groups "juice-project-discuss" group. To post to this group, send email to juice-project-discuss@googlegroups.com<mailto:juice-project-discuss@googleg roups.com>. To unsubscribe from this group, send email to juice-project-discuss+unsubscribe@googlegroups.com<mailto:juice-project-dis cuss+unsubscribe@googlegroups.com>. For more options, visit this group at http://groups.google.com/group/juice-project-discuss?hl=en.
Any views or personal opinions expressed within this email may not be those of Talis Information Ltd or its employees. The content of this email message and any files that may be attached are confidential, and for the usage of the intended recipient only. If you are not the intended recipient, then please return this message to the sender and delete it. Any use of this e-mail by an unauthorised recipient is prohibited.
Talis Information Ltd is a member of the Talis Group of companies and is registered in England No 3638278 with its registered office at Knights Court, Solihull Parkway, Birmingham Business Park, B37 7YB.
From some very casual research, the two licenses are compatible, so it
shouldn't prove a problem from that angle.
I do agree with Richard that it would be nice to finish off some of
the polish before bundling it with another product.
I've got a branch where I'm working on some optimisations,
accessibility enhancements and a move towards being a jQuery plugin.
It would probably be worth getting those in trunk before bundling.
Speaking of which, if anybody wants to take a look at the work so far
it's in: branches/20100702-mm-jqplugin
> As long as it is OS and attributable to those that produced it, I am fairly ambivalent about which actual licences we use.
> What you suggest sounds fine, especially as that approach seems to be OK for JQuery.
> What do others think.
> It would be good if we could get to a version 1.0, with a few desirable tweaks, fixes and finished off new extensions in it, before others such as Saki started distributing it.
> Regards,
> Richard.
> On 4 Aug 2010, at 09:53, Owen wrote:
> I'm working with the University of Oxford on a project to enhance
> resource lists they present in their learning environment - Sakai. We
> have proposed using Juice to add various enhancements to the lists,
> and if we did this, we would of course be contributing back the
> metadefs/extensions we develop.
> Our ideal outcome in Sakai would be to be able to distribute the Juice
> code as part of the Sakai distribution. However, the licensing of
> Juice as GPL is slightly problematic - so, the question is whether
> there is any chance of dual licensing Juice under GPL and another (non-
> viral) licensing regime. For example JQuery itself is licensed under
> GPL and MIT License.
> Is there any possibility of doing this?
> Thanks,
> Owen
> --
> You received this message because you are subscribed to the Google Groups "juice-project-discuss" group.
> To post to this group, send email to juice-project-discuss@googlegroups.com<mailto:juice-project-discuss@googleg roups.com>.
> To unsubscribe from this group, send email to juice-project-discuss+unsubscribe@googlegroups.com<mailto:juice-project-dis cuss+unsubscribe@googlegroups.com>.
> For more options, visit this group athttp://groups.google.com/group/juice-project-discuss?hl=en.
> Any views or personal opinions expressed within this email may not be those of Talis Information Ltd or its employees. The content of this email message and any files that may be attached are confidential, and for the usage of the intended recipient only. If you are not the intended recipient, then please return this message to the sender and delete it. Any use of this e-mail by an unauthorised recipient is prohibited.
> Talis Information Ltd is a member of the Talis Group of companies and is registered in England No 3638278 with its registered office at Knights Court, Solihull Parkway, Birmingham Business Park, B37 7YB.
I'm not an expert on licensing, but I'm assuming that since JQuery is
licensed under MIT and GPL, they are compatible, and it would make
sense to adopt the same model for Juice, as it means it can't end up
in conflict with JQuery?
The latest developments sound good - any idea on timescale - our
project runs until the end of the year, but I'm expecting to be
working on the bits that use Juice in October/November (the project is
called 'Sir Louie' http://blogs.oucs.ox.ac.uk/sirlouie - I'll post a
summary in another thread highlighting how we intend to use Juice)
Owen
On Aug 4, 11:46 am, Matt Machell <mattmach...@googlemail.com> wrote:
> From some very casual research, the two licenses are compatible, so it
> shouldn't prove a problem from that angle.
> I do agree with Richard that it would be nice to finish off some of
> the polish before bundling it with another product.
> I've got a branch where I'm working on some optimisations,
> accessibility enhancements and a move towards being a jQuery plugin.
> It would probably be worth getting those in trunk before bundling.
> Speaking of which, if anybody wants to take a look at the work so far
> it's in: branches/20100702-mm-jqplugin
> On Aug 4, 10:14 am, Richard Wallis <Richard.Wal...@talis.com> wrote:
> > Hi Owen,
> > As long as it is OS and attributable to those that produced it, I am fairly ambivalent about which actual licences we use.
> > What you suggest sounds fine, especially as that approach seems to be OK for JQuery.
> > What do others think.
> > It would be good if we could get to a version 1.0, with a few desirable tweaks, fixes and finished off new extensions in it, before others such as Saki started distributing it.
> > Regards,
> > Richard.
> > On 4 Aug 2010, at 09:53, Owen wrote:
> > I'm working with the University of Oxford on a project to enhance
> > resource lists they present in their learning environment - Sakai. We
> > have proposed using Juice to add various enhancements to the lists,
> > and if we did this, we would of course be contributing back the
> > metadefs/extensions we develop.
> > Our ideal outcome in Sakai would be to be able to distribute the Juice
> > code as part of the Sakai distribution. However, the licensing of
> > Juice as GPL is slightly problematic - so, the question is whether
> > there is any chance of dual licensing Juice under GPL and another (non-
> > viral) licensing regime. For example JQuery itself is licensed under
> > GPL and MIT License.
> > Is there any possibility of doing this?
> > Thanks,
> > Owen
> > --
> > You received this message because you are subscribed to the Google Groups "juice-project-discuss" group.
> > To post to this group, send email to juice-project-discuss@googlegroups.com<mailto:juice-project-discuss@googleg roups.com>.
> > To unsubscribe from this group, send email to juice-project-discuss+unsubscribe@googlegroups.com<mailto:juice-project-dis cuss+unsubscribe@googlegroups.com>.
> > For more options, visit this group athttp://groups.google.com/group/juice-project-discuss?hl=en.
> > Any views or personal opinions expressed within this email may not be those of Talis Information Ltd or its employees. The content of this email message and any files that may be attached are confidential, and for the usage of the intended recipient only. If you are not the intended recipient, then please return this message to the sender and delete it. Any use of this e-mail by an unauthorised recipient is prohibited.
> > Talis Information Ltd is a member of the Talis Group of companies and is registered in England No 3638278 with its registered office at Knights Court, Solihull Parkway, Birmingham Business Park, B37 7YB.
On Tue, Aug 10, 2010 at 6:45 AM, Owen <owen.pa...@gmail.com> wrote: > I'm not an expert on licensing, but I'm assuming that since JQuery is > licensed under MIT and GPL, they are compatible, and it would make > sense to adopt the same model for Juice, as it means it can't end up > in conflict with JQuery?
BTW, few users of Juice will distribute it, so the provisions of the GPL related to distribution are not really meaningful. Some for this reason use the Affero GPL.
If you're not distributing derived works, the question of compatibility of MIT/GPL doesn't arise, either. (Both licenses give you the right to use the code, which is what you're doing in your server that uses Juice. You're not distributing derived works.)
> I'm not an expert on licensing, but I'm assuming that since JQuery is
> licensed under MIT and GPL, they are compatible, and it would make
> sense to adopt the same model for Juice, as it means it can't end up
> in conflict with JQuery?
> The latest developments sound good - any idea on timescale - our
> project runs until the end of the year, but I'm expecting to be
> working on the bits that use Juice in October/November (the project is
> called 'Sir Louie'http://blogs.oucs.ox.ac.uk/sirlouie- I'll post a
> summary in another thread highlighting how we intend to use Juice)
> Owen
> On Aug 4, 11:46 am, Matt Machell <mattmach...@googlemail.com> wrote:
> > From some very casual research, the two licenses are compatible, so it
> > shouldn't prove a problem from that angle.
> > I do agree with Richard that it would be nice to finish off some of
> > the polish before bundling it with another product.
> > I've got a branch where I'm working on some optimisations,
> > accessibility enhancements and a move towards being a jQuery plugin.
> > It would probably be worth getting those in trunk before bundling.
> > Speaking of which, if anybody wants to take a look at the work so far
> > it's in: branches/20100702-mm-jqplugin
> > On Aug 4, 10:14 am, Richard Wallis <Richard.Wal...@talis.com> wrote:
> > > Hi Owen,
> > > As long as it is OS and attributable to those that produced it, I am fairly ambivalent about which actual licences we use.
> > > What you suggest sounds fine, especially as that approach seems to be OK for JQuery.
> > > What do others think.
> > > It would be good if we could get to a version 1.0, with a few desirable tweaks, fixes and finished off new extensions in it, before others such as Saki started distributing it.
> > > Regards,
> > > Richard.
> > > On 4 Aug 2010, at 09:53, Owen wrote:
> > > I'm working with the University of Oxford on a project to enhance
> > > resource lists they present in their learning environment - Sakai. We
> > > have proposed using Juice to add various enhancements to the lists,
> > > and if we did this, we would of course be contributing back the
> > > metadefs/extensions we develop.
> > > Our ideal outcome in Sakai would be to be able to distribute the Juice
> > > code as part of the Sakai distribution. However, the licensing of
> > > Juice as GPL is slightly problematic - so, the question is whether
> > > there is any chance of dual licensing Juice under GPL and another (non-
> > > viral) licensing regime. For example JQuery itself is licensed under
> > > GPL and MIT License.
> > > Is there any possibility of doing this?
> > > Thanks,
> > > Owen
> > > --
> > > You received this message because you are subscribed to the Google Groups "juice-project-discuss" group.
> > > To post to this group, send email to juice-project-discuss@googlegroups.com<mailto:juice-project-discuss@googleg roups.com>.
> > > To unsubscribe from this group, send email to juice-project-discuss+unsubscribe@googlegroups.com<mailto:juice-project-dis cuss+unsubscribe@googlegroups.com>.
> > > For more options, visit this group athttp://groups.google.com/group/juice-project-discuss?hl=en.
> > > Any views or personal opinions expressed within this email may not be those of Talis Information Ltd or its employees. The content of this email message and any files that may be attached are confidential, and for the usage of the intended recipient only. If you are not the intended recipient, then please return this message to the sender and delete it. Any use of this e-mail by an unauthorised recipient is prohibited.
> > > Talis Information Ltd is a member of the Talis Group of companies and is registered in England No 3638278 with its registered office at Knights Court, Solihull Parkway, Birmingham Business Park, B37 7YB.
> I'm hoping to get those modifications tested and into trunk some time
> in the next few months, so that should mesh with your timelines quite
> well.
> On Aug 10, 11:45 am, Owen <owen.pa...@gmail.com> wrote:
> > I'm not an expert on licensing, but I'm assuming that since JQuery is
> > licensed under MIT and GPL, they are compatible, and it would make
> > sense to adopt the same model for Juice, as it means it can't end up
> > in conflict with JQuery?
> > The latest developments sound good - any idea on timescale - our
> > project runs until the end of the year, but I'm expecting to be
> > working on the bits that use Juice in October/November (the project is
> > called 'Sir Louie'http://blogs.oucs.ox.ac.uk/sirlouie-I'll post a
> > summary in another thread highlighting how we intend to use Juice)
> > Owen
> > On Aug 4, 11:46 am, Matt Machell <mattmach...@googlemail.com> wrote:
> > > From some very casual research, the two licenses are compatible, so it
> > > shouldn't prove a problem from that angle.
> > > I do agree with Richard that it would be nice to finish off some of
> > > the polish before bundling it with another product.
> > > I've got a branch where I'm working on some optimisations,
> > > accessibility enhancements and a move towards being a jQuery plugin.
> > > It would probably be worth getting those in trunk before bundling.
> > > Speaking of which, if anybody wants to take a look at the work so far
> > > it's in: branches/20100702-mm-jqplugin
> > > On Aug 4, 10:14 am, Richard Wallis <Richard.Wal...@talis.com> wrote:
> > > > Hi Owen,
> > > > As long as it is OS and attributable to those that produced it, I am fairly ambivalent about which actual licences we use.
> > > > What you suggest sounds fine, especially as that approach seems to be OK for JQuery.
> > > > What do others think.
> > > > It would be good if we could get to a version 1.0, with a few desirable tweaks, fixes and finished off new extensions in it, before others such as Saki started distributing it.
> > > > Regards,
> > > > Richard.
> > > > On 4 Aug 2010, at 09:53, Owen wrote:
> > > > I'm working with the University of Oxford on a project to enhance
> > > > resource lists they present in their learning environment - Sakai. We
> > > > have proposed using Juice to add various enhancements to the lists,
> > > > and if we did this, we would of course be contributing back the
> > > > metadefs/extensions we develop.
> > > > Our ideal outcome in Sakai would be to be able to distribute the Juice
> > > > code as part of the Sakai distribution. However, the licensing of
> > > > Juice as GPL is slightly problematic - so, the question is whether
> > > > there is any chance of dual licensing Juice under GPL and another (non-
> > > > viral) licensing regime. For example JQuery itself is licensed under
> > > > GPL and MIT License.
> > > > Is there any possibility of doing this?
> > > > Thanks,
> > > > Owen
> > > > --
> > > > You received this message because you are subscribed to the Google Groups "juice-project-discuss" group.
> > > > To post to this group, send email to juice-project-discuss@googlegroups.com<mailto:juice-project-discuss@googleg roups.com>.
> > > > To unsubscribe from this group, send email to juice-project-discuss+unsubscribe@googlegroups.com<mailto:juice-project-dis cuss+unsubscribe@googlegroups.com>.
> > > > For more options, visit this group athttp://groups.google.com/group/juice-project-discuss?hl=en.
> > > > ________________________________
> > > > Please consider the environment before printing this email.
> > > > Find out more about Talis athttp://www.talis.com/ > > > > shared innovation(tm)
> > > > Any views or personal opinions expressed within this email may not be those of Talis Information Ltd or its employees. The content of this email message and any files that may be attached are confidential, and for the usage of the intended recipient only. If you are not the intended recipient, then please return this message to the sender and delete it. Any use of this e-mail by an unauthorised recipient is prohibited.
> > > > Talis Information Ltd is a member of the Talis Group of companies and is registered in England No 3638278 with its registered office at Knights Court, Solihull Parkway, Birmingham Business Park, B37 7YB.
> Any progress on both the next release and the dual licensing?
> Thanks,
> Owen
> On Aug 23, 1:21 pm, Matt Machell <mattmach...@googlemail.com> wrote:
> > Owen,
> > I'm hoping to get those modifications tested and into trunk some time
> > in the next few months, so that should mesh with your timelines quite
> > well.
> > On Aug 10, 11:45 am, Owen <owen.pa...@gmail.com> wrote:
> > > I'm not an expert on licensing, but I'm assuming that since JQuery is
> > > licensed under MIT and GPL, they are compatible, and it would make
> > > sense to adopt the same model for Juice, as it means it can't end up
> > > in conflict with JQuery?
> > > The latest developments sound good - any idea on timescale - our
> > > project runs until the end of the year, but I'm expecting to be
> > > working on the bits that use Juice in October/November (the project is
> > > called 'Sir Louie'http://blogs.oucs.ox.ac.uk/sirlouie-I'llpost a
> > > summary in another thread highlighting how we intend to use Juice)
> > > Owen
> > > On Aug 4, 11:46 am, Matt Machell <mattmach...@googlemail.com> wrote:
> > > > From some very casual research, the two licenses are compatible, so it
> > > > shouldn't prove a problem from that angle.
> > > > I do agree with Richard that it would be nice to finish off some of
> > > > the polish before bundling it with another product.
> > > > I've got a branch where I'm working on some optimisations,
> > > > accessibility enhancements and a move towards being a jQuery plugin.
> > > > It would probably be worth getting those in trunk before bundling.
> > > > Speaking of which, if anybody wants to take a look at the work so far
> > > > it's in: branches/20100702-mm-jqplugin
> > > > On Aug 4, 10:14 am, Richard Wallis <Richard.Wal...@talis.com> wrote:
> > > > > Hi Owen,
> > > > > As long as it is OS and attributable to those that produced it, I am fairly ambivalent about which actual licences we use.
> > > > > What you suggest sounds fine, especially as that approach seems to be OK for JQuery.
> > > > > What do others think.
> > > > > It would be good if we could get to a version 1.0, with a few desirable tweaks, fixes and finished off new extensions in it, before others such as Saki started distributing it.
> > > > > Regards,
> > > > > Richard.
> > > > > On 4 Aug 2010, at 09:53, Owen wrote:
> > > > > I'm working with the University of Oxford on a project to enhance
> > > > > resource lists they present in their learning environment - Sakai. We
> > > > > have proposed using Juice to add various enhancements to the lists,
> > > > > and if we did this, we would of course be contributing back the
> > > > > metadefs/extensions we develop.
> > > > > Our ideal outcome in Sakai would be to be able to distribute the Juice
> > > > > code as part of the Sakai distribution. However, the licensing of
> > > > > Juice as GPL is slightly problematic - so, the question is whether
> > > > > there is any chance of dual licensing Juice under GPL and another (non-
> > > > > viral) licensing regime. For example JQuery itself is licensed under
> > > > > GPL and MIT License.
> > > > > Is there any possibility of doing this?
> > > > > Thanks,
> > > > > Owen
> > > > > --
> > > > > You received this message because you are subscribed to the Google Groups "juice-project-discuss" group.
> > > > > To post to this group, send email to juice-project-discuss@googlegroups.com<mailto:juice-project-discuss@googleg roups.com>.
> > > > > To unsubscribe from this group, send email to juice-project-discuss+unsubscribe@googlegroups.com<mailto:juice-project-dis cuss+unsubscribe@googlegroups.com>.
> > > > > For more options, visit this group athttp://groups.google.com/group/juice-project-discuss?hl=en.
> > > > > ________________________________
> > > > > Please consider the environment before printing this email.
> > > > > Find out more about Talis athttp://www.talis.com/ > > > > > shared innovation(tm)
> > > > > Any views or personal opinions expressed within this email may not be those of Talis Information Ltd or its employees. The content of this email message and any files that may be attached are confidential, and for the usage of the intended recipient only. If you are not the intended recipient, then please return this message to the sender and delete it. Any use of this e-mail by an unauthorised recipient is prohibited.
> > > > > Talis Information Ltd is a member of the Talis Group of companies and is registered in England No 3638278 with its registered office at Knights Court, Solihull Parkway, Birmingham Business Park, B37 7YB.
> On Oct 19, 7:58 am, Owen <owen.pa...@gmail.com> wrote: > > Hi Matt,
> > Any progress on both the next release and the dual licensing?
> > Thanks,
> > Owen
> > On Aug 23, 1:21 pm, Matt Machell <mattmach...@googlemail.com> wrote:
> > > Owen,
> > > I'm hoping to get those modifications tested and into trunk some time > > > in the next few months, so that should mesh with your timelines quite > > > well.
> > > On Aug 10, 11:45 am, Owen <owen.pa...@gmail.com> wrote:
> > > > I'm not an expert on licensing, but I'm assuming that since JQuery is > > > > licensed under MIT and GPL, they are compatible, and it would make > > > > sense to adopt the same model for Juice, as it means it can't end up > > > > in conflict with JQuery?
> > > > The latest developments sound good - any idea on timescale - our > > > > project runs until the end of the year, but I'm expecting to be > > > > working on the bits that use Juice in October/November (the project > is > > > > called 'Sir Louie'http://blogs.oucs.ox.ac.uk/sirlouie-I'llpost a > > > > summary in another thread highlighting how we intend to use Juice)
> > > > Owen
> > > > On Aug 4, 11:46 am, Matt Machell <mattmach...@googlemail.com> wrote:
> > > > > From some very casual research, the two licenses are compatible, so > it > > > > > shouldn't prove a problem from that angle.
> > > > > I do agree with Richard that it would be nice to finish off some of > > > > > the polish before bundling it with another product.
> > > > > I've got a branch where I'm working on some optimisations, > > > > > accessibility enhancements and a move towards being a jQuery > plugin. > > > > > It would probably be worth getting those in trunk before bundling.
> > > > > Speaking of which, if anybody wants to take a look at the work so > far > > > > > it's in: branches/20100702-mm-jqplugin
> > > > > On Aug 4, 10:14 am, Richard Wallis <Richard.Wal...@talis.com> > wrote:
> > > > > > Hi Owen,
> > > > > > As long as it is OS and attributable to those that produced it, I > am fairly ambivalent about which actual licences we use.
> > > > > > What you suggest sounds fine, especially as that approach seems > to be OK for JQuery.
> > > > > > What do others think.
> > > > > > It would be good if we could get to a version 1.0, with a few > desirable tweaks, fixes and finished off new extensions in it, before others > such as Saki started distributing it.
> > > > > > Regards, > > > > > > Richard.
> > > > > > On 4 Aug 2010, at 09:53, Owen wrote:
> > > > > > I'm working with the University of Oxford on a project to enhance > > > > > > resource lists they present in their learning environment - > Sakai. We > > > > > > have proposed using Juice to add various enhancements to the > lists, > > > > > > and if we did this, we would of course be contributing back the > > > > > > metadefs/extensions we develop.
> > > > > > Our ideal outcome in Sakai would be to be able to distribute the > Juice > > > > > > code as part of the Sakai distribution. However, the licensing of > > > > > > Juice as GPL is slightly problematic - so, the question is > whether > > > > > > there is any chance of dual licensing Juice under GPL and another > (non- > > > > > > viral) licensing regime. For example JQuery itself is licensed > under > > > > > > GPL and MIT License.
> > > > > > Is there any possibility of doing this?
> > > > > > Thanks,
> > > > > > Owen
> > > > > > -- > > > > > > You received this message because you are subscribed to the > Google Groups "juice-project-discuss" group. > > > > > > To post to this group, send email to > juice-project-discuss@googlegroups.com<mailto: > juice-project-discuss@googleg roups.com>. > > > > > > To unsubscribe from this group, send email to > juice-project-discuss+unsubscribe@googlegroups.com<juice-project-discuss%2B unsubscribe@googlegroups.com> > <mailto:juice-project-dis cuss+unsubscribe@googlegroups.com<cuss%2Bunsubscribe@googlegroups.com> > >. > > > > > > For more options, visit this group athttp:// > groups.google.com/group/juice-project-discuss?hl=en.
> > > > > > ________________________________ > > > > > > Please consider the environment before printing this email.
> > > > > > Find out more about Talis athttp://www.talis.com/ > > > > > > shared innovation(tm)
> > > > > > Any views or personal opinions expressed within this email may > not be those of Talis Information Ltd or its employees. The content of this > email message and any files that may be attached are confidential, and for > the usage of the intended recipient only. If you are not the intended > recipient, then please return this message to the sender and delete it. Any > use of this e-mail by an unauthorised recipient is prohibited.
> > > > > > Talis Information Ltd is a member of the Talis Group of companies > and is registered in England No 3638278 with its registered office at > Knights Court, Solihull Parkway, Birmingham Business Park, B37 7YB.
> -- > You received this message because you are subscribed to the Google Groups > "juice-project-discuss" group. > To post to this group, send email to > juice-project-discuss@googlegroups.com. > To unsubscribe from this group, send email to > juice-project-discuss+unsubscribe@googlegroups.com<juice-project-discuss%2B unsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/juice-project-discuss?hl=en.
