runwayml / runwayml/sdk-python

Document licensing and copyright for reused code

Open
#202 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
26
Forks
10
Avg merge
3h 33m
Merged PRs (30d)
19

Description

Hello,

I noticed that part of the code in this repo is copied from other projects, with comments for attribution, for instance:

https://github.com/runwayml/sdk-python/blob/b28a4525782e8675e316dff460f23b7d3ff1a593/src/runwayml/_streaming.py#L1

https://github.com/runwayml/sdk-python/blob/b28a4525782e8675e316dff460f23b7d3ff1a593/src/runwayml/_compat.py#L196

This makes it difficult to vendor this repo, as one has to track all sources and their licenses / copyright information to ensure compliance with their licenses.
Would you consider standardizing this in a machine-readable format? I recommend using REUSE Specification, which enforces the SPDX license open standard.

For instance, _compat.py could look like:

+ # SPDX-FileCopyrightText: 2026 RunwayML
+ #
+ # SPDX-License-Identifier: Apache-2.0

...

     # we define a separate type (copied from typeshed)
     # that represents that `cached_property` is `set`able
     # at runtime, which differs from `@property`.
     #
     # this is a separate type as editors likely special case
     # `@property` and we don't want to cause issues just to have
     # more helpful internal types.

+   # SPDX-SnippetBegin
+   # SPDX-SnippetCopyrightText: Contributors to typeshed <https://github.com/python/typeshed>
+   # SPDX-SnippetCopyrightText: 2015 Jukka Lehtosalo and contributors
+   # SPDX-License-Identifier: Apache-2.0 AND MIT
    class typed_cached_property(Generic[_T]):
      ...
+   # SPDX-SnippetEnd

If you are ok with that I could help with a PR (just based on the "copied from ..." comments).

Thanks!

Contributor guide

Open the contributing guide

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.

Research direction

Start by reviewing the copied-from comments and the examples in _compat.py, then compare the repository's reused code with the REUSE Specification and SPDX guidance linked in the issue. Document copyright and license information in the proposed machine-readable format for each identified snippet, with attribution and license coverage complete across the reused code.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.