Dear all, My name is uday
I would like to participate from Melbourne VIC Australia. I will configure all the repos for codescans and static analysis (security and code quality) with sonarqube on sonarcloud. No additional login required, GitHub handle would be sufficient. I will not be able to be part of the calls and emails will be the primary source of my communication. Additionally, I am looking at exploring graphql for spdx. Cheers Uday On Fri., 11 Jan. 2019, 7:00 am Steve Winslow <[email protected] wrote: > That works for me! If you can create an empty repo with tools-golang as > the name, I'll move the code over and start making internal changes to > refer to the new location. > > On Thu, Jan 10, 2019 at 2:58 PM Gary O'Neall <[email protected]> > wrote: > >> Hi Steve, >> >> >> >> How about tools-golang as a name? This would be consistent with the >> current naming conventions for the SPDX repos. >> >> >> >> We could rename tools-go to ATTIC-tools-go so there isn’t any confusion. >> >> >> >> Gary >> >> >> >> *From:* Steve Winslow <[email protected]> >> *Sent:* Thursday, January 10, 2019 11:24 AM >> *To:* Gary O'Neall <[email protected]> >> *Cc:* spdx-tech <[email protected]> >> *Subject:* Re: [spdx-tech] Google Summer of Code 2019 >> >> >> >> Hi Gary, >> >> >> >> I'd be happy to have my SPDX Golang tools brought into the official SPDX >> tooling org! >> >> >> >> Since it's a rewrite rather than an update of the existing tools, I'd >> suggest that we may want to leave the existing tools-go repo in place (and >> mark it as deprecated), in case other projects are making use of them. >> Rather than just replacing the existing repo with the new one. My new >> version is currently at https://github.com/swinslow/spdx-go; perhaps we >> can use "spdx-go" for the name of the new repo also? >> >> >> >> Very glad to have any and all input from other Golang users on this list, >> regarding any changes or improvements for these tools =) >> >> >> >> I updated the GSoC wiki page section on the Golang tools, but can revise >> it further if we do go ahead and bring in the new tools. >> >> >> >> Thanks, >> >> Steve >> >> >> >> On Thu, Jan 10, 2019 at 1:40 PM Gary O'Neall <[email protected]> >> wrote: >> >> Hi Steve, >> >> >> >> Catching up on the GSoC emails: >> >> >> >> *From:* Steve Winslow <[email protected]> >> *Sent:* Monday, January 7, 2019 5:51 AM >> *To:* Gary O'Neall <[email protected]> >> *Cc:* spdx-tech <[email protected]> >> *Subject:* Re: [spdx-tech] Google Summer of Code 2019 >> >> >> >> Hi Gary, thanks for kicking this off! A few thoughts: >> >> >> >> * For the project "Update Parser Libraries to SPDX 2.1 for Go", I've >> recently started a replacement Golang library which handles version 2.1 of >> the spec, and includes near-full test coverage and some other features. >> It's currently at https://github.com/swinslow/spdx-go -- there's plenty >> of opportunities for this to be improved. Most notably it's only handling >> tag-value files at present, so RDF import/export has yet to be added. But >> I'd be interested in others' thoughts if this might be a good baseline for >> an updated version of the official Golang tools, and for a summer student >> to work on. I'd be happy to volunteer as a mentor for this. >> >> *[G.O.] Why don’t you update the definition of this project to be to >> support multiple formats including RDF and perhaps the XML, JSON and YAML >> formats we’re discussing. Should we go ahead and merge your version into >> the official SPDX repo? I I just invited you to the repo which should >> provide write access.* >> >> >> >> * For the project "SPDX Specification in MarkDown", I think this is >> basically done, isn't it? I'm not sure if it was part of GSoC or not, but I >> think the move from Google Docs to GitHub + MarkDown is complete. (Or if it >> isn't, then I've been looking in the wrong place.) =) >> >> *[G.O.] I’ll check with Kate and Thomas on this one. I think there is >> more work to be done, but it may not be enough for a project.* >> >> >> >> * I'd also be happy to be a mentor if there are any students interested >> in the "SPDX Spec Views for legal counsels and developers" project. >> >> *[G.O.] Great! Go ahead and add yourself as a mentor.* >> >> >> >> I'll give some thought to any other tooling ideas that come to mind for >> possible GSoC projects. >> >> >> >> Thanks, >> >> Steve >> >> >> >> >> >> >> >> >> >> On Sun, Jan 6, 2019 at 2:34 PM Gary O'Neall <[email protected]> >> wrote: >> >> Google summer of code 2019 will open up to organization applications on >> January 15th. >> >> >> >> If you are interested in being a mentor this year, please let me know >> which project ideas you would be interested in mentoring. >> >> >> >> We also need to update our list of project ideas. >> >> >> >> I removed the projects from last year which were completed. Here is the >> updated ideas page: https://wiki.spdx.org/view/GSOC/GSOC_ProjectIdeas >> >> >> >> We can definitely use more ideas! >> >> >> >> If you would like to add a project idea, feel free to add to the ideas >> wiki or reply to this distribution list with a proposal. >> >> >> >> Thanks, >> Gary >> >> >> >> >> >> ------------------------------------------------- >> >> Gary O'Neall >> >> Principal Consultant >> >> Source Auditor Inc. >> >> Mobile: 408.805.0586 >> >> Email: [email protected] >> >> >> >> >> >> -- >> >> Steve Winslow >> Director of Strategic Programs >> The Linux Foundation >> >> [email protected] >> >> >> >> -- >> >> Steve Winslow >> Director of Strategic Programs >> The Linux Foundation >> >> [email protected] >> > > > -- > Steve Winslow > Director of Strategic Programs > The Linux Foundation > [email protected] > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#3635): https://lists.spdx.org/g/Spdx-tech/message/3635 Mute This Topic: https://lists.spdx.org/mt/28955546/21656 Group Owner: [email protected] Unsubscribe: https://lists.spdx.org/g/Spdx-tech/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
