Re: public domain
An extract of the files that are interesting in this case:
File README.txt:
...
...
Disclaimer
----------
855resolution is free to use, distribute or modify. But please mention
my name and the names of the respective contributors.
I tried to make the programs as safe as possible but obviously I can't
guarantee that they'll work for you. So don't blame me if something bad
happens.
File LICENSE.txt:
/* =====================================================================
* This source code is into the public domain.
*
* THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
* WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
* OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
* DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR THE CONTRIBUTORS BE
* LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
* CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
* SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
* BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
* WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
* OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN
* IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
* =====================================================================
*/
IMHO this fulfills the requirements of the DFSG, so i'm going to package
it :)
If i'm wrong, please correct me.
Cheers
El mié, 30-03-2005 a las 10:13 +0200, Frank Küster escribió:
> Carlos Parra <cparra@emergya.info> wrote:
>
> > Hello,
> > I'd like to package a program that's licensed under "public domain".
> > I've been talking with the autor and says that he likes also BSD-style
> > license...
> >
> > The change of license is necesary to get into the main archive, isnt
> > it?
>
> As far as I know, a proper "public domain" license also fulfills the
> requirements of the DFSG. However, it is not sufficient to just say
> "This software is in the public domain", because this term is not very
> well defined. Instead, it could be something like
>
> "This software is in the Public Domain. You may freely use, modify
> and/or distribute it."
>
> And of course the other requirements must be fulfilled, i.e. we need the
> source code. And it must be clear for which files this license is
> intended, either by listing them with the license statement, or
> somewhere else, or by repeating the statement in every file.
>
> Regards, Frank
--
Carlos Parra Camargo
Emergya, Soluciones Tecnológicas
Tel. +34 954 98 10 53 FAX +34 954 98 11 79
Avda. Luis Montoto, 105
E41007 Sevilla
cparra@emergya.info
http://www.emergya.info
Reply to: