Search results

...any, but the snippet is a byte range in a specific file, so it needs to be 1 file to many snippets

...e.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=0 * discussed use of numbers in existing exceptions and the ones to add for 2.1 - decided to not use a version number unless there is one for the exception

'''1) Update on joint call with Tech team regarding NONE and NOASSERTION''' - ...f licenses to add to the License List''' - OBSD license approved, Cecil 2.1 approved, Open Government License still under consideration since multiple

'''1) status of v2.1''' - up now. quality control? release notes? ...e.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=0

1) update from last week's call from Mark:

...e discussion concerning SPDX. Jilayne created a spreadsheet providing a 1:1 match between SPDX and Fedora short identifiers. Developers are looking fo

...37be4de78152fbd3ed54761627c960010ce26a3/src/licensedcode/data/rules/apache-1.1_38.RULE#L17 ...78152fbd3ed54761627c960010ce26a3/src/licensedcode/data/rules/bzip2-libbzip-1.0.5_1.RULE#L1

1) Update from LinuxCon - quick thoughts from Mark, but will do bigger update

Sept 1, 2015 * Kate to research byte offset starting with 1 rather than 0

** Decided to make the change for 2.1 and not rev in 2.0 ...and files as a scenario for a Snippet Comment on License into section X.5.1

'''1) Announcements/updates:''' ...e.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=0 for potentially adding to v2.2 (see spreadsheet for full info, summ

Sept 1, 2015

'''1) LinuxCon Europe update:''' ...go from there, but as to overall timing - would be good to line up for v2.1 aiming to have that ready for Collab Summit (end of March). Note: Kate is w

...d process can create a canonical "correct" form of the text to-match, thus 1) obviating implementations from the need to write boilerplate parsing code ...urrent markup – but I observe two elements in the current markup syntax: 1) entity replacement and 2) optional section blocks. These are quite readily

* Bytes ranges - start at 1 or 0 ** The RDF standard states 1

1) v2.3 items: ...ore "contribution-friendly" infrastructure (e.g., Github) should be number 1 priority for 2016

** 1 new exception * Lined up speakers for next 1-2 meetings

1) A discussion came up on the tech team regarding how to identify when there

1) Quick update from general call; good agenda shaping up for Collab Summit f

* Planning for Collab Summit: 1/2 day Tech team and 1/2 day Legal, with SPDX “Office Hours” for folks to bring questions, iss

'''1) License List templatizing proposal''': update/review from Kris on state of ...l have a room for work group all day on Wednesday: morning for review of 2.1 spec and afternoon for license templatizing work - would be great to have a

<p><strong>1. How These Guidelines Are Applied</strong></p> <p style="padding-left: 30px;"><span style="text-decoration: underline;">1.1 Purpose:</span>&nbsp; To ensure consistent results by different SPDX docume

** 1 new exception * Lined up speakers for next 1-2 meetings

March 1, 2016

...e.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=695212681 * Free Art License 1.3 - approved for 2.4, but need to resolve different language/versions quest

1) Review proposed draft for new appendix to the spec: Appendix V - Using SPD * OSET Public License version 2.1 - short identifier issue, hoping to hear back from Heather Meeker by Monday

1) update from Collab Summit: * went over 2.1 spec, Appendix V will be included - can view now as part of entire spec, so

1) New license requests and related topics:

...ussion on this latter item with legal team, but not pushing to do so for 2.1 release. Mark can try to start collecting use cases so we can assess soluti

1) Normal business/updates:

1) review of to-do items for 2.5 release and what's "on hold'

1) nuclear license discussion for addition to v2.5 release- there are 3 varia

'''1) v2.5 is now live'''

Next call is Aug 18, then Sept 1 - so we may schedule an additional call the week of Aug 22nd if need be

1) Went through all items in Github repo that were tagged "needs legal discus ...use it and what guidelines we use to make this call. Matching Guidelines 2.1.4 is starting point, explaining the omitable text means text marked as such

*** Appendix 1 is list of licenses - check

* SPDX 2.1 all comment incorporated * 1 1/2 month feedback cycle

** This would allow a 1:1 mapping to RDFa

...is non-conformant UTF-8 an error? Gary - Yes, it should be an error. +1 Kris.

1) Update from joint call with tech team, Oct 25th, to go over XML tag names.

1) Reviewed Dennis' draft document of process for Github management of licens

...e.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=695212681 * see notes for LPG-Bolivia-1.0 and Unicode licenses in spreadsheet (to add)

** should the SPDX License List and all it entails (e.g. Appendix 1, 2, 4) be its own spec, which would enable development at a different pace

* 12:00-1:00 Lunch * 1:00-2:00 File formats discussion (tech) – Yev will provide some examples o

1) Open Source Leadership Summit, Feb 14-16 at Squaw Valley, Lake Tahoe, CA

1. Use a comment statement

*** Remaining differences are centered on (1) naming things and (2) external references

1-5 ...urage them to continue to contribute and maintain ongoing dialog through 1:1 emails with the mentors, inclusion in the SPDX mailing lists, and encouragi

** At the outset Yocto build only supported SPDX 1.0 and uses FOSSology for scanning *** Based on LiD Scores (1-perfect)

1) SPDX License List v2.6 - remaining things to tie up before release