Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm not sure that's a bad thing given that the previous approach was hampered so much by confusion about where the value is.

If this is a commitment to a set of source then the players can compete on ease of use, support or other stuff.



Right now I'm thinking about it in the way that I think about Let's Encrypt.

Let's Encrypt has their own infrastructure, governance, etc., but I don't use Let's Encrypt products to interact with Let's Encrypt. Instead, I interact with Let's Encrypt via products like Certbot from the EFF.

If OpenELA's going to provide source, and I access that source through builds provided by CIQ or SUSE or someone else, then I'll be thinking of it in the same way as I think about Let's Encrypt.


Or java.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: