Update the license keys of the ABOUT file from 'license' to 'license_expression' and 'license_text_file' to 'license_file'

Open
#24 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

Edit src/publicsuffix2/public_suffix_list.ABOUT and compare its license keys with the supported keys referenced in src/attributecode/model.py around line 900. Done means replacing license with license_expression and license_text_file with license_file while keeping the existing values unchanged.

Written by the indexing model from the issue text.

Description

See https://github.com/aboutcode-org/aboutcode-toolkit/blob/develop/src/attributecode/model.py#L900 for the current supported keys.

https://github.com/aboutcode-org/python-publicsuffix2/blob/develop/src/publicsuffix2/public_suffix_list.ABOUT#L10

Current

about_resource: public_suffix_list.dat
name: Public Suffix List
version: 2020-01-27T10:24:28
download_url: https://publicsuffix.org/list/public_suffix_list.dat
home_url: https://publicsuffix.org/

owner: Mozilla
copyright: Copyright (c) Mozilla and others
license: mpl-2.0
license_text_file: mpl-2.0.LICENSE

Porposed

about_resource: public_suffix_list.dat
name: Public Suffix List
version: 2020-01-27T10:24:28
download_url: https://publicsuffix.org/list/public_suffix_list.dat
home_url: https://publicsuffix.org/

owner: Mozilla
copyright: Copyright (c) Mozilla and others
license_expression: mpl-2.0
license_file: mpl-2.0.LICENSE
Dominant language
Python
Stars
31
Forks
16
PR merge metrics
No merged PRs in 30d

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/python-publicsuffix2

All issues in aboutcode-org/python-publicsuffix2

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.