https://gitlab.wikimedia.org/repos/cloud/toolforge/builds-api is missing a software license.
@aborrero, @dcaro, @Raymond_Ndibe, @Slst2020, as the primary contributors of that repository, do you have any preferences? If not, I'll send a patch for AGPL-3.0-only.
| Title | Reference | Author | Source Branch | Dest Branch | |
|---|---|---|---|---|---|
| builds-api: bump to 0.0.136-20240410072458-06de24b4 | repos/cloud/toolforge/toolforge-deploy!239 | project_1317_bot_df3177307bed93c3f34e421e26c86e38 | bump_builds-api | main | |
| dev: add AGPL-3.0-or-later license | repos/cloud/toolforge/builds-api!83 | sstefanova | slavina/add-license | main |
To do this right, we need to add a license notice to every file in the repo in addition to a COPYING file. Is that correct?
Ideally, a SPDX license header on every source file + a LICENSE file in the root of the repo.
To clarify, do we want AGPL-3.0-only or AGPL-3.0-or-later?
The latter option seems more sensible to me, see https://www.gnu.org/licenses/identify-licenses-clearly.en.html
I'm ok with later
Is there any check/autoformatting we can do for the SPDX headers? I really don't want to have to care
sstefanova opened https://gitlab.wikimedia.org/repos/cloud/toolforge/builds-api/-/merge_requests/83
dev: add AGPL-3.0-only license
sstefanova merged https://gitlab.wikimedia.org/repos/cloud/toolforge/builds-api/-/merge_requests/83
dev: add AGPL-3.0-or-later license
project_1317_bot_df3177307bed93c3f34e421e26c86e38 opened https://gitlab.wikimedia.org/repos/cloud/toolforge/toolforge-deploy/-/merge_requests/239
builds-api: bump to 0.0.136-20240410072458-06de24b4
sstefanova merged https://gitlab.wikimedia.org/repos/cloud/toolforge/toolforge-deploy/-/merge_requests/239
builds-api: bump to 0.0.136-20240410072458-06de24b4