Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create LICENSE #110

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Create LICENSE #110

wants to merge 2 commits into from

Conversation

Maniues
Copy link

@Maniues Maniues commented May 24, 2024

Add standard 2-Clause BSD license to top-level directory

Add standard 2-Clause BSD license
@Maniues
Copy link
Author

Maniues commented May 25, 2024

@Simn here is also a license issue. haxelib.json information: BSD, most files: BSD or BSD-like license. I can also prepare NOTICE file with 3rd party licenses for this project

@Maniues
Copy link
Author

Maniues commented May 26, 2024

@Simn I included notices, so in my opinion it is ready to merge and close license issues in this repo.

@Simn
Copy link
Member

Simn commented May 26, 2024

I'll let @ncannasse check this one.

@Maniues
Copy link
Author

Maniues commented May 26, 2024

Okay, no problem

@Maniues
Copy link
Author

Maniues commented May 26, 2024

To clarify: I took the license info from haxelib.json and added many copyright notices that come from particular files in subdirectories.

@Maniues
Copy link
Author

Maniues commented Aug 18, 2024

@Simn is there any update in this case (and in another Haxe repositories)?

@Maniues
Copy link
Author

Maniues commented Sep 15, 2024

@ncannasse @Simn any updates here?

@Maniues
Copy link
Author

Maniues commented Sep 25, 2024

@Simn @ncannasse

For this repository:

haxelib.json -> license BSD
Most files have the BSD-2 Clause license
The following directories/files DON'T have license header:

/flash
/tests
format/:
elf/*
gif/*
hl/*
ico/*
lz4/*
map/*
mp3/Data.hx
neko/Templo.hx
pex/*
tga/*
tgz/*
tools/MemoryBytes.hx

From some files there is the standard BSD license that refers to format project, not specific file module:

* format - Haxe File Formats
 *
 * Copyright (c) 2008, The Haxe Project Contributors
 * All rights reserved.
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions are met:
 *
 *   - Redistributions of source code must retain the above copyright
 *     notice, this list of conditions and the following disclaimer.
 *   - Redistributions in binary form must reproduce the above copyright
 *     notice, this list of conditions and the following disclaimer in the
 *     documentation and/or other materials provided with the distribution.
 *
 * THIS SOFTWARE IS PROVIDED BY THE HAXE PROJECT CONTRIBUTORS "AS IS" AND ANY
 * EXPRESS 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 HAXE PROJECT 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.
 */

@Maniues
Copy link
Author

Maniues commented Oct 6, 2024

@Simn @ncannasse I don't know why I don't get any response with this PR...
This change is actually a supplement to the actual state of affairs.
The haxelib.json file has a BSD license inserted and the same license appears in many files.
This PR is nothing more than adding this license as information in the top directory.

@Simn
Copy link
Member

Simn commented Oct 6, 2024

Look, I appreciate that you're willing to look into this license stuff, but pinging an issue four times over the course of two hours on a Sunday is a bit crazy. I already said that I don't know what to do with this repository in this regard, so no, there are no updates.

@Maniues
Copy link
Author

Maniues commented Oct 6, 2024

Look, I appreciate that you're willing to look into this license stuff, but pinging an issue four times over the course of two hours on a Sunday is a bit crazy. I already said that I don't know what to do with this repository in this regard, so no, there are no updates.

I'm so sorry, I've been a bit stressed lately, especially today, and I'm trying to wrap up everything I can to have a little less on my mind.

The Haxe licensing threads are unfortunately quite important to me, as I'm serious about legal use of this toolkit.

So I'm giving you time to consider these issues, both here and in the API documentation and elsewhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants