Hmm, that is interesting! Sometimes it depends on the situation, usually licenses are discussed as soon as the intent of the product is out or the idea is out. As license is a way of protecting your idea, product and the interest.
A license can help a business decide the scope of the product and also the target audience. I will not k8s as an example, because Google hid Borg from the rest of the industry for almost 10 years. That is how i see it, 2014 is when docker started to gain traction, meanwhile Google was already using something which could manage or orchestrate containers. Also k8s is a section of Borg the original product :) This is what I think. Warm regards Ragini. > Hi all, hopping this message finds you well, and hoping you enjoying > the day off > > Have a point to descuss > > We are having talk/discussion/lecture about how we should license our > products , and which laws, regulations should it follows, however we > still don't have a real product/idea to apply/ attach this license to > > Is like we are talking about how to use our product and who can use it > and who can't... and we don't have the product it self 😂 > > For me... i would more focused on internal devolpment like what > google make with k8s, > > They had it running in there environment internally for years (Borg) > since 2004 and they announced and make it public in 2014 and they > choose which license and all follow as it was something > > What do you think?
