|
Thursday SPDX General Meeting Reminder...with interesting guest presentations.
Phil Odence
“SPDX Lite”- Hiroyuki Fukuchi from Sony will present a proposal from the OpenChain Japan Workgroup on a slimmed down version of an SPDX doc. Big thanks to Fukuchi-san for joining us at this hour which is not very convenient for him.
We may also have another GSoC presentation; still working on that.
GENERAL MEETING
Meeting Time: Thurs, Sept 5, 8am PT / 10 am CT / 11am ET / 15:00 UTC. http://www.timeanddate.com/worldclock/converter.html
New dial in number: 415-881-1586 No PIN needed
The weblink for screenshare will stay the same at:
Administrative Agenda Attendance Minutes Approval: https://wiki.spdx.org/view/General_Meeting/Minutes/2019-08-01
GSoC Presentations
Technical Team Report – Kate/Gary
Legal Team Report – Jilayne/Paul
Outreach Team Report – Jack
Any Cross Functional Issues –All
|
|
|
|
Re: SPDX Survey Results
Shane Coughlan <coughlan@...>
Exactly! :)
toggle quoted messageShow quoted text
On 4 Sep 2019, at 08:47, J Lovejoy <opensource@...> wrote:
|
|
|
|
Re: SPDX Survey Results
J Lovejoy
Very cool, Shane!
toggle quoted messageShow quoted text
When you say sharing, do you mean to share the results so far, but also a link to the survey to collect more results? (I think another push might get some more folks to fill it out, if we all spread the word.) Jilayne
On Sep 3, 2019, at 4:37 PM, Shane Coughlan <coughlan@...> wrote:
|
|
|
|
Re: SPDX Survey Results
Gary O'Neall
Great information - very insightful.
toggle quoted messageShow quoted text
Thanks Shane! +1 on sharing on social media. Gary
-----Original Message-----Coughlan Sent: Tuesday, September 3, 2019 3:38 PMa link to the survey, I think we can get some more useful data.
|
|
|
|
SPDX Survey Results
Shane Coughlan <coughlan@...>
Hello all!
33 responses to our survey! https://docs.google.com/forms/d/1uhYUlCwQ59ZveqSsGC_0h1OxRLYRb1OZprfRHVNYfys/edit#responses Looking good. Shall we start sharing on social media? If we all take a show, and include a link to the survey, I think we can get some more useful data. Regards Shane -- Shane Coughlan General Manager, OpenChain e: coughlan@... p: +81 (0) 80 4035 8083 w: www.openchainproject.org Schedule a call: https://calendly.com/shanecoughlan
|
|
|
|
Re: SPDX General Meeting
Hiro Fukuchi
Thank you, Phil-san.
--- Hiro Fukuchi (Hiroyuki.Fukuchi@...) Sony
From: Phil Odence <Phil.Odence@...>
Fukuchi-san, This sounds like a great idea. I will contact you about this. Best regards, Phil
From:
"spdx@..." <spdx@...> on behalf of Hiro Fukuchi <hiroyuki.fukuchi@...>
Hi Phil-san and all,
My name is Hiro Fukuchi from Sony. I am a member of the OpenChain project Japan workgroup.
Can I join the next uberconference and explain about the background of the “SPDX Lite” which is being proposed by Japan workgroup. I am creating the slides for explanation.
--- Hiro Fukuchi (Hiroyuki.Fukuchi@...) Sony
-----Original Appointment-----
When: Occurs every month on the first Thursday of the month from 11:00 AM to 12:00 PM effective 8/2/2018 until 1/1/2020. (UTC-05:00) Eastern Time
(US & Canada) I’m extending this recurring meeting to run through 2019. Please accept so it is updated on your calendar, however no need to send a response to me.
New dial in number: 415-881-1586 No PIN needed The weblink for screenshare will stay the same at:
|
|
|
|
Re: SPDX General Meeting
Phil Odence
Fukuchi-san, This sounds like a great idea. I will contact you about this. Best regards, Phil
From: "spdx@..." <spdx@...> on behalf of Hiro Fukuchi <hiroyuki.fukuchi@...>
Hi Phil-san and all,
My name is Hiro Fukuchi from Sony. I am a member of the OpenChain project Japan workgroup.
Can I join the next uberconference and explain about the background of the “SPDX Lite” which is being proposed by Japan workgroup. I am creating the slides for explanation.
--- Hiro Fukuchi (Hiroyuki.Fukuchi@...) Sony
-----Original Appointment-----
When: Occurs every month on the first Thursday of the month from 11:00 AM to 12:00 PM effective 8/2/2018 until 1/1/2020. (UTC-05:00) Eastern Time (US & Canada) I’m extending this recurring meeting to run through 2019. Please accept so it is updated on your calendar, however no need to send a response to me.
New dial in number: 415-881-1586 No PIN needed The weblink for screenshare will stay the same at:
|
|
|
|
Re: SPDX General Meeting
Hiro Fukuchi
Hi Phil-san and all,
My name is Hiro Fukuchi from Sony.
I am a member of the OpenChain project Japan workgroup.
Can I join the next uberconference and explain about the background of the “SPDX Lite” which is being proposed by Japan workgroup.
I am creating the slides for explanation.
---
Hiro Fukuchi (Hiroyuki.Fukuchi@...)
Sony
-----Original Appointment-----
From: Phil Odence <podence@...> Sent: Thursday, February 7, 2019 4:09 AM To: Phil Odence; spdx@... Subject: [spdx] SPDX General Meeting 2018 (replacement) When: 2019年9月5日木曜日 11:00-12:00 (UTC-05:00) 東部標準時 (米国およびカナダ) Where: Bridge info enclosed When: Occurs every month on the first Thursday of the month from 11:00 AM to 12:00 PM effective 8/2/2018 until 1/1/2020. (UTC-05:00) Eastern Time (US & Canada)
Where: Bridge info enclosed *~*~*~*~*~*~*~*~*~* I’m extending this recurring meeting to run through 2019. Please accept so it is updated on your calendar, however no need to send a response to me.
New dial in number: 415-881-1586
No PIN needed
The weblink for screenshare will stay the same at:
http://uberconference.com/SPDXTeam MEETING MINUTES FOR REVIEW: http://spdx.org/wiki/meeting-minutes-and-decisions
|
|
|
|
Working with Python maintainers to adopt SPDX license expressions
Philippe Ombredanne
All:
I started working with the Python community to draft what we call a PEP (Python Enhancement Proposal) to adopt SPDX license expressions to document the license of Python packages. You can join the discussions here: https://discuss.python.org/t/improving-license-clarity-with-better-package-metadata/2154/57 And see, comment and propose updates to the draft PEP here: https://github.com/pombredanne/spdx-pypi-pep/pull/2 -- Cordially Philippe Ombredanne +1 650 799 0949 | pombredanne@... DejaCode - What's in your code?! - http://www.dejacode.com AboutCode - Open source for open source - https://www.aboutcode.org nexB Inc. - http://www.nexb.com
|
|
|
|
Re: SPDX 2019 Survey - Ready for your thoughts - Let's collect data
Phil Odence
Thanks, Shane, for your work on this and for sending out.
SPDXers, in addition to sharing your thoughts, please forward to anyone colleagues or acquaintances whom you think might have a useful perspective. Phil On 8/6/19, 5:32 PM, "spdx@... on behalf of Shane Coughlan" <spdx@... on behalf of coughlan@...> wrote: Dear all The SPDX 2019 Survey is now open and accepting contributions: https://urldefense.proofpoint.com/v2/url?u=https-3A__forms.gle_h958R6kkvFhxRJtz7&d=DwIFAg&c=DPL6_X_6JkXFx7AXWqB0tg&r=6RejxoO58WZ8e0SKjO9DwnbnAWbcLSaQRQp3CZDH85w&m=aQam-BJyZPypGLr32LS3C2O_wHyP41mqY3R_zeeLbnY&s=JDrekKfFj8YxDxZ7wpimHqc54vZdBsJx0pv-fwfrndc&e= Please help us with building out information regarding the status of the community and what we need to do next. The survey should only take 3~5 minutes. Regards Shane -- Shane Coughlan General Manager, OpenChain e: coughlan@... p: +81 (0) 80 4035 8083 w: https://urldefense.proofpoint.com/v2/url?u=http-3A__www.openchainproject.org&d=DwIFAg&c=DPL6_X_6JkXFx7AXWqB0tg&r=6RejxoO58WZ8e0SKjO9DwnbnAWbcLSaQRQp3CZDH85w&m=aQam-BJyZPypGLr32LS3C2O_wHyP41mqY3R_zeeLbnY&s=0cGyK8IYIAP0q3OyCL4PBmI7yramFccO59FpW0VMs8Q&e= Schedule a call: https://urldefense.proofpoint.com/v2/url?u=https-3A__calendly.com_shanecoughlan&d=DwIFAg&c=DPL6_X_6JkXFx7AXWqB0tg&r=6RejxoO58WZ8e0SKjO9DwnbnAWbcLSaQRQp3CZDH85w&m=aQam-BJyZPypGLr32LS3C2O_wHyP41mqY3R_zeeLbnY&s=WCdJEEFPfF2XvjP-nhu-qi2_R2mQAVRW9gdR5EBGfbQ&e=
|
|
|
|
SPDX 2019 Survey - Ready for your thoughts - Let's collect data
Shane Coughlan <coughlan@...>
Dear all
The SPDX 2019 Survey is now open and accepting contributions: https://forms.gle/h958R6kkvFhxRJtz7 Please help us with building out information regarding the status of the community and what we need to do next. The survey should only take 3~5 minutes. Regards Shane -- Shane Coughlan General Manager, OpenChain e: coughlan@... p: +81 (0) 80 4035 8083 w: www.openchainproject.org Schedule a call: https://calendly.com/shanecoughlan
|
|
|
|
SPDX Aug General Meeting Minutes
Phil Odence
https://wiki.spdx.org/view/General_Meeting/Minutes/2019-08-01
General Meeting/Minutes/2019-08-01< General Meeting | Minutes · Attendance: 11 · Lead by Phil Odence · Minutes of July meeting approved
Contents[hide] · 1 Special Presentations - Umang Taneja, Tanjong Smith, GSoC · 2 Tech Team Report - Kate/Gary · 3 Legal Team Report - Jilayne/Paul/Steve · 4 Outreach Team Report - Kate Special Presentations - Umang Taneja, Tanjong Smith, GSoC[edit]· Umang · License submittal workflow automation · Aim is to enhance user experience · Compare submitted text against existing licenses to see if there’s duplication or close match · Problems he’s trying address · What if the license is on the list, proposed, rejected…or a close match to one of those · Current XML formatting- word-wrap doesn’t match license · Also creating/documenting an API · Tasks: · Create API- use without logging in, so can be accessed by other tools · Create License Matcher- looks for exact and close matches · Returns all matches and close matches · Compare with not accepted as well as rejected licenses. · Reports appropriately according to match · Relies on user input regarding whether to go ahead with submittal · Improve formatting of generated license · Screenshots available at: https://docs.google.com/document/d/1NMcLZVXxBV2PZobPJh1OugbCfC2d8kbAOX4m4TauEYk/edit?usp=sharing · Some discussion of how the workflow should work with close matches · Aiming for demo in future Legal Team meeting · Tanjong · License namespace · A way to name valid licenses outside of the License List · Created namespace and UI · Also a mechanism for turning into a license request · Took feedback from the joint/legal team meeting Tech Team Report - Kate/Gary[edit]· Spec · Progress on Appendix for including other fields in the source like the license ID · Keeping scope at file level · Tags with SPDX prefix · Allows to make it easier for tools to pick up. · Source file analysis · Philip demoed · Heavy testing mode · Tools · GSoC · Continues to go very well · All students passed second evaluation · Looking for feedback from community: · License matching algorithm approaches · Some encoded rules · Some depended on XML markup · Should we encode in XML or handle programmatically? (Discuss with Gary) Legal Team Report - Jilayne/Paul/Steve[edit]· License List · 3.6 version went out last month · Working issues in 3.7 · Good input/support from Tech Team · Recent meetings have been joint with Tech Team · Very helpful at this point
Outreach Team Report - Kate[edit]· Shane has readied the survey Cross Functional -[edit]· None Attendees[edit]· Phil Odence, Black Duck/Synopsys · Matthew Crawford, ARM · Umang Taneja, GSoC · Tanjong Smith, GSoC · Steve Winslow, LF · Gary O’Neall, SourceAuditor · Kate Stewart, Linux Foundation · Paul Madick, Dimension Data · Mark Atwood, Amazon · Jilayne Lovejoy, Canonical · Jack Manbeck, TI
|
|
|
|
Today SPDX General Meeting Reminder...More Google Summer of Code Updates
Phil Odence
Please excuse the later reminder. I was shocked this morning to notice it’s August already. Was thinking we had a week.
We will be joined by at least one, maybe two, of our Google SoC students to present their work. Please join.
GENERAL MEETING
Meeting Time: Thurs, Aug 1, 8am PT / 10 am CT / 11am ET / 15:00 UTC. http://www.timeanddate.com/worldclock/converter.html
New dial in number: 415-881-1586 No PIN needed
The weblink for screenshare will stay the same at:
Administrative Agenda Attendance Minutes Approval: https://wiki.spdx.org/view/General_Meeting/Minutes/2019-07-11
GSoC Presentations
Technical Team Report – Kate/Gary
Legal Team Report – Jilayne/Paul
Outreach Team Report – Jack
Any Cross Functional Issues –All
|
|
|
|
Re: In favour of what are §4.9–4.11 deprecated?
Gary O'Neall
Hi Matija,
toggle quoted messageShow quoted text
-----Original Message-----[G.O.] [G.O.] The idea is that there would be a package definition. It could be in a separate SPDX document, or more likely, as a separate SPDX package definition within the same SPDX document. The originating package definition could have the FilesAnalyzed set to false which allows for a rather small number of required fields. The origin could then be indicated by a relationship between the file and the package. -=-=-=-=-=-=-=-=-=-=-=- [G.O.] Gary
|
|
|
|
In favour of what are §4.9–4.11 deprecated?
Hi all,
I notice that in 2.1 spec the following are marked as deprecated on the file-level: • 4.9 Artifact of Project name • 4.10 Artifact of Project Homepage • 4.11 Artifact of Projecr Uniform Resource Identifier …and I wonder what was the new equivalent to get information of origin for a file in the package. Is the assumption now that files of alien origin to the analysed package must belong to a different package and that package should have its own SPDX file, to which the first SPDX file should refer to? A use common use case I can see could be how to mark font and image files that are commonly copied from elsewhere instead of each piece of software reinventing their icons and type faces. cheers, Matija Šuklje -- gsm: +386 41 849 552 www: http://matija.suklje.name xmpp: matija.suklje@... sip: matija_suklje@...
|
|
|
|
Minutes from July SPDX General Meeting
Phil Odence
https://wiki.spdx.org/view/General_Meeting/Minutes/2019-07-11
General Meeting/Minutes/2019-07-11< General Meeting | Minutes · Attendance: 14 · Lead by Phil Odence · Minutes of June meeting approved
Contents[hide] · 1 Special Presentations - Xavier Figouoa/ Philip Ekong Obie, GSoC · 2 Tech Team Report - Kate/Gary · 3 Legal Team Report - Jilayne/Paul/Steve · 4 Outreach Team Report - Kate Special Presentations - Xavier Figouoa/ Philip Ekong Obie, GSoC[edit]· Python Library- Adding support for more formats · Generating SPDX docs from IDs in code Tech Team Report - Kate/Gary[edit]· Spec · All known issues are addressed in 2.2 · Under discussion: · Idea of a short format for copyrights ala license IDs from FSFE · Would be added as an appendix (like license IDs) · Could use a joint tech/legal teams call · Exploring branching strategy · Pared down version, defining minimal subset (from Japan work group) · Still SPDX compliant as it will utilize mandatory fields · Part of the spec · Important to communicate that; it’s not a fork · Tools · GSoC · 8 projects total (a record) · Great progress, all passed first evaluations · Flurry of tooling work with the new license list · Better matching/copyright matching · License format improvements Legal Team Report - Jilayne/Paul/Steve[edit]· License List · 3.6 version went live yesterday · 10 new licenses and exceptions · Other mark up and doc updates · Attention now turning to 3.7 · Other topics of discussion already covered. · Namespace Project · Need to make clear the difference between LL and NS registry · NS is an option for rejected licenses · Could be a stop before being accepted
Outreach Team Report - Kate[edit]· Shane has readied the survey · Based on input from Phil, Jack, Kate, Gary · Will go do the General Meeting mailing list Cross Functional -[edit]· Will designate one Tech Call per month to include Legal Team · Third one of the month · Starting next week Attendees[edit]· Phil Odence, Black Duck/Synopsys · Jilayne Lovejoy, Canonical · Steve Winslow, LF · Gary O’Neall, SourceAuditor · Kate Stewart, Linux Foundation · Philippe Ombrédanne- nexB · Alexios Zavras, Intel · Michael Herzog- nexB · David Ryan · Dave McLaughlin, Rogue Wave · Paul Madick, Dimension Data · Mark Atwood, Amazon · Xavier Figouoa · Philip Ekong Obie
|
|
|
|
Thurs SPDX General Meeting Reminder...special guest stars this month
Phil Odence
Joining us will be two students doing Google Summer of Code projects for us. Xavier will be talking about his and Philip will do a short demo.
Xavier Figueroa, Undergraduate Computer Science student from Ecuador, first time contributing to an Open Source project Title: GSoC Project: Addtional format support for Python libraries Abstract: The GSoC Project Addtional format support for Python libraries initially implied adding support for JSON/XML/YAML formats to the SPDX Python Library, but now some additional work will be done. In this presentation, it will be covered what the project currently entails, where we are and what it is next.
Philip Ekong Obie SPDX Document Generator for projects using SPDXIDs
GENERAL MEETING
Meeting Time: Thurs, July 11, 8am PT / 10 am CT / 11am ET / 15:00 UTC. http://www.timeanddate.com/worldclock/converter.html
New dial in number: 415-881-1586 No PIN needed
The weblink for screenshare will stay the same at:
Administrative Agenda Attendance Minutes Approval: https://wiki.spdx.org/view/General_Meeting/Minutes/2019-06-06
GSoC Presentations
Technical Team Report – Kate/Gary
Legal Team Report – Jilayne/Paul
Outreach Team Report – Jack
Any Cross Functional Issues –All
|
|
|
|
SPDX June General Meeting Minutes (slightly belated)
Phil Odence
Note, July Meeting has been moved to July 11. June minutes: https://wiki.spdx.org/view/General_Meeting/Minutes/2019-06-06 Thanks to Paul for hosting in my stead. Phil
L. Philip Odence General Manager, Black Duck On-Demand Synopsys Software Integrity Group, Burlington, MA M (781) 258-9502 | phil.odence@...
General Meeting/Minutes/2019-06-06< General Meeting | Minutes · Attendance: 12 (attendance list at bottom) · Lead by Paul Madick · Minutes of May meeting approved
Contents[hide] · 2 Legal Team Report - Jilayne/Paul · 3 Outreach Team Report - Jack Manbeck Tech Team Report - Gary[edit]· Spec No issues remaining to latest spec, 8 GOSC students approved and working. Looking forward to new tools this summer. Lots of new projects adopting SPDX and Linux kernel clean up of licensing still working (about 2/3 through). Making great progress. · Tools
Legal Team Report - Jilayne/Paul[edit]· License List · GSOC student on last call. Great information. Legal Meeting minutes has the description, take a look if you are interested or would like to provide input. · Reworking the license inclusion guidelines and moving into github repository in the documentation folder. Please weigh in if you are interested in more licenses. Still looking for more volunteers to move license submissions into license approvals. · A big welcome to new co-lead of legal team Steve Winslow and a big thank you to Karen for her years of stewardship as she steps away from the co-lead position.
Outreach Team Report - Jack Manbeck[edit]· Not a lot going on now, but working on a survey. Intention is to send the survey to companies to see where they are at in using/implementing SPDX. Maybe include some community in survey, but not sure yet. General Items[edit]· Conversation: are we meeting for summer LF event in SD. Not currently, but Kate will look into getting meeting room for ½ day, etc. Jack, Paul, Kate, Steve and others are potentially available to attend at least one day in SD.
Attendees[edit]· Alexios Zavras, Intel · JC Herz, Ion Channel · Dave McLoughlin · Paul Madick, Dimension Data · Jilayne Lovejoy · Steve Winslow, LF · Kate Stewart, Linux Foundation · Alexios Zavras, Intel · Philippe Ombrédanne- nexB · Jack Manbeck · Mike Herzog · Mark Atwood
|
|
|
|
Thurs SPDX General Meeting Reminder
Phil Odence
Notes:
GENERAL MEETING
Meeting Time: Thurs, June 6, 8am PST / 10 am CST / 11am EST / 15:00 UTC. http://www.timeanddate.com/worldclock/converter.html
New dial in number: 415-881-1586 No PIN needed
The weblink for screenshare will stay the same at:
Administrative Agenda Attendance Minutes Approval: https://wiki.spdx.org/view/General_Meeting/Minutes/2019-05-02
Technical Team Report – Kate/Gary
Legal Team Report – Jilayne/Paul
Outreach Team Report – Jack
Any Cross Functional Issues –All
|
|
|
|
SPDX General Meeting 2018 (replacement)
Phil Odence
Moving the July 4 instance of this meeting to July 11 due to the US holiday.
***** I’m extending this recurring meeting to run through 2019. Please accept so it is updated on your calendar, however no need to send a response to me.
New dial in number:
415-881-1586 No PIN needed The weblink for screenshare will stay the same at:
|
|
|
