Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[discussion] Should group name be tensorflow.org or kubeflow.io or kubeflow.org? #337

Closed
gaocegege opened this issue Jan 19, 2018 · 22 comments
Closed

[discussion] Should group name be tensorflow.org or kubeflow.io or kubeflow.org? #337

gaocegege opened this issue Jan 19, 2018 · 22 comments
Milestone
Kubecon Europe

Comments

@gaocegege
Copy link
Member

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.
@jlewi
Copy link
Contributor

jlewi commented Jan 20, 2018 •
edited
Loading

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?

@jlewi jlewi changed the title [discussion] Rethink the group name [discussion] Should group name be tensorflow.org or kubeflow.io? Jan 20, 2018
@jlewi jlewi changed the title [discussion] Should group name be tensorflow.org or kubeflow.io? [discussion] Should group name be tensorflow.org or kubeflow.io or kubeflow.org? Jan 20, 2018
@jlewi jlewi added this to the Kubecon Europe milestone Jan 20, 2018
@DjangoPeng
Copy link
Member

DjangoPeng commented Jan 21, 2018 •
edited
Loading

Vote for kubeflow.org.

The domain name org is a generic top-level domain (gTLD) of the Domain Name System (DNS) used in the Internet.

The .io domain is administered by the Internet Computer Bureau, a domain name registry company based in the United Kingdom.

Ref:

@pineking
Copy link
Member

kubeflow.org +1

@erikerlandson
Copy link

erikerlandson commented Jan 23, 2018 •
edited
Loading

-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

@wbuchwalter
Copy link
Contributor

+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.

@jlewi
Copy link
Contributor

jlewi commented Jan 24, 2018

:( somebody seems to already own kubeflow.org.

@wbuchwalter
Copy link
Contributor

Registered Nov 23rd...
Well, let's go with kubeflow.io then?

@DjangoPeng
Copy link
Member

:) I bought kubeflow.org for our kubeflow open-source project.

@yupbank
Copy link
Member

yupbank commented Jan 26, 2018

+1 for for kubeflow.org

@jlewi
Copy link
Contributor

jlewi commented Jan 26, 2018

Up vote this comment for kubeflow.org

@jlewi
Copy link
Contributor

jlewi commented Jan 26, 2018

Up vote this comment for kubeflow.io

@subramp
Copy link

subramp commented Jan 26, 2018

+1 kubeflow.org
Also @DjangoPeng seems to own! :)

@erikerlandson
Copy link

+1 for kubeflow.org

@animeshsingh
Copy link

+1 kubeflow.org

1 similar comment
@rongou
Copy link
Member

rongou commented Jan 26, 2018

+1 kubeflow.org

@nellaivijay
Copy link

kubeflow.org +1

@aronchick
Copy link

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).

@gaocegege
Copy link
Member Author

+1 kubeflow.org

1 similar comment
@net-sniper
Copy link

+1 kubeflow.org

@DjangoPeng
Copy link
Member

+1 for kubeflow.org

@gaocegege
Copy link
Member Author

If we come to an agreement, I could file a PR to rename the group name of the CRD.

@gaocegege gaocegege mentioned this issue Jan 30, 2018
Merged
@jlewi
Copy link
Contributor

jlewi commented Jan 30, 2018

Consensus is kubeflow.org.

jlewi pushed a commit that referenced this issue Jan 30, 2018
@gaocegege @jlewi
feat(group): Update to kubeflow.org (#354)
7f97cf0 
* Fix #337 

* Per the discussion we've decided to use kubeflow.org as the group and not tensorflow.org. This PR makes all the relevant changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Kubecon Europe
Development

No branches or pull requests