[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linuxbios
Subject:    [coreboot] Need help from anyone at Meraki/Cisco
From:       David Hendricks via coreboot <coreboot () coreboot ! org>
Date:       2024-02-28 6:16:28
Message-ID: 4f9d9e67bba22ac1ad04f0b4a3698123 () coreboot ! org
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hi folks,
As discussed in the Feb. 21 coreboot leadership meeting [1][2], concerns have been \
raised about coreboot source code releases for certain Meraki switch products. \
Requests have been made to open-source@meraki.com (mailto:open-source@meraki.com) \
about this with limited success in the past (MX84, MX250), though current requests \
for MS350 have gone practically unanswered. Since this problem scales with the \
product line-up, it seems an engineering approach to get code published - preferably \
upstream - will be a better way to solve it rather than repeated requests or \
escalation to the SFC.

We're looking for anyone from Meraki/Cisco who would like to solve this by getting \
the code published. Several members of the coreboot community have experience working \
at (or with) companies in similar situations, and we're willing to help with this \
process. A few quick ideas mentioned in the recent meeting include a packaging tool \
to remove unused modules, a repo or branch on coreboot.org to host Meraki changes if \
they can't be mainlined easily, a license package that can integrate with Meraki's OS \
installer, etc.

It's great that coreboot is used on these products and we believe that the coreboot \
community and corporate users such as Meraki mutually benefit when everyone's rights \
are respected. We strongly prefer an engineering approach to compliance with the \
GPLv2, but will look to other options if progress can't be made.

If anyone at Meraki/Cisco happens to be reading this, feel free to contact me \
privately.

[1] https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkKrgKjeDQ/edit#bookmark=id.vsy0tj8jwgu \
(https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkKrgKjeDQ/edit#bookmark=id.vsy0tj8jwgu)
 [2] https://www.mail-archive.com/coreboot@coreboot.org/msg58333.html \
(https://www.mail-archive.com/coreboot@coreboot.org/msg58333.html)


[Attachment #5 (text/html)]

<!DOCTYPE html><html><head><meta http-equiv="Content-Type" content="text/html; \
charset=utf-8" /></head><body><div data-html-editor-font-wrapper="true" \
style="font-family: arial, sans-serif; font-size: 13px;"><div><div><div \
style="font-family: arial, sans-serif;font-size: 13px"><div><div><div \
style="font-family: arial, sans-serif;font-size: 13px"><div><div><div \
style="font-family: arial, sans-serif;font-size: 13px">Hi folks,<br>As discussed in \
the Feb. 21 coreboot leadership meeting [1][2], concerns have been raised about \
coreboot source code releases for certain Meraki switch products. Requests have been \
made to <a rel="external nofollow noopener noreferrer" target="_blank" tabindex="-1" \
href="mailto:open-source@meraki.com">open-source@meraki.com</a> about this with \
limited success in the past (MX84, MX250), though current requests for MS350 have \
gone practically unanswered. Since this problem scales with the product line-up, it \
seems an engineering approach to get code published - preferably upstream - will be a \
better way to solve it rather than repeated requests or escalation to the \
SFC.<br><br>We're looking for anyone from Meraki/Cisco who would like to solve this \
by getting the code published. Several members of the coreboot community have \
experience working at (or with) companies in similar situations, and we're willing to \
help with this process. A few quick ideas mentioned in the recent meeting include a \
packaging tool to remove unused modules, a repo or branch on coreboot.org to host \
Meraki changes if they can't be mainlined easily, a license package that can \
integrate with Meraki's OS installer, etc.<br><br>It's great that coreboot is used on \
these products and we believe that the coreboot community and corporate users such as \
Meraki mutually benefit when everyone's rights are respected. We strongly prefer an \
engineering approach to compliance with the GPLv2, but will look to other options if \
progress can't be made.<br><br>If anyone at Meraki/Cisco happens to be reading this, \
feel free to contact me privately.<br><br>[1] <a rel="external nofollow noopener \
noreferrer" target="_blank" tabindex="-1" \
href="https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkKrgKjeDQ/ \
edit#bookmark=id.vsy0tj8jwgu">https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkKrgKjeDQ/edit#bookmark=id.vsy0tj8jwgu</a><br>[2] \
<a rel="external nofollow noopener noreferrer" target="_blank" tabindex="-1" \
href="https://www.mail-archive.com/coreboot@coreboot.org/msg58333.html">https://www.mail-archive.com/coreboot@coreboot.org/msg58333.html</a> \
</div></div></div></div></div></div></div></div></div></div></body></html>



_______________________________________________
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-leave@coreboot.org


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic