Hi mentors,

After some brainstorming sessions and research, here are some aspects of
the project which I would like us to be clear with.

For me it would make sense for us to consider only files that contain
program instructions, possibly with comments, written using a
human-readable programming language, usually as ordinary text as source
files. For our purpose, an intermediate file "is not real source code and
does not count as source file since there are generated by the machine.

>From this perspective, to get our source files, we'll get the list of mime
type of all programming languages and for each mime types we list the
extensions we want to consider.

In terms of the sketch of what should be parametrized, the grader tool, I
think, should be taking just the spdx document of the package to be
evaluated.

Please could you assess these so we discuss more tomorrow, during the
meeting?

Thanks.



On Thu, May 25, 2017 at 7:30 PM, Kate Stewart <[email protected]>
wrote:

> Hi Krys
>
> On Wed, May 24, 2017 at 3:56 AM, Krys Nuvadga <[email protected]>
> wrote:
>
>> Hi kate,
>>
>> I am sending your an early update on my progress as of our last hangout.
>> ---------------Updates--------------------
>>
>> 1) Work with Scancode <https://github.com/nexB/scancode-toolkit> to
>> generate license and copyright infos
>>
>
> Great.   Glad you're able to generate SPDX documents with it now.
> Between this tool and FOSSology, we should be able to create some good
> input files for testing the tool.
>
>
>>
>> 2) Played aronud with dosocs2 <https://github.com/sschuberth/dosocs2>
>> toolkit to create and store SPDX 2.0 document in  SQlite database
>>
>
> Probably best to focus on using ScanCode & FOSSology at this point, as
> there isn't anyone maintaining dosocs2 at the moment.
>
>
>>
>> 3) I also looked at Linguist <https://github.com/github/linguist>. This
>> was an attempt to find a solution to one of the open questions in the
>> problem statement which is to determine what files should be considered as
>> source files.
>>
>
> Very good.   Figuring out how we get source files identified with
> confidence is one of the aspects we need to figure out for the tooling.
>
> Thank you for sending your summary to the mail list so others can follow
> and chime in if they have ideas.  :-)
>
> Kate
>



-- 
krys Nuvadga
Piar, Inc.
_______________________________________________
Spdx-tech mailing list
[email protected]
https://lists.spdx.org/mailman/listinfo/spdx-tech

Reply via email to