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.
Just add any FSF/OSI approved LICENSE file to the repository.
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...
Adding on to this, a reminder for projects to add a LICENSE or COPYING file (if one doesn't already exist) would be good.
A reminder banner with button to select/create the LICENSE file sounds pretty cool
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.
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.
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.
To begin, something like a repo banner reminding of a missing LICENSE file would be wonderful.
But also make it easy do add one.
contributions and PR (to templates or gitea?) welcome!
linking #414 (different idea, same purpose)
I created an issue upstream: https://github.com/go-gitea/gitea/issues/15626
I would say mostly solved by Codeberg/gitea#36
but upstream still lacks moderation ...
Auto-detection of licences is still an important thing for this ...
Glad to be involved in this conversation. What are the key possibilities for keeping up with the current license for now?
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?