Yeah, I'm not too bothered with the code per se as it's not that alive, however I emailed the original author and he's said it's fine to change the javadoc to just say:
> * This Java implementation originally coded by William B. Brogden, > * December 1997. > * @author [EMAIL PROTECTED] I'll also make this change to Jakarta-Taglib which probably has the same problem internally. Hen [authors response below: ] Date: Mon, 21 Oct 2002 13:43:47 -0500 From: William Brogden <[EMAIL PROTECTED]> To: 'Henri Yandell' <[EMAIL PROTECTED]> Subject: RE: Metaphone.java Thats fine with me, but you might remove the Compuserve number. [EMAIL PROTECTED] Author of Soap Programming with Java - Sybex; ISBN: 0782129285 Coauthor of Cocoon 2 Programming - Sybex; ISBN: 0782141315 > -----Original Message----- > From: Henri Yandell [mailto:bayard@;generationjava.com] > Sent: Monday, October 21, 2002 1:16 PM > To: William Brogden > Subject: Re: Metaphone.java > > > > Hey William, > > Bit of a reorganisation going on at Jakarta at the moment. One thing > that's been pointed out to me is that I left your: > > * This Java implementation, Copyright 1997, William B. Brogden > * is hereby released for all uses. I would appreciate > hearing about it > * if you find a good use for the class. December, 1997 > * > * @author [EMAIL PROTECTED] CompuServe 75415,610 > > in the source code for Metaphone. > > This is an issue for them as code is meant to be copyright ASF. > > Do you mind me removing this part and replacing it with: > > * This Java implementation originally coded by William B. Brogden, > * December 1997. > * @author [EMAIL PROTECTED] CompuServe 75415,610 > > at all? > > Thanks, > > Hen On Mon, 21 Oct 2002, Michael A. Smith wrote: > On Mon, 21 Oct 2002, Henri Yandell wrote: > > On Mon, 21 Oct 2002, Martin Cooper wrote: > > > I found a few things not yet mentioned: > > > > > > 1) In codec\Metaphone.java, "Copyright 1997, William B. Brogden", which is > > > clearly a problem. > > > > Sorry, my fault. I can and will remove this, and will go back in my > > records for the email in which he gave me the acceptance to take the code. > > [I think he said it was public domain.] > > > > Will provide more info in a bit. > > I do not believe we can attach a copyright and/or license to any public > domain code without getting into murky water. Actually, I don't believe > *anyone* can attach a copyright to public domain code without getting > into murky water. Actually, I don't even think that's murky. > > The way I've understood discussion on reorg@apache, when we need answers > on whether things like this will cause problems, we send them to > [EMAIL PROTECTED] So, if you want to keep the code (it's sandbox code > in a not-very-active component), dig up your documentation on where the > code originated and any circumstances surrounding it, and attach it to > an email to [EMAIL PROTECTED] where you can ask whether its ok. It'd > probably be nice to include an executive summary so that the board can > decipher what you're talking about a bit quicker. > > regards, > michael > > > -- > To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: <mailto:commons-dev-help@;jakarta.apache.org> > > -- To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:commons-dev-help@;jakarta.apache.org>
