Hello Patrick,
On May 13, 2011, at 10:25 AM, Moreau Patrick wrote:
> The licence tree function is no more avaliable. I send an email to Bruno
> Cornec and he answered that " it was replaced by License List". We are not
> fully satisfied by the Licence List. Indeed, we appreciated to be able to
> double-clicked and to access directly to the licence text in order to read it.
When you say that you want to read the license text, I think you mean that you
want to view the file that you uploaded. That is you want to view the file
that contains a license reference. This is opposed to view the text of the
actual license (e.g. the full GPL license text). Is that right?
> This is still possible to do that but it required to look for the file ans it
> takes more time. It could become difficult to perform analysis for important
> SW.
It sounds like you are using the license list as a license browser. Why don't
you use the license browser instead? Do you prefer the format of all the files
listed on a single page?
The purpose of the License List is to give people a list of all file paths and
their licenses so they can do processing outside of fossology. So for that,
the links were unwanted. Putting them in would be easy but I'd like to hear
from more people who use this function before deciding what to do. It would
really help to know why you use this instead of the license browser. If we
need the links in the License List, I'd be tempted to create a new web page
where you choose what you want in the list (like links or not), and if you want
to view or download it. I think that would satisfy the most people.
How much does the slowness of License List (or License Tree) bother you?
> We have also one question. When it is written for example "LGPL_v2.1+", we
> understand that the licence is not fully compliant. We don't know:
Why do you say that it is not compliant? To me "compliance" means that you
are complying with the license terms. LGPL, out of context, doesn't mean you
are in or out of compliance. I think I need more context around what you are
trying to do.
> - if all the licence texts are the same in this bucket
What is the definition of your bucket?
> or
> - if you put all the licence texts that are not fully compliant in it and, in
> this case, we would have different differences that we would have to detect.
Are you referring to the GPL demo bucket? If so, any license that has "GPL" in
it is put in that bucket. So LGPL, GPLv2, GPLv3, Affero GPL, ... all go in it.
That bucket was only a sample to show how to create a simple bucket. If you
are really using this bucket, you might consider other buckets to be more
useful. For example, a copyleft bucket, or a "source required" bucket. I've
been wanting to create those buckets for a while but haven't found the time to
figure out what should be in them.
> Thank you for support.
> Best regards
> Patrick
>
> PS: the new feature called Copyright/Email/URL Browser is very nice!
Thank you. :-)
Bob Gobeille
_______________________________________________
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology
