#293 Add license to existing repo / License reminder

Open
opened 4 weeks ago by ivan-paleo · 10 comments

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.
hw commented 4 weeks ago
Owner

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

Just add any FSF/OSI approved LICENSE file to the repository.
ivan-paleo commented 4 weeks ago
Poster

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...
n commented 4 weeks ago

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.
hw commented 4 weeks ago
Owner

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
lhinderberger commented 4 weeks ago
Collaborator

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.
lhinderberger added the
enhancement
label 3 weeks ago
lhinderberger changed title from Add license to existing repo to Add license to existing repo / License reminder 3 weeks ago
davidak commented 1 week ago
Collaborator

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.
hw commented 1 week ago
Owner

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.
hw commented 1 week ago
Owner

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.
davidak commented 1 week ago
Collaborator

But also make it easy do add one.

But also make it easy do add one.
hw commented 1 week ago
Owner

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

contributions and PR (to templates or gitea?) welcome!
Sign in to join this conversation.
No Milestone
No Assignees
5 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.