Re: Help a newbie
Michael C. Jaeger
oh interesting, I have not seen your point from your answer, glad that our e-mails crossed.
Kind regards, Michael
From: main@... [mailto:main@...] On Behalf Of Nicolas Toussaint
Sent: Freitag, 12. Oktober 2018 17:03
Subject: Re: [FOSSology] Help a newbie
On 12/10/2018 16:56, marc.mcgarry@... wrote:
OAB - Orange Applications for Business - Lyon
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
VS: [FOSSology] Help a newbie
Martin von Willebrand
Fossology agent doing the unpacking will unpack zip-packages and jar-packages, even if they are nested.
You likely want to run source code files through Fossology, though, because many build systems remove texts that would be interesting for license analysis purposes. In java, you should look at uploading .java-files and not .class-files.
Martin von Willebrand, Attorney-at-law, Partner
HH Partners shines in international rankings. See details at hhpartners.fi.
Privileged and confidential information may be contained in this message. If you are not addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, kindly notify us by reply e-mail and delete this message immediately. Thank you.
Lähettäjä: main@... [mailto:main@...]
I am trying to run software packages/components through fossology. If i zip the package folder (with the jar file inside), will this successfully test all of the classes inside?
Re: VS: [FOSSology] Help a newbie
On Fri, Oct 12, 2018 at 08:05 AM, Martin von Willebrand wrote:
Is there any plans to use ALL features of SPDX 2.1 specification in future releases?
Key features in FOSSology 3.1 are:
I have tried the fossology installation in the ways of docker as well as from source.
Re: Is there any plans to use ALL features of SPDX 2.1 specification in future releases?
Michael C. Jaeger
Hello,toggle quoted messageShow quoted text
currently, I am not aware of the FOSSology project planning to support "ALL features of SPDX 2.1 specification in future releases", for a number of reasons, just a few examples:
* Spec 2.1 supports identification of code snippets (See section 5), currently fossology does not support it and I am not aware of plans by someone to contribute it
* Spec 2.1 support for example besides the copyright statement also a file contributor, which could be taken, maybe, from some SCM information. I am not aware of plans here neither
and so forth. I think FOSSology will support only parts of the SPDX 2.1 spec as they are covered by the application functionality.
I am not sure of that answer covers your question? The fact that you have used bold types letters in your e-mail provides a slight impression that you expect something in particular from the FOSSology project?
Maybe the following two issues provide also helpful information to you?
Please do not hesitate to clarify what you intended to say about our release notes or our idea of SPDX 2.1 document generation.
Kind regards, Michael
On 12. Mar 2019, at 13:30, thuy.tran.xh@... wrote:
Release of 3.5.0
Shaheem Azmal M MD
Particular corrections after RC1 can be found under RC2.
Mainly 3.5.0 adds more documentation, infrastructure improvements and support for brand new FOSSology REST API. A brief introduction about the REST API can be found at:
Moreover, new functionality has improved JSON output for nomos and restructured license detection for nomos. Last but not the least, FOSSology now have capabilities to ignore files specific to version control systems from the scanning improving scan times.
From the git commit history, we have following contributors since 3.4.0:
Please find the release and binary packages for Debian and Ubuntu based systems here https://github.com/fossology/fossology/releases/tag/3.5.0
Thanks & Regards
Shaheem Azmal M MD
Need to remove Debian packaging meta info from master branch
During our effort to publish FOSSology as a Debian package, we got few suggestions from the Debian community.
One of those suggestion is to remove the Debian packaging information (debian folder) from the master branch and put it into another branch like chore/debian/jessie.
This is done so to avoid conflicts as Debian maintainers will be editing this packaging information in the FOSSology mirror (hosted at Debian Sala). And any change in upstream can result in conflicts.
As this change will alter the packaging steps required by many of FOSSology users, we need your feedback.
I have opened an issue on GitHub for the same: https://github.com/fossology/fossology/issues/1341
Kindly respond either on this thread or on the GitHub issue if you have any concerns regarding the same.
With best regards,
GSoC 19 - Spasht Agent Documentation
FOSSology 3.6.0 release
Shaheem Azmal M MD
After two release candidates, making fixes for migration tests, unified report and load issues with tree-view, FOSSology is stable enough for a new release. The main features of the 3.6.0 release can be found under
[RC1](https://github.com/fossology/fossology/releases/tag/3.6.0-rc1). Particular corrections after RC1 can be found under [RC2](https://github.com/fossology/fossology/releases/tag/3.6.0-rc2).
Few interesting features in this release are:
Credits to 3.6.0
From the git commit history, we have following contributors since 3.5.0:
> @andi8086 <andreas.reichel@...>,
> @ag4ums <anupam.ghosh@...>,
> @hastagAB <classicayush@...>,
> @chienphamvu <chienphamvu@...>,
> @ChristopheRequillart <christophe.requillart@...>,
> @GMishx <mishra.gaurav@...>,
> @maxhbr <maximilian.huber@...>,
> @mcjaeger <michael.c.jaeger@...>,
> @NicolasToussaint <nicolas1.toussaint@...>,
> @PeterDaveHello <hsu@...>,
> @rlintu <raino.lintulampi@...>,
> @sandipbhuyan <sandipbhuyan@...>,
> @shaheemazmalmmd <shaheem.azmal@...>,
> @tiegz <tieg@...>,
> @vivekaindia <vvksindia@...>
Google Summer of Code final report, Integration of Software Heritage in FOSSology
I am Sandip Kumar Bhuyan was a Google Summer of Code 2019 intern for fossology organization. Thank you for selecting my proposal for this year GSoC. I think I have reached the expectation. I was working on integrating software heritage in fossology. I have completed the GSoC 2019 successfully. You can find my report in my blogpost Blog Post. I hope everyone will like it.
Fossology REST Clients for .NET
I like to inform you, that I have added a .NET implementation of the FOSSology REST API
to the FOSSology GitHub project:
The implementation covers most of the REST commands.
The unit tests will run on FOSSology in a docker container. Our goal is to add one further step
to the automation of software license compliance.
Do not hesitate to drop me an email in case of questions or suggestions.