mirrors
/
licensee
mirror of https://github.com/licensee/licensee.git
7
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
1,058 Commits 19 Branches 104 Tags 45 MiB
Commit Graph

35 Commits

Author SHA1 Message Date
Mike Linksvayer fc40fd0c86
Merge branch 'master' into manufacture-source 2018-08-06 23:39:54 +00:00
Mike Linksvayer 471b4824e3 update docs 2018-08-06 16:39:22 -07:00
Mike Linksvayer 973299d2be
parenthetical to note why project is emphasized 2018-07-16 11:38:52 -07:00
Mike Linksvayer d811a940f5
Merge branch 'master' into master 2018-07-16 18:32:41 +00:00
Mike Linksvayer c31186637c
make current 
licensee for a long time has optionally looked at some of the things this file says it doesn't

also add a bit of nuance
 2018-07-16 10:55:07 -07:00
1138-4EB ce53067495
Update README.md 2018-04-15 02:30:12 +02:00
Antonio Diaz 3ee6322a37
update to new default confidence threshold 2018-04-07 19:58:26 -07:00
Ben Balter 24b216861b Update docs/CONTRIBUTING.md 2018-03-29 16:35:15 -04:00
Ian Kelling 15082c08c4 correct bad information about license notice in source files 
https://www.gnu.org/licenses/identify-licenses-clearly.html:
"I did not know how developers would respond to this innovation, so I
decided to give each developer a choice about allowing future
versions. This meant developers could release a program under GNU GPL
version 1 only, or release it under GPL version 1 or any later
version. The way developers state their choice is in the license notice
that goes at the start of each source file. That's where the GPL says
the decision is stated."

https://spdx.org/using-spdx#identifiers:
"The SPDX Work-group proposes to use SPDX license identifiers to
indicate the license at the file level."
 2018-03-14 00:48:13 -04:00
Mike Linksvayer cce8e5d5f5 document how to check against expected license 
inspired by https://github.com/benbalter/licensee/issues/276#issuecomment-372448925
 2018-03-12 14:53:39 -07:00
Sebastian Schuberth e045686acd README: Explain how to run licensee directly from source 2018-02-12 13:15:19 +01:00
Ben Balter b667a99888
document command-line usage 2018-02-06 12:22:05 -05:00
Mike Linksvayer e3d88aa465 more explicit documentation 2017-12-31 10:37:38 -08:00
Nick Campbell 1b9d1f2b00
Add support for GitHub projects 
Rather than querying the local filesystem, we can use the Github API to
resolve folder contents and the individual files within.

This isn't going to be performant - requests are not made in parallel -
and there is absolutely no error handling.
 2017-12-27 22:08:40 +00:00
Ben Balter c439bd65d0 Update docs/CONTRIBUTING.md 2017-10-24 10:21:22 -04:00
Ben Balter 0ed77bee64
add PRs welcome tag to README 2017-10-17 14:27:50 -04:00
Ben Balter 1d3d2807f9 Update docs/CONTRIBUTING.md 2017-10-17 14:08:12 -04:00
Ben Balter c3fb95016e
update intro to contributing file 2017-10-17 11:43:39 -04:00
Ben Balter 279fe9081a
update CONTRIBUTING 2017-10-17 11:34:31 -04:00
Ben Balter 4e5a71af44 Remove description from _config.yml 2017-08-11 11:37:42 -04:00
Ben Balter f938574b80 Create _config.yml 2017-07-17 12:37:49 -04:00
Ben Balter 437b0754c2
disambiguate support 2017-07-17 10:38:15 -04:00
Ben Balter 904c5a0f1c Rename CODE_OF_CONDUCT.md to docs/CODE_OF_CONDUCT.md 2017-06-01 14:20:30 -04:00
Ben Balter 4149a7c486 Rename CONTRIBUTING.md to docs/CONTRIBUTING.md 2017-06-01 14:16:50 -04:00
Ben Balter 22a11001b3 Update relative links 2017-06-01 14:16:38 -04:00
Ben Balter 401acbf5ff
highlight symver example 2017-03-29 15:55:01 -04:00
Ben Balter 24f5681083
reverse README symlink 2017-03-29 15:50:11 -04:00
Ben Balter f21d6dafbd
symlink readme 2017-03-29 15:39:09 -04:00
Ben Balter 325de73c4b add more to why not package managers 2017-03-17 09:25:19 -04:00
W. Trevor King 3f2ed3ab2b docs/what-we-look-at: Remove "Is it GPLv2? GPLv2 or later?" 
Some packaging systems allow you to make these distinctions.  For
example, Python supports "or later" Trove classifiers [1] and npm
allows SPDX license expression syntax v2.0 [2] (and SPDX expressions
support '+', e.g. 'GPL-2.0+' [3]).

The point of this paragraph is that such an entry is metadata which
may not be sufficiently binding [4], while including the full license
text is much more likely to be legally binding.  By removing the FUD
about "cannot distinguish between GPL-2.0 and GPL-2.0+", we can focus
on the point that actually matters.

[1]: https://pypi.python.org/pypi?%3Aaction=list_classifiers
     > License :: OSI Approved :: GNU General Public License v2 (GPLv2)
     > License :: OSI Approved :: GNU General Public License v2 or later (GPLv2+)
[2]: https://docs.npmjs.com/files/package.json#license
     > If your package is licensed under multiple common licenses, use
     > an SPDX license expression syntax version 2.0 string...
[3]: https://spdx.org/sites/cpstandard/files/pages/files/spdx-2.0.pdf#page=82
     > An SPDX License List Short Form Identifier with a unary "+"
     > operator suffix to represent the current version of the license
     > or any later version.  For example: GPL-2.0+
[4]: https://github.com/benbalter/licensee/issues/4
     What's legally sufficient to constitute a grant of an open source
     software license?
 2017-02-20 13:06:13 -08:00
Rory O’Kane 5baeb5ad65 Update range of linked lines in docs 
`license_file.rb` was edited since the link was first made, so the range pointed to the wrong part of the file. With this change, the range once again cover the `FILENAME_REGEXES` hash contents.
 2017-01-18 16:10:56 -05:00
Jim Hester 7394be1e73 Add support for the CRAN package manager for R packages. 2016-09-23 10:15:44 -04:00
Jim Hester 967982e3a0 Instructions invalid, should call Licensee.project() 2016-09-23 08:39:34 -04:00
Jim Hester 1c0155ba4c Fix broken links 
The '.md' suffix was missing
 2016-09-23 08:38:33 -04:00
Ben Balter bc5e4506e7 update documentation 2016-09-22 10:45:17 -04:00