Hi, Thanks Gary. I will do well to join the tech call on Tuesday. In the meantime, I stubble on this https://github.com/ndip007/spdx-maven-plugin. As you will notice, that is my fork of your own repos.
I am currently looking through the code and thank goodness is clearing out some of my worries. I think with the work you have already done with the maven-plugin, we will just have to add a web-hook to Github and port the other dependence from the exiting maven-plugin code. Please kindly let me know if I am missing out on some details Thanks Ndip Tanyi On Sun, Mar 26, 2017 at 6:26 PM, <[email protected]> wrote: > Hi Ndip, > > > > Feel free to email the distribution list on any specific questions you > have. > > > > You can also join our tech call which is at 8AM Pacific time on Tuesday: > > > > Dial-in number: +1-857-216-2871 <(857)%20216-2871> > > Conference code: 38633 > > http://uberconference.com/SPDXTeam pin # 38633 > > > > We can also setup some time to discuss via chat or uberconference it he > above time doesn’t work. > > > > Gary > > > > *From:* Ndip Tanyi [mailto:[email protected]] > *Sent:* Sunday, March 26, 2017 5:33 AM > *To:* Gary O'Neall > *Cc:* [email protected]; [email protected] > *Subject:* Re: Google Summer of Code 2017 > > > > Hi Gary, > > Thank you for detailing out the expectations and deliverables of this > project. I have looked most of the resources links provided on the project > ideas page. As you pointed out, I still like to get more infos and ideas to > enable with drafting my proposal. > > Thanks > > Ndip Tanyi > > > > On Sat, Mar 25, 2017 at 6:43 PM, <[email protected]> wrote: > > Hi Ndip, > > > > I’m happy to hear of your interest on the Git plugins project. I think > this is one of the more interesting projects on the list. > > > > One of the challenges in this project is how to obtain good license > information from a general github account, so I would suggest an > incremental approach where we can introduce more sophisticated licensing > parsing information once the basic framework is in place. > > > > One of the first steps would be to setup the basic framework for a git > plugin that could be invoked for producing the SPDX documents – perhaps > just producing a dummy file to demonstrate we had the basic git hooks > working. > > > > Another step would be to produce a valid SPDX document based on the files > in github. This could be accomplished using one of the libraries in > github.com/spdx. The first SPDX document could be just for the package > without file information by setting the analyzed files flag to false. To > get started, we could set the license information to “UNKNOWN”. > > > > We could then start refining the license information based on the license > files present in github. This would require some parsing, but there have > already been some work done in this area in the NPM project. Github has > also been including more SPDX specific information which could be leveraged. > > > > Once we get the package level working, we could work in the file level > information – this would involve looking for license information in the > file. We could also start out by setting the license to UNKNOWN then > refining the license information with better parsing. > > > > Let me know if you would like more info/ideas. > > > > Gary > > > > *From:* Ndip Tanyi [mailto:[email protected]] > *Sent:* Friday, March 24, 2017 5:58 PM > *To:* [email protected]; [email protected]; > [email protected] > *Subject:* Google Summer of Code 2017 > > > > Hi Mentors, > > I am a first year Engineering student from the university of Alberta, > Canada. I will like to contribute with SPDX during this internship program. > > I find the project on creating "GIT Plugin to generate SPDX" interesting > and affordable looking at my skills level. > > I will like to discuss this project more with the mentors, so I can be > able to clearly spell out the various micro task in my milestones and > timeline as I work on my proposal for thesame. > > Hope to hear from you mentors soon > > > > Thanks > > Ndip Tanyi > > >
_______________________________________________ Spdx-tech mailing list [email protected] https://lists.spdx.org/mailman/listinfo/spdx-tech
