MIT licensing state is unhealthy

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Domain
documentation

Research direction

Start with the top-level LICENSE-MIT file and compare its copyright notice against the OSI MIT license linked in the issue. Identify the appropriate copyright information from the repository history or project context, then update the license so it includes the required notice and verify that the licensing text is complete.

Written by the indexing model from the issue text.

Description

I don't think it's currently possible to comply with wasi-libc's license because copyright information has largely been stripped from the project

the top-level LICENSE file says:

wasi-libc as a whole is multi-licensed under the Apache License v2.0 with LLVM Exceptions, the Apache License v2.0, and the MIT License. See the LICENSE-APACHE-LLVM, LICENSE-APACHE and LICENSE-MIT files, respectively, for details.

the top-level LICENSE-MIT file says:

Permission is hereby granted, free of charge, to any
person obtaining a copy of this software and associated
documentation files (the "Software"), to deal in the
Software without restriction, including without
limitation the rights to use, copy, modify, merge,
publish, distribute, sublicense, and/or sell copies of
the Software, and to permit persons to whom the Software
is furnished to do so, subject to the following
conditions:

The above copyright notice and this permission notice
shall be included in all copies or substantial portions
of the Software.

except the license file lacks any copyright information. it seems the file was edited from the standard/stock one to delete that information. see the OSI MIT license as a reference.

Dominant language
C
Stars
1k
Forks
268
Avg merge
1d 3h
Merged PRs (30d)
20

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 WebAssembly/wasi-libc

All issues in WebAssembly/wasi-libc

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.