-
### Please confirm these before moving forward
- [x] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
- [x] I have not been informed if the issue is resolved in…
-
Have a page somewhere in the app listing contributors.
This is usually next to stuff like About and licenses.
In addition, make sure to include mentions to third party contributions inside app c…
-
**### Please confirm these before moving forward**
I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
I have not been informed if the issue is resolved in a prev…
-
source-build-reference-packages have a bunch of `THIRD-PARTY-NOTICES.TXT` files. For example:
- https://github.com/dotnet/source-build-reference-packages/blob/main/src/targetPacks/ILsrc/microsoft.n…
-
There are third party licenses, but not license of the app.
-
### Operating system
macOS
### Joplin version
1.0.5
### Desktop version info
_No response_
### Current behaviour
Background:
As part of maintaining the integrity and legal compliance of our pr…
-
There is a bug with Google Maven packages (maybe other package types too?) where a notices file license data (which should be "discovered" licenses) are erroneously included in the "declared" field. …
-
See; [license checking with Bazel](https://docs.google.com/document/d/1uwBuhAoBNrw8tmFs-NxlssI6VRolidGYdYqagLqHWt8/edit#) for background.
We should use rules_license in Bazel. This would
- serve a…
aiuto updated
9 months ago
-
## What kind of business use case are you trying to solve? What are your requirements?
Clarity on third-party software licenses (attributions) in OpenSearch projects.
In particular, the Data Pre…
-
### Brief description of your issue
When I run the `winget upgrade --all` I noticed that it tried to install x64 version of the OpenJS.NodeJS package (notice the installer URL).
```
(11/18) Found…