Re: [FOSSology] Handling duplicate files from multiple uploads....
On Aug 13, 2009, at 10:45 AM, thomas.j.mur...@kodak.com wrote: We would like our product teams to submit their source code for open source analysis at periodic times throughout the development cycle (at least once per year for active projects). Most likely they will create a .tar for their source code directory and upload to our fossology server. We would like to avoid re-analyzing and reporting files that have already been reported from earlier runs. Can you recommended a method for handling this situation without burdening the product development teams too much (i.e. so they don't have to keep track of the files and somehow filter them for subsequent runs)? Hi Tom, I just wrote (yesterday) the sql to do this in v 1.2. Take two uploads - report the license changes. Bob Gobeille b...@fossology.org ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Handling duplicate files from multiple uploads....
Bob and Mary, I was aware that reanalysis was not performed on duplicate files --- but how do we present the data so that the user isn't tracking down the same files that have been 'flagged' with a license. It looks like v 1.2 will indicate if there are license changes from one upload of the same file(s) to the next? I must have missed that in the features list how will it be reported? or is there a mockup screenshot of this capability? --- Basically, I just want the user to be able to zero in on the changes from the last upload relative to detected licenses. thanks Tom Murray Bob Gobeille bob.gobei...@hp.com 08/13/2009 12:56 PM To thomas.j.mur...@kodak.com thomas.j.mur...@kodak.com cc fossology@fossology.org Subject Re: [FOSSology] Handling duplicate files from multiple uploads On Aug 13, 2009, at 10:45 AM, thomas.j.mur...@kodak.com wrote: We would like our product teams to submit their source code for open source analysis at periodic times throughout the development cycle (at least once per year for active projects). Most likely they will create a .tar for their source code directory and upload to our fossology server. We would like to avoid re-analyzing and reporting files that have already been reported from earlier runs. Can you recommended a method for handling this situation without burdening the product development teams too much (i.e. so they don't have to keep track of the files and somehow filter them for subsequent runs)? Hi Tom, I just wrote (yesterday) the sql to do this in v 1.2. Take two uploads - report the license changes. Bob Gobeille b...@fossology.org ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Handling duplicate files from multiple uploads....
Tom, Here is a mockup of how it will be reported http://fossology.org/~bobg/1.2reqs/pkghistory.html. Is this useful? Mary From: thomas.j.mur...@kodak.com [mailto:thomas.j.mur...@kodak.com] Sent: Thursday, August 13, 2009 11:15 AM To: Gobeille, Robert; Laser, Mary Cc: fossology@fossology.org Subject: Re: [FOSSology] Handling duplicate files from multiple uploads Bob and Mary, I was aware that reanalysis was not performed on duplicate files --- but how do we present the data so that the user isn't tracking down the same files that have been 'flagged' with a license. It looks like v 1.2 will indicate if there are license changes from one upload of the same file(s) to the next? I must have missed that in the features list how will it be reported? or is there a mockup screenshot of this capability? --- Basically, I just want the user to be able to zero in on the changes from the last upload relative to detected licenses. thanks Tom Murray Bob Gobeille bob.gobei...@hp.com 08/13/2009 12:56 PM To thomas.j.mur...@kodak.com thomas.j.mur...@kodak.com cc fossology@fossology.org Subject Re: [FOSSology] Handling duplicate files from multiple uploads On Aug 13, 2009, at 10:45 AM, thomas.j.mur...@kodak.commailto:thomas.j.mur...@kodak.com wrote: We would like our product teams to submit their source code for open source analysis at periodic times throughout the development cycle (at least once per year for active projects). Most likely they will create a .tar for their source code directory and upload to our fossology server. We would like to avoid re-analyzing and reporting files that have already been reported from earlier runs. Can you recommended a method for handling this situation without burdening the product development teams too much (i.e. so they don't have to keep track of the files and somehow filter them for subsequent runs)? Hi Tom, I just wrote (yesterday) the sql to do this in v 1.2. Take two uploads - report the license changes. Bob Gobeille b...@fossology.orgmailto:b...@fossology.org ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Handling duplicate files from multiple uploads....
I just added the pkg and archive diffs (numbers 9, 10): http://fossology.org/task_list I need to do a mockup for the file diffs. If you have something in particular in mind, please mock it up your self and send it to me. Bob Gobeille b...@fossology.org On Aug 13, 2009, at 11:18 AM, Laser, Mary wrote: Tom, Here is a mockup of how it will be reported http://fossology.org/~bobg/1.2reqs/pkghistory.html . Is this useful? Mary From: thomas.j.mur...@kodak.com [mailto:thomas.j.mur...@kodak.com] Sent: Thursday, August 13, 2009 11:15 AM To: Gobeille, Robert; Laser, Mary Cc: fossology@fossology.org Subject: Re: [FOSSology] Handling duplicate files from multiple uploads Bob and Mary, I was aware that reanalysis was not performed on duplicate files --- but how do we present the data so that the user isn't tracking down the same files that have been 'flagged' with a license. It looks like v 1.2 will indicate if there are license changes from one upload of the same file(s) to the next? I must have missed that in the features list how will it be reported? or is there a mockup screenshot of this capability? --- Basically, I just want the user to be able to zero in on the changes from the last upload relative to detected licenses. thanks Tom Murray ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] Handling duplicate files from multiple uploads....
Bob, This would be another benefit of having FOSSology point back to Subversion to get the files it needs. From: Bob Gobeille bob.gobei...@hp.com To: thomas.j.mur...@kodak.com thomas.j.mur...@kodak.com Cc: fossology@fossology.org fossology@fossology.org Date: 08/13/2009 04:04 PM Subject: Re: [FOSSology] Handling duplicate files from multiple uploads Sent by: fossology-boun...@fossology.org Thanks Tom. That's good. How does one select or recognize the previous version? bob On Aug 13, 2009, at 1:19 PM, thomas.j.mur...@kodak.com wrote: How about something like this? ATT1.gifThanks, Tom Murray___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
