foundation VS netboot.xyz

A mature open source project may be governed under an open source foundation which usually gives it a charter https://github.com/cncf/foundation/blob/main/charter.md#3-va...

... and/or set of values: https://kubernetes.io/community/values/

There's also a lot of open source guides here https://todogroup.org/resources/guides/ that may help you if you're looking at building mature open source projects.

The CNCF has made exceptions on their license policy before, specifically for MPL based software. It'll probably be easier for OpenTF to go through that process than to relicense (which is likely not even possible for anyone other than Hashicorp).

- https://github.com/cncf/foundation/tree/main/license-excepti...

- https://github.com/cncf/foundation/blob/main/license-excepti...

Your comment or post were removed for violating the CNCF Code of Conduct. Please take a moment to review that here: https://github.com/cncf/foundation/blob/master/code-of-conduct.md

His behavior offends me as a professional software engineer and/ in my opinion, violates CNCF Code of Conduct https://github.com/cncf/foundation/blob/master/code-of-conduct.md.

Anyone can become a member. Non-profit as in https://github.com/cncf/foundation/blob/master/charter.md

Read more about role of the CNCF, their projects and Values here.

https://github.com/cncf/foundation/blob/master/allowed-third...

I haven't read the details, or ever seen this policy before (I'm new to both projects) but it was summarized by one of our counterparts at the Linux Foundation here:

https://twitter.com/cra/status/1384859663615864833

Tl;dr: licenses must be approved for use, and the CNCF has this list of allowed licenses, AGPL is not on it. The CNCF is in the business of distributing permissively-licensed software is the short version I guess. I don't understand, I don't work on the legal side, I am a dev and I support end users.

It seems if your Apache 2.0 licensed project needs to modify and distribute as modified Grafana, which it seems likely we will need to do at some point, then you cannot distribute them together. Chris says they are going to work something out, but when a component has made a decision to re-license with a restrictive-copyleft license such as AGPL, I don't know what there is that can be done.

Maybe the CNCF adopts AGPL too, (which would mean that then all those "viral-GPL" FUD-spreaders will have been right...) that seems counter-productive if that is the outcome.

Your comment or post were removed for violating the CNCF Code of Conduct. Please take a moment to review that here: https://github.com/cncf/foundation/blob/master/code-of-conduct.md

I replied to a reply of yours with this same info, but since you’re both sorta asking the same thing, I’ll post it here for you also.

https://netboot.xyz/

https://github.com/netbootxyz/netboot.xyz

Knew about http://netboot.xyz, but had no idea iVentoy existed. Good to know.

Set the computer to PXE boot, or use a boot image with iPXE (such as netboot.xyz). That would quickly rule out a problem with Debian or the Linux kernel (at least until you download and boot one). I don't know anything about your network setup, but making sure DHCP is enabled on your router and there are enough unreserved IP addresses would probably help.

Hey thanks for the detailed response. You're saying you boot FCOS on bare metal over PXE, correct? I've thought about trying that approach, but have little experience with PXE and TFTP. I just checked out netboot.xyz and it looks surprisingly easy to get going. Last time I played around with PXE I used Synology's TFTP server and, while I got it working, I was more confused by the end than when I started. I think actually learning PXE end-to-end and understanding what I am doing there would be a solid foundation for building my environment the right way.

For netbooting we rely on a netboot.xyz inspired ipxe based setup.

[[UPDATE]]: The fix was as 'simple' as going into the 'bios', and selecting 'add a boot option', which automatically came up with the correct EFI file/path, then putting it at the top of the boot order. 'Simple' it wasn't, many new and temporary instances brought online while digging my way through it all, and finally just going with a brand new Debian Bookworm and migrating my data over from the old disk file. At least I learned a lot about recovering from this weird circumstance. The incorrect EFI file/path must be an artifact of using netboot.xyz to install Deb Bookworm over a previously provisioned Ubuntu instance. Makes sense I guess. Still loving netboot.xyz as a super fast way to spin up an unsupported OS.

I learned about GRML only a few years ago. Absolutely love the mixture of power and minimalism. Here is the only ISO which increases my mileage even more: https://netboot.xyz