License Carve out for Scripting

Open
#2,406 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
cpp
Domain
documentation

Research direction

Compare the licensing carve-out on the linked Project website with the repository’s LICENCE file. The issue also asks about adding a more permissive dual license, which requires resolving licensing scope and terms before work can begin; done would be an approved, accurate license update in the repository.

Written by the indexing model from the issue text.

Description

On the Project website there is an intended carve out for script access however it does not show up in the repo, which makes justifying usage for non-gpl projects harder.

Is it possible to add that carveout to the LICENCE file.

It would make life even easier if a dual license with something more permissive like MIT were included as well.

Dominant language
C++
Stars
1.2k
Forks
305
Avg merge
3d 2h
Merged PRs (30d)
11

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from KLayout/klayout

All issues in KLayout/klayout

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.