I’ve just added an issue to consider adding the OHSW (as well as an open data) reference to our license inclusion guideline here: https://github.com/spdx/license-list-XML/issues/719 <https://github.com/spdx/license-list-XML/issues/719>
We have a fair amount of topics to cover at the next couple upcoming meetings, but we can carry on this conversation here in the meantime, and I think it’s also fine to start submitting the licenses for consideration so they are in the queue. Jilayne > On Oct 23, 2018, at 6:58 PM, J. Simmons <j...@mach30.org> wrote: > > Welcome to SPDX-legal! > Thanks! Happy to be here. > > Yes, it would be great to bring the open source hardware community into the > fold. > That was just what I was hoping to hear. > > Of course, we’d need to make sure we have the various open source hardware > licenses on the SPDX License List first > Yup, I am happy to submit one or two as test cases, I just wanted to give > fair warning that hardware licenses were on their way before I tossed in what > might have been wildly unexpected submissions. > > I think it’d be useful but do wonder if our reliance on the OSD will be an > appropriate guideline. > I think that is an important question. Would the group be willing to > entertain the idea of extending the guidelines to include the OHSW Definition > <https://www.oshwa.org/definition/> when looking at OSHW licenses as a means > of addressing that concern? > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#2429): https://lists.spdx.org/g/Spdx-legal/message/2429 Mute This Topic: https://lists.spdx.org/mt/27459493/21656 Group Owner: spdx-legal+ow...@lists.spdx.org Unsubscribe: https://lists.spdx.org/g/Spdx-legal/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
