Add license to existing repo / License reminder #293

Open
opened 2020-09-22 09:15:25 +02:00 by ivan-paleo · 15 comments
Image

It's easy to add a license during the creation of a repo, but I could not find a way to add/change a license (file) to/of an existing repo.

Maybe I've just missed it, but if not, I would suggest to add this function.

It's easy to add a license during the creation of a repo, but I could not find a way to add/change a license (file) to/of an existing repo. Maybe I've just missed it, but if not, I would suggest to add this function.
Image
Member

Just add any FSF/OSI approved LICENSE file to the repository.

Just add any FSF/OSI approved LICENSE file to the repository.
Image
Author

Just add any FSF/OSI approved LICENSE file to the repository.

Yes, of course, but you first have to find such a file! This is why the best would be to be able to add it afterwards just like during the creation.

I mean it's not a big issue, but it would surely help. Just suggesting...

> Just add any FSF/OSI approved LICENSE file to the repository. Yes, of course, but you first have to find such a file! This is why the best would be to be able to add it afterwards just like during the creation. I mean it's not a big issue, but it would surely help. Just suggesting...
Image

Adding on to this, a reminder for projects to add a LICENSE or COPYING file (if one doesn't already exist) would be good.

Adding on to this, a reminder for projects to add a LICENSE or COPYING file (if one doesn't already exist) would be good.
Image
Member

A reminder banner with button to select/create the LICENSE file sounds pretty cool

A reminder banner with button to select/create the LICENSE file sounds pretty cool
Image

In that banner, we could link to a site that helps users find a license.

We could link directly to FSF and OSI - https://www.gnu.org/licenses/license-list and https://opensource.org/licenses.

I also like the idea of choosealicense.com, particularly https://choosealicense.com/licenses/.

The SPDX License list contains a vast array of licenses and information about if they're FSF/OSI approved. But it might be too much and overwhelm users. Also it contains non-approved licenses.

In that banner, we could link to a site that helps users find a license. We could link directly to FSF and OSI - https://www.gnu.org/licenses/license-list and https://opensource.org/licenses. I also like the idea of choosealicense.com, particularly https://choosealicense.com/licenses/. The [SPDX License list](https://spdx.org/licenses/) contains a vast array of licenses and information about if they're FSF/OSI approved. But it might be too much and overwhelm users. Also it contains non-approved licenses.
Image lhinderberger changed title from Add license to existing repo to Add license to existing repo / License reminder 2020-09-22 23:36:03 +02:00
Image

I think https://choosealicense.com/ is on point and not overwhelming, like any long list of licenses.

Should we even threaten users, that we delete repositories, that are not open source, after 14 days or so? They are not allowed.

I think https://choosealicense.com/ is on point and not overwhelming, like any long list of licenses. Should we even threaten users, that we delete repositories, that are not open source, after 14 days or so? They are not allowed.
Image
Member

Should we even threaten users, that we delete repositories, that are not open source, after 14 days or so? They are not allowed.

That's what we currently do (trying to be nice) in a manual manner. Automatizing part or all of this process, or even some feature to enforce a valid license when creating/importing a repository would be valuable.

> Should we even threaten users, that we delete repositories, that are not open source, after 14 days or so? They are not allowed. That's what we currently do (trying to be nice) in a manual manner. Automatizing part or all of this process, or even some feature to enforce a valid license when creating/importing a repository would be valuable.
Image
Member

To begin, something like a repo banner reminding of a missing LICENSE file would be wonderful.

To begin, something like a repo banner reminding of a missing LICENSE file would be wonderful.
Image

But also make it easy do add one.

But also make it easy do add one.
Image
Member

contributions and PR (to templates or gitea?) welcome!

contributions and PR (to templates or gitea?) welcome!
Image
Owner

linking #414 (different idea, same purpose)

linking #414 (different idea, same purpose)
Image

I created an issue upstream: https://github.com/go-gitea/gitea/issues/15626

I created an issue upstream: https://github.com/go-gitea/gitea/issues/15626
Image

I would say mostly solved by Codeberg/gitea#36

but upstream still lacks moderation ...

I would say mostly solved by https://codeberg.org/Codeberg/gitea/pulls/36 but upstream still lacks moderation ...
Image
Owner

Auto-detection of licences is still an important thing for this ...

Auto-detection of licences is still an important thing for this ...
Image

Glad to be involved in this conversation. What are the key possibilities for keeping up with the current license for now?

Glad to be involved in this conversation. What are the key possibilities for keeping up with the current license for now?
Sign in to join this conversation.
No milestone
No project
No assignees
8 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#293
No description provided.