Skip to content
This repository was archived by the owner on May 27, 2024. It is now read-only.
This repository was archived by the owner on May 27, 2024. It is now read-only.

Redefining the three steps #20

Closed
Closed
@carmenbianca

Description

@carmenbianca

Max and I are working on redefining the three REUSE steps.

The current steps are:

  1. Provide the exact text of each license used
  2. Include a copyright notice and license in each file
  3. Provide an inventory for included software

During our sprint, we produced this:

  1. Choose and provide a license
  2. Add a license header to each file
  3. Confirm compliance with the linter

I am not entirely happy with the exact wording, but I like the gist of it.

  1. "Choose and provide a license" is more succinct than the first iteration, and puts emphasis on actually choosing a license. But it does not emphasise the fact that you are very likely to have multiple licenses, at all. Is this an okay trade-off?

  2. "Add a license header to each file". This is good, but I'm not sure if "license header" necessarily includes copyright tags. Is there a short synonym we can use instead? "Add a copyright and license tag to the header of each file"?

  3. "Confirm compliance with the linter". This is good, but I feel that the wording is wrong. "linter" should probably be replaced by "REUSE tool". And I am not really sure on the word "compliance". Compliance is one step removed from what the developer really wants: Every file having clear copyright and licensing information.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions