license-management
Here are 191 public repositories matching this topic...
Could we set some constants to identify
profiles id (ex PROF_SUPERADMIN_ID, PROF_OBSERVER_ID, etc)
users id (USER_GLPI_ID, USER_TECH_ID, etc)
Rights values (READ, UPDATE, etc)
-
Updated
Apr 6, 2020 - Swift
While inspecting the installer, I noticed the fallbacks for Linux / OSX when appdirs isn't available (in data_dir()).
Wouldn't it make sense to add an if for Windows based on %APPDATA% or %LOCALAPPDATA%, before resorting to globally installing appdirs?
Description
Running the following Command:
./scancode -clp --json-pp sample_filter_clues.json samples --filter-clues
Gives the Error:
ERROR: failed to run post-scan plugin: filter-clues:
Traceback (most recent call last):
File "/home/ayansm/Desktop/GSoD/scancode-toolkit-versions/scancode-toolkit-3.1.1/src/scancode/cli.py", line 1033, in run_codebase_plugins
plugin.p
-
Updated
Oct 10, 2019 - C++
Currently licensed includes files matching:
LEGAL_FILES = /\A(AUTHORS|COPYING|NOTICE|LEGAL)(?:\..*)?\z/iI think COPYING is superfluous, see #84, but there are some other files (also with any extension) that often include legal notices that would be useful to automatically collect, eg:
LICENSES,NOTICES(plural)THIRD-PARTY-LICENSE(variations including3rd, n
-
Updated
May 20, 2019 - JavaScript
-
Updated
May 16, 2020 - Go
Description
Hello,
I am trying to integrate a fossology instance with my project workflow.
What i want to do is make the task easier for the users of my app, and get the resul
The notice-pre-processor.kts file allows for customisation of the generated notice file, see https://github.com/oss-review-toolkit/ort/blob/master/docs/notice-pre-processor-kts.md.
Not all customisations seem possible, though. I would like to:
- customize the notice separator
- get rid of the separator between the different headers
- include the license name/id before the license text
Multiple projects
I have several projects and each project has several libraries. I would like to control the license at library scale.
How should I do that? Do I need to generate one license file for each library of each project?
-
Updated
May 31, 2020 - Go
-
Updated
Mar 19, 2020 - JavaScript
-
Updated
Mar 4, 2020 - JavaScript
Property 'config.cache.$0.fileNameCache' is private and annotated with @Input. This behaviour has been deprecated and is scheduled to be removed in Gradle 7.0. See https://docs.gradle.org/6.2.2/userguide/more_about_tasks.html#sec:up_to_date_checks for more details.
Property 'config.cache.$1.filterConfigForCache' is private and annotated with @Input. This behaviour has been deprecated and is
-
Updated
May 28, 2020 - Go
-
Updated
Jan 11, 2020 - Go
Problem
The copy function used for save preserves all permissions, which means when files are copied from the module cache for Reciprocal/Restricted licenses all the files and directories are readonly as well. This means that multiple runs of save won't work because the directories containing
Example
package example
import (
_ "github.com/hashicorp/errwrap"
)
`-
Updated
Jul 12, 2019 - Python
-
Updated
Oct 24, 2019 - Swift
There are several partial JavaDoc statements present in the library which make it difficult to use for someone trying to get familiar with it. In addition, the started documentation which isn't finished is causing the Maven build to fail if someone doesn't force Maven to use Java 7 or earlier for its own operations (there is a strict setting for things like "param" annotations to have text).
Note
-
Updated
May 10, 2020 - Java
-
Updated
May 20, 2020 - HTML
-
Updated
Dec 9, 2019 - JavaScript
-
Updated
Mar 6, 2020 - PHP
Basic documentation is still missing, ideally at least these documents should be written:
- README.md to quickly introduce the topic and this library.
- Wiki pages to introduce license management topics, best practices and usage examples.
Improve this page
Add a description, image, and links to the license-management topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the license-management topic, visit your repo's landing page and select "manage topics."


Server (please complete the following information):
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
the feature request is not related to a problem. Howe