Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Philippe Ombredanne
    @pombredanne

    @tyrion re:

    As far as I can understand, both texts are needed. You can distinguish which license is used in each file from the preamble in each file I guess

    and where there are only a gpl and lgpl at the root and nothing else, the license is not clear at all and that happens.

    I think the FSF did goof there IMHO
    @tyrion (pardon my french)
    ;)
    a single text for a license would have been much better , as it was before
    Germano Gabbianelli
    @tyrion

    a single text for a license would have been much better , as it was before

    I think I agree with this, not sure why it is this way

    Germano Gabbianelli
    @tyrion
    Does anybody know why the GPL here https://github.com/spdx/license-list-data/blob/master/text/GPL-3.0-or-later.txt looks formatted differenty than the official one? https://www.gnu.org/licenses/gpl-3.0.txt
    Is it intended, or should I open an issue about it?
    Philippe Ombredanne
    @pombredanne
    @tyrion open an issue :)
    that's unlikely intended
    @tyrion note that in general, since texts @ SPDX contain possible markup and sometimes comments they are generally poorly suited to be used as reference texts
    Germano Gabbianelli
    @tyrion
    Umh, reading here ( spdx/license-list-data#32 ) it seems the text versions are generated from the HTML ones
    Philippe Ombredanne
    @pombredanne
    @tyrion from the XML ones rather https://github.com/spdx/license-list-XML/ ... but this is a lossy process for sure.
    init AG
    @init-dcat-ap-de
    Hi, I just created a new issue: spdx/spdx-spec#144
    Also: the comment for http://spdx.org/rdf/terms#algorithm still says: "Identifies the algorithm used to produce the subject Checksum. Currently, SHA-1 is the only supported algorithm. It is anticipated that other algorithms will be supported at a later time. "
    Even though you now support three (and hopefully soon even more) algorithms
    Shabd Saran
    @saran-shabd
    hello, I want to get started with contributing. where should I begin with?
    I am good at Java and Python3
    Rohit Lodha
    @rtgdk
    Welcome to SPDX @saran-shabd . Here are some links to understand what SPDX is about : https://github.com/david-a-wheeler/spdx-tutorial#spdx-tutorial , https://spdx.org/sites/cpstandard/files/pages/files/fosdem_2015-v2-static.pdf . You can start contributing by taking up any issue and raising a PR to fix them in any SPDX repo. Find all the repos here - http://github.com/spdx.
    Since you are already familiar with Java and python, do check out tools, tools-python and spdx-online-tools repos
    Smit Sanghavi
    @smit-s
    Hello, I am new to this community...I have gone through the tutorial. What shall I do next to contribute?
    Rohit Lodha
    @rtgdk
    @smit-s Pick up any issue from any repo you would like to contribute and raise a PR for that.
    mohitg55555
    @mohitg55555
    Hello there, My name is Mohit Pandey i have experience of doing projects in java, python and several new algorithm , technologies. I want to contribute to the organization this year. What shall i do next to contribute?
    Gary O'Neall
    @goneall
    Greetings and welcome to the SPDX community. There are a number of SPDX tools in the git repository referenced previously by @rtgdk Feel free to take on any issues in the repos.
    Philippe Ombredanne
    @pombredanne
    @mohitg55555 @smit-s welcome :wave:
    mohitg55555
    @mohitg55555
    thaks @pombredanne
    RishabhBhatnagar
    @RishabhBhatnagar
    Hello all, I am RishabhBhatnagar. I want to try contributing to this community again for GSOC 2020. I would like to contribute to tools-golang project. Referencing spdx/tools-golang#7 this issue, I am making a parser for RDF files. Where can I find more examples of RDF files that SPDX is using?? I found one of the RDF files here.
    Rohit Lodha
    @rtgdk
    @RishabhBhatnagar Here are some rdf files provided by Steve Winslow. https://drive.google.com/drive/folders/16xVotiY1YPztHMgdzeNTyoWl161dQ6Hy?usp=sharing
    These were created with various tools, so they may be formatted or arranged differently. And some are version 2.0 of the spec rather than 2.1, but those should be forward-compatible so should still work with the v2.1 parser.
    Abhishek Gaur
    @abhishekspeer
    Welcome @RishabhBhatnagar! Thank you for your interest in contributing to https://github.com/spdx/tools-golang Project. I had worked with the files @rtgdk has shared earlier, so feel free to ask in case you have any queries related to it. Good luck!
    RishabhBhatnagar
    @RishabhBhatnagar

    For converting tools-golang repository into a module, releases must be defined. We can put a back-dated tag for past releases.

    In the repository, there is a v0 directory and some of the subdirectories of v0 have their name of type dir2v1(for example builder2v1).
    I am slightly confused between the versions. If current HEAD is version 2.1.0, then, which commit marks the last of version 1 or version 0??

    spdx/tools-golang@df8bf23 - this is the last commit which doesn't have directories with 2v1 in their names. Does this commit mark the end of version 0 or 1??

    RishabhBhatnagar
    @RishabhBhatnagar
    Ignoring the previous question,
    Let me know if I'm wrong.
    The current tools-golang codebase is in version 0 which is capable of dealing with spdx documents version 2.1.
    Abhishek Gaur
    @abhishekspeer
    Yes @RishabhBhatnagar, you’re going in the right direction. The current version of tools-golang deals mainly with version 2.1 of SPDX Documents and as you said, you can find the codebase for the same in v0. Also, I’d suggest you to go through the examples if you’ve not already to get a better understanding.
    Rohit Lodha
    @rtgdk
    @RishabhBhatnagar Please also report these findings and questions on the related github issue page since Steve is more active on github and can provide more deep thoughts on how to proceed.
    RishabhBhatnagar
    @RishabhBhatnagar
    @abhishekspeer, thank you clarification. I've already went through version 2.1 related documents as I had built a parser in python language for demonstration before gsoc2019.
    @rtgdk, I'll surely update the question on related github issue page.
    Purvansh Singh
    @Purvanshsingh
    Hello all, I am a newcomer and a little familiar with opensource, had worked on several Python projects, I want to contribute to this organization can anyone guide me from where and how should I start?
    Abhishek Gaur
    @abhishekspeer
    Welcome to SPDX @Purvanshsingh.
    You can start by reading what SPDX is:
    https://github.com/david-a-wheeler/spdx-tutorial/.
    Please find all the project repositories here: https://github.com/spdx
    Also, feel free to start contributing by working on any of the issues and raising a PR for the same.
    Good luck!
    Preet Mishra
    @preetmishra
    Hello, everyone. I am Preet, a 3rd-year undergraduate from DIT University, Dehradun, India. I am worked with Python for my personal projects. I am looking forward to contributing to SPDX and GSOC 2020.
    Philippe Ombredanne
    @pombredanne
    @preetmishra welcome!
    Rohit Lodha
    @rtgdk
    @preetmishra Welcome to spdx! You can find all the relevant how-to-start guide in the previous messages.
    Preet Mishra
    @preetmishra
    Thank you so much.
    I couldn't find any active good first issue in https://github.com/spdx/tools-python/issues. Where can I start contributing?
    Rohit Lodha
    @rtgdk
    @preetmishra There are many issues in tools-python which can give you a good overview of the project. If you are interested in python, you can check https://github.com/spdx/spdx-online-tools/issues too.
    Philippe Ombredanne
    @pombredanne
    @preetmishra and you can ping me here if you want to tackle some of these
    Krishduttm
    @Krishduttm
    Hello everyone, my name is Krishna. i am a first year under-graduate. i have decent knowledge in python programming. i would like to contribute to SPDX. since i am moderately new to this platform can anyone help me get started?
    Abhishek Gaur
    @abhishekspeer
    Welcome @Krishduttm. Please find the relevant links with previous messages to know more about SPDX. As you are familiar with python feel free to check out the project links attached below and start contributing. Good luck!
    https://github.com/spdx/tools-python/issues
    https://github.com/spdx/spdx-online-tools/issues
    Preet Mishra
    @preetmishra
    Thank you!
    Preet Mishra
    @preetmishra
    @pombredanne I would like to tackle some. Right now I am finding it difficult to find a starting point. Can you please help me with that whenever you've time?
    Philippe Ombredanne
    @pombredanne
    @preetmishra will do tomorrow :+1:
    @/all
    [ANNOUNCE] if you care about open source compliance automation and if you are going to FOSDEM end of January there is a one day hackathon and meeting taking place the day before FOSDEM on Friday January 31st as fringe event. The topic is open source compliance tooling and automation... the format is an unconference. I expect several open source projects in that space to be represented there including ORT, Fossology, ClearlyDefined, SPDX tools of course, Scancode and more.
    
    I am co-organizing this with Michael Jaeger from Fossology.
    
    See https://docs.google.com/document/d/1UphruKKAlsoUEidPCwTF2LCcHFnQkvQCQ9luTXfDupw/edit#heading=h.p2d7mni4lrcu for details.
    
    To "register", just add you name to this document!
    I look forward seeing you there!