release preparation: legal issue

[Xavier Hanin <xa...@gmail.com>]

Hi All,

I've done some work on xooki to be able to generate the documentation, to
avoid packaging xooki in the distribution. This works pretty fine now, but I
now realize we may have a legal issue. Indeed, the documentation rely on a
small javascript for the menu found here:
http://www.dynamicdrive.com/dynamicindex1/navigate1.htm

The problem is that even when the doc is generated we need to package those
scripts if we want to have the same tree view as on the web site. But this
script hasn't a standard OSI approved license, so I think it's a problem to
distribute it, isn't it?

If we really can't distribute it, we can remove it completely (in this case
the menu will be always fully expanded) and I can review the menu generation
in this case to generate only the relevant parts (what is opened by default
when you navigate to the page). I'd prefer keeping the menu, especially if
we later want to use the batch generation instead of in browser generation
for the public website (to improve accessbility and web crawlers
compatibility). Maybe I could make that an option during batch generation...

WDYT?

- Xavier

Re: release preparation: legal issue

[Eric Crahen <er...@gmail.com>]

I think a static option would be great in the long run anyways. Even if you
do eventually find some DHTML thing you like for popup-y menus. Its more of
a personal preference but stuff like that drives me nuts :)

On 3/25/07, Xavier Hanin <xa...@gmail.com> wrote:
>
> On 3/24/07, Stefan Bodewig <bo...@apache.org> wrote:
> >
> > On Fri, 23 Mar 2007, Xavier Hanin <xa...@gmail.com> wrote:
> >
> > > I've done some work on xooki to be able to generate the
> > > documentation, to avoid packaging xooki in the distribution. This
> > > works pretty fine now, but I now realize we may have a legal
> > > issue. Indeed, the documentation rely on a small javascript for the
> > > menu found here:
> > > http://www.dynamicdrive.com/dynamicindex1/navigate1.htm
> >
> > Section 3 in <http://www.dynamicdrive.com/notice.htm> sounds scary.
>
>
> Yes, even if I think we fall in what's allowed by  the license, I don't
> want
> to face legal issues with the first Ivy release. So I think I'll generate
> something without any dhtml menu, only a static one will be enough for the
> offline doc distributed with Ivy. Unless somebody point me to a script I
> would use and distribute to replace the menu I used so far.
>
> - Xavier
>
> The best option would be to ask them for a non-exclusive licence to
> > redistribute their code with Ivy.  Or to replace the menu generating
> > code with something else ...
> >
> > Stefan
> >
>



-- 

- Eric

Re: release preparation: legal issue

[Xavier Hanin <xa...@gmail.com>]

On 3/24/07, Stefan Bodewig <bo...@apache.org> wrote:
>
> On Fri, 23 Mar 2007, Xavier Hanin <xa...@gmail.com> wrote:
>
> > I've done some work on xooki to be able to generate the
> > documentation, to avoid packaging xooki in the distribution. This
> > works pretty fine now, but I now realize we may have a legal
> > issue. Indeed, the documentation rely on a small javascript for the
> > menu found here:
> > http://www.dynamicdrive.com/dynamicindex1/navigate1.htm
>
> Section 3 in <http://www.dynamicdrive.com/notice.htm> sounds scary.


Yes, even if I think we fall in what's allowed by  the license, I don't want
to face legal issues with the first Ivy release. So I think I'll generate
something without any dhtml menu, only a static one will be enough for the
offline doc distributed with Ivy. Unless somebody point me to a script I
would use and distribute to replace the menu I used so far.

- Xavier

The best option would be to ask them for a non-exclusive licence to
> redistribute their code with Ivy.  Or to replace the menu generating
> code with something else ...
>
> Stefan
>

Re: release preparation: legal issue

[Stefan Bodewig <bo...@apache.org>]

On Fri, 23 Mar 2007, Xavier Hanin <xa...@gmail.com> wrote:

> I've done some work on xooki to be able to generate the
> documentation, to avoid packaging xooki in the distribution. This
> works pretty fine now, but I now realize we may have a legal
> issue. Indeed, the documentation rely on a small javascript for the
> menu found here:
> http://www.dynamicdrive.com/dynamicindex1/navigate1.htm

Section 3 in <http://www.dynamicdrive.com/notice.htm> sounds scary.

The best option would be to ask them for a non-exclusive licence to
redistribute their code with Ivy.  Or to replace the menu generating
code with something else ...

Stefan