REQUEST: Repository maintenance on ruby projects fossa

Open
#3,558 0 comments 1 reaction 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
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
ruby
Domain
tooling

Research direction

Start by inspecting the FOSSA configuration in the three affected repositories and compare its detected license entries with the linked YARD, diff-lcs, and RDoc license files. Consolidate or amend the declarations as described, then run the repository license checks to confirm the false positives are resolved across the listed projects.

Written by the indexing model from the issue text.

Description

area/repo-maintenance
Affected Repository
Requested changes

Currently fossa is wrongly flagging license issues for the ruby projects. To address this could we have the following:

  • yard, it is detecting a gpl 2.0 only license. This should in fact be gpl-2.0-only OR ruby, see source https://github.com/lsegal/yard/blob/main/LEGAL. Doing a search surfaces no other matches. As such can you add the ruby licence to that detected licence (the text is the ruby license) and conclude we use that.
  • diff-lcs is impacted by a badly structured license file see https://github.com/halostatue/diff-lcs/blob/main/LICENCE.md. The only spot which isn't gpl-2.0 or later is the heading. Can the 3 declared licences be consolidated into 1 as per the file & the discovered licence replaced with gpl 2.0 or later to match the wording.
  • rdoc. Is treating it as having 2 licences when it should be 1 see https://github.com/ruby/rdoc/blob/master/LICENSE.rdoc with the solution being to combine them and select ruby. Note only an issue for contrib.
Purpose

We want to have all license issues resolved.

Expected Duration

permanently

Repository Maintainers
  • @open-telemetry/ruby-maintainers
  • @open-telemetry/ruby-contrib-maintainers
  • @open-telemetry/ruby-instrumentation-maintainers
Dominant language
Python
Stars
1.2k
Forks
326
Avg merge
1d 12h
Merged PRs (30d)
13

Getting set up

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 open-telemetry/community

All issues in open-telemetry/community

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.