Determine Project Licensing

In support of our Open Collective submission I added the GPL-2.0-or-later license to the repository.

We can still discuss alternatives, but wanted to make sure the repository reflected where we'd be if no action was taken.

I'm thinking it makes sense to work through this as part of our proposal to the Drupal JS maintainers.

@fago helpfully raised this issue once again on Twitter.

Having GPL currently is a combination of the source being on Drupal gitlab (I read that as being implied here: https://drupal.org/about/licensing#content-license) and also needing to have a license in the repo early on when establishing an Open Collective.

I'd be open to changing this if possible, and agree that it would be a good discussion for the community. MIT was proposed as an alternative, which I personally prefer. It is also the common standard in the projects that we have modeled this work on.

I'll look at trying to start discussion with the licensing working group. Might also be able to catch someone face to face in Portland if necessary.

Discussion on this topic in Drupal #licensing slack: https://drupal.slack.com/archives/C204BR9ML/p1714924304161589

Need to figure out concrete next steps, but it sounds like we might have a path forward here.

Created the following issue in the LWG project as a next step: https://www.drupal.org/project/drupal_lwg/issues/3447461 ✨ Allow GPL-Compatible Licensing for Non-Derivative Code and Drupal.org General Projects Active

brianperry → credited fago → .

brianperry → credited hestenet → .

Marking as fixed. Based on the general agreement with the LWG I've published a release of our packages that uses an MIT license: https://www.drupal.org/project/api_client/issues/3389581 →

Automatically closed - issue fixed for 2 weeks with no activity.