Interpretation of variants

Open
#110 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Read the license data and Python module or CLI to understand how licenses and variants are currently represented. The issue proposes a compatibility_as field but leaves its behavior and the expected handling of license variants open. First establish the project's conventions and decide what representation should mean before estimating implementation; done would require an agreed approach and examples covering the listed variants.

Written by the indexing model from the issue text.

Description

BSD-3-Clause has variants such Google and Facebook. Other examples

  • BSD-like

Adding a compatibility_as would be useful, but what is the most common practice in dealing with these licenses?

Dominant language
Python
Stars
7
Forks
3
Avg merge
2h 53m
Merged PRs (30d)
7

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 aboutcode-org/foss-licenses

All issues in aboutcode-org/foss-licenses

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.