SPDX Wiki - User contributions [en]

User talk:Rday

2020-04-19T20:36:02Z

Lfadmin:

test to generate email 
another test 
test 
test2 
test3

User talk:Rday

2020-04-19T19:03:47Z

Lfadmin:

test to generate email 
another test 
test 
test2

Technical Team/Minutes/2017-07-11

2017-07-18T17:53:37Z

Lfadmin: /* Attendees */

July 11, 2017
== Attendees ==
* Gary O’Neall
* Thomas Steenberg
* Anna Buhman
* Yev Bronshteyn
* Kate Stewart
* Philippe Ombredanne
* Krys Nuvadga
* Rohit Lodha
* Alexios Zavras
* Aleksandr Lisianoi

==Student Reports==
* Updates from Krys, Alex, and Anna
* All projects making progress – details in gitter
* Anna will test the github project against a clone of the Linux kernel and post the results to gitter
==Spec Github Repository==
* Discussed Trevor’s proposal
* Discussed where to host the HTML web pages – github or spdx.org
** Consensus on spdx.org
** Will confirm with Jack
* Moving to issues to track spec bugs and enhancements
==Next SPDX Specification==
* PackageTag
** See notes in https://docs.google.com/document/d/1vJqWGU02ynzrJ5CvmX1z2mBssOSpuBvuKene8jVJGNI/edit

[[Category:Technical|Minutes]]
[[Category:Minutes]]

Technical Team/Minutes/2017-06-13

2017-07-18T17:06:56Z

Lfadmin:

June 13, 2017
== Attendees ==
* Gary O’Neall
* Thomas Steenberg
* Kate Stewart
* Anna Buhman
* Krys Nuvadga
* Alexios Zavras
* Yev Bronshteyn
* Uday Korlimarla

==Spec Git Repository==
* https://github.com/tsteenbe/spdx-spec
* Nearly complete
* Releases fixed
* History is in sync with the SPDX release dates
* Need to add contributing.md
* Worked needed for TravisCI

==Next Release Project==
* see https://github.com/tsteenbe/spdx-spec
* Discussion on optional fields
** Agree to make snippet byte range optional
** PackageLicenseDeclared
*** Semantics different from other fields
** VerificationCode
*** Discussed public repositories having a checksum already
^^^ Discussed whether required since file checksums are in the SPDX document – although there is also a proposal to not include all files in the SPDX document
*** Tabled the discussion for now
** Document namespace – needed for external document references.
*** Some confusion on how to apply – seems arbitrary
*** Only requirement is that it is unique
*** Agree to update the documentation and add best practices to describe this field more clearly
** Document name
*** Required for the RDF model
*** Could provide some best practices and/or better documentation
*** Proposal to have a default of “Document” since we have a namespace
[[Category:Technical|Minutes]]
[[Category:Minutes]]

Technical Team/Minutes/2017-06-13

2017-07-18T17:06:38Z

Lfadmin:

Technical Team/Minutes/2017-07-11

2017-07-18T16:54:01Z

Lfadmin:

Technical Team/Minutes/2017-05-15

2017-07-13T21:04:51Z

Lfadmin:

May 15, 2017
== Attendees ==
* Gary O’Neall
* Sai Uday Shankar
* Thomas Steenberg
* Kate Stewart
* Anna Buhman
* Yev Bronshteyn

==SPDX specification to github==
* Philippe gave Thomas access to repository
* Thomas still moving over, Appendix 1. Base content is there. see:
** https://github.com/tsteenbe/specification/blob/master/chapters/appendix-I-SPDX-license-list.md
** https://github.com/tsteenbe/specification/blob/master/chapters/7-relationships-between-SPDX-elements.md
* Basic markdown is present. will work on Readme & contribution MD before pushing live.
* Improve rendering in .pdf in progress - works on mac. Willl send announcement to mail list as soon as pushed
==GSoC Coordination==
* Gary: online validation tools overlap concern, Kate clarified – only the titles are the same
* Uday: how will someone use a resource to get started?
** Gary - mirroring same AWS instance from OpenChain, and make it available for students to use. $35/month to host. Same account and create an instance. Work out accounting.
** Approval from OpenChain group to use their instance for additional work. Set up right credentials and access. Elastic beanstalk. Push from development to production cleanly.
** Need a redirect subdomain mapping for AWS. Do this during bonding period. Will start creating github repositories - github.com/spdx/
**Gary will set up repositories in SPDX github account - just needs to know name of repository and github id. (Kate to send in for Krys).
==Github cleanup==
* Some of the repos were contributed by other companies. (airs, osip) - would like their permission to rename/relocate
* Some created by core team but should be removed. (gitolite admin, spdx-rdf-vocabulary)
* Thomas & Gary to research best practice for dealing with older repositories, pinning them, deprecated, other solution

==Next SPDX Spec==
* See https://docs.google.com/document/d/1vJqWGU02ynzrJ5CvmX1z2mBssOSpuBvuKene8jVJGNI/edit
* relationships in license
** Agree this is a good proposal
** Gary will take to legal for discussion
** Result an appendix
* Dependency version range
** A solution to the problem when licenses may not be determinable at build time due to version range rather than specific version
** Agree this is a good problem to solve
* Size of File optional
** Some concern on additional fields being added to the spec, but it is optional
** Agree this is OK to add
* Discussion on Limited information for some file contents of package, but not requiring all the files of the license
** Can we use filesAnalyzed=false?
*** Doesn’t solve all the use cases
** Discussion on views as being a solution
*** Discussion on whether this is a standard, tool, or best practices
*** SPARQL can be provided for views
** Is this reducing the minimum to allow smaller documents

[[Category:Technical|Minutes]]
[[Category:Minutes]]

Technical Team/Minutes/2017-05-15

2017-07-13T21:04:38Z

Lfadmin:

Technical Team/Minutes/2017-06-20

2017-07-13T21:02:17Z

Lfadmin:

June 20, 2017
== Attendees ==
* Gary O’Neall
* Thomas Steenberg
* Anna Buhman
* Krys Nuvadga
* Alexios Zavras
* Yev Bronshteyn
* Uday Korlimarla

==GitHub SPDX Project Architecture ==
* Review architecture for github spdx project
* Proposal – use github webhooks for the user integration and integrate multiple back-end scanners through a REST based API
* Reference: https://github.com/spdx/spdx-github/wiki/Architecture
* Yev suggested integrating with a Continuous Integration system may be a better approach
** Yev suggested generating outside of github was an overkill, Thomas agreed
** Gary suggested focus could be on open source project originators where dependencies are not as prevalent – example, NodeJS where there are only 2-3 files
** Gary responded that there is a separate project proposal for integration system hooks, and this project is focused on github
* Discussion on the multiple scanner integration
** Could use the integration for a build oriented SPDX generator (such as the Maven build) – Gary will build an integration once the tool is available
**Existing scanners can be “wrapped” by the API – either a command line or a library call
* Discussion on authentication
** Primary mechanism would be github
** Need to authenticate external services if used
** First release, we could scope it to everything running on a local server
== Other Topics==
* Further discussion on next SPDX spec postponed to next week, waiting larger quorum
* Thomas has first draft of OpenChain specification 1.0 in Markdown, building HTML via GitBook: https://github.com/tsteenbe/openchain-spec
** work-in-progress; history being re-written

[[Category:Technical|Minutes]]
[[Category:Minutes]]

Technical Team/Minutes

2017-07-13T18:33:09Z

Lfadmin:

{{#subpages:|format=ul|kidsonly=no|pathstyle=none|sort=desc}}

[[Category:Technical|Minutes]]
[[Category:Minutes]]
[[Technical Team/Minutes/CollabSummitPhotos|White Boards from Collab Summit]]

Technical Team/Minutes

2017-07-13T18:32:54Z

Lfadmin:

{{#subpages:|format=ul|kidsonly=no|pathstyle=none|sort=desc}}

[[Category:Technical|Minutes]]
[[Category:Minutes]]
[[Category:Technical|Minutes]]
[[Category:Minutes]]
[[Technical Team/Minutes/CollabSummitPhotos|White Boards from Collab Summit]]

Technical Team/Minutes/2017-06-13

2017-07-13T17:59:39Z

Lfadmin:

Technical Team/Minutes/2017-06-20

2017-07-13T17:59:36Z

Lfadmin:

June 20, 2017
== Attendees ==
* Gary O’Neall
* Thomas Steenberg
* Anna Buhman
* Krys Nuvadga
* Alexios Zavras
* Yev Bronshteyn
* Uday Korlimarla

==GitHub SPDX Project Architecture ==
* Review architecture for github spdx project
* Proposal – use github webhooks for the user integration and integrate multiple back-end scanners through a REST based API
* Reference: https://github.com/spdx/spdx-github/wiki/Architecture
* Yev suggested integrating with a Continuous Integration system may be a better approach
** Yev suggested generating outside of github was an overkill, Thomas agreed
** Gary suggested focus could be on open source project originators where dependencies are not as prevalent – example, NodeJS where there are only 2-3 files
** Gary responded that there is a separate project proposal for integration system hooks, and this project is focused on github
* Discussion on the multiple scanner integration
** Could use the integration for a build oriented SPDX generator (such as the Maven build) – Gary will build an integration once the tool is available
**Existing scanners can be “wrapped” by the API – either a command line or a library call
* Discussion on authentication
** Primary mechanism would be github
** Need to authenticate external services if used
** First release, we could scope it to everything running on a local server
== Other Topics==
* Further discussion on next SPDX spec postponed to next week, waiting larger quorum
* Thomas has first draft of OpenChain specification 1.0 in Markdown, building HTML via GitBook: https://github.com/tsteenbe/openchain-spec
** work-in-progress; history being re-written
[[Category:Technical|Minutes]]
[[Category:Minutes]]

Technical Team/Minutes/2017-06-13

2017-07-13T17:58:31Z

Lfadmin: IT helpdesk team reviewing

June 13, 2017
== Attendees ==
* Gary O’Neall
* Thomas Steenberg
* Kate Stewart
* Anna Buhman
* Krys Nuvadga
* Alexios Zavras
* Yev Bronshteyn
* Uday Korlimarla

==Spec Git Repository==
* https://github.com/tsteenbe/spdx-spec
* Nearly complete
* Releases fixed
* History is in sync with the SPDX release dates
* Need to add contributing.md
* Worked needed for TravisCI

==Next Release Project==
* see https://github.com/tsteenbe/spdx-spec
* Discussion on optional fields
** Agree to make snippet byte range optional
** PackageLicenseDeclared
*** Semantics different from other fields
** VerificationCode
*** Discussed public repositories having a checksum already
^^^ Discussed whether required since file checksums are in the SPDX document – although there is also a proposal to not include all files in the SPDX document
*** Tabled the discussion for now
** Document namespace – needed for external document references.
*** Some confusion on how to apply – seems arbitrary
*** Only requirement is that it is unique
*** Agree to update the documentation and add best practices to describe this field more clearly
** Document name
*** Required for the RDF model
*** Could provide some best practices and/or better documentation
*** Proposal to have a default of “Document” since we have a namespace

[[Category:Technical|Minutes]]
[[Category:Minutes]]

Technical Team/Minutes/2010-11-16

2017-07-11T21:40:09Z

Lfadmin:

== Attendees ==

* Kate Stewart
* Bill Schineller
* Peter Williams
* Gary O'Neall

== Topics ==

* we now have a mailing list for technical team (thanks Kate) self-register at [[Technical Team] (click the 'mailing list here' link http://lists.spdx.org/mailman/listinfo/spdx-tech )
* Peter reviewed the re-vamped structure of spec.html currently maintained in master branch of his github repo at https://github.com/pezra/spdx-spec spec.html has directives for the rake task to include contents of section_2,3,4,5 such that one html file is generated with the complete ontology. Team asked that the generated file also get committed (to lower the barrier of entry for someone wishing to look at the rendered html during development)
* Reviewed Peter's writeup of the composite license proposal at [[Technical_Team/Proposals/2010-10-21/Composite_licensing]]. Team agreed the "OrLater" concept in the proposal best be split out into a separate proposal. Bill asked technical question about whether the references to standard spdx licenses should use rdf:resource vs. rdf:Description... rdf:about Bill asked whether the e.g. DisjunctiveLicenseSet should itself be a subclass of spdx:License; Peter's recommendation was that it be another object in the range of properties which currently have License in their range.
* Mozilla Tri-License usage scenario for composite license. Proposal shows its usage in Package/Declared and Discovered licenses. How to avoid repeating for every File object in a) RDF format and b) tag-value format? Kate noted that if the 'Mozilla Tri-License' is well known to exist in the wild, then it is a good candidate for inclusion in the SPDX license list. But more generally, team agreed it would be good form if a 'composite license' is encountered to model it once within the NonStandardLicense section of the SPDXDoc with a locally unique id and reference it from other places within the document.
* re: the artifactOf proposal, Kate noted that the tag-value example was unclear. Peter and Kate discussed a convention...
* Peter raised idea of additional properties between licenses such as 'laterVersionOf'
* Bill asked about use case of SPDX analysis reporting the discovery of a phrase like "This file is licensed under the GPL' - clearly too ambiguous to map to one of the standard SPDX licenses, but perhaps of interest to consumer of an SPDX doc. With current spec, *could* report such as a NonStandardLicense whenever encountered. Raised idea (in future rev of spec?) of modeling license 'families' as an additional way to express associations between licenses, and allow reporting such a discovery in a standard way.
* Time expired on the meeting.

[[Category:Technical|Minutes]]
[[Category:Minutes]]

Technical Team/Minutes/2010-11-16

2017-07-11T21:35:25Z

Lfadmin: LF IT testing minor edit to tags

Technical Team

2015-03-24T21:59:04Z

Lfadmin:

This is the working area for the technical team. This team has primary responsibility for drafting the specification and developing documentation, templates, samples and tools.

The Technical Team meets weekly on Tuesdays at 18:00 GMT (10:00AM PT, 11:00 MT, 12:00PM CT, 1:00PM ET).
Dial-in number: 877.435.0230 (U.S. and Canada) or 1.253.336.6732 (International)
Conference code: 7833942033

Screenshare:
https://blackducksoftware.adobeconnect.com/spdxrdf/

* [[Technical_Team/SPDX_Specification_Versions|SPDX Specification Versions]]
* [[Technical_Team/SPDX_RDF_Vocabularies_and_Terms|SPDX RDF Vocabularies and Terms]]
* [[Technical_Team/Minutes|Meeting Minutes for the Technical Team]]
* [[Technical_Team/Priorities|Current Priorities and Work in Progress for the Technical Team]]
* [[Technical_Team/Old|Older Items for the Technical Team]]
* [[Technical_Team/Field_Names|Field Names]]
* [[Technical_Team/Spreadsheet_Template|Spreadsheet Template]]

[[Category:Technical]] [[Category:TestCategory]]

Testpage

2015-02-13T18:22:20Z

Lfadmin: Created page with "This is a page to test functionality after software updates."

This is a page to test functionality after software updates.

SPDX Wiki:Terms of Service

2015-01-26T19:04:30Z

Lfadmin:

Please refer to the [https://www.linuxfoundation.org/terms Linux Foundation Terms of Use.]

SPDX Wiki:Terms of Service

2015-01-26T19:04:14Z

Lfadmin: Created page with "Please refer to the [https://www.linuxfoundation.org/terms Linux Foundation Terms of Service.]"

Please refer to the [https://www.linuxfoundation.org/terms Linux Foundation Terms of Service.]

MediaWiki:Termsofservicepage

2015-01-26T19:02:30Z

Lfadmin: Created page with "Project: Terms of Service"

Project: Terms of Service

MediaWiki:Termsofservice

2015-01-26T19:01:33Z

Lfadmin: Created page with "Terms of Service"

Business Team/Minutes

2014-07-07T20:38:03Z

Lfadmin: switch kidsonly to no

These are the minutes and decisions for the Business Team.

{{#subpages:format=ul|kidsonly=no|pathstyle=none|sort=desc}}

[[Category:Business|Minutes]]

Business Team/Minutes

2014-07-07T20:27:23Z

Lfadmin: tweak subpages format

These are the minutes and decisions for the Business Team.

{{#subpages:format=ul|kidsonly=yes|pathstyle=none|sort=desc}}

[[Category:Business|Minutes]]

Legal Team

2013-04-11T19:43:01Z

Lfadmin:

This is the working area for the Legal Team. The SPDX Legal Team supports and provides recommendations to the SPDX working groups regarding licensing issues for the specification itself; maintains the [http://spdx.org/licenses/ SPDX License List]; and promotes the SPDX --[[User:Lfadmin|Lfadmin]] ([[User talk:Lfadmin|talk]]) 19:43, 11 April 2013 (UTC)specification
to the legal community at-large.

The Legal Team meets every other Thursday at 18:00 GMT (10:00AM PT, 11:00 MT, 12:00 CT, 1:00PM ET).
Dial-in number: 1.866.740.1260 (US Toll-free) or 1.303.248.0285 (International)
Conference code: 2404545

* [[Legal_Team/Priorities|Current Priorities and Work in Progress for the Legal Team]]
* [[Legal_Team/Minutes|Meeting Minutes of the Legal Team]]
* [[Legal_Team/Decisions|Decisions of the Legal Team]]
* [[Legal_Team/Old|Older Items for the Legal Team]]

[[Category:Legal]]

MediaWiki:Sidebar

2013-04-10T22:40:51Z

Lfadmin: bogus edit

MediaWiki:Sidebar

2013-04-10T18:36:44Z

Lfadmin: Add SPDX links to sidebar