Hello,
> you would need admin rights to do this
Ok.
> Does this help?
Yes.
> Unfortunately the public test instance does not allow for admin access as
public login, so it is not there [1].
Also, initially, I tried to avoid running the full fledge instance (IIRC, I
tried the demo though and did not see it indeed).
To try your proposition, I installed docker and run one local instance from
the git repository.
I was then able to extract one listing following the thorough example you
gave me.
So thanks a bunch.
> BUT, since you mention data model.
...
> Is that the info you were looking for?
Well, in a way yes.
I was looking for a simple flag on nomossa (Nomos Stand-Alone) to list what
licenses it supported.
But your links and hints definitely helped a lot so thanks again.
Cheers,
Antoine R. Dumont
On Mon, Nov 21, 2016 at 4:40 PM, Jaeger, Michael C. <
michael.c.jae...@siemens.com> wrote:
> Hello,
>
>
>
> you would need admin rights to do this. On your own installation, you
> could:
>
>
>
> 1) Go to Admin, Licenses, Candidates -> Web Ui for all licenses
>
> 2) Go to Admin, Licenses, CSV Export -> get a CSV file of all licenses
>
> 3) check table licenseref on a deployed version
>
>
>
> Does this help? Unfortunately the public test instance does not allow for
> admin access as public login, so it is not there [1].
>
>
>
> BUT, since you mention data model. I think there is important input in the
> FOSSology data model: consider the following fields as entry:
>
>
>
> 1. License Short name =SPDX ID if present
>
> 2. Name = see the SPDX License List
>
> 3. Text
>
> 4. Text for report: sometimes a „license text“ found in file is not the
> license text you would like to see in the report, for example, standardized
> headers for Apache, GPL licenses.
>
> 5. Common ID for decisions: Sometimes you have a license variant that
> should not bother license deciding, because variant is not licensing
> relevant. Examples are the BSD licenses with their adaptations w.r.t. tot
> he author/copyright holder.
>
>
>
> A good source for data model is also the SPDX license list repo [2]
>
>
>
> Is that the info you were looking for?
>
>
>
> Kind regards, Michael
>
>
>
> [1] http://52.26.97.143/repo/
>
> [2] https://spdx.org/licenses/
>
>
>
>
>
>
>
>
>
> -Original Message-
> From: fossology-boun...@lists.fossology.org [mailto:fossology-bounces@
> lists.fossology.org] On Behalf Of antoine.romain.dum...@gmail.com
> Sent: Mittwoch, 9. November 2016 23:45
> To: fossology@lists.fossology.org
> Subject: [FOSSology] current supported license listing in nomossa
>
>
>
> Hello,
>
>
>
> is there some way to have a comprehensive list of the current supported
> licenses?
>
>
>
> I found some listing [1] but it's not up-to-date (latest version mentioned
> there is 2.6.0 and the last stable version is 3.0).
>
>
>
> For now, I'm trying to determine the supported licenses from the parse.c
> file [2] [3].
>
>
>
> We are currently using nomossa in the Software Heritage Project [4] and
> that list would help in our data model.
>
>
>
> Thanks for your time
>
>
>
> [1] http://archive15.fossology.org/projects/fossology/wiki/
> Nomos_license_list
>
> [2] https://github.com/fossology/fossology/blob/master/src/
> nomos/agent/parse.c
>
> [3] https://forge.softwareheritage.org/rDSNIP09923374e0f321da78faa0b3
> 7b2814fea9c5f1c1
>
> [4] https://www.softwareheritage.org/
>
>
>
> Cheers,
>
> --
>
> tony / @ardumont
>
>
>
> -
>
> gpg fingerprint BF00 203D 741A C9D5 46A8 BE07 52E2 E984 0D10 C3B8
>
___
fossology mailing list
fossology@lists.fossology.org
https://lists.fossology.org/mailman/listinfo/fossology
