Applying the new license

[Jeremias Maerki <de...@greenmail.ch>]

I guess you'all seen the commit messages. I got a headache now, so I'll
stop for the moment. Maybe I can do the rest this weekend. Only some
manual work is left to do. Help is welcome. That little Java class in
the committer CVS module really made this whole thing a piece of cake
without me having to set up any script language environments on my
Windows box. :-)

We still have copyright statements in some of our hyphenation patterns.
Seems like I gave up last year before sorting everything out. Sigh. I'll
have to sleep over that. If anyone has any ideas or, better, surplus
time.......

Jeremias Maerki

Re: Applying the new license

[Jeremias Maerki <de...@greenmail.ch>]

On 28.02.2004 20:16:56 Clay Leeds wrote:
> It would also be nice, if there were some sort of "repository" or links 
> page on the FOP site where people can go to get hyphenation files that 
> cannot be included in FOP because they do not meet the needs of the 
> ALv2 (assuming there are no negative legal ramifications). That way, 
> this valuable information is still accessible, and simplifies the 
> process of getting the information. It might mean a little more legwork 
> on our part, but it may end up being 'worth it' in the long run.

Well, IMO our website says just about everything there is to know about
hypenation patterns. Even a link to the most important source for
hypenation patterns is there. One possibility for the community is to
create a project at SourceForge (or somewhere else) to put hyphenation
patterns which cannot be distributed by the ASF.

> Also, I don't know how I can be of use, but if there's anything I can 
> do in this regard (e.g., take a text blurb and 'apply' it to a set of 
> files), I'd be happy to help. I just need a little direction on how to 
> contribute.

You could try to get a few people together to create that place where
people can download additional hyphenation patterns. Also, simply send
in patches for the documentation as you see possibilities for
improvement. I don't think you have to care about the relicensing issues.
We can handle that. Just continue doing what you do. That way you
already help a lot. If you want to do even more, you could buy yourself
a good beginners guide to Java.


Jeremias Maerki

Re: Applying the new license

[Clay Leeds <cl...@medata.com>]

On Feb 28, 2004, at 1:22 AM, Jeremias Maerki wrote:
> Especially for the hyphenation patterns this may still be problematic
> because someone who does a hyphenation file conversion may not be
> entitled to submit it to the ASF because he is not the (only)
> copyright holder and license restrictions may not allow our
> distributing the file.
>
> On 28.02.2004 00:27:19 Peter B. West wrote:
>> Apart from the hyphenation problem below, what manual work remains?
>
> Jeremias Maerki

It would also be nice, if there were some sort of "repository" or links 
page on the FOP site where people can go to get hyphenation files that 
cannot be included in FOP because they do not meet the needs of the 
ALv2 (assuming there are no negative legal ramifications). That way, 
this valuable information is still accessible, and simplifies the 
process of getting the information. It might mean a little more legwork 
on our part, but it may end up being 'worth it' in the long run.

Also, I don't know how I can be of use, but if there's anything I can 
do in this regard (e.g., take a text blurb and 'apply' it to a set of 
files), I'd be happy to help. I just need a little direction on how to 
contribute.

Web Maestro Clay

Re: Applying the new license

[Jeremias Maerki <de...@greenmail.ch>]

The (documentation) sources all need a license header (docs and
src/documentation). That's one part remaining. The other is the rest of
the hyphenation files. But there it may not be so simple as to apply the
Apache license. We will need to doublecheck the audit results and see
where we can apply the ALv2 and where we have to do something else
(getting grants, or doing something like we do for the JARs in our
repository).

BTW, we need to update our site to reflect that new releases and
especially new contributions by developers will fall under the new
license. The new license contains in implicit copyright grant which
makes our life a lot easier when we accept contributions. And what's
equally important is that it's a lot easier for contributors, too,
because they don't have to send in grants for bigger contributions
anymore. See section 5 in the new license. But all that doesn't mean we
can neglect our duty to check the origin of contributions. Especially
for the hyphenation patterns this may still be problematic because
someone who does a hyphenation file conversion may not be entitled to
submit it to the ASF because he is not the (only) copyright holder and
license restrictions may not allow our distributing the file.

On 28.02.2004 00:27:19 Peter B. West wrote:
> Apart from the hyphenation problem below, what manual work remains?


Jeremias Maerki

Re: Applying the new license

["Peter B. West" <pb...@powerup.com.au>]

Thanks for all the housekeeping, Jeremias.

Jeremias Maerki wrote:
> I guess you'all seen the commit messages. I got a headache now, so I'll
> stop for the moment. Maybe I can do the rest this weekend. Only some
> manual work is left to do. Help is welcome. That little Java class in
> the committer CVS module really made this whole thing a piece of cake
> without me having to set up any script language environments on my
> Windows box. :-)

Apart from the hyphenation problem below, what manual work remains?

> 
> We still have copyright statements in some of our hyphenation patterns.
> Seems like I gave up last year before sorting everything out. Sigh. I'll
> have to sleep over that. If anyone has any ideas or, better, surplus
> time.......

Peter
-- 
Peter B. West <http://www.powerup.com.au/~pbwest/resume.html>