Display a License tab #84

@tboerger commented on GitHub (Nov 27, 2016):

Ah, that makes more sense.

@tboerger commented on GitHub (Nov 27, 2016): Ah, that makes more sense.

GiteaMirror commented

@lunny commented on GitHub (Nov 27, 2016):

But for a self-hosted server, I seems there is no requirement.

@lunny commented on GitHub (Nov 27, 2016): But for a self-hosted server, I seems there is no requirement.

GiteaMirror commented

@thibaultmeyer commented on GitHub (Nov 27, 2016):

we are no forced to do something like github who scan repo to determine license. maybe just a selectbox field on repo settings page is enough ?

@thibaultmeyer commented on GitHub (Nov 27, 2016): we are no forced to do something like github who scan repo to determine license. maybe just a selectbox field on repo settings page is enough ?

GiteaMirror commented

@tboerger commented on GitHub (Nov 27, 2016):

This is something we can integrate at some point, so I moved it to a future milestone

@tboerger commented on GitHub (Nov 27, 2016): This is something we can integrate at some point, so I moved it to a future milestone

GiteaMirror commented

[1] https://github.com/ryanuber/go-license

@bkcsoft commented on GitHub (Nov 28, 2016):

Using something like go-license[1] it'd be fairly simple to implement, just remember to cache the result until the license-file changes (just add another column in the repo-table)

@bkcsoft commented on GitHub (Nov 28, 2016): Using something like go-license[1] it'd be fairly simple to implement, just remember to _cache_ the result until the license-file changes (just add another column in the repo-table) [1] https://github.com/ryanuber/go-license

GiteaMirror commented

@thibaultmeyer commented on GitHub (Nov 28, 2016):

yes we could add a new field on repo model and update it at each push / merge event.

@thibaultmeyer commented on GitHub (Nov 28, 2016): yes we could add a new field on repo model and update it at each push / merge event.

GiteaMirror commented

@bkcsoft commented on GitHub (Nov 29, 2016):

@0xbaadf00d preferably only update when LICENSE* have been updated ;)

@bkcsoft commented on GitHub (Nov 29, 2016): @0xbaadf00d preferably only update when `LICENSE*` have been updated ;)

GiteaMirror commented

@bamboleeeero-bamboleeeero commented on GitHub (Nov 29, 2016):

@bkcsoft that may not be always he case... some projects use COPYING for instance

@bamboleeeero-bamboleeeero commented on GitHub (Nov 29, 2016): @bkcsoft that may not be always he case... some projects use COPYING for instance

GiteaMirror commented

@bamboleeeero-bamboleeeero commented on GitHub (Nov 29, 2016):

LICENSE files my also not necessarily contain a single license, but a list of licenses for various components

@bamboleeeero-bamboleeeero commented on GitHub (Nov 29, 2016): LICENSE files my also not necessarily contain a single license, but a list of licenses for various components

GiteaMirror commented

@bkcsoft commented on GitHub (Dec 2, 2016):

@bamboleeeero-bamboleeeero

some projects use COPYING for instance

How does GitHub handle this?

but a list of licenses for various components

Same here. How does others handle that?

As I see it, it's a new feature, do the smallest amount of work first then extend on that in a later version :)

@bkcsoft commented on GitHub (Dec 2, 2016): @bamboleeeero-bamboleeeero > some projects use COPYING for instance How does GitHub handle this? > but a list of licenses for various components Same here. How does others handle that? As I see it, it's a new feature, do the smallest amount of work first then extend on that in a later version :)

GiteaMirror commented

@nogweii commented on GitHub (Jan 6, 2017):

Github handles this through the gem licensee.

some projects use COPYING for instance

Github scans the root of a project, and matches the files in that directory against a series of regular expressions with scores. High enough and it's treated as a file that likely contains the license text.

but a list of licenses for various components

The first license that Licensee detects and knows about is used. A better solution is being discussed at https://github.com/benbalter/licensee/issues/57

@nogweii commented on GitHub (Jan 6, 2017): Github handles this through the gem [licensee](https://github.com/benbalter/licensee). > some projects use COPYING for instance Github scans the root of a project, and matches the files in that directory against a series of regular expressions with scores. High enough and it's treated as a file that likely contains the license text. > but a list of licenses for various components The first license that Licensee detects and knows about is used. A better solution is being discussed at https://github.com/benbalter/licensee/issues/57

GiteaMirror commented

2025-11-02 03:08:05 -06:00

@gsantner commented on GitHub (Dec 16, 2017):

I can agree to @bamboleeeero-bamboleeeero - the filename is not always LICENSE. E.g. LICENSE.txt, LICENSE.md, COPYING are often used too

@gsantner commented on GitHub (Dec 16, 2017): I can agree to @bamboleeeero-bamboleeeero - the filename is not always LICENSE. E.g. LICENSE.txt, LICENSE.md, COPYING are often used too

GiteaMirror commented

@stale[bot] commented on GitHub (Feb 10, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 10, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 03:08:05 -06:00

@lunny commented on GitHub (Mar 17, 2020):

ref. https://github.com/src-d/go-license-detector

@lunny commented on GitHub (Mar 17, 2020): ref. https://github.com/src-d/go-license-detector

GiteaMirror commented

@hendrikbl commented on GitHub (Jul 20, 2020):

@lunny Any plans to implement this? The library looks promising.

@hendrikbl commented on GitHub (Jul 20, 2020): @lunny Any plans to implement this? The library looks promising.

GiteaMirror commented

@lafriks commented on GitHub (Jul 20, 2020):

Library moved to https://github.com/go-enry/go-license-detector

@lafriks commented on GitHub (Jul 20, 2020): Library moved to https://github.com/go-enry/go-license-detector

GiteaMirror commented

@mxmehl commented on GitHub (May 21, 2021):

May I suggest to also support the more flexible REUSE standard when implementing this important feature?

License detection would become really easy, especially if multiple licenses are in use. All you have to do is fetching the file names from the LICENSES directory. For instance, check this.

The files names (without .txt) indicate the unique SPDX license identifiers, and save everyone from interpreting the often diverging text in files like LICENSE or COPYING.

@mxmehl commented on GitHub (May 21, 2021): May I suggest to also support the more flexible [REUSE](https://reuse.software) standard when implementing this important feature? License detection would become really easy, especially if multiple licenses are in use. All you have to do is fetching the file names from the `LICENSES` directory. For instance, [check this](https://github.com/fsfe/reuse-tool/tree/master/LICENSES). The files names (without `.txt`) indicate the unique SPDX license identifiers, and save everyone from interpreting the often diverging text in files like `LICENSE` or `COPYING`.

GiteaMirror commented

@6543 commented on GitHub (Sep 25, 2021):

google did start developing a licence detector: https://github.com/google/licensecheck

@6543 commented on GitHub (Sep 25, 2021): google did start developing a licence detector: https://github.com/google/licensecheck

GiteaMirror commented