Spdx-legal@lists.spdx.org

Home Messages Hashtags Subgroups

Messages

Between

and

Hi Bob, I’m copying the SPDX tech team on this, as I suspect they will be better suited to answer your question or address any issues here :) Thanks, Jilayne SPDX Legal Team

By J Lovejoy · #1206 ·

License name character set

We (FOSSology) have discovered some of our license short names that violate your list of allowed characters. For example, here is the output from your verification tool when I ran it against your

By Gobeille, Robert <bob.gobeille@...> · #1205 ·

Re: SPDX license question

Hi Bob, Here’s some feedback on license identification in FOSSology based a recent scan I was looking at. I think some of the things I saw originally would be taken care of by using the

By J Lovejoy · #1204 ·

Re: SPDX license question

Hi Michael, Bob, Apologies for the delayed response here, this got a bit buried in the old Inbox. I had a look at the table in the link Michael provided. For ease of reference, I cut and pasted your

By J Lovejoy · #1203 ·

Re: meeting minutes

Hi Kris, Philippe and all, The markup language for the templates was crafted in a way that retains the original text. The optional tags surround the original text and the replaceable text has an

By Gary O'Neall · #1202 ·

Re: meeting minutes

There are two purposes at odds here and, I suspect, responsible for the markup vs no markup debate. One is: a repository of data that can be used to identify license names/ids from content. The other

By Kris.re <Kris.re@...> · #1201 ·

Re: meeting minutes

Hi Philippe, Comments below: There is already markup in about 15% of the licenses, as per our in depth discussions a couple years ago. The conversation on the call was about improving some of the

By J Lovejoy · #1200 ·

Re: meeting minutes

Adding matching markup inside the reference license texts will eventually lead to un-resolvable conflicts: - markup will make a license text no longer a reference - it will make it less readable or

By Philippe Ombredanne · #1199 ·

meeting minutes

For the last two calls: http://wiki.spdx.org/view/Legal_Team/Minutes/2015-07-23 http://wiki.spdx.org/view/Legal_Team/Minutes/2015-08-06 Thanks! Jilayne & Paul SPDX Legal Team co-leads

By J Lovejoy · #1198 ·

call today!

Sorry for the last minute reminder! Call this number: (United States): +1-857-216-2871 User PIN: 38633 International: visit the URL at http://uberconference.com/SPDXTeam Jilayne SPDX Legal

By J Lovejoy · #1197 ·

Reminder- SPDX Legal Call Today @ 10 am PT

Please join us for the SPDX legal call today (call-in information below the agenda). AGENDA Fedora List (Kate) Standard headers update (Mark) Mark-up bug raised on tech team call (Kate/Gary)

By Madick, Paul <paul.madick@...> · #1196 ·

Re: SPDX license question

Hi Jilayne, We are discussing this in one of our issues: https://github.com/fossology/fossology/pull/478#issuecomment-121556613 Michael (cc’d) has added a table of new licenses we are considering.

By Gobeille, Robert <bob.gobeille@...> · #1195 ·

Re: SPDX license question

Hi Bob, Nice to see that Ninka will be added to Fossology. Looking forward to checking that out in the near future. Cheers, Scott -- www.linkedin.com/in/scottlamons CONFIDENTIALITY NOTICE: This

By Scott Lamons <spl518@...> · #1194 ·

Re: SPDX license question

Thanks Jilayne. We look forward to your FOSSology feedback. FYI, in FOSSology 3.0 we are adding a third license scanner - ninka. The idea behind three scanners that operate so differently is to give

By Gobeille, Robert <bob.gobeille@...> · #1193 ·

Re: SPDX license question

Great Bob! Funny timing, as I was just looking at some FOSSology scans (haven’t done so in awhile, it’s like re-visiting an old friend :) and may have some other feedback for re: license

By J Lovejoy · #1192 ·

Re: SPDX license question

Thanks Jilayne and Kate, It looks like we need to do some updating on FOSSology to be SPDX 2.0 compliant. Thanks for your answers. Bob Gobeille bobg@...

By Gobeille, Robert <bob.gobeille@...> · #1191 ·

Re: [Bug 1302] Apache 2.0 license text includes appendix

Thanks, Kris. Would Aug 6th work for you? Here is the info for the meeting: http://wiki.spdx.org/view/Legal_Team and for joining the Legal mailing list as well:

By J Lovejoy · #1190 ·

Re: SPDX license question

Hi Bob, Thanks for asking! My additional comments to Kate’s also below: This should definitely be handled as a new exception added to the exception list; if you think this is something SPDX should

By J Lovejoy · #1189 ·

Re: SPDX license question

Hi Bob, Comments inline... This could be handled either as an explicit exception (add to exception list) or as a new license being added to the main list. Legal team is probably best ones to

By Kate Stewart · #1188 ·

SPDX license question

We (FOSSology project) are having a discussion about how to name dual licenses. What is the SPDX policy on naming dual licenses? Here are some examples: 1. The Asterisk license is GPL-2.0 with

By Gobeille, Robert <bob.gobeille@...> · #1187 ·

2201 - 2220 of 3406

Home Hashtags Subgroups Terms