AW: AW: AW: [Tm4j-developers] Source code license text

[<eso...@gm...>]

I agree with Christoph in all points ;-)
His proposal for the license versioning problem is great. Lets bother
with this problem if it actually arises.

Elmar

> -----Urspr=FCngliche Nachricht-----
> Von: Christoph Froehlich [mailto:cf...@fo...]=20
> Gesendet: Donnerstag, 26. Februar 2004 13:35
> An: Kal Ahmed
> Cc: Elmar Seest=E4dt; tm4j developers
> Betreff: Re: AW: AW: [Tm4j-developers] Source code license text
>=20
>=20
> Hi Kal,
>=20
> so many things to consider. sigh..
> I see your point, that the local copy may be altered or vanishes.
>=20
> Maybe this is leading too far and we should just use your first
> proposal:
> /*
>  Copyright (c) 2000-2004 The TM4J Project. All rights reserved.
> =20
>  This software is licensed under a modified version of the=20
>  Apache Software License. The full license text can be found=20
> at  http://tm4j.org/LICENSE.txt=20
> */
>=20
> This is short, simple and non-ambigous.
>=20
> In the unlikely case that the license will change, we will=20
> create a new stable adress, something like =20
> http://tm4j.org/LICENSE-2.txt and update all relevant resources.
>=20
>=20
> bye
> c
> =20
>=20
>=20
>=20
> Am Do, den 26.02.2004 schrieb ka...@te... um 12:51:
> > Hi Cristoph,
> >=20
> > I understand your point. I don't think that it is likely that the=20
> > license will change, but it could happen I suppose. The=20
> only problem=20
> > with referring only to the local license is that it could=20
> be that the=20
> > license file gets moved or altered. So, if there is only one=20
> > reference, referring to a copy of the license file that we have=20
> > control over makes more sense to me.
> >=20
> > Perhaps we should put a version number or version date in=20
> the license=20
> > file URL so the URL reference could be to, for example,=20
> > http://tm4j.org/LICENSE_20040226.txt Then if we use a different=20
> > license for a future release, that could have a different URL - of=20
> > course, that would mean updating all of the file headers, but that=20
> > shouldn't be a problem.
> >=20
> > Cheers,
> >=20
> > Kal
> >=20
> > Christoph Froehlich writes:
> >=20
> > > Hi
> > >=20
> > >=20
> > > I would opt for a version, that mentions only ONE occurrence. But=20
> > > maybe the local one:
> > >=20
> > > /*
> > >  Copyright (c) 2000-2004 The TM4J Project. All rights reserved.
> > > =20
> > >  This software is licensed under a modified version of the=20
> > >  Apache Software License. The full license text can   =20
> > >  be found in the file LICENSE.txt in the root directory   =20
> > >  of the source tree.
> > > */
> > >=20
> > > I wonder what would happen to the resources that reference the=20
> > > license on tm4j.org if we change the file tm4j.org/LICENSE.txt=20
> > > somewhere in the future.
> > >=20
> > > All theese resources would change their license too,=20
> aren't they? A=20
> > > kind of floating license. This sounds a bit strange to me. The=20
> > > license of a particular distribution, should be fixed. Or=20
> do I miss=20
> > > something?
> > >=20
> > > bye
> > > c
> > >=20
> > >=20
> > > Am Do, den 26.02.2004 schrieb ka...@te... um 11:58:
> > > > Hi Elmar,
> > > >=20
> > > > I agree the license text should be in the distributions (both=20
> > > > binary and source distributions). I just wondered=20
> whether to make=20
> > > > a reference to it
> > > > from the source code headers or just to reference the=20
> license file on
> > > > the
> > > > website. I'm in two minds about it - on the one hand=20
> having one place
> > > > referenced in all the source files means that there should be no
> > > > problem
> > > > about inconsistencies between the file on the site and=20
> the file in a
> > > > distribution. On the other hand the license file will be in the
> > > > distribution and it would be sensible to reference it there...
> > > >=20
> > > > I think it is something we can spend a lot of time=20
> worrying about=20
> > > > so I propose this slightly modified version of your=20
> proposed text=20
> > > > - just changed because LICENSE.txt is actually in the root=20
> > > > directory of the whole distro,
> > > > not at the root of the source tree (to me the "root of=20
> the source
> > > > tree" is
> > > > the src directory).
> > > >=20
> > > >  /*
> > > >   Copyright (c) 2000-2004 The TM4J Project. All rights reserved.
> > > > =20
> > > >   This software is licensed under a modified version of=20
> > > >   the  Apache Software License. The full license text can=20
> > > >   be found in the file LICENSE.txt in the root directory=20
> > > >   of the distribution or at http://tm4j.org/LICENSE.txt  */
> > > >=20
> > > > Hows that ?
> > > >=20
> > > > Cheers,
> > > >=20
> > > > Kal
> > > > Elmar_Seestdt writes:
> > > >=20
> > > > > Hi Kal,
> > > > >=20
> > > > > Another point from me. The License text should be included in=20
> > > > > the
> > > > source
> > > > > distribution as a text file as well. Maybe in the=20
> root directory=20
> > > > > of
> > > > the
> > > > > sources.
> > > > > And there should be a reference to this file in the header:
> > > > >=20
> > > > > /*
> > > > >   Copyright (c) 2000-2004 The TM4J Project. All=20
> rights reserved.
> > > > > =20
> > > > >   This software is licensed under a modified version of=20
> > > > >   the  Apache Software License. The full license text can=20
> > > > >   be found in the file LICENSE.txt in the root directory=20
> > > > >   of the source tree or at
> > > > >   http://tm4j.org/LICENSE.txt
> > > > > */
> > > > >=20
> > > > > >=20
> > > > > > I think its better just to point to one place (the TM4J.org
> > > > > > website) and to say "modified version" so that=20
> people cannot=20
> > > > > > claim that we have passed the IP to the Apache Software
> > > > Foundation!
> > > > > >=20
> > > > >=20
> > > > > Thats a good idea people tend to get weird ideas.
> > > > >=20
> > > > > Elmar
> > > > >=20
> > > > >=20
> > > > >=20
> > > > > -------------------------------------------------------
> > > > > SF.Net is sponsored by: Speed Start Your Linux Apps=20
> Now. Build=20
> > > > > and deploy apps & Web services for Linux with a free DVD=20
> > > > > software kit from IBM. Click Now!=20
> > > > > http://ads.osdn.com/?ad_id=1356&alloc_id438&opclick
> > > > > _______________________________________________
> > > > > Tm4j-developers mailing list=20
> > > > > Tm4...@li...
> > > > > https://lists.sourceforge.net/lists/listinfo/tm4j-developers
> > > >=20
> > > >=20
> > > >=20
> > > >=20
> > > >=20
> > > > -------------------------------------------------------
> > > > SF.Net is sponsored by: Speed Start Your Linux Apps=20
> Now. Build and=20
> > > > deploy apps & Web services for Linux with a free DVD=20
> software kit=20
> > > > from IBM. Click Now!=20
> > > > http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick
> > > > _______________________________________________
> > > > Tm4j-developers mailing list=20
> Tm4...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/tm4j-developers
> > > --
> > > Christoph Froehlich <cf...@fo...>
> > >=20
> > >=20
> > >=20
> > > -------------------------------------------------------
> > > SF.Net is sponsored by: Speed Start Your Linux Apps Now.=20
> Build and=20
> > > deploy apps & Web services for Linux with a free DVD software kit=20
> > > from IBM. Click Now!=20
> > > http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick
> > > _______________________________________________
> > > Tm4j-developers mailing list Tm4...@li...
> > > https://lists.sourceforge.net/lists/listinfo/tm4j-developers
> >=20
> >=20
> >=20
> >=20
> >=20
> > -------------------------------------------------------
> > SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and=20
> > deploy apps & Web services for Linux with a free DVD=20
> software kit from=20
> > IBM. Click Now!=20
> http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D> 3438&op=3Dclick
> >=20
>=20
> _______________________________________________
> > Tm4j-developers mailing list
> > Tm4...@li...
> > https://lists.sourceforge.net/lists/listinfo/tm4j-developers
> --=20
> Christoph Froehlich <cf...@fo...>
>=20