Now our group name is tensorflow.org, and I think the scope of kubeflow is not included in tensorflow. We may support MXNet or other ML frameworks, so I think kubeflow.org may be more appropriate.
The code is TensorFlow specific so I think tensorflow.org is fine although kubeflow.org would also work and I agree probably better.
Should it be kubeflow.org or kubeflow.io?
Vote for kubeflow.org.
The domain name
orgis a generic top-level domain (gTLD) of the Domain Name System (DNS) used in the Internet.
The
.iodomain is administered by the Internet Computer Bureau, a domain name registry company based in the United Kingdom.
Ref:
kubeflow.org +1
-1 for kubeflow
My mental model of this is that kubeflow is decoupled from tensorflow, and anything tensorflow specific ought not to refer to kubeflow.
unless tensorflow/k8s is now being treated as a component of kubeflow, which seems like yet another argument for clarifying all of this via a new github org
+1 for for kubeflow.org
unless tensorflow/k8s is now being treated as a component of kubeflow
I always assumed it was, see Kubeflow's README which refers to this component, and tensorflow/k8s is embedded as a submodule in Kubeflow's code base.
But I do agree that it would be much clearer with a separate org.
:( somebody seems to already own kubeflow.org.
Registered Nov 23rd...
Well, let's go with kubeflow.io then?
:) I bought kubeflow.org for our kubeflow open-source project.
+1 for for kubeflow.org
Up vote this comment for kubeflow.org
Up vote this comment for kubeflow.io
+1 kubeflow.org
Also @DjangoPeng seems to own! :)
+1 for kubeflow.org
+1 kubeflow.org
+1 kubeflow.org
kubeflow.org +1
Sorry about that Erik. You can blame me - but it's Kubeflow. (Flow in the concept of ML flow or FB Learner Flow, not TensorFlow).
+1 kubeflow.org
+1 kubeflow.org
+1 for kubeflow.org
If we come to an agreement, I could file a PR to rename the group name of the CRD.
Consensus is kubeflow.org.
Most helpful comment
Up vote this comment for kubeflow.org