chef / chef/chef-web-docs

[BUG] Inconsistante wording/broken link about licensing change

Open
#3,182 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Documentation Status: Adopted Type: Bug
Dominant language
HTML
Stars
143
Forks
438
Avg merge
1d 10h
Merged PRs (30d)
16

Description

General details

From https://docs.chef.io/chef_license/ we can find this paragraph a bunch of people are asking about on slack and which creates its fair amount of talk outside Chef ecosystem:

In April 2019 many of our software distributions switched to being governed under the Chef EULA, while the software projects remained governed by the Apache 2.0 license. To understand which license applies to those distributions, see the versions page. General information about this change can be found in our announcement.

The specific sentence "To understand which license applies to those distributions, see the versions page." have a link which brings to https://docs.chef.io/versions/ and sadly there's absolutely nothing in this page about the license change nor wich version the switch happened to be in effect to guide peoples but only the general supported lifecycle of Chef products.

Product

[x] Chef Automate
[x] Chef Habitat
[x] Chef Infra Client
[x] Chef Infra Server
[x] Chef InSpec
[x] Other Mostly Everything in chef as things as super unclear for a newcomer.

Describe the update that needs to be made. Be as specific as possible:

Implement #2792 or just blankly remove this paragraph which just cause confusion now the "free" versions are EOL.
My personnal point of view is that not willing to have a clear table of when things have changed is sweeping the dust under the rug and making the community work harder without an official reference point.

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

Read the licensing paragraph at https://docs.chef.io/chef_license/ and follow its link to https://docs.chef.io/versions/. Review issue #2792 to understand the proposed update before changing the documentation. Done means the paragraph no longer leaves the licensing transition unclear, either through an authoritative reference or by removing the outdated wording.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.