Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

x/pkgsite: Requesting BSL inclusion #59183

Closed
jsimnz opened this issue Mar 22, 2023 · 9 comments
Closed

x/pkgsite: Requesting BSL inclusion #59183

jsimnz opened this issue Mar 22, 2023 · 9 comments
Labels
pkgsite/license Issues related to licenses on pkg.go.dev. See our license policy https://pkg.go.dev/license-policy pkgsite
Milestone
pkgsite/backlog

Comments

@jsimnz
Copy link

jsimnz commented Mar 22, 2023 •
edited

What did you do?

Tried to access documentation for a Business Source License 1.1 (BSL 1.1) repo.

What did you expect to see?

Generated documentation.

What did you see instead?

Unsupported due to licensing restrictions

--

I'm seeking to have my (and potentially all) repo(s) included in pkg.go.dev that uses the BSL 1.1 license. https://mariadb.com/bsl11/

The BSL 1.1 license is becoming very popular for open source projects that are also balancing commercialization priorities. Although it is not an official OSI license, it does have the endorsement from Bruce Perens[0] who is the founder of the OSI Foundation. Additionally, it automatically converts to an "official" OSI license after a period of no more than 4 years from release. Finally, it's designed around an "Additional Use Grant" which my self (and Im sure other repo authors) would be happy to make inclusions to accomodate pkgsite.

These repos are fundamentally open-source / source available, so it's unfortunate that the current structure of pkg.go.dev doesn't support them.

[0] - https://perens.com/2017/02/14/bsl-1-1/#:~:text=So%2C%20there%20can,works%20Open%20Source.
@jsimnz jsimnz added the pkgsite label Mar 22, 2023
@gopherbot gopherbot added this to the Unreleased milestone Mar 22, 2023
@seankhliao seankhliao added the pkgsite/license Issues related to licenses on pkg.go.dev. See our license policy https://pkg.go.dev/license-policy label Mar 23, 2023
@seankhliao seankhliao mentioned this issue Mar 23, 2023
Closed
@jamalc
Copy link

jamalc commented Mar 24, 2023

We have forwarded this request and are waiting to hear back from our legal team.

@jamalc jamalc modified the milestones: Unreleased, pkgsite/later Mar 24, 2023
@jsimnz
Copy link
Author

jsimnz commented Mar 24, 2023

Appreciate the update, looking forward.

@jsimnz jsimnz mentioned this issue Mar 28, 2023
Closed
@jsimnz
Copy link
Author

jsimnz commented Apr 22, 2023

@jamalc any update on this? Thanks.

@gopherbot
Copy link

Change https://go.dev/cl/491775 mentions this issue: static/frontend/license-policy: clarify license addition requirement

gopherbot pushed a commit to golang/pkgsite that referenced this issue May 3, 2023
@hyangah
static/frontend/license-policy: clarify license addition requirement
56be3a4 
Currently we can add a new license to the list only if it is
also OSI approved.

Updates golang/go#59183

Change-Id: Ib799983a436e5f1eed5cf9c87fc947b9f559dff5
Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/491775
Run-TryBot: Hyang-Ah Hana Kim <hyangah@gmail.com>
TryBot-Result: kokoro <noreply+kokoro@google.com>
Reviewed-by: Robert Findley <rfindley@google.com>
@hyangah
Copy link
Contributor

hyangah commented May 4, 2023

Thank you for your patience.
We discussed with the legal team and learned we cannot add BSL to the list now.

Our license policy (https://pkg.go.dev/license-policy) is updated to clarify that
we currently accept only OSI-approved licenses.

@hyangah hyangah closed this as not planned Won't fix, can't repro, duplicate, stale May 4, 2023
@willfaught
Copy link
Contributor

@hyangah Then shouldn't BlueOak-1.0.0 and the CC licenses be removed from that list? They aren't OSI-approved.

@cespare
Copy link
Contributor

cespare commented May 5, 2023

@willfaught the policy doesn't say that the list can only contain OSI-approved licenses. It says that being OSI-approved is a requirement for adding new licenses to the list.

@jsimnz
Copy link
Author

jsimnz commented May 6, 2023

@hyangah was there specific items about the BSL that is preventing it from being approved that you can share, other than not being OSI-approved?

@orpheuslummis orpheuslummis mentioned this issue May 8, 2023
Open
@hyangah
Copy link
Contributor

hyangah commented May 8, 2023

@jsimnz The biggest challenge in adding a new non-OSI-approved license to the pkg.go.dev side is the need for manual reviews. We also discussed with the legal team the option of utilizing BSL's additional use grant section, but that will still need legal persons' review and involvement, which unfortunately we cannot do at this moment.

@willfaught We added a few non-OSI licenses at the time of the pkg.go.dev launch after manual reviews on each license (and many rounds of discussion between the go team and the legal team), and they are grandfathered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
pkgsite/license Issues related to licenses on pkg.go.dev. See our license policy https://pkg.go.dev/license-policy pkgsite
Projects
None yet
Milestone
pkgsite/backlog
Development

No branches or pull requests
7 participants
@willfaught @cespare @jsimnz @hyangah @gopherbot @seankhliao @jamalc